This policy explains what IPOWATCH collects when you read the site, use the contact form, or see an advertisement. We wrote it in plain language because a privacy page that hides the advertising cookies is not a privacy page. If advertising is turned on, third parties — including Google AdSense — may set cookies and collect data as described below.
Who is responsible
IPOWATCH operates this website. For privacy requests, use the contact form. Put “Privacy” in the subject. We do not ask you to create a public account to read guides or trackers.
Information you give us
The contact form asks for your name, email address, a subject, and a message. We use that information only to read the request, reply if a reply is needed, and spot abuse (repeated automated submissions). Do not include PAN, Aadhaar, demat account numbers, UPI PIN, OTPs, or bank details. If you include them anyway, delete-and-rewrite the message without those details; we do not need them to correct a date or answer a question about how the site works.
Contact messages are stored in the site database and shown to the site administrator. We keep them while a thread is open and for a limited period afterwards so we can follow up on a correction. You can ask us to delete a message you sent. We will delete it unless we need to keep a record of abuse or a legal claim.
Information collected automatically
Like almost every web server, the host may log the IP address, browser type, referring URL, and the page requested. We use those logs to keep the site reliable, block obvious attacks, and understand which pages fail. The contact form stores a one-way hash of the IP address with the message so we can rate-limit spam. We do not sell logs and we do not build a public profile of readers.
The site sets a first-party session cookie (ipowatch_sess) so the contact form can use a security token and so the admin area can stay signed in. That cookie is HTTP-only. A small preference in your browser’s local storage remembers that you dismissed the cookie notice. That preference stays on your device; we do not receive it as an account record.
Cookies we use
- Session cookie. Required for the contact form’s security check and for the administrator login. It expires when the browser session ends, or as the browser’s cookie rules decide.
- Cookie-notice preference. Stored locally so the notice does not repeat on every page.
- Advertising cookies, when ads run. Google and its advertising partners may set cookies to serve ads, limit how often you see an ad, measure ad performance, and (depending on your settings and region) personalise ads based on your visits to this site and other sites.
We do not operate our own analytics product. If the site administrator later pastes a third-party script into the site settings (for example an analytics tag), that provider may set its own cookies. Those scripts are the administrator’s responsibility and should be named in an update to this policy when they are added.
Third-party advertising, including Google AdSense
IPOWATCH may display advertisements served by Google AdSense and other Google advertising services. Third-party vendors, including Google, use cookies to serve ads based on a user’s prior visits to this website and other websites. Google’s use of advertising cookies enables it and its partners to serve ads to you based on your visit to this site and/or other sites on the Internet.
You can opt out of personalised advertising by visiting Google Ads Settings. You can also read how Google uses information from sites that use its services in Google’s advertising policies and technologies page, and how Google uses data generally in Google’s privacy policy. An industry opt-out page is available at aboutads.info (more relevant if you browse from outside India).
We do not control Google’s cookies and we do not receive your Google account data. Advertisers do not get the contents of the contact form. Turning ads off in your browser or in Google’s settings does not block you from reading the guides or using the trackers.
If you are in a region that requires a consent choice before advertising cookies (for example the EEA or UK), ads should not be personalised until that choice is collected. The site is written for readers in India. If we later serve personalised ads into a consent region, we will add a consent tool and update this section.
Links to other sites
Allotment buttons and registrar links leave IPOWATCH and open the registrar or exchange. Their privacy policies govern what happens after you leave. A registrar will ask for PAN or an application number because that is how allotment status is looked up. Type those details only on the official registrar page, which you should recognise by its domain (for example KFintech, Link Intime, Bigshare, Skyline, or Purva).
Children
This site is not directed at children. IPO applications in India are made through demat and bank accounts that have their own eligibility rules. We do not knowingly collect personal information from anyone under 18. If a parent believes a child sent us a contact message, ask us to delete it.
How long we keep information
Server logs follow the host’s normal rotation. Contact messages are kept as described above. The session cookie is not a long-term profile. Advertising cookies follow Google’s own retention rules, which Google publishes in its policies.
Your choices
- You can browse the trackers and guides without sending the contact form.
- You can block third-party cookies in your browser. Some ads may then be less relevant or may not load. The articles will still load.
- You can opt out of personalised Google ads at adssettings.google.com.
- You can ask us to delete a contact message you sent.
Changes
If we start using a new kind of personal data, or we turn on a new advertising or analytics vendor, we will update this page and change the date at the top. Continued use of the site after the date changes means you are reading the current policy. The previous date on this version is 27 September 2026.
Contact
Privacy questions go through the contact form. See also the terms of use and the disclaimer.