English

What does a VPN log? Read the record categories

The word “logs” can refer to several different kinds of records. A connection event, an account subscription, an error message and a website access entry are not interchangeable. Asking only whether a service has logs can therefore leave important questions unanswered.

A useful privacy explanation identifies the categories, their purposes, who or what they are linked to, and how retention works. ZARDO currently retains account, subscription and payment records, device and connection records, last-handshake timestamps, diagnostic data and operational website logs. Some records are included in backups. The service does not operate under a zero-logs policy.

Start with the account and subscription

An account record helps the service recognise a user and manage access. Subscription information describes an arrangement such as the selected device allowance and its term. These records are operational data even if they are not called network logs in a product interface.

Payment records describe purchases or payment-related operations. They can remain associated with an account and the terms that applied to an operation. A privacy explanation that mentions only an email address would not describe the full set of categories retained by the reviewed ZARDO service.

Do not infer the contents of one category from another. For example, the existence of payment records does not by itself establish exactly which card fields a payment path stores. Specific claims about sensitive payment fields need evidence from that particular path, rather than an assumption based on the word “payment”.

Distinguish devices from connection events

A device record can help the service associate access with a device and apply account limits. A connection record concerns a session or access event. The categories can be related, but they answer different operational questions.

In the reviewed ZARDO implementation, connection records are not limited to a temporary on-screen connected indicator. Records and last-handshake state can persist. It would therefore be inaccurate to describe all sessions as existing only in memory or to promise that no connection history is retained.

A last-handshake timestamp is a technical observation about a VPN peer. It should not be described as a list of visited pages. Equally, the absence of a dedicated visited-page field in one inspected schema is not a comprehensive audit of every component, log format and runtime situation. Keep the claim as specific as the evidence.

Understand what diagnostics can contain

Diagnostics help investigate failures and unexpected behaviour. They may record timing, state changes, session identifiers or measurements associated with a connection. Calling something diagnostic does not automatically make it anonymous.

ZARDO's reviewed diagnostic records can be linked to accounts, devices or sessions. Technical observations include handshake state and traffic counters. Those associations matter when assessing privacy: an otherwise ordinary event can be more informative when joined to account and device records.

If you contact support, consider the material you add yourself. A screenshot or diagnostic attachment can contain more information than the short error description you intended to share. Remove passwords, recovery information and unnecessary account details, and use a verified support channel for anything that needs private handling.

Website logs are a separate category

A VPN service can operate websites for registration, account management and updates. Those systems have their own operational records. A statement about the tunnel's data format does not establish the contents of a website's access or error logs.

ZARDO keeps operational website logs. Error logs can contain addresses, so a universal statement that addresses are never retained would be inaccurate. The verified account site supports HTTPS, but transport encryption does not mean that the service handling a request keeps no operational record of it.

Similarly, a static public page with no external analytics does not establish that a separate account application has no technical cookies or server logs. Assess the public site, account service and VPN connection as related but distinct parts of the product.

Read retention as a category-specific process

Retention is more than a single number on a page. A configuration may state a rotation period, a cleanup job may act on selected records, and backups may preserve another copy. These processes need separate descriptions.

For ZARDO, operational journals and web logs have a 14-day retention configuration. A daily job removes older connection-attempt diagnostics and replaces diagnostic-report content after 30 days. Those statements do not apply to every connection record or every backup, and deletion is not instantaneous.

Some old diagnostic records were still present at the readback. It would therefore be inaccurate to turn a configured cleanup rule into a universal maximum age for all retained data. Replacing the contents of a report also differs from deleting its associated database row and every related record.

Ask what happens to copies

Backups can preserve records outside the active database. Deleting or changing an active row does not establish that every backup containing an older version has been removed at the same time. A complete policy needs to explain those boundaries.

ZARDO's current verified wording says that some records are included in backups. It does not promise that every backup is encrypted, current or subject to one universal deletion deadline. Those stronger statements would require a separate basis.

Location deserves similar care. A proposal for a different control-plane location or memory-only sessions is not evidence that either change has already been deployed. Privacy decisions should use the actual service and current verified records rather than an architecture that exists only in planning.

Turn a privacy label into concrete questions

Before choosing a VPN, ask which account, payment, device, connection, diagnostic and website records it uses. Then ask how each category is linked, how cleanup works and what happens to backups. These questions produce more meaningful answers than an unqualified privacy slogan.

ZARDO's full privacy page still needs final operator and contact details, purposes, recipients, legal grounds and retention decisions. The factual interim explanation should not be mistaken for a complete legal policy or an independent security audit.

Read the platform information and pricing details separately as well. Encryption, software readiness, renewal behaviour and data retention are different parts of the same service decision. Understanding each one lets you assess the product without assigning it protections that have not been established.