Privacy Policy

Below is what VPN for India collects while you use the service, the reason and legal basis for each item, and how long we hold it. Our company is registered in Poland, so the policy is laid out the way the EU General Data Protection Regulation asks.

1. Your traffic stays unrecorded

Your traffic is not logged: neither its content nor where it goes. Session start and end times are not kept either, nor are DNS queries, the sites and apps you open, or your source IP address matched to a time. A breach could not leak a browsing history from us, and nobody could buy or demand one, because it does not exist.

2. Records about you, and the lawful ground for each

• Your Telegram user id. Without it the bot has nowhere to send the key and support has no one to answer (GDPR Art. 6(1)(b), performance of a contract).
• When your plan ends, and the identifier of your key: the server checks both before it lets a connection through (performance of a contract).
• A total of traffic per key, which shows abuse such as spam relaying (GDPR Art. 6(1)(f), our legitimate interest in a network people can use).
• Amount, date and plan from the payment provider's confirmation, because accounting law requires proof of each transaction (GDPR Art. 6(1)(c), legal obligation).
• Messages you send to support, kept only so the conversation can continue (legitimate interest).

3. Retention periods

• No later than 30 days after a plan ends, its key identifier and expiry date are deleted.
• Traffic totals are reset every month and not archived.
• Five years for payment records, which is what Polish accounting law demands at the moment.
• Twelve months after your last message to support, the chat is erased, if not sooner.

4. Who else can see something

• Telegram. Chats with the bot run over its platform, so its rules on personal data apply to them as well.
• Whichever service takes your UPI or crypto payment; it sees the details that payment rules require for the transaction.
• The data centres that rent us the hardware. They can measure how much traffic flows, but cannot look inside it.

Personal data is never sold, and advertisers get none of it. Authorities with a lawful request would get no more than the key's existence and its end date.

5. Where the data is kept

Data sits on servers outside India. Should any of it leave the European Economic Area, standard contractual clauses approved by the European Commission cover the transfer. Having no servers in India also puts us beyond the 2022 CERT-In directive, which makes providers with infrastructure there store customer records for five years and supply them on request.

6. How we protect it

• TLS 1.3 encrypts traffic.
• Servers accept logins with keys only, not passwords.
• Only the people who run support can open key records.

7. Your rights

• Get a copy of every record tied to your key (right of access).
• Have the records erased, apart from payment records that accounting rules oblige us to keep (right to erasure).
• Have anything inaccurate fixed (right to rectification).
• Take your data with you in a machine-readable file (right to data portability).
• Say no to any use of your data that rests on our legitimate interest (right to object).
• Bring a complaint to the data protection authority in your country; in Poland, that is the UODO.

Send any of these requests to [email protected] and you will get an answer within 30 days. Since there are no accounts, that answer is usually brief.

8. Cookies and tracking

The site sets only the cookies it needs to work, for example the one that remembers whether you chose the light or dark theme. Nothing on it follows you around: no ad trackers, no cross-site pixels, no analytics profiles run by third parties. You see no consent banner because there is no tracking to consent to.

9. Children

Tell us if a child under 16 has used the service, and we will delete the record tied to it. Users must be 16 or over, and we do not knowingly collect children's data.

10. Who is responsible for your data

Privacy questions: [email protected]. Anything else: [email protected] or the Telegram bot. The controller responsible for your data is VPN for India, ul. Wielicka 28, 30-552 Kraków, Poland.

11. Changes to this policy

When something important in this policy changes, the date at the top changes too, and we post a notice in our Telegram channel. If you keep using the service after that, you accept the new version.