Privacy Policy
Last updated: 2026-08-25
Svoboda Digital processes the minimum data required to deliver digital access, handle payments, provide support, and protect the service from abuse.
1. Data we process
Telegram IDs and interface language when you use the Telegram bot; technical access-delivery and recovery events; hashes of recovery credentials; public keys of added devices and public key fingerprints (cryptographic hashes of those keys used to bind credentials); payment statuses and provider identifiers; support messages; subscription status; issued-node status; and aggregated technical service counters. The app derives an irreversible SHA-256 proof from the personal-link token on the device to open one-time account access: the link and token are not sent to the server, and the proof is not stored. For aggregate measurement of the public website, we process the page path without its query string, referring hostname, approximate country, device type, browser, operating system, and loading performance. With separate consent, Google Analytics also receives a sanitized page URL, the referring source without its query string, approved UTM parameters, an approximate region, and clicks on payment and app-download buttons.
2. Purpose
Access delivery and renewal, refund handling, abuse prevention, support replies, node availability monitoring, capacity planning, and evaluation of advertising sources.
3. Legal basis
Performance of contract and legitimate interests in fraud prevention, operational security, and data-minimized measurement of the public website. Google Analytics is enabled only on the basis of separate consent.
4. VPN connections
Svoboda does not collect or store browsing history, DNS queries, destination hostnames or URLs, traffic content, or payloads from VPN connections. Network addresses and connection identifiers are processed only as needed to establish, secure, and route the requested connection; they are not retained as per-user browsing records. Raw runtime identifiers used to calculate service health are processed in memory. Durable usage measurement consists only of anonymous aggregate technical counters.
Svoboda processes the minimum connection data only in real time to operate the VPN connection requested by the user. Except for this real-time processing, Rhizomedia does not use VPN activity data for any purpose and does not sell or disclose it to third parties for any purpose. Contracted hosting and network providers process transient connection data solely on Rhizomedia's behalf to operate Rhizomedia-controlled service components; they are not provided retained VPN activity records. We do not store VPN traffic content or browsing history on that infrastructure, and the app contains no advertising, tracking, or third-party analytics SDKs.
5. Retention
Web access logs, where enabled, omit raw IP addresses and requested URLs and are configured for deletion within 14 days. VPN service journals are configured with a maximum retention of 14 days. Analytics cookies expire within 180 days and are not automatically extended. Account, payment, and support records are retained only as long as needed for service delivery, refunds, abuse prevention, and legal obligations.
6. Payment providers
Card and PayPal payments may be processed by Stripe; other payments may use Telegram Stars or direct TON and USDT on TON. We store technical payment statuses and identifiers, but we do not store full card or PayPal credentials or keep wallet private keys on the server.
7. Website analytics and cookies
Public pages use cookie-free Cloudflare Web Analytics. Cloudflare does not collect query strings or UTM parameters, discards the source IP address after deriving an aggregate country, and exposes only aggregate page path, referring hostname, country, device type, browser, operating system, and loading-performance data to us. This beacon is not enabled on personal subscription, payment, rescue-access, gift, administration, authentication, speed-test, or warrant-canary pages.
Google Analytics is not loaded until you select “Allow analytics.” After consent, it receives a sanitized page URL, the referrer without its query string, approved UTM parameters and click identifiers from supported advertising campaigns, the site language, and events for opening the bot or downloading a client. Google uses raw IP addresses only to derive an approximate region and does not expose them to us. Automatic collection of forms, search, video, and arbitrary clicks is disabled. Analytics is not enabled on personal subscription, payment, rescue-access, gift, administration, authentication, speed-test, or warrant-canary pages. Your consent choice is stored locally in the browser and can be changed through “Cookie settings” at the bottom of the page.
If a public-page URL contains a valid campaign UTM parameter, the site keeps only its validated key for the current tab and adds that key to Telegram bot links. This lets us connect an acquisition source to access issuance and payment in aggregate without sending Telegram IDs, payment data, or personal access links to Google. Arbitrary URL parameters, referrers, and advertising click IDs are not forwarded to Telegram. This functional campaign key operates independently of Google Analytics consent.
8. Rights
You may request access or correction by contacting support@svoboda.digital. The steps, scope, and retention rules for deletion requests are described on our data deletion page.