Transparency
What we keep, for how long, and who else sees it.
This page is the privacy policy with the lawyers’ sentences taken out. Nothing here says less than the policy, and nothing here says more.
We do not log the sites you visit, your DNS queries, or anything else inside the tunnel. We cannot read it. We keep a small record while a session is running, deleted when the session ends. Operational logs that include your IP address are kept for no more than two days, then deleted. A VPN is not invisibility: it changes where your traffic joins the public internet, not what you do once it gets there.
Are there any free no log VPNs?
We do not use the phrase, because every VPN keeps something while you are connected; instead, here is the complete list of what NetCloak keeps, which is short, and how long each item lives.
The session record, field by field
While a session is running, our server holds one row for it. These are its fields, in full:
- WireGuard® public key
- Generated on your phone for this session. Identifies the tunnel, not you.
- Tunnel address
- A private address in the 10.8.x.x range assigned inside the tunnel. It is not your public address.
- Created, expires, last active
- Three timestamps. They are how the server knows when to end the session and whether the tunnel has gone idle.
- Extension count
- How many times the session was extended.
- Anonymous identifier
- The subject of your access token: a random value with no link to a person, account, or email.
- Bytes transferred
- Measured against a fair-use ceiling of 10 GB per session, which exists so that one session cannot exhaust a shared server. It is not a quota and the app does not show it.
- Mode
- Marathon, Balanced or Sprint.
The row is deleted when the session ends, for any of the reasons on the how it works page.
Logs, and the two-day rule
Our server writes operational logs: which requests arrived, which were refused by the rate limiter, which sessions were created and reclaimed. Those logs contain your public IP address, because that is what a request arrives from. They are kept for no more than two days and then deleted. Rate limits are five requests a minute per address for creating or extending a session and thirty for checking its status.
There are no browsing logs, no DNS query logs, and no record of traffic content. This is not a policy choice we could quietly reverse; the traffic is encrypted with a key we do not hold, so there is nothing to record.
The server
One, in New York, United States, rented from Contabo GmbH, a hosting company based in Germany. We say this plainly because “servers in 90 countries” is the kind of sentence that usually hides rented capacity and virtual locations. Ours is one machine, we know exactly where it is, and everyone connects to it.
Who else touches data, and what each receives
- Google AdMob and User Messaging Platform
- Serve the rewarded video ads and collect your consent choice. AdMob receives your device’s advertising identifier, which you can reset or delete in Android settings. When an ad reward is verified, the app attaches a random single-use number and the anonymous identifier from your token, and Google calls our server to confirm the reward. Nothing about your browsing reaches AdMob, because it does not pass through the app.
- Cloudflare
- Runs the DNS-over-HTTPS resolver at 1.1.1.1 the app uses to find its server list and settings. Like any DNS query, that tells Cloudflare which record was asked for, from which network address.
- Google Play
- Distributes the app under its own terms and sees the install.
- Contabo GmbH
- Hosts the server. Sees the machine, not the contents of the tunnel.
There is no analytics provider, no crash-reporting service, and no payment processor, because the app sends no analytics, reports no crashes to a third party, and sells nothing.
What we cannot see
The sites you visit, the apps you use, the content of anything you send or receive, your DNS queries, and your location beyond the coarse fact of which network address you connected from. The tunnel is encrypted end to end between your phone and our server with a key your phone generated. We can see that a tunnel exists and how many bytes have crossed it. That is all.
Legal requests
Legal requests received to date: 0 (as of 2026-09-20). This line is updated whenever that changes. What could be produced in response is limited by what exists: a session row that lives for the length of a session, and operational logs that live for two days.
How the app uses Android’s VPN service
NetCloak uses Android’s VpnService to route the device’s traffic through an encrypted tunnel to our server. It does not redirect, inspect or manipulate the traffic of other apps for advertising or any other purpose, and it does not inject anything into it. This is the same statement we make to Google Play in the VPN declaration every VPN app must file.
The full privacy policy, with every past version, is at legal.neuera.app, and a copy is kept at /privacy/.