Document
Privacy Policy
Effective date: November 18, 2026
This Privacy Policy explains what personal data IcegateVPN LLC (“IcegateVPN,” “we,” “us,” or “our”) collects when you use our VPN service, apps, website, Telegram bot, or support channels. It also explains why we use that data, how long we keep certain records, and when we share information with others. Your privacy is our top priority.
1. Core Principles and Contact Information
IcegateVPN LLC operates the service. You can contact us about this policy, your personal data, or a request to withdraw consent at the address below.
2. No Logs Policy
We adhere to a strict no-logs policy to ensure your anonymity. Our VPN servers do not log your activity inside the VPN tunnel. We do not keep records of:
- Your real IP address in connection with your VPN traffic
- The IP addresses of websites or other servers you reach through the VPN
- Your DNS queries
- Your browsing history, traffic, or use of other applications through the VPN
- How long you stay connected to the VPN
To provide a working VPN key, we keep a record of which VPN server the key is for and when we issued it. For a signed-in device, we keep only its current key until you connect again, sign out, or your access ends. In our free apps, each key is valid for one hour. We keep the key and its associated device identifier for up to two weeks from the date of issue.
While the VPN is on, our apps resolve domain names through public DNS resolvers such as Google Public DNS and Cloudflare. Lookups for sites reached through the VPN normally originate from our VPN server, so the resolver sees that server’s IP address. For sites routed outside the VPN, such as certain local services in your country, lookups originate from your device. If you add your own server to our Shadowsocks app, lookups go through that server. IcegateVPN does not log these DNS queries.
Our website, apps, and account services also make requests outside the VPN tunnel, for example when you sign in or download a subscription link. Sections 3 and 5 explain what information we and our providers receive when handling those requests.
3. Data Collection and Usage
Email address and account access
Your account has a 16-digit User ID. You may add an email address to sign in and receive login or verification codes. Providing an account email is optional.
If you pay by card, Stripe’s payment form asks for an email address, which may differ from your account email. Stripe uses it to send receipts and offer its Link service. If your account has no confirmed email address, we save the checkout address at Stripe as your billing email. We will not send you marketing emails without your explicit consent.
Subscription information
We keep your subscription status, expiration date, and history of subscription changes, referrals, and rewards. We use these records to manage your access to the service. They do not show which websites you visit or what you do through the VPN.
Account and device data
When you sign in from an app, our servers store the device type, operating system version, device model, device identifier, push-notification token, Adjust identifier, and the VPN country you choose. On Android, the device identifier may be the Android ID or a Firebase installation identifier. Our apps also send us the country they determine from your IP address so that we can provide the appropriate routing rules.
We use this information to sign you in, send notifications, issue VPN keys, attribute purchases, and select routing rules.
Payment information
The providers listed in section 5 process payments. We do not store your card number or other sensitive payment details. We receive and keep a notice of each payment, including the amount, currency, status, and transaction identifiers. Depending on the provider, the notice may also contain the email address supplied at checkout, the card type and last four digits, your App Store country, or the transaction hash of a cryptocurrency payment.
Where needed, we also receive a token for subscription renewals or a card fingerprint used to prevent the same card from being used repeatedly for free trials.
App Store refund requests
By accepting this Privacy Policy, you authorize IcegateVPN to share the information described in this paragraph with Apple if you request a refund for an IcegateVPN subscription purchased through the App Store. If Apple asks us to help review your request, we may tell Apple whether we provided access to the subscription, how long your IcegateVPN account has existed, whether it received a free trial, and whether we recommend granting the refund. You may withdraw this authorization at any time by emailing [email protected]. Once you withdraw it, we will stop sharing this information with Apple for refund reviews.
Purchase analytics
When a payment, free trial, or renewal goes through, we record the event, its amount and currency where applicable, and the transaction or subscription identifier. If you have used our app, we send Adjust the event type, amount, and currency together with your Adjust identifier. We use this information to understand which campaigns lead to subscriptions.
Our apps
We use Adjust to attribute app installations to the advertising campaign or link that led to them. We use Google Firebase to deliver notifications and, in our free apps, to check that requests come from a genuine copy of the app. Our Android apps also use Google Analytics for Firebase.
These services receive technical information such as the device model, operating system, language, app version, IP address, and an app installation or device identifier. Adjust also receives events such as account creation, sign-in, opening the subscription screen, and restoring a purchase. In the free apps, it also receives ad impressions and taps.
In our Android apps, Google Analytics for Firebase receives information about screens opened, app sessions, and Google Play purchases. In the free Android app, it also receives information about each ad shown, including the ad network and revenue.
Our apps do not use Apple’s Identifier for Advertisers (IDFA). The identifiers used for advertising and campaign attribution are the identifiers provided by CAS.ai and Adjust and, on Android, your device’s Google Advertising ID (GAID). Adjust, Google Analytics for Firebase, and CAS.ai and its ad networks may receive the GAID unless you delete it in your device settings (Android 12 or later); if you reset it, they receive the new one. The account, device, and Firebase installation identifiers used for app functions are described above.
Advertising in free apps
Our free apps show ads provided by CAS.ai and the ad networks it works with. These may include Google AdMob, Meta Audience Network, AppLovin, Pangle, Liftoff, ironSource, Mintegral, and Unity Ads. CAS.ai manages its network list, which may change over time.
CAS.ai uses its own identifier and, on Android, the GAID to help select, deliver, and measure ads. CAS.ai and participating networks receive technical information about your device and the app, your IP address, and information about ad impressions and interactions. An ad may appear when you tap Connect, so our advertising and analytics partners may learn when that ad was shown. Where required by law, the app asks for your consent to personalized advertising. Our paid apps do not show ads.
Our website
If you visit our website through an advertisement, we use the click identifier in the incoming link to attribute an app installation to that ad. During your visit, the page holds the identifier in memory and adds it to app download links. We do not save it in cookies or persistent browser storage.
Google reCAPTCHA helps protect registration, sign-in, payments, and account changes against abuse. Stripe checks card payments for fraud. Our Cookie Policy explains how these services are used on the website.
Server logs
When our website or an app sends a request to the IcegateVPN backend API, our servers log the client’s IP address, the time of the request, the requested address, and the response status code. This includes requests from VPN apps to download subscription links. We use these logs for security and troubleshooting and retain them for up to one month from the date of each request. For the specific purpose of limiting abusive sign-up attempts, we also keep the IP address used for an attempt for one hour. The API logs do not contain the websites you visit or the traffic you send through the VPN tunnel.
Telegram bot
If you use our Telegram bot, we receive your Telegram user ID and language. We record the link you used to start the bot, when you last started it, the device you tell us you use, and whether you have turned off reminders. We use start links to measure our campaigns.
The bot sends reminders and occasional offers until you send /stop. You may still receive messages about payments and the end of your subscription.
Support communications
When you contact support by email or Telegram, we receive your messages, any attachments you send, and the contact details visible through that channel, such as your email address or Telegram username. We use this information to answer your request and improve our support.
We retain support conversations for up to 12 months and then delete them. We may keep excerpts for longer after removing personal data to review the quality of our support. We do not link support conversations to your activity inside the VPN tunnel.
If you choose to send us an app log file, we also receive the technical information in that file. This may include your device model, operating system, local IP address, and the VPN servers you connected to and when.
4. Cookies Policy
Our website keeps a sign-in token in your browser’s local storage, not in a cookie, to authenticate you and maintain your signed-in session. Google reCAPTCHA and Stripe help protect your account and payments against unauthorized access and fraudulent requests. They may set cookies when their security or payment features are used. We load Stripe’s payment software when you choose to pay by card. The website also remembers the language you select.
We do not use advertising or analytics cookies on the website. For details, see our Cookie Policy.
5. Data Sharing with Third Parties
We do not sell your personal data. We share it only with the following services, and only for the purposes described in this policy. Each of them handles the data under its own privacy policy.
Payment providers
Apple (App Store), Google (Google Play), Stripe, Telegram (Telegram Stars), 1Payment, NOWPayments, and YooKassa process payments. YooKassa handles card subscriptions through our Telegram bot. Each provider receives the information needed to process the payment or renew the subscription.
To link a payment to your account, Stripe, 1Payment, and YooKassa receive your User ID or a random account identifier. Apple and Google receive a random account token. If you request an App Store refund, we may also share the information described under App Store refund requests in section 3 with Apple.
Analytics and attribution
Adjust provides campaign attribution and purchase analytics. Google Analytics for Firebase provides app analytics on Android. Section 3 describes the identifiers and events these services receive.
Advertising in free apps
CAS.ai and its participating ad networks deliver and measure advertising in our free apps. Section 3 describes the data used for these purposes.
Security
Google reCAPTCHA helps protect our website against abuse. Stripe helps detect fraudulent card payments. Our free apps use Google Firebase App Check to confirm that requests come from a genuine app. Firebase App Check uses Apple App Attest on iOS and Google Play Integrity on Android.
Email and notifications
Postmark delivers login and verification emails and receives the email address and code needed to deliver them. It also delivers internal alerts, which may include your User ID. Apple Push Notification service and Google Firebase Cloud Messaging deliver app notifications.
Infrastructure
Cloudflare handles traffic to our website and API. Google Cloud, through Firebase, hosts a mirror of our website. The mirror serves subscription links for third-party VPN apps and provides access to the website in places where the main site is blocked. When a request passes through the mirror, Google receives your IP address, the requested address, and our response. For a subscription link, the address includes the secret part of the link, and the response contains your VPN settings.
Our apps use your IP address to determine your country and choose routing rules for local sites. They request this information from Cloudflare and may use country.is, ipwho.is, or GeoJS if Cloudflare does not respond. If none of these services responds on Android, the app may use the country of your mobile network.
Our apps may also send encrypted requests to IcegateVPN through public DNS-over-HTTPS resolvers operated by Cloudflare, Google, NextDNS, Control D, AdGuard, or DNS4EU. The resolver sees your IP address but cannot read the encrypted request.
Telegram
Telegram delivers messages exchanged with our bot and support team. Depending on how you use the bot, those messages may contain your User ID, subscription details, sign-in keys, subscription links, or links to payment pages.
AI processing of support requests
We use AI models provided by a third-party language model provider to help answer support questions and review past requests to improve support. The provider processes message text and any photos, screenshots, images, or video frames included in the request.
Before sending text to the provider, we remove or mask passwords, User IDs, email addresses, payment details, access keys, and subscription links. Images and videos are sent as provided, so please avoid including passwords, payment card details, or other sensitive information in them.
Our assistant does not repeat User IDs, email addresses, or payment details in its replies. Where necessary, it passes those details to our support staff so they can locate your account. The provider does not use this data to train its models. A human operator handles requests the assistant cannot resolve.
We do not share a record of the websites you visit or the traffic you send through the VPN. Section 2 explains how public DNS resolvers handle domain lookups.
6. Changes to This Privacy Policy
We may update this Privacy Policy from time to time. Each version applies from the effective date shown at the top of the page. If we make a material change to how we handle your personal data, we will notify you in advance through the app or another channel reasonably likely to reach you. Where a change requires your consent, we will ask for it before using your data in the new way.
