Data Retention Policy
Effective date: February 17, 2026 | Version: 2026.02-global
This Data Retention Policy defines how operational, financial, privacy, and security records are retained, archived, and securely deleted across VelisAds Network systems.
Retention periods must align with legal obligations, contractual duties, and operational necessity.
Scope and Applicability
- Applies to account data, traffic logs, reports, payment records, and audit evidence.
- Applies to structured databases, file storage, logs, backups, and exports.
- Applies to production and non-production systems containing real or regulated data.
- Applies to subprocessors handling retention tasks under contractual obligations.
- Applies to legal hold and regulator preservation requests.
- Applies to full lifecycle from collection through secure destruction.
Mandatory Requirements
Retention Schedule Management
- Every dataset must have a documented retention period and business rationale.
- Retention periods must satisfy legal, tax, and contractual requirements.
- Indefinite retention is not allowed without explicit legal justification.
- Retention catalogs must be reviewed by data owners and compliance teams.
Deletion and Anonymization
- Expired records must be removed or anonymized using controlled workflows.
- Deletion jobs must generate auditable completion evidence.
- Anonymization must prevent practical re-identification in normal use.
- Catch-up cleanup must run after prolonged processing interruptions.
Backup and Legal Hold Handling
- Backups with regulated data must follow defined retention windows.
- Legal holds must be scoped, documented, and reviewed periodically.
- Released legal holds should trigger controlled post-hold deletion.
- Archive access must enforce least privilege and full auditability.
Prohibited Practices
- Retaining expired data in active systems without legal necessity.
- Deleting records that are subject to active legal hold.
- Maintaining hidden shadow datasets outside approved inventories.
- Restoring expired records to production without retention revalidation.
- Destroying security or compliance evidence required for investigations.
- Using unapproved tools for mass deletion of critical records.
- Exposing archived sensitive data without proper access control.
- Disabling lifecycle jobs to avoid policy enforcement.
Governance, Monitoring, and Enforcement
- Data owners are accountable for retention mapping and classification quality.
- Lifecycle automation health is monitored with failure alerts.
- Legal holds are tracked in a central register with owner and release status.
- Internal audits validate both retained and deleted record samples.
- Vendor contracts must include return or deletion obligations.
- Deletion evidence is retained to demonstrate policy execution quality.
- Material deviations require documented risk acceptance and remediation plan.
- Policy updates are versioned and announced with effective dates.