Privacy Policy

Last updated: October 13, 2026

This Privacy Policy explains what information Silent VPN ("we", "us", the "Service") collects when you use the Silent VPN application ("the App") or buy/manage a subscription through @remsysvpn_bot on Telegram ("the Bot"), why we collect it, and the choices you have. We built both around collecting as little as possible — if something isn't listed below, we don't collect it.

1. Who we are

Silent VPN is operated by:

Dmytro Trofimchuk, an individual developer
Contact: support@rem-sys.com

2. Data we collect

A full itemized breakdown lives on the Data We Collect page — this section summarizes it in policy language.

2.1 Data you don't have to give us

The App does not require an account. You are not asked for your name, email address, phone number, or any other directly identifying information to install, open, or use the free tier of the App. On first launch, the App generates a random anonymous subscriber ID (shown in Settings) used only to associate a subscription with your device/purchase.

2.2 Data required to process an in-app purchase

If you buy or start a trial of a paid plan through Google Play Billing, our backend receives:

• The Google Play purchase token and product ID, used to verify your purchase with Google's servers.
• A backend-generated anonymous subscriber ID, mapped internally to your VPN account so a purchase (or its renewal, or a restore on a new device/platform) is credited correctly.

We do not receive your name, card number, billing address, or any other payment details — those are handled entirely by Google Play Billing under Google's own privacy policy. We only ever see that a valid purchase was made.

2.3 Data processed if you buy through the Telegram bot

If you use @remsysvpn_bot instead of the app, Telegram automatically shares your Telegram user ID (and, if your Telegram privacy settings allow it, your username/first name) with any bot you message — this is how Telegram bots work in general, not something we request beyond what the platform already provides. We use it only to:

• Credit a purchase or balance top-up to the right account and deliver your connection link.
• Track your bot-side balance, if you choose to use the top-up/auto-renew feature.

Card payments through the bot are handled by our payment processor — we do not receive or store your full card number. Crypto payments are verified against the transaction recorded on the relevant public blockchain; we store only what's needed to confirm the payment and credit your balance (e.g. a transaction reference and amount), not a real-world identity — a blockchain transaction is pseudonymous, not anonymous, and its public ledger is outside our control.

2.4 Data necessary to operate the VPN connection

To establish and maintain a VPN tunnel and enforce your plan's data/time limits, our VPN infrastructure processes:

• Connection timestamps and total bytes transferred per session — used only for enforcing subscription limits, not stored longer than needed for that purpose.
• The IP address your device connects from, transiently, as is technically required to route any network connection — not retained in a persistent per-user log tied to your browsing.

We do not log the websites you visit, the content of your traffic, or your DNS queries. See Security & Encryption for a plain-language explanation of why: your traffic is end-to-end encrypted between your device and the exit server, so its contents are not something we have access to even if we wanted to log them.

2.5 Technical/diagnostic data

The App does not bundle third-party analytics, advertising, or crash-reporting SDKs. Standard operating-system-level logs (e.g. Android's own crash logs, if you choose to share them with Google) are outside our control and governed by the OS vendor's own policy, not ours.

3. Why we process this data

4. Who we share data with

• Google Play Billing — processes in-app payments; see Google's Privacy Policy for how they handle payment data.
• Our payment processor — processes card payments made through the Telegram bot; we never receive your full card number.
• Public blockchain networks — a crypto payment is recorded on its own public ledger, outside our control, by the nature of how blockchains work.
• Telegram — the messaging platform the bot runs on; your interactions with the bot are also subject to Telegram's own Privacy Policy.
• Our VPN panel infrastructure — the backend system that provisions your VPN credentials operates under our control and this policy; it is not a separate third party we hand your data to.

We do not sell personal data, and we do not share it with advertisers.

5. Data retention

Subscriber/purchase-token and bot-account records are kept for as long as needed to service an active or renewable subscription (including resolving restores on a new device or platform), plus a limited period after cancellation for support and legal/accounting purposes. Connection metadata used for quota enforcement is retained only as long as operationally necessary, not indefinitely.

6. Your choices

• You can stop using the App or the Bot at any time — no account to delete on the app side, because none was created.
• You can request deletion of your subscriber/purchase/bot-account record by contacting support@rem-sys.com — note that this may end your ability to restore an active subscription.
• Camera access (used only for scanning a subscription QR code) is optional and only requested when you choose to scan a code — it is never used to capture or store photos/video.

7. Changes to this policy

If this policy changes materially, we'll update the "Last updated" date above and, for significant changes, note it in the app's release notes or the bot's own announcement.

8. Contact

Questions about this policy: support@rem-sys.com or Telegram support.