SafePassVpn

SafePassVPN

All systems operational
Transparency Report

We have nothing to hide. Literally.

Every legal request, DMCA notice, and government inquiry SafePassVPN has ever received — and exactly how we responded. Updated regularly.

Last updated: May 7, 2026

Warrant Canary

As of May 7, 2026, SafePassVPN confirms the following statements are true. If any of these statements are ever removed, users should treat that as a signal that our legal situation has changed.

We have NOT received any National Security Letters.

We have NOT received any binding gag orders.

We have NOT been compelled to install any backdoor or surveillance software.

We have NOT disclosed any private encryption keys.

We have NOT been forced to modify our systems to allow access by any third party.

We have NOT provided bulk access to user traffic to any government or agency.

What We Store vs. What We Don't

We do NOT store

VPN connection logs
IP addresses assigned to you
Browsing history or DNS queries
Traffic content or metadata
Connection timestamps
Bandwidth usage per user

We DO store

Email address (for your account)
App version & OS type (crash reports — opt-out in Settings → Help us fight censorship)

Even if compelled by law, we have no VPN activity data to give — because we never collect it.

RAM-Only Server Infrastructure

SafePassVPN servers are built on a RAM-only architecture — here's what that means for your privacy:

All servers run entirely in RAM

No user data, configuration, or VPN session information is ever written to disk. Everything lives in volatile memory only.

A reboot wipes everything

Any server restart — planned or forced — permanently and instantly erases all data. There is nothing left to seize or hand over.

Even a court order can't produce what doesn't exist

If a server were ever seized or imaged by any party, they would find an empty system. This is a technical guarantee, not just a policy promise.

We have not disclosed any private encryption keys to any third party.

DMCA & Government Requests

The table below shows every DMCA notice and government inquiry SafePassVPN has received since launch, and the outcome of each. We will update this quarterly.

PeriodDMCA NoticesGov. InquiriesUser Data Disclosed
Jan 1 – Mar 31, 2026100
Apr 1 – May 7, 2026 (ongoing)000

DMCA Incident — February 2026

SafePassVPN received a DMCA notice forwarded by our infrastructure provider relating to torrenting activity originating from one of our VPN server IPs. We responded by implementing infrastructure-level controls on that server. We did not — and could not — identify the individual user, as SafePassVPN retains no connection logs, timestamps, or user IP assignments. Zero user data was disclosed.

This incident is an example of our no-logs policy working exactly as intended.

How We Handle Legal Requests

1

We review every request carefully

We assess whether the request is legally valid, properly scoped, and issued by a jurisdiction we are legally required to comply with.

2

We notify users when permitted

If we receive a request and are legally allowed to inform the affected user, we will do so before complying.

3

We push back on overbroad requests

We challenge requests that are vague, overly broad, or lack proper legal basis.

Questions about this report?

If you're a researcher, journalist, or user with questions about our privacy practices or this report, reach out directly.

contact@safepassvpn.com