Last updated: 2026-05-03
This Policy explains what data Privex VPN ("we", "the service") collects when you use our VPN client apps, browser extensions, and the privexvpn.app website. We aim to keep this short, plain-spoken, and accurate.
| Data | Purpose | Retention |
|---|---|---|
| Email + hashed password (argon2id) | Sign-in, account recovery | Until account deletion |
| Optional name | Personalization | Until account deletion |
| Subscription tier & renewal date | Plan enforcement | Until account deletion |
| Device list (id, platform, name, last-seen) | Concurrent-device limit + remote sign-out | Until you revoke or account is deleted |
| Audit log (login, password change, device add/remove, session rotate) | Account security forensics | 180 days |
| Active session token hashes | Sign-in across browser restarts | Until you sign out |
| WireGuard / VLESS peer entries | Issuing tunnel keys | Until the device or peer is revoked |
| Anonymous telemetry (opt-in) | Product improvement | 90 days, no userId |
The Privex VPN nodes encrypt and forward your network traffic. They handle packets in real-time but do not write per-user traffic logs. Server-level metrics that are recorded — CPU/memory/load, total bandwidth, current peer count, last-handshake timestamps — exist only as aggregate operational data and are not tied back to specific user accounts.
For the browser-extension HTTP CONNECT proxy, our Squid layer logs short connection events to the control plane (so the admin dashboard can show "active proxy clients"). These records contain only the user id and the node, not the destination URL or content.
You can:
Profile → My Devices.[email protected].Privex VPN is not intended for users under 13. We do not knowingly collect data from minors.
If we materially change this Policy we will notify you in-app and update the "Last updated" date above.
Questions: [email protected]. We respond within 5 working days.