Privacy Policy

1. The short version

We collect the minimum an account and a tunnel need: your email address, the password hash behind it, your plan, and — while you are connected — the node you are on, how many bytes moved, and for how long.

We do not collect the sites you visit, the pages you open, the searches you run, the DNS names your browser asks about, or anything you type into a website. That is not a promise about marketing; it is a property of the software: the tunnel carries encrypted traffic and we never hold the keys to read it.

Everything below is the long version of the same three things: what, why, and who.

2. Who we are

DI VPN ("we", "us") operates the network at divpn.com and issues the DI VPN Chrome extension and mobile apps. We are the data controller for the personal information described here.

For any question about this policy, or to exercise a right in it, write to support@divpn.com. We answer from the same address.

3. What we collect

3.1 When you visit the website

Our servers receive the information any web server needs to answer a request: your IP address, the time of the request, the page or file asked for, the referring page, your browser and operating system, and the response status. This is used to serve the page, to rate-limit abuse, and to keep the service up.

To show you the map, we also resolve your IP address to an approximate country, region, city, time zone, network operator and autonomous system. The answer is accurate to the city, never to a street, and it is cached for six hours and then discarded.

What we show you is your real location, and we do not invent one. The extension page and the map show the country and city that resolve from your own request. We do not substitute a random or simulated country to make you harder to identify, and we do not display simulated traffic, session times or protection results. Where a figure is not a real measurement — for example the counters in the preview of the extension popup on this website, where no tunnel is opened — the page shows it as empty rather than filling it with invented numbers. Anything on this site that is a demonstration is labelled as one.

3.2 When you create an account

• Email address — the identifier for the account, and the address for password recovery and service messages.
• Password — stored only as a one-way hash. We cannot read it, and we cannot send it to you.
• Name and username — only if you type one. A name is optional.
• Preferred language — so the site and the extension answer in your language.
• Sign-in method — "email" or "google", depending on how you registered.
• Plan and trial dates — what you are on, and when a trial or subscription ends.
• Last seen and device count — to enforce the device limit on a plan.
• Device identifier — on Android we use the Android ID; on iOS we use the identifier-for-vendor supplied by the operating system. It is used to recognise a registered installation, enforce device limits and associate push-notification registrations.
• Password reset token and its expiry — temporary, deleted after use.

If you choose Google sign-in in the Android app, Google Sign-In returns an authentication ID token. Our server validates the token and its verified-email claim, then uses the verified email address to find or create your DI VPN account. The available display name may be used as your account name if you have not set one. The app requests the email scope and does not request access to Gmail messages, Drive files, Google Contacts or calendars. The specific Google account data handling is described in section 3.9 below.

3.3 When you use the extension or an app

While a tunnel is connected, we record the connection, not the browsing:

• the node you connected to (identifier, city, country),
• the device label the browser gives us,
• bytes uploaded and downloaded,
• the time the connection started and ended,
• the exit IP observed from outside, to confirm the tunnel actually works.

No hostname, no URL, no page title, no DNS query and no payload is stored. The counters are the same numbers your browser already shows you.

3.4 The breach scanner

When you run a scan, the address you type is sent to our breach-data provider and the result is shown to you. Two different things happen depending on where you run it:

• Scan from the website or the extension popup — the address is not written to any of our tables. The result is cached in memory for an hour so the same scan is not repeated, and a per-account daily counter records how many scans you have used.
• Breach tools inside your account area — the address and the time are saved to your own scan history so you can see it later, and you can delete the record.

We do not sell, share or enrich addresses with anyone.

3.5 Payments

Card details never reach DI VPN. Purchases made inside the Android app are processed through Google Play Billing; website purchases are handled by the payment provider shown at checkout. We receive the transaction or order reference, product or plan, amount and payment status needed to grant and reconcile the purchase. The relevant store or payment provider processes the payment details under its own privacy terms.

3.6 Push notifications

After sign-in, the Android app obtains a Firebase Cloud Messaging (FCM) registration token for the installation and sends it with the account and device identifier so service messages and reminders can be routed to that device. Google processes the token and message-delivery data as the FCM provider. A refreshed FCM token replaces the previous token for that registered device. Whether a notification is displayed is controlled by the operating system's notification permission; turning that permission off does not necessarily erase the server-side token registration by itself.

3.7 Mobile advertising

The Android app integrates the Google Mobile Ads SDK. When advertising features are enabled, Google and its advertising partners may process data needed to serve, limit, measure and protect ads. Depending on the device and the ad request, this can include an advertising or other device identifier, IP address (which may be used to estimate general location), app and ad interactions, and diagnostic or performance information. The SDK's processing is governed by Google's policies and the choices available through the app's advertising consent and privacy options. Where consent is required, ads are requested only when the consent framework reports that they may be requested.

Advertising is separate from the VPN tunnel. We do not give advertising partners the websites you visit, destination URLs, DNS queries or the contents of VPN traffic, and we do not redirect other apps' traffic to monetise ads. The website does not use Google Mobile Ads to serve ads.

