Privacy and Browser Storage
This page explains the current application design. IPO Allotment provides no cloud database for saved PAN lists or allotment history.
Information used for a lookup
Your chosen registrar, IPO identifier, and PAN, application number, or Demat details pass through the website’s Cloudflare Worker and are sent to the selected registrar. The application validates those details on the server as well as in the browser. Guest searches do not require Google sign-in.
The application does not intentionally persist lookup bodies or results on its server, and its result endpoint returns no-store cache headers. Hosting and registrar infrastructure still process requests under their own terms and policies; this is not a claim that those services retain no request metadata.
Saved PANs and cached results
Saved PANs and confirmed result caches are encrypted using browser Web Crypto and stored in IndexedDB with an origin-scoped key. This protects stored records from casual inspection, but does not protect data from someone who can use your unlocked browser or compromise the website origin. Saved records do not sync between devices or browser profiles.
Remove entries through Saved Applications, or clear this site’s browser storage to remove the local vault and its key. Clearing storage cannot be undone by this website. Signing out of Google does not itself erase the browser vault.
Sign-in and service providers
Google sign-in uses Firebase Authentication. The application uses the sign-in state to enable management of saved PANs. Firebase, Google, Cloudflare, data-feed providers, and the selected registrar may process the requests needed to operate the service. Review their applicable privacy policies when using those services.
Do not share sensitive information in support messages
Use public issue names, error descriptions, and page URLs when reporting problems. Do not send a PAN, complete Demat identifier, password, or OTP by email.