What we log and what we don't
We prefer exact detail to a marketing line. Here is what is kept, what is not, and for how long.
What is NOT kept
On our own nodes, the VPN does not log connections, destinations or content. The app holds no browsing history and transmits none anywhere. For the nodes we do not operate, read the next section before drawing conclusions.
There is no account. No email, no phone number, no user identifier. There is no profile to attach activity to.
There is no analytics, advertising or crash-reporting SDK inside the application. It carries neither Firebase nor Crashlytics, and it sends no crash reports and no usage data.
Who runs the node, and why it matters
The catalogue mixes two different things, and the difference is the most important item on this page. Some nodes are our own infrastructure, run by Veritas Nexus Legal LLC, DBA Veritas Digital. Others are community nodes: they are operated by people who are not us, and they come from public sources.
Of our own nodes we can state that they keep no connection logs, because we configure them, we administer them and we can show the configuration. Of the community ones we can state nothing. We do not know what they record, for how long, or who can read it. They could be keeping everything and there would be no way to tell.
We do not hide them, because they widen the coverage and because, in a country that blocks, having somewhere to go matters. But the application labels every node with its origin — "Veritas" or "Operated by a third party" — in the list, on the selected-node card and in the status bar. If this distinction matters to you, and it should, pick one of our own.
Saying "we keep no logs" flatly, knowing this, would be exactly the kind of convenient phrase this page exists to avoid.
What IS kept
Access logs of the website and catalogue proxy. As on any website, the proxy keeps IP address, date and requested path when someone visits this site or when the app downloads the server catalogue. They are kept for about 5 weeks.
Technical error logs. The servers keep error logs that may contain IP addresses, such as the source address of a failed connection. They are kept for a limited time.
Defence systems. To protect the service, the defence systems process the IP addresses of those who attack the servers.
What technical third parties see, even though we keep none of it. Outside the tunnel, the app does only two things: it sends encrypted DNS queries to Cloudflare and Google to resolve the catalogue addresses, and it opens test TLS connections, carrying none of your data, to large public domains to choose how to disguise the connection. There, those third parties see your device's IP address, but none of your data. While the VPN is on, your apps' DNS queries are also resolved by Cloudflare and Google, but they travel through the tunnel and leave from the node: the resolvers receive the domain names being looked up with the node's IP address, not yours.
Why we put it this way
Many services say "zero logs" without qualification. It is a convenient phrase that is almost never literal: if a service has a website, that website has access logs.
We would rather state what is kept and for how long, so you can judge for yourself instead of trusting a slogan.
The formal detail is in the privacy policy and the transparency report.