3.8 App Firewall and split-tunnelling list

If you open App Firewall or split-tunnelling settings, the Android app reads the installed-app list provided by Android. This can include app names, package identifiers and icons. The list is processed on your device so you can search for apps, open Android App Info, or choose apps for split tunnelling. The app does not upload this installed-app list to DI VPN servers as part of these features. Your selected split-tunnelling preferences are stored on the device.

3.9 Google account data — access, use, storage and sharing

This section explains the data returned by Google Sign-In and how DI VPN handles it. The Android app sends the Google authentication ID token to our DI VPN authentication backend over HTTPS. The backend verifies the token against the app's configured Google OAuth client and checks the verified-email claim before accepting the sign-in.

• Android app — verified email address and email-verification status: used to find an existing DI VPN account or create a new one, sign you in and mark the Google-verified email as verified.
• Android app — token subject claim: part of the signed identity token checked during verification. The mobile sign-in endpoint does not save this claim as a separate account profile field.
• Website Google sign-in — display name, when Google supplies one: the website may use it to fill an otherwise empty DI VPN account name. The Android app's unified sign-in endpoint does not import a Google display name; it creates a default account name from the email address.

Purpose and limits: Google account data is used to authenticate the user, associate a verified email address with the DI VPN account, and, for website sign-in only, fill a missing display name. The Android app requests the email scope; it does not request Gmail messages, Drive files, Google Contacts or calendar data. We do not use Google sign-in data to serve ads, personalise advertising, sell data, build browsing profiles or conduct surveillance. Google Mobile Ads processes advertising data separately as described in section 3.7; DI VPN does not send Google sign-in data to the advertising SDK for ad targeting.

Sharing and transfers: the Android sign-in token is sent to the DI VPN authentication backend for validation and is not sent to divsim.com. For Google sign-ins completed on the website, the resulting DI VPN account record (account ID, name, email address, password hash where one exists, and provider) is synchronised with divsim.com for the stated cross-service account functionality. The website sign-in token itself is not included in that synchronisation. Google processes the sign-in interaction under its own Google Account and privacy terms.

Storage and protection: DI VPN retains the account email address, sign-in provider and account name while the account exists. The Android Google ID token is used to verify the request, rather than retained as an account profile field. Sign-in requests are protected in transit with HTTPS/TLS; access to account records is limited to people who need it to operate and support the service.

Deletion: Google sign-in data held in the DI VPN account record is deleted or anonymised when the associated account deletion request is completed, subject to records that must be retained for legal, accounting, security or fraud prevention purposes. To request deletion, use the instructions in section 10 — Account deletion requests.

4. Why we collect it

Data	Purpose	Legal basis
Email address	Account, sign-in, password recovery, service messages, breach scan for your own address	Contract; legitimate interests
Password hash	Signing you in only	Contract
Plan, trial and order records	Giving you what you paid for	Contract
IP address and derived location	Signing in, showing the map, rate limiting, abuse prevention	Legitimate interests
Temporary connection metadata	Operating the tunnel, troubleshooting and enforcing usage limits; raw session details are automatically deleted after your selected retention window	Contract; legitimate interests
Device identifier	Recognising a registered installation, device limits and linking push registrations	Contract; legitimate interests
FCM registration token	Routing service notifications to the signed-in app installation; display depends on OS permission	Service functionality and device notification settings
Mobile advertising data	Ad delivery, frequency limits, measurement and fraud prevention through Google Mobile Ads	Ad consent where required; otherwise the basis applicable to the relevant request
Scanned address (account tools only)	Your own scan history	Consent
Infrastructure security records	Protecting service availability and investigating security incidents; not used to record VPN browsing destinations	Legitimate interests; legal obligation

5. What we never collect

• The websites you visit, the pages you open, or the links you follow.
• Search queries, or anything you type into another website.
• DNS names your device resolves.
• The contents of your traffic, in any form — it is encrypted between you and the node.
• We do not build a DI VPN profile of the websites or pages you visit, or use browser fingerprinting to profile your browsing. The Android app's Google Mobile Ads SDK may process advertising or device identifiers for ad delivery as explained in section 3.7; those identifiers are not used by DI VPN to record your VPN browsing activity.
• Passwords for anything other than your DI VPN account, ever.

6. Who else can see your data

We share information only with the parties that make the service work, and only to the extent needed:

• Payment providers — Google Play Billing for Android in-app purchases and the provider shown at website checkout, to process payment and confirm the transaction.
• Google Mobile Ads — the Android app's advertising SDK and its advertising partners, for ad delivery, frequency capping, measurement and fraud prevention, subject to the consent and privacy choices described above. Google explains its partner data use in its How Google uses data when you use our partners' sites or apps notice.
• Google sign-in and Firebase Authentication — the sign-in token is sent to our authentication backend for validation. We use the verified email to create or sign in to your DI VPN account, and the optional display name as described above. Firebase Cloud Messaging separately processes the app's push-notification token and message-delivery data.
• Breach-data provider (XposedOrNot) — the address you typed, for the lookup you asked for. A provider receives the address only when the relevant lookup is requested.
• Fallback geolocation provider (ipapi.co) — only if our local GeoLite2 database has no answer for your IP; only the IP address is sent.
• Content delivery network (Cloudflare) — in front of divpn.com, to deliver pages and absorb attacks. It processes connection data under its own policy.
• Push notification delivery (Google FCM) — to deliver a message to your device.
• Our related service (divsim.com) — a limited account record (DI VPN account identifier, name, email address, password hash where one exists, and sign-in provider) is mirrored for cross-service account continuity. Google sign-in tokens are not mirrored for this purpose.
• Authorities — if we are legally required to disclose something, we will tell you unless the law forbids it.

We do not sell personal information. The Android app's Google Mobile Ads SDK does disclose limited advertising and device data to Google and its advertising partners as described in section 3.7; consent and opt-out choices apply where required by law. This advertising data flow is separate from VPN traffic.

7. Cookies and similar technologies

The website uses the minimum set of cookies to work:

• Session cookie — keeps you signed in and protects forms against cross-site request forgery. Required.
• Language cookie — remembers which of our ten languages you read in.
• Extension token — stored by the extension, not as a cookie, and revocable from the extension.

We run no advertising or cross-site tracking cookies on the DI VPN website, and we do not build a website browsing profile for marketing. The Android app's Google Mobile Ads SDK is described separately in section 3.7; it is not a website cookie and is subject to the app's consent and privacy choices.

8. How long we keep it

• Account information — while the account exists. When you delete the account, account access and authentication tokens are revoked immediately and identifiable account data is deleted or anonymised as part of the deletion process, subject to the limited records listed below.
• Connection-level metadata — after a tunnel session ends, account-linked session details (such as its IP address, selected country/route, device/session identifiers, timestamps, bytes and duration) are automatically deleted after the retention period you select in Profile. The default is 30 minutes; you may choose a longer period up to 6 hours maximum. An active session record is kept only while it is needed to operate that active tunnel.
• Minimal usage counters — after the session-level record is deleted, a small daily aggregate may remain to enforce monthly traffic allowances and daily country limits. It contains totals/counters (and, where needed, a country code), not an IP address, device identifier, exact node, connection timestamp, visited website, DNS query or traffic content. Traffic counters remain only for the relevant usage-limit period.
• Order, invoice and payment records — for as long as tax, accounting or payment-dispute law requires. When an account is deleted, the account link and direct contact details are removed or anonymised where the record must be retained.
• Breach scan history — until you delete it or close the account.
• Derived location — the IP-to-location lookup cache is kept for up to six hours.
• Device identifiers and FCM tokens — while the installation remains registered to the account. Account deletion removes the associated device registrations and FCM tokens.
• Mobile advertising data — Google and its advertising partners determine their own retention under their published policies; DI VPN does not set the SDK partners' retention periods.
• Infrastructure security records — limited server/CDN security and diagnostic records may be retained under the applicable infrastructure configuration and provider policies. They are not VPN browsing-history logs, and the per-account connection-retention selector does not control third-party provider retention.

9. How we protect it

• Passwords are hashed; we never see or store the plain text.
• Traffic between you and a node is encrypted, and we do not hold keys that could read it.
• Data in transit uses TLS, and sensitive columns are stored hashed or encrypted.
• Access to personal data is limited to the people who need it to run the service.

No system is perfect. If a breach ever affects your data, we will notify you and the relevant authority as the law requires.

10. Your rights

Wherever you live, you can ask us to:

• Access — a copy of the personal data we hold about you.
• Correct — fix anything wrong, from the profile page or by mail.
• Delete — close the account and remove its data.
• Restrict or object — to processing you did not ask for.
• Portability — get your data in a machine-readable form.
• Withdraw consent — for anything that relies on consent, such as the breach history or push notifications.

For access, correction, restriction, objection, portability or consent-withdrawal requests, write to support@divpn.com from the address on the account. We aim to respond within 30 days, subject to any shorter or longer period required by applicable law.

If you are unhappy with the answer, you can complain to your local data protection authority.

11. International transfers

Our servers and our providers are in more than one country. Where personal information leaves your country, it is protected by the same policy and by standard contractual safeguards. You can ask which countries are involved by writing to us.

12. Children

DI VPN is not for anyone under 13, and we do not knowingly collect information from children. If you believe a child has given us personal data, write to us and we will delete it.

13. Security of the extension

The extension runs only in your browser. It reads the node list from our API, sets Chrome's own proxy setting, and keeps your settings on your device. It does not send us the content of any page, and it does not contain advertising code. The permissions it asks for are the ones the protection tools need — that is why you can read them on the store listing.

14. Changes to this policy

When this policy changes materially, we update the date at the top of this page and, for account holders, tell you by email or in the extension before the change takes effect. Continuing to use DI VPN after that means the new policy applies.

15. Contact

DI VPN — Privacy
Email: support@divpn.com
Website: https://divpn.com