Privacy, in plain language.

Last updated: 21 October 2026

This policy explains how IPO Board handles information when you use the watchlist, marketing page, or installed web app. No account is required. We do not ask for your name, email address, payment details, or investment holdings.

Analytics and its purpose

We use Cloudflare Web Analytics for legitimate analytics purposes: understanding overall traffic, measuring page usage and load performance, improving navigation, and finding reliability problems. We use aggregate reports to improve the service, not for advertising, personalized offers, or investment profiling.

Cloudflare Web Analytics does not use analytics cookies, local-storage identifiers, or fingerprinting to track individual visitors. This website does not show an analytics cookie popup or save an analytics consent preference.

What the analytics service measures

The Cloudflare beacon measures page visits and performance, including page-load timing and Core Web Vitals. Reports can include page paths, referring sites, browser, operating system, device category, and country. We do not add names, email addresses, account IDs, investment activity, or custom visitor identifiers to the beacon.

Your browser connects to Cloudflare to download the beacon and send measurements. Like other network requests, those connections necessarily convey technical network information. Cloudflare states that its Web Analytics does not track individual visitors across customer websites or fingerprint them using IP addresses or browser information.

Read Cloudflare’s Web Analytics privacy description, its data collection documentation, and the Cloudflare privacy policy for details about its processing. Analytics availability and retention are governed by Cloudflare’s service and policies.

Your browser choices

You can use browser content-blocking tools to block the Cloudflare beacon. This does not prevent access to the watchlist or installation features. Any analytics cookies or preference records left by an earlier website version are no longer read or renewed by this version; you can remove them using your browser’s site-data controls.

Information needed to deliver the service

Your browser sends an IP address and HTTP request headers to the services that deliver website files and IPO data. Our frontend is hosted on Vercel and our backend on Render. These providers may process technical information and keep operational or security logs under their policies, separately from website analytics.

Read the Vercel privacy policy and Render privacy policy. Provider log retention is controlled by those services, rather than your local browser storage settings.

Your saved watchlist and offline files

The last successfully fetched public IPO list is saved in IndexedDB so the watchlist can show saved figures if a refresh fails. A service worker caches website files for offline access. These stores support app functionality and do not contain analytics visitor identifiers. Installing the app does not create an account.

Saved IPO data is replaced after a successful refresh. Website caches are replaced when an updated service worker activates. Local data stays until it is replaced, your browser removes it, or you clear site data. Clearing it may remove offline access until your next online visit. Saved figures may be out of date; always check the displayed timestamp.

Optional IPO reminders

If you enable notifications, IPO Board uses Firebase Cloud Messaging to send a closing-day IPO reminder. We store a random browser-installation identifier, a push registration token, browser and operating-system family, notification preference, and synchronization timestamps. Browser and OS details describe the installation; they do not uniquely identify your physical device. No account or login is required.

Your browser stores the installation identifier, token, and a management credential in a separate IndexedDB database so you can update or disable reminders. Only a hash of that management credential is stored on our server. Firebase and your browser’s push service process delivery data. These identifiers are not sent to website analytics or used for advertising.

Use the bell’s Disable Notifications button or revoke permission in browser settings. If offline, disabling on the server is retried after reconnecting; reminders may continue until that request succeeds. Invalid tokens are removed when the provider reports them. Disabled or tokenless server records are deleted after 90 days; enabled subscriptions are not removed just because you have not visited recently. Delivery records track acceptance by Firebase, not proof that you read a notification.

Clearing browser storage or moving to a different domain creates a new installation; notification preferences do not automatically follow. You may need to opt in again. Read Firebase’s privacy information for details about its services.

Your choices and privacy requests

We do not sell personal information or share it for cross-context behavioral advertising. Depending on the laws that apply to you, including GDPR, CCPA, or India’s DPDPA, you may have rights to access, correct, or request deletion of personal information, withdraw consent, or raise a complaint with the relevant authority. We will assess requests under applicable law.

For privacy questions or requests, contact the project maintainer. Issues are public: do not post personal information; ask for a private contact method. We do not maintain a directory of analytics visitor identities.

External links and policy updates

Public IPO information comes from InvestorGain through our backend. If you follow a link to InvestorGain, Groww, or another external website, that service’s privacy policy applies. We will update the date above when this policy changes.