The Memory in the Tunnel: VPN Log Retention and the Subpoena Your Firm Hasn't Met
Photo: Jaggery , CC BY-SA 2.0, via Wikimedia Commons
A VPN that claims not to log is not necessarily a VPN that forgets. The distinction matters for accounting firms because a VPN connection record can become evidence in a client dispute, a regulatory inquiry, or a subpoena years after the engagement ends. Firms spend considerable time deciding how long to keep workpapers. Few apply the same discipline to the tunnel that carried the work.
No-log is not no-memory
A no-log policy usually means the vendor does not record browsing activity, destination IP addresses, or DNS queries tied to a user. It does not mean the vendor retains nothing. Account records, payment records, support tickets, app diagnostics, authentication events, and connection metadata may persist for business, fraud-prevention, or legal reasons. The scope and duration depend on the vendor, the jurisdiction, and the contract.
For a CPA firm, the relevant question is not only what the vendor logs. It is what the vendor can produce, how quickly, and under what legal process. A policy that sounds absolute in marketing language may be narrower in the terms of service.
The vendor comparison, without false precision
As of our November 2026 policy review, the major consumer VPNs we evaluated fall into recognizable postures. The table below summarizes public claims, not a warranty. Firms should verify the current policy, the jurisdiction, and the contract before relying on any row.
| Vendor | Public posture | Jurisdiction to verify | Retention question for the vendor |
|---|---|---|---|
| Mullvad | Account-number model; minimal account data; no activity logs claimed | Sweden | What is retained for payment and support, and for how long? |
| Proton VPN | Audited no-logs posture | Switzerland | Which audits cover connection metadata, not just browsing activity? |
| ExpressVPN | No activity logs claimed; TrustedServer architecture | British Virgin Islands | What account and payment records survive, and under what process? |
| NordVPN | Audited no-logs posture | Panama | Does the audit scope include authentication and support records? |
| Surfshark | No-logs posture | Netherlands | What is retained for billing, fraud prevention, and legal requests? |
| Private Internet Access | No-logs posture | United States | How does US jurisdiction affect subpoena response and retention? |
| IPVanish | No-logs posture | United States | What connection metadata is available to law enforcement, if any? |
We are not publishing guessed day counts. A vendor's public policy may change, and a reseller or business plan may carry different terms. The purpose of the table is to force a contract-level question: what data exists, where is it stored, and who can be compelled to produce it?
Metadata that can survive the tunnel
Even a strict no-log VPN may retain the following categories. Each has a legitimate business purpose, and each can become relevant in e-discovery.
- Authentication events: timestamps, success or failure, and account identifiers.
- Device or app identifiers: installation records, device names, and app version data.
- Payment records: name, billing address, card metadata, and transaction history.
- Support records: emails, chat transcripts, and troubleshooting details.
- Fraud-prevention data: IP addresses or device signals used to detect account abuse.
The firm's own systems may retain more. Firewall logs, identity-provider logs, endpoint logs, and document-management audit trails can establish who connected, from where, and when. A VPN vendor's no-log claim does not erase the firm's internal records.
A retention matrix for counsel
Before busy season, build a one-page matrix with counsel. It should cover the firm's own logs as well as the vendor's.
| Data type | Business purpose | Proposed retention | Legal-hold trigger | Owner |
|---|---|---|---|---|
| VPN authentication logs | Security monitoring and incident response | 12 months, or as required by insurer | Litigation or regulatory inquiry | IT lead |
| Firewall and gateway logs | Intrusion detection and client questionnaire evidence | 6 to 12 months | Incident or subpoena | IT lead |
| MFA enrollment records | Access control and offboarding audit | Life of account plus 12 months | Investigation | Identity administrator |
| Vendor support tickets | Troubleshooting and vendor accountability | 24 months | Dispute or legal hold | Vendor manager |
| Billing records | Tax and accounting | 7 years, subject to firm policy | Audit or legal hold | Finance |
The matrix is not a legal opinion. It is a structured conversation. State boards, engagement letters, client contracts, and firm policy can all affect retention. Counsel should confirm the final schedule.
The subpoena you have not met yet
A subpoena or client request may arrive years after the engagement. If the firm retained too little, it may be unable to show that access was controlled. If it retained too much, it may face production costs and privacy exposure. The right answer is a documented schedule applied consistently, with a legal-hold process that suspends deletion when needed.
Before the next busy season, ask the VPN vendor three questions in writing: what connection metadata is retained, for how long, and under what circumstances it is disclosed. Then compare the answer with the firm's own retention matrix. The tunnel remembers more than the marketing page suggests.