Privacy Policy โ€” SceptraVPN

Effective date: October 5, 2026
Data controller/operator: SceptraVPN, operated by Individual Entrepreneur Rodion Proskuriakov (Identification Number 304803041), registered with Georgia's National Agency of Public Registry (registration date March 2, 2026)
Registered address: Georgia, Tbilisi, Ponichala 3 Settlement, Building 5, Entrance 2, Floor 4, Auxiliary Storage Room
Privacy contact: [email protected]

1. Scope

This Policy explains how we process personal information when you visit our website, use our Telegram Mini App or account dashboard, purchase a subscription, retrieve connection configurations, or connect through our VPN/proxy infrastructure.

2. Information we process

CategoryInformation and sourcePurpose
Account and sign-inTelegram login data received from your sign-in flow, which may include your numeric Telegram ID, name, username, profile-photo URL, and authentication metadata. Our account records retain the Telegram ID linked to an internal user ID and account creation time. Before you add a real email, we generate an internal placeholder address from your Telegram ID.Verify sign-in, create and identify your account.
EmailAn email address you submit, pending confirmation records, confirmation status, and timestamps.Confirm the address, update your account, and send confirmation or account-security messages.
Sessions and handoff linksSession identifiers, token hashes, creation and expiry times; single-use purchase-link token hashes and use/expiry records.Authenticate dashboard requests and associate a checkout with your account.
Subscription and credentialsPlan and subscription identifiers, validity dates, promocodes, subscription-link tokens and wrapped links, VPN account identifiers and credentials, assigned server, protocol, and relevant timestamps. The time added by each payment, and a record of manual changes to validity dates with the identifier of the staff or system account that made them.Supply and manage paid access and connection configurations, and calculate refunds.
PaymentsAccount ID, email or internal placeholder, payment and provider references, checkout URL, plan, duration, USD price, status, and timestamps. Cryptocurrency records may include currency, quoted and received amounts, confirmations, transaction hashes, source and destination wallet addresses, block numbers, and first-seen timestamps. Telegram Stars payments made in our Telegram Mini App record the Stars price, Telegram's payment charge ID, and the User Agreement version you confirmed before buying.Create checkout, reconcile payments, grant subscription time, resolve billing issues, and maintain required records.
RefundsRefund requests and their payment reference, the time we received them, the refund address and network you provide, your stated reason, our review decisions and notes, the calculated refund amount and network fee, and the payout transaction hash and time.Assess and pay refunds, adjust subscription time, resolve disputes, and maintain required records.
Traffic-volume metricsPeriodic upload/download or total byte counters associated with VPN accounts or access keys, collection times, protocol, and server identifiers/names. Account/key labels may also be stored.Understand usage and capacity and diagnose service operation. These records may be linkable to your account; they are not necessarily anonymous.
Website/API and operational logsClient IP address, request method, matched route, response status, timing, operational errors, and diagnostic traces where enabled.Operate and secure the Service and investigate failures.
SupportInformation you choose to provide to [email protected], including account/payment references and messages.Respond to requests and investigate problems.

The current login flow uses Telegram; it does not retrieve your Telegram conversations or contact list. Profile information may be received to verify a login without being saved as an account profile.

Information needed for sign-in, payment confirmation, and connection provisioning is required to supply those features. If you do not provide it, the relevant feature may not work. You do not need to add a real email to create a Telegram-linked account; an internal placeholder is used until you confirm an address.

3. VPN traffic and logging

Our infrastructure processes network traffic to route your connection. This necessarily involves connection addressing and the data needed to forward traffic. Our VPN servers disable access logs and enable per-account traffic-volume counters. The reviewed application does not implement a browsing-history or traffic-content analytics database.

We do retain service records and operational logs described above, including IP addresses in website/API request logs and account-linked traffic volumes. This Policy does not promise an absence of all logs. Our application request logger uses route templates rather than raw subscription-token paths or query strings, but hosting platforms, proxies, client applications, and external services may have separate logging practices.

Our server-side DNS configuration lists Cloudflare (1.1.1.1) and Google (8.8.8.8) resolvers. DNS requests handled by those resolvers are subject to their own processing practices. Actual DNS handling also depends on the selected VPN client and connection configuration.

Some of our entry nodes are located in Russia, so the Service keeps working on Russian networks that only allow approved destinations. Traffic between your device and these nodes, and from these nodes to our exit servers outside Russia, is encrypted. It is decrypted only in the node's memory while being forwarded, and we do not record it. The provider hosting these servers is subject to Russian law and controls the underlying hardware, so we cannot rule out access to a server itself, and your connecting IP address is visible to the networks carrying your connection. These servers hold your VPN credential, a label made from a random internal account ID, live traffic-volume counters, and error logs that may include connection addresses. They do not hold your Telegram ID, email, or payment records, which are stored outside Russia.

Encrypted connections between your device and our nodes do not guarantee that all onward traffic is encrypted. Use secure application protocols, such as HTTPS, for end-to-end protection with the destination service.

4. Local storage and external clients

The website stores your session token and expiry in browser local storage to keep you signed in across pages. Sessions currently expire after one hour; the website clears an expired session when it next checks it. Signing out or clearing site storage removes the locally stored session. Blocking local storage may prevent persistent sign-in.

Your chosen VPN client may store imported subscription URLs, credentials, and connection settings on your device. Revoking a subscription URL stops future retrieval through that URL but does not necessarily remove settings already imported into a client.

We do not use cookies or CDN-level storage. Where configured, our website and Telegram Mini App use PostHog product analytics, which stores an anonymous device/session identifier in browser local storage rather than a cookie - see "Who receives information" below for what that analytics integration receives.

5. Who receives information

We use infrastructure and external services to provide the Service:

Authorized personnel may access records as needed to operate the Service or handle your request. We may disclose information where required by a binding legal process or where lawfully necessary to protect the Service or others. Requests are assessed under applicable law; we can disclose only information available to us. We do not act on requests from Russian state authorities, including Roskomnadzor, to disclose information about you or to restrict your access, and we are not registered with Roskomnadzor.

We do not sell your information, and we do not use it for targeted third-party advertising.

6. Purposes and legal bases

Where a law requires a legal basis, the proposed bases are:

We serve users in Russia and the European Union in addition to other markets; formal confirmation from qualified counsel that these bases, and the Happ link-sharing disclosure above, satisfy both jurisdictions' specific requirements is still pending.

The reviewed code automatically checks payment and subscription status to grant or expire access. It does not implement credit scoring or behavioral profiling.

7. Retention

We retain information only for the period needed for the stated purpose and applicable legal obligations. Before publication, we will specify and implement the following schedule:

RecordsRetention period or criterion to finalize
Account, sign-in identity, subscription records and credentialsPending: active-account period; post-closure period; credential removal process.
Payments, refunds, and cryptocurrency records, including analytics copiesPending: applicable accounting/tax period and billing-dispute requirements.
Account-linked traffic snapshotsPending: fixed period; aggregation or deletion method.
IP-bearing request logs, errors, and monitoring tracesPending: per-system period, including hosting/proxy logs.
Expired session, confirmation, and purchase-link recordsPending: database cleanup period.
Support messagesPending: period after resolution.
Backups and failed-analytics retry filesPending: backup rotation period; retry-file cleanup and failure limits.

Session validity is currently one hour, email-confirmation links are valid for 24 hours, and purchase-handoff links for 30 minutes and one use. These are access-validity periods, not deletion deadlines. Expiry or revocation does not automatically erase database records. Public blockchain records remain outside our control.

8. Security and international processing

We use measures designed to limit unauthorized access, including signed Telegram login verification, expiring sessions, hashed session/confirmation/purchase-handoff tokens, and scoped operator access. VPN configuration credentials and subscription-link tokens must remain available to supply connectivity and are stored in service records. These measures do not eliminate all security risk.

We are registered in Georgia and serve users in Russia and the European Union, among other markets. Depending on the plan and infrastructure in use, your information may be processed in Georgia, the European Union, Russia (VPN entry nodes, see section 3), and other countries where our hosting and node providers (DigitalOcean, Hetzner, Selectel) operate. Confirmation from qualified counsel of the specific transfer safeguards required for EU- and Russia-based users given this cross-border setup is still pending - a provider's support in our code does not by itself establish a lawful international-transfer arrangement.

9. Your choices and rights

You can view subscription status and payment history, manage subscription links, and submit a confirmed email change through the account interface. Contact [email protected] to request account closure or exercise privacy rights; there is currently no self-service account-deletion interface.

Depending on applicable law, you may have rights to access, correct, erase, or obtain a portable copy of your information; restrict or object to processing; withdraw consent; and complain to a competent supervisory authority. Identifying the relevant authority/authorities for Georgia, EU, and Russian users and any required local rights or appeal procedure is still pending.

We may need proportionate verification of your identity before acting on a request. Erasure rights may be subject to legal recordkeeping or other lawful exceptions. Where records must be retained, we will explain the applicable reason. We cannot delete public blockchain data or independently controlled records held by third-party platforms.

10. Children, changes, and contact

The Service is intended for people who are at least 18 years old.

We may update this Policy when practices or requirements change. We will post a notice on our website and email registered users at least 30 days before a material change takes effect, except where a shorter period is required by law or an urgent security need. Where required, we will obtain consent before starting new processing.

Contact [email protected] about this Policy or a privacy request.