The session is gone
Keys, addresses and the connection table are released when the tunnel closes. Nothing is written to disk on the way out, because the node has no disk to write to.
Privacy and logs / Revised 1 August 2026
Written as a record, not as reassurance.
This page lists every field that touches a SecuredView VPN machine, how long it stays there, and what would be available to anyone who asked us for it. If a claim elsewhere on this site conflicts with this page, this page is the one that binds.
While you are connected
What sits on the node during a session.
A node has to know a few things to move your packets. All of them live in memory, and memory is all the node has.
| Field | Where it lives | How long it stays |
|---|---|---|
| Session keys | Node memory | Until you disconnect |
| Your address on the way in | Node memory, routing table | Until you disconnect |
| Address assigned inside the tunnel | Node memory | Until you disconnect |
| Open connection table | Node memory, kernel | Until you disconnect |
| Node connection count | Counter store | 14 days |
| Node bytes carried | Counter store | 14 days |
| Everything else | Nowhere | Not applicable |
The counter store, in full
Each node writes one line a minute. The line holds the node identifier, the minute it covers, how many tunnels were open, and how many bytes moved in each direction. Four values and a timestamp. There is no address in it, no session identifier, and no order of events that could be walked backwards to a person. It exists so we know which cities need more hardware.
After you disconnect
What is left, and how it goes.
Immediately
On reboot
The machine forgets itself
The system is loaded over the network into memory at boot. A restart returns the node to a clean state with no record of anything it carried before.
After 14 days
The counters roll off
Minute lines older than fourteen days are deleted. What remains is a monthly total per city, which is what appears on the network page.
The apps
What the client sends home
On first launch the app asks our directory service for the current node list and a set of keys. That request carries the app version and the platform, and it reaches us from your address like any other request. We do not record it.
After that the app talks only to the node you are connected to. There is no telemetry, no analytics library, no crash reporter that uploads on its own. If something breaks and you want to send us a report, the app shows you the whole file first and you decide.
What the website records
This site serves static files and sets no cookies. Our web server keeps request logs for 48 hours to catch abuse, with the last octet of each address removed before the line is written. After 48 hours the file is deleted. There is no analytics service on any page, which is also why we cannot tell you how many people read this one.
Jurisdiction
SecuredView VPN operates under a strict no-logs policy and is structured to minimize data collection. There is no legal requirement to retain user activity data, and we have chosen not to build such records.
Individual nodes are subject to the law of the country they sit in. This is why every node runs from memory and holds nothing. A node seized in any of our 61 countries yields the hardware and nothing else.
Independent audit
Someone outside the company checked.
A claim about logging is worth what the person making it is worth. We commission a review every year, hand over root access to the fleet, and publish the report whatever it says.
- Most recent review completed March 2026, covering the node build, the counter store and both client applications
- Scope included live root access to twelve nodes chosen by the reviewers, not by us
- Two findings raised, both about the directory service, both fixed and re verified in April 2026
- No finding contradicted the no logs position on any node
- The full report is published without redaction, including the two findings
2026 report available on request
Transparency
Every request we have received.
Courts and law enforcement do ask. We answer every valid order, and what we have to give is the counter line described above.
| Period | Requests received | Responses containing user data | Responses stating no such data exists |
|---|---|---|---|
| January to June 2026 | 14 | 0 | 14 |
| July to December 2025 | 9 | 0 | 9 |
| January to June 2025 | 6 | 0 | 6 |
Standing statement, renewed 1 August 2026
As of this date SecuredView VPN has received no order requiring us to alter the client software, weaken any transport, or place collection on any node. We have received no demand accompanied by a prohibition on saying so. This paragraph is renewed on the first of each month. If it is ever missing, or the date stops moving, draw the obvious conclusion.
Housekeeping
Changes to this page
Every revision is dated at the top and the previous versions stay online. A change that reduces your privacy will be announced in the apps thirty days before it takes effect, so that leaving is a real option rather than a discovery.
Reaching us
Write to securedviewvpn@protonmail.com for anything on this page, or securedviewvpn@protonmail.com to report traffic coming from one of our nodes. Abuse reports are answered by a person and are usually handled within a day.
We cannot identify who was behind a given connection, and saying so is not obstruction. It is the direct consequence of the design set out on this page.