NOKZ Transparency

Last updated: April 2026

NOKZ is built around one principle: reduce data exposure while keeping the service technically workable in the real world.

What NOKZ Is Designed Not to Retain

• Browsing history
• Traffic destinations
• DNS query history
• Contents of VPN traffic

What NOKZ May Retain for Operations

• Authentication and restore state for anonymous access
• Subscription and entitlement state
• VPN provisioning metadata and internal peer state
• Technical and error logs needed for debugging, uptime, and service integrity
• Basic website analytics in privacy-oriented aggregate form

How Access Works

NOKZ supports anonymous access keys generated in the app. These keys can be used without email registration and are intended to reduce personal data exposure during onboarding.

How NOKZ Handles Service Risk

NOKZ is not designed to inspect VPN traffic contents. Where needed to protect uptime, billing state, infrastructure, or upstream provider relationships, the service may limit or revoke access using operational controls rather than traffic inspection.

Infrastructure

NOKZ currently operates on managed server infrastructure. This allows the service to run and expand, while keeping retained user data limited. Managed infrastructure also means NOKZ does not control every underlying physical layer.

Principles

• Minimal data retention
• No traffic inspection by default service design
• Anonymous access where possible
• Operational realism over exaggerated marketing claims
• Honest limitations: no service can guarantee absolute anonymity

Contact

Transparency inquiries: support@nokz.io