What we collect, and what we don't
There are no accounts on this site, no ads, and nothing is sold to anyone. But it is not zero-collection either, and it would be dishonest to imply otherwise. Here is the whole list.
The short version
- You never need an account, an email, or a phone number to read anything here. An email address is asked for in one place only: if you choose to get change alerts.
- We do not sell, rent or share data with advertisers. There are no ad networks on this site.
- We do not ask for your PAN, Aadhaar, card number, CVV, OTP or bank credentials, anywhere, ever. Nothing on this site legitimately needs them.
- What we do collect is aggregate usage data and the content of things you deliberately submit, like a chat question or a thumbs-down.
What is collected, in detail
| What | When | Why |
|---|---|---|
| Page views, referrer, approximate location, device and browser type | Every page, via PostHog, Google Tag Manager and Vercel Analytics | To see which guides people actually read and where they leave |
| A session replay: a recording of how a visit went, meaning the pages seen, scrolling, clicks and what was on screen | On some visits, via PostHog | To spot pages and tools that confuse people. Anything typed into a box is masked before it leaves your browser, and AI chat conversations are excluded from the recording entirely |
| Which features you use: a feedback vote, a share button, sending a chat message, using a calculator or checker, opening a search result | When you use them, via PostHog | To see which features help. Only the action and the choice are recorded (for example “shared via WhatsApp”), never text you typed |
| The text of questions you ask the AI assistant | When you send a message in the chat | Repeated questions tell us what to write next. Stored with a timestamp and no identifier linking it to you |
| Your thumbs up or thumbs down, and which article it was on | When you vote on an article | To find guides that are not working. No identifier attached |
| What you say a guide was missing, if you choose to tell us after a thumbs down | When you send it | To fix the guide. Stored with the article name and no identifier |
| The answers you give the eligibility checker, and the score produced | When you complete the checker | To improve the scoring model. The answers are bands (for example “750+”), not exact figures, and are not linked to you |
| Anything you type into the contact form | When you submit it | To read and reply. Include an email only if you want a response |
| Your email address and the card you chose, if you sign up for change alerts | When you sign up, and when you confirm or unsubscribe | Only to send those alerts. Nothing is sent until you open the confirmation link, and every alert has a one-click unsubscribe |
Who processes it
We are a small site and we use standard third-party services rather than running our own infrastructure. Data reaches these processors:
- Vercel hosts the site and keeps standard server logs, which include IP addresses.
- PostHog and Google Tag Manager handle analytics. PostHog stores an anonymous identifier in your browser via localStorage and a cookie so returning visits are not double-counted, and keeps the session replays described above.
- Supabase stores the chat questions, feedback votes, eligibility answers, contact messages and alert sign-ups described above, in a database hosted in Mumbai.
- Resend sends the change-alert emails, so it receives your address and the email's contents when one is sent to you.
- OpenAI processes typed questions that our own fee lookup cannot answer, in order to generate a reply. Questions you tap in the assistant's menu, and plain fee questions we can answer from our card database, never reach OpenAI. Do not put personal or financial details into the chat: treat it as you would any public form.
Please do not send us sensitive details. Not in the chat, not in the contact form. We do not need your card number, your full name, your account number or your CIBIL report to answer a question, and we do not want to be holding them.
Cookies
The only cookies set on this site come from the analytics tools above. There are no advertising cookies and no cross-site tracking pixels for ad networks. Blocking cookies, using a tracker blocker, or enabling Do Not Track will not break anything on the site: every guide works fine without them.
How long it is kept, and how to get it removed
Analytics data is retained for as long as the accounts above retain it under their own defaults. Chat questions, votes and checker answers are kept indefinitely because they contain nothing that identifies anyone.
If you believe you submitted something identifying and want it deleted, email hello@onecardhub.org with enough detail to find the record (roughly when, and what it said) and we will remove it. We will not ask you to prove who you are, because we do not know who you are.
Change alerts
The alerts list holds an email address, the cards you chose, and when you signed up, confirmed or unsubscribed. It is not shared, not used for anything but these alerts, and not readable with the public key the site uses for its other forms. If you unsubscribe, we keep the address marked as unsubscribed so it is never emailed again by mistake; email hello@onecardhub.org if you want it deleted outright.
Children
This site is written for adults making credit decisions and is not directed at children under 13.
Changes to this page
If we add a tool that collects something new, this page gets updated in the same change. The date at the top is the last time that happened.