Privacy & cookie policy
In plain language: what we collect, why, and how to opt out. This site is built to respect the DPDP Act principles — purpose-limited collection, easy withdrawal of consent, and no behavioural tracking of children.
We keep this deliberately tiny
PrepaidCards.in is a static informational site. We do not have accounts, we do not collect Aadhaar/PAN/KYC documents, and we do not host checkout. The only data we store is a single first-party preference cookie:
| Cookie | Purpose | Lifetime | Opt-out |
|---|---|---|---|
pc_consent | Remembers whether you accepted or declined the cookie notice, so we don't re-ask every visit. | 1 year | Clear it in your browser settings; we never re-ask once set. |
We do not use advertising cookies, analytics trackers, or third-party scripts. No Cloudflare Insights or any other tracking script is present on any page. Our visitor count is anonymous and does not identify you.
DPDP Act: full consent and notice obligations phase in through 2027. We have built the stack now — opt-in consent, plain-language notice, and easy withdrawal — so the site is ready ahead of the deadlines.
What we never do
- Collect Aadhaar, PAN or any KYC document "to show you cards".
- Host a checkout or load value — we are not a PPI issuer.
- Run behavioural ads targeting children or run teen-card pages with ad trackers.
- Sell or share personal data with third parties.
Your choices
You can decline the cookie notice on first visit, clear cookies in your browser at any time, or stop using the site. Because we store so little, withdrawing consent is trivial — nothing is retained server-side beyond anonymous visit counts.
Contact
Questions about privacy or corrections to any page? Email our domain administrator at — the address is obfuscated so it never appears to crawlers and is revealed only when you click.
Grievance / content policy
We are an informational publisher, not a PPI issuer or a financial adviser. If you spot an error in a limit, fee or rule, please write to us and we will correct and log it in the change log.