How long CipherVPN retains data, why, and how it is securely destroyed
Effective Date: 1 January 2026 · Last Updated: 25 February 2026 · Version 2.1
CipherVPN's data retention framework is governed by three principles derived from GDPR Article 5(1)(e), the UK Data Protection Act 2018, and industry best practices:
Storage Limitation: Personal data is kept only for as long as necessary for the purpose for which it was collected. When that purpose has been fulfilled, data is securely and permanently deleted.
This policy applies to all data held in CipherVPN production systems, backup archives, disaster recovery systems, and data held by sub-processors acting on our behalf.
Key: Auto-deleted = enforced programmatically Legal hold = retention required by statute Manual review = reviewed case-by-case
| Data Category | Retention Period | Legal Basis | Type |
|---|---|---|---|
| Account email address | Duration of account + 30 days after deletion | Contract performance | Auto-deleted |
| Password hash | Duration of account | Contract performance | Auto-deleted |
| Account creation / deletion timestamps | 7 years | Fraud prevention, legal obligation | Legal hold |
| Subscription & plan history | 7 years from last transaction | Tax/accounting law (UK: Companies Act 2006) | Legal hold |
| Payment transaction records | 7 years | HMRC requirement, EU VAT Directive | Legal hold |
| Invoices | 7 years | Statutory accounting requirement | Legal hold |
| VPN connection timestamps (connect/disconnect) | 7 days (rolling) | Abuse detection, legitimate interest | Auto-deleted |
| Aggregate bandwidth usage (per-day total) | 90 days | Fair use enforcement, capacity planning | Auto-deleted |
| WireGuard session keys | 24 hours (key rotation) — never persisted | Technical necessity only | Auto-deleted |
| Support ticket content | 3 years from ticket close date | Legitimate interest (QA), potential claims | Auto-deleted |
| Support attachments | 1 year from ticket close | Support QA | Auto-deleted |
| Infrastructure/admin access logs | 90 days | Security operations, incident response | Auto-deleted |
| App crash reports | 30 days (anonymised form only) | Product improvement (consent) | Auto-deleted |
| 2FA / security event logs | 180 days | Security investigation capability | Auto-deleted |
| Marketing communication preferences / consent records | 3 years from last contact or consent withdrawal | Consent documentation (PECR/ePrivacy) | Legal hold |
| Anonymised analytics & aggregates | Indefinite (no personal data) | N/A — not personal data | — |
| Legal hold / investigation data | Duration of hold + 30 days | Legal obligation / court order | Manual review |
In addition to the general schedule, the following VPN-specific retention rules apply:
The following data categories are architecturally excluded from CipherVPN infrastructure and are never written to any storage medium:
Connection timestamps (session start and end, UTC) and server node used are retained for a maximum of 7 days as a rolling window for:
Automatic deletion of session timestamps is enforced by a scheduled job running every 24 hours that purges records older than 7 days. This is auditable by inspection of the infrastructure configuration.
Messages encrypted using CipherVPN's E2E encryption protocol or PGP are stored as opaque encrypted ciphertext. CipherVPN holds no decryption keys. These messages are retained until:
When you send email to external addresses (non-CipherVPN recipients), the message passes through SMTP relays for delivery. SMTP relay logs (sender, recipient, timestamp, delivery status) are retained for 14 days for delivery diagnostics, then automatically deleted. Message body content is never logged.
For internal CipherVPN-to-CipherVPN messages, routing metadata (sender, recipient, timestamp) is retained within your encrypted mailbox. It is encrypted at-rest and subject to the same deletion rules as message content.
To prevent spam, we store one-way cryptographic hashes of flagged message fingerprints for 90 days. These hashes cannot be reversed to reveal message content.
Financial records are subject to mandatory statutory retention under tax and company law. These records are retained regardless of account deletion requests.
| Record Type | Retention | Statutory Basis |
|---|---|---|
| Transaction receipts and invoices | 7 years from transaction date | UK HMRC, EU VAT Directive 2006/112/EC |
| Subscription history (plan, amount, dates) | 7 years from last transaction | Companies Act 2006 (UK) |
| Refund records | 7 years | Consumer Rights Act 2015, tax law |
| Chargeback documentation | 7 years | Payment card network requirements |
| Credit/promo code issuance | 3 years | Contractual record-keeping |
Payment card numbers are never stored by CipherVPN. The payment processor (Stripe) maintains tokenised payment methods in accordance with PCI-DSS. Upon account deletion, payment tokens are revoked from the payment processor within 30 days.
When CipherVPN receives a valid legal order requiring preservation or disclosure of data, a legal hold is activated:
Legal holds affect only the specific data described in the order. Other data for the same account continues to be deleted per this schedule. We fight overbroad orders and narrow scope wherever possible.
When data reaches the end of its retention period or an account deletion request is processed:
Data deleted from production systems persists in encrypted backups until the backup rotation cycle completes (maximum 90 days). After 90 days, all production-deleted data has been purged from the backup chain.
When physical media (SSDs, HDDs) is decommissioned, we follow NIST SP 800-88 Rev. 1 media sanitisation guidelines:
| Backup Type | Frequency | Retention | Encryption |
|---|---|---|---|
| Full database snapshot | Daily | 30 days | AES-256-GCM, separate key management |
| Incremental database backup | Every 6 hours | 7 days | AES-256-GCM |
| Transaction logs (PITR) | Continuous | 14 days | AES-256-GCM |
| Configuration backups | On change | 90 days (last 50 versions) | AES-256-GCM |
| Disaster recovery snapshots | Weekly | 90 days | AES-256-GCM |
All backup archives are stored in geographically separate locations from production systems, with access restricted to a maximum of 3 named operations personnel. Backup restoration procedures are tested quarterly.
Enterprise customers can configure custom retention policies for their organisation's data through the Admin Dashboard → Data Governance panel:
Enterprise retention configurations do not override CipherVPN's minimum or maximum retention obligations under this policy or applicable law. Contact enterprise@ciphervpn.eu for configuration assistance.
Under GDPR Article 17 and equivalent laws, you have the right to erasure of your personal data. To request deletion:
We will confirm deletion within 30 days. Note that legally-required data (billing records under 7-year rule) will be retained in isolated, restricted storage — we will inform you which categories cannot be deleted and the legal basis.
You may also request a Data Portability export (GDPR Art. 20) before deleting your account. Exports are provided in JSON format within 30 days of request to privacy@ciphervpn.eu.