Privacy Policy

Last updated: 14 Oct 2026



Policy overview

We do not store activity logs of any kind. We believe in minimal data retention: we want you to remain anonymous.

However, to operate the service (manage subscriptions, limit simultaneous connections), we must process some data. This policy explains exactly what we store, why, and when it is deleted, using a “Technical Evidence” approach.


1. Our anonymous, code-based accounts

We do not ask for any personal information – no username, no password, no email address. Instead, a random 16-digit code (user_code) is generated.

Important for Support:

  • Never share your 16-digit Account Code (user_code) publicly or even with our support team unless explicitly asked in a secure channel.
  • For all support inquiries, use the Support Code generated in the app (Menu -> Support Code). This is a temporary, 8-character code (e.g. ABCD-1234) valid only for one day, which allows us to find your account without exposing your master credentials.
Data TypeExampleRetention
Account Code1234567812345678Deleted 1 year after last login (unless paid time remains).
Support CodeABCD-1234Ephemeral. Valid for 24 hours. Used only for safe account lookup.
Telegram ID123456789Linked only if you use the Telegram Bot. Deleted immediately upon Sign Out from the bot.

2. Device Data (What we store and why)

To enforce the 5-device limit and help with troubleshooting, we store the following metadata when you authorize a device:

FieldExamplePurpose
Device IDUnique IDTo distinguish between your devices.
PlatformAndroid, WindowsTo deliver correct configurations and updates.
App Versionv1.2.0To identify outdated clients during support.
Device NamePixel 7(Optional) To help you identify your devices in the menu.

Retention: This data is stored until you Sign Out that device or remove it via the “My Devices” menu.

Trial device fingerprint: When you start a free trial in the browser extension, the extension reads technical characteristics of the device on the device itself (operating system and CPU architecture, number of logical processors, touch points, screen size and color capabilities, and time zone) and computes a SHA-256 hash there. Only that hash is sent to us and stored, linked to your account, so the same device cannot receive another free trial. The raw characteristics are not transmitted and are not written to our logs. The hash is kept for as long as that limit is needed, which is longer than ordinary device metadata deleted on sign-out. We do not use it for advertising or analytics.


3. What we don’t log

We log nothing that can be connected to an account’s activity:

  • No logging of traffic contents or destinations.
  • No logging of DNS requests.
  • No logging of original IP addresses.
  • No logging of connection history (start/stop times).

Technical Evidence

To prove this, here are the actual configuration snippets from our production servers:

Nginx (Web & Proxy):

# No access logs (no-logs policy)
access_log off;
error_log /dev/null crit;

OpenVPN:

verb 0
status /dev/null
ifconfig-pool-persist /dev/null

Proxy server (logging configuration):

"log": {
  "loglevel": "warning",
  "access": "/dev/null",
  "error": "/dev/null",
  "maskAddress": "full"
}

4. Active Session State (How we limit connections)

Question: How do you limit the maximum number of simultaneous connections (5 devices) if you don’t log activity?

Answer: We maintain a real-time state of currently active sessions in our central database. This is not a history log; it is a list of “who is connected right now”.

Data TypeDescriptionRetention
Active SessionLinks device_id to a specific VPN server.Ephemeral. Created when you connect. Deleted from the database when you disconnect or the session times out.

Important: If a server is seized, this “active state” might theoretically show which devices are connected at that exact moment, but it contains no history of past connections or traffic data.


5. Server Metrics

We monitor the health of our servers to ensure speed and stability. We collect aggregated system metrics only.

MetricDetails
System LoadCPU, RAM usage per server.
BandwidthTotal bytes sent/received by the server network interface. Not attributed to individual users.

6. Payments

We support two payment methods. Data handling differs by provider:

A. Telegram Stars (In-App)

Payments are processed by Telegram. We receive only confirmation metadata.

Data we storeRetention
Transaction ID, Amount, DateUp to 3 years (accounting/tax laws).
Note: We do not see your card details. Telegram handles the financial transaction.

B. Cryptocurrency (NowPayments)

We use NowPayments as a processor.

Data we storeRetention
Transaction Hash, Amount, Currency, StatusUp to 3 years (accounting/tax laws).
Note: Blockchain transactions are public. NowPayments may collect data according to their policy.

C. Bank Cards (YooKassa)

We use YooKassa to accept payments via bank cards (RF).

Data We StoreRetention
Email for ReceiptsStored in encrypted form (AES-256). Used only for sending receipts in accordance with 54-FZ law. No spam/marketing.
Card DataWe do not store full card details (PAN, CVV). We store only the mask (last 4 digits) and a payment token for recurring payments (if you authorized them).
Transaction MetadataTransaction ID, Amount, Status. Stored for up to 3 years (accounting requirements).

How We Protect Your Email: The email entered during payment is encrypted in our database immediately upon receipt. It is not available in plain text to support staff and is used exclusively by the automated system to transmit to the OFD (Fiscal Data Operator) at the moment of payment creation to send you a receipt. We do not link this Email to your user_code for marketing purposes.


7. Support

If you contact support (Email or Telegram Bot):

  • Email: We keep correspondence to resolve your issue. Deleted after 1 year or upon request.
  • Telegram Support Bot: Messages are stored in the chat history. You can delete the chat at any time.

Contact