<media type="image" src="…"/>
as a child of <hero>, switching this page to the
full-bleed dark variant.
Recommended : 1920 × 1080 px (16:9)
Formats : PNG · JPEG · WebP · SVG
Off-spec uploads are rejected — aspect ratio outside 16:9 ±2 %, dimensions outside 800 × 450 … 3840 × 2160.
Retention policies enforced by the engine; GDPR-aligned subject access by query.
Retention policies per record type with regulatory minimums respected. Lawful destruction with the engine's authorisation rather than ad-hoc deletion. GDPR-aligned subject-access, rectification and erasure routed through the engine's audit-grade controls.
Retention by record type
Per-record-type retention configured to the regulatory minimum; longer where institutional policy demands. Approaching-expiry alerts surface in the compliance dashboard.
Lawful destruction
Records destroyed only through the engine's authorised destruction workflow — with the policy reference, the approver and the destruction confirmation logged.
Subject-access response
GDPR Article 15 subject-access requests answered as a query against the engine. Personal data identifiable by the subject's reference.
Rectification and erasure
Article 16 rectifications create new entries with the corrected value; Article 17 erasures execute through the destruction workflow, preserving the audit trail of the erasure.
What the retention and privacy surface covers
Retention policy
Per record type — invoices, contracts, audit logs, employee records — with the regulatory minimum baked in (Spanish commercial law: 6 years; tax: 4 years longer; sector-specific extensions where applicable).
Destruction controls
No path to destroy records outside the engine's destruction workflow. The workflow requires policy reference, approver, and produces a destruction certificate.
Electronic archive
Beyond retention, records archived to compliant electronic storage with legal evidentiary value. Retrievability preserved through the retention period.
GDPR subject rights
Article 15 (access), Article 16 (rectification), Article 17 (erasure), Article 18 (restriction), Article 20 (portability) — each routed through the engine with audit trail.
Subject reconstruction
A subject's personal data across the engine, identified by reference, retrievable as a query. The 30-day GDPR response deadline becomes a process, not a project.
Legitimate-interest balancing
Erasure requests against records held for legitimate interest (tax, audit, regulatory) routed for legal review. The decision and its rationale preserved in the audit trail.
Why retention enforcement is an engine capability, not a procedure
Retention policies stated in procedures documents are enforced — if at all — by individual users remembering them. The result is records destroyed too early (regulatory non-compliance) and records retained too long (over-retention, increased breach exposure, increased erasure cost).
Axional enforces retention through the engine. The destruction workflow is the only path to remove a record; the policy is the only authorisation; the destruction certificate is the only proof. Both regulatory minimums and lawful destruction are first-class engine behaviours.