Loading…
Last updated 15 October 2026
This policy explains what IPOCheckr does with the information you give it. “IPOCheckr” is a working product name; no separate legal entity is named here yet.
A PAN you type in is sent to our server, which forwards it to the registrar handling the issue you selected in order to look up your application. It is used for that lookup and nothing else.
If you are not signed in, your PAN exists only in the memory of the browser tab you are using and is discarded when you close or reload it. Nothing is stored.
If you create an account and choose to save a PAN, it is stored in our database against your account so you do not have to retype it. Saved PANs are only ever returned to your browser in masked form — the full value stays on the server, and the application resolves it there when you run a check.
You can delete a saved PAN at any time from the My PANs page. Deleting your account removes its saved PANs along with it.
You may optionally give a saved PAN a name so you can tell them apart (for example “Mom” or “Dad”). If you leave this blank, and a registrar returns the applicant’s name while you check an allotment, we save that name against the PAN so it is shown the same way next time. This never happens if you have already given the PAN a name yourself, and this name is shown only to you.
Accounts are handled by Supabase Auth. Your email address and password are submitted directly to Supabase; we do not store your password, and we hold no password hashes or reset tokens of our own. We can see the email address associated with your account.
We keep a record of allotment checks for operational purposes such as rate limiting and diagnosing failures. PANs in these records are stored as a one-way cryptographic fingerprint rather than the PAN itself, so a check can be counted without the PAN being recoverable from the record.
To answer a query, the application communicates with the registrar that holds the issue you selected. Those registrars operate their own systems and their own privacy practices, which we do not control. We also use Supabase for accounts and data storage, and Render Redis for caching and rate limiting.
We show ads from third-party advertising networks, Adsterra and Monetag, on some public IPO information pages, such as IPO GMP, upcoming IPOs and IPO subscription status. These ads are loaded from the networks’ servers, so they and their advertising partners may use cookies and similar technologies to serve and measure ads. Ads are not shown on the sign-in, sign-up, PAN entry, allotment result, account or admin pages.
You can opt out of personalised advertising by visiting Google Ads Settings. You can also opt out of some third-party vendors’ use of cookies for personalised advertising at aboutads.info. Ads are never shown based on the PAN you enter, and PANs are never shared with advertisers.
The application does not send your PAN to any analytics service. Pages that handle PANs are marked so that search engines do not index them.
For questions about this policy or to request deletion of your data, use the contact route published alongside the deployed application. A dedicated contact address will be listed here once it is available.