Glim / Legal
Privacy Policy
What Glim processes, why it is needed, and the choices and rights you have over your information.
At a glance
- VPN browsing activity is different from operational data. We do not keep a history of the websites you browse or the content of your communications.
- Account and service data are processed. This includes sign-in information, payments, device sessions, and connection-quality and usage metrics.
- App analytics are disclosed. Supported clients use Google Firebase Analytics and Glim’s own product-event reporting; this data may be linked to your account.
This summary is a guide. Please read the full document below.
1. Who we are & what this covers
NetAI LTD., Intershore Chambers, Road Town, Tortola, British Virgin Islands, is responsible for the personal information described in this policy. Contact support@glim.cc for privacy questions or requests.
This policy covers Glim websites, supported apps, account services, payments, referral features, and communications with us, including our Telegram services when you use them. App stores, payment providers, sign-in providers, and Telegram also process information under their own policies.
2. VPN activity & routing
We do not retain a browsing history, the contents of your communications, or a log of the individual DNS queries and destination addresses you visit through the VPN. Network addresses and routing information must nevertheless be processed to establish connections and deliver traffic.
This is not a promise that all connection-related data is absent or anonymous. Account sign-in IP addresses and times, device sessions, node identifiers, time-bucketed traffic totals, and connection-quality statistics can be recorded and linked to your account, as explained below. Counts of DNS requests are operational metrics, not the text of the queries.
In Fast Mode or other selective-routing configurations, some traffic goes directly to its destination rather than through Glim’s VPN tunnel. Your internet provider and destination service may process that traffic under their own policies. Signing into a website still identifies you to that website.
Orbits and routing preferences describe the services and regions you choose. When saved to your account, those preferences are used for cross-device consistency; a saved preference is not a record of a visit. The website and apps provide the controls available for your platform.
3. Information we process
Account & sign-in
We process your email address, account identifier, authentication information, language, and subscription status to create and secure your account. Apple or Google sign-in supplies provider identifiers and the profile information authorized for sign-in. Account and device records can include a device identifier, operating system, app version, user agent, login and logout times, sign-in IP address, and an approximate location or time zone inferred from that address.
Payments & subscriptions
We process order references, payment-provider identifiers, amounts, currency, purchase and renewal dates, payment status, and refund or dispute records. Website checkout is available through providers including Stripe and regional payment providers such as Platega where offered. Apple and Google process in-app purchases. Payment credentials are handled by the payment provider; do not send us full card numbers or security codes in support messages.
Service operation & quality
We process traffic totals, upload and download volumes, DNS request counts, node identifiers, network type, approximate country, connection success and failure counts, latency, and connection-duration or throughput statistics. These records can include account or session identifiers and reporting times. They help display usage, diagnose failures, maintain network capacity, and prevent misuse; they should not be described as entirely anonymous statistics.
Product analytics
Supported app versions use Google Firebase Analytics and our own event reporting to understand app use, onboarding, connection outcomes, and purchases. Events can include app and device information, app-instance identifiers, event times and parameters, and a Glim account identifier when signed in. Availability and data fields differ by platform and version. See Firebase’s privacy information for the provider’s practices.
Preferences, referrals & Telegram
We process saved routing choices and regions to provide account features. If you use referrals or rewards, we record the referral association, qualifying events, and reward status. The inviter may see the limited referral and reward status needed to track the offer; this does not give them your VPN browsing history or payment credentials.
If you use Telegram sign-in, our bot, or our Mini App, we process the Telegram identifier and profile or language information supplied through that interaction, account-linking information, and messages you send us.
Support
We process your messages, contact details, and files you choose to send so we can respond. Diagnostic files may contain personal information. Remove unrelated sensitive data before sending them.
4. Why we process information
- Providing the service: account access, VPN authorization, device allowance, saved preferences, billing, subscription management, and requested support. Where applicable, this processing is necessary to perform our contract with you.
- Security and reliability: detecting fraud, troubleshooting, measuring connection quality, and maintaining capacity. Where applicable, we rely on legitimate interests, balanced against your rights, or a legal obligation.
- Product analytics: understanding use and improving the service. Consent is required where applicable law requires it, including for non-essential device storage or access; otherwise a valid legal basis and appropriate safeguards are required.
- Legal obligations: accounting, tax, lawful requests, and records needed to establish or defend legal claims.
- Optional marketing: where offered, we use consent when required. You may unsubscribe without losing essential service communications.
Using Glim or agreeing to its terms is not consent to every form of analytics, marketing, or advertising. Where consent is required, it must be obtained separately and can be withdrawn. Contact us to exercise applicable objection or withdrawal rights.
6. Cookies & local storage
Our website uses browser storage to keep you signed in, remember your preferences, display cached information, and continue checkout. Cookies, localStorage, and sessionStorage are different ways to store information on your device. The entries below describe storage used by Glim's website; not every entry is created on every visit.
What we store and for how long
- Sign-in: localStorage holds your authentication token (
token). It is removed when you sign out on the website or the website detects an invalid session. Server-side session expiry does not, by itself, erase the stored value from your browser. - Language and appearance: localStorage holds your language and theme preferences (
localeandtheme). These preferences have no automatic expiry in our website code; they remain until replaced or cleared by you or your browser. - Display caches: localStorage holds the last successfully received website and plan information (
web_home_cache) and, when signed in, account information including your email address (user_info_cache). These caches help display information while fresh data is requested. They have no automatic expiry in our website code. New responses replace them; signing out or detecting an invalid session also clears the account cache. A refresh interval is not a deletion deadline. - Checkout continuity: sessionStorage can hold the email entered for guest checkout, your selected plan and payment method, and temporary markers used to resume a payment redirect (
checkout:guest-email,checkout:selection, and keys beginningcheckout:trusted-redirect-url:orcheckout:pending-redirect-attempt:). These support checkout and returning from sign-in or a payment provider. They last for the tab's page session, unless removed earlier by the checkout flow. Browsers that restore a session may also restore this storage.
Website measurement and other providers
We use Cloudflare Web Analytics to understand website visits and loading performance. Its browser beacon sends usage and performance measurements to Cloudflare. Cloudflare states that this service does not use cookies or localStorage to collect usage metrics or fingerprint individual visitors. This measurement is separate from the functional storage listed above and from app analytics. See Cloudflare's Web Analytics privacy information.
Cloudflare's security services may use cookies when a security check is needed. Payment and sign-in providers may also use their own cookies or similar technologies on their services when you use those features. Their purposes and retention periods depend on the service and its settings; see Cloudflare's cookie information and the notices presented by the provider you choose.
Your controls
You can remove Glim's cookies and other site data through your browser's site-data settings, or restrict storage through its privacy settings. To remove persistent website data, clear site data rather than only browsing history. Clearing Glim's site data may sign you out, reset preferences, remove cached information, or interrupt checkout. Third-party services may use separate domains, so clear their site data separately if needed. Clearing browser data does not delete your Glim account or cancel a subscription.
Where non-essential cookies or similar technologies require consent, they must not be enabled before that consent. Accepting our terms or continuing to browse is not that consent. Any consent-based use must offer a way to refuse and withdraw consent. Contact support@glim.cc with questions about website storage or your privacy choices.
7. How long information is kept
We retain information for the purpose for which it was collected, subject to legal requirements. Retention depends on the type of record and its purpose:
- Account and preferences: while needed to provide your account and until deletion can be completed, except for information that must be retained for a legal obligation or a specific unresolved issue.
- Payments: for the accounting, tax, fraud-prevention, and dispute periods applicable to the transaction.
- Device, security, operational, and analytics records: for the period needed to manage sessions, investigate issues, and measure service performance, followed by deletion or aggregation when identifiable records are no longer needed.
- Support records: for resolving your request and necessary follow-up or legal claims.
A 30-day usage chart is a display window, not a promise that every underlying record is deleted after 30 days. Where records remain in backups or must be retained by law, deletion may not be immediate. Retained information is subject to continued protection and purpose limits. You can ask us about the retention applicable to your information.
8. International processing & security
Glim and its providers may process information outside your country, including in the British Virgin Islands and countries where our infrastructure, analytics, and payment providers operate. Privacy laws may differ between those countries.
Where a transfer is subject to EU or UK data-protection law, an applicable transfer mechanism and any necessary supplementary safeguards are required, such as an adequacy decision or appropriate contractual safeguards. Contact us for information about the destinations and safeguards applicable to your data. This policy does not itself constitute a transfer agreement or your consent to a restricted transfer.
We use technical and organizational safeguards appropriate to the information and risks, including encrypted communications and access controls. No service can guarantee absolute security. Notify us promptly if you suspect unauthorized access to your account.
9. Your choices & rights
Depending on the laws that apply, you may have rights to access, correct, delete, or receive a portable copy of your information; restrict or object to processing; withdraw consent; and complain to your local data-protection authority. Withdrawal does not affect processing that was lawful before it. California residents may also have applicable rights to know, correct, delete, and opt out of sale or sharing for cross-context behavioral advertising, and to exercise rights without unlawful discrimination.
Email support@glim.cc from your account address, or use the available account-deletion control. We may request proportionate verification of your identity or an authorized agent’s authority. We respond within the period required by applicable law—generally one month for EU/UK requests, with any permitted extension explained to you. If a request is refused or limited, we will explain why and any available complaint or appeal route.
You can edit supported preferences, sign out of devices, and request account deletion. Deletion may end access to your account, but does not itself cancel an Apple or Google subscription. See subscription cancellation instructions to avoid further charges.
10. Children’s privacy
Glim is not intended for children under 16. Users aged 16 or older who cannot enter a contract under local law need a parent or guardian’s agreement as set out in the Terms of Service. We do not knowingly collect personal information from children under 16. If you believe a child has provided information, contact us so we can investigate and take appropriate steps, including deletion where required.
11. Policy updates & contact
We will update this policy when our practices change. Material changes will be communicated before they take effect through an appropriate notice, and we will request fresh consent if required. A policy update does not retroactively authorize a new use of your information.
Privacy requests: support@glim.cc
Legal correspondence: legal@glim.cc
Intershore Chambers, Road Town, Tortola
British Virgin Islands