How Nsec VPN handles information, and where other providers are involved.
Updated 2026-10-12 · Nsec VPN
01
Scope and operator
This policy covers the Nsec VPN Android app and this website. The published contact section identifies the service operator and provides its contact details. The published retention schedule below describes how long service records are retained and how deletion requests are handled.
02
VPN traffic
The supplied app, backend, and agent do not persist browsing history, DNS queries, traffic content, or originating client IP addresses. Current peer endpoint, handshake, and transfer information exists in WireGuard memory during operation.
03
Service records
A random per-install ID, registered device and app information, authentication proofs, refresh-token hashes, entitlement information, public peer keys, tunnel addresses, node and lease expiry, purchase ownership hashes, promo redemptions, reward tickets, and server requests are stored to operate the service. Admin actions are recorded separately.
04
Private keys
WireGuard private keys are generated and stored on the Android device. They are not sent to the backend or node. Android Keystore protects local encryption keys, with hardware backing depending on the device.
05
Ads and payments
Google AdMob supplies ads and Google Play handles purchases. These providers process information under their own policies. The app’s ads and service requests intentionally bypass the VPN and may expose the ordinary network address to those providers. Review consent choices offered in the app.
06
Optional speed tests
Where the matching companion is installed, speed-test traffic is sent through the VPN to Cloudflare endpoints. The provider sees the node’s exit IP and may retain its own records. Completed test results are kept locally on the phone, not as browsing history.
07
Website storage
This website has no analytics or advertising scripts. Public pages do not set tracking cookies. The website dashboard uses an essential session cookie and local server files for content, administrator credentials, and content revisions. Theme preference is stored locally in your browser. Hosting and reverse-proxy access logs depend on the actual deployment; the supplied guide disables this website’s Nginx access logging.
08
Retention, deletion, and requests
Clearing app data removes local credentials and history but does not delete backend records. Use the published support address for access or deletion requests. The operator’s retention schedule and deletion procedures appear below. Some records may need to be retained to fulfill legal obligations.
09
Changes
The current policy date is shown on this page. Material changes should be described before they take effect. Contact support if you need clarification.