Privacy Policy

Public pages — exam guides, prep courses, lessons, glossaries — are served as static files. Visiting them creates no account and requires no sign-in. It does send a measurement request to Google Analytics, which sets its own cookie — described in its own section below.

These are stored in your own browser:

• pg-theme — whether you chose light or dark, so the site does not flash the wrong theme on your next visit. Never sent to us.
• pg-nav — a display-only hint (your name, email and access tier) so a returning signed-in visitor sees their own avatar in the nav on the first paint rather than a Login button. It is never consulted to decide what you are allowed to access; every access check happens on the server against the database.
• pg-auth-event — a cookie that exists for one minute and holds one word: whether you just signed up, signed in or signed out. Signing in sends you to another page, and this is how the page you land on knows to count the sign-in once. It carries no name, email or identifier, and it deletes itself as soon as it has been read.
• pg-sid — this one is worth reading carefully, because it is the only identifier we set that links your activity together. If you answer a practice question without being signed in, we set a signed, randomly generated identifier that lasts a year, so that your streak and progress survive a page reload and can be carried over if you later create an account. It contains no name, email or device information and is not readable by JavaScript, but it is a persistent identifier and it does reach our server with the activity recorded against it. Clearing your cookies removes it.

Your browser also requests the site’s three typefaces from Google Fonts, which receives your IP address as part of that request, as it would for any site using the same service.

We use Google Analytics to see which lessons get read, which practice modes get used and where visitors arrive from. Without it we would be writing a 267-lesson course with no idea which parts of it work.

The practical consequence, stated plainly:

• A cookie is set by the analytics tag so Google can recognise the same browser on a later visit — that is what lets us see whether a reader who starts a course comes back to finish it. No name or email is ever attached to it.
• Signed in, your account id travels too — not your name or email, the same internal id everything else on this page calls your account identifier — so Google can recognise the same person across devices, not only the same browser. Signed out, there is no such id to send, and none is.
• What is sent is the page you are on, the page that referred you, your approximate location derived from your IP address, your browser and device type, and the events described in the next paragraph.
• What is not sent: your email address, your name, anything you type into the AI tutor, and the answers you give to practice questions. Where a question is referenced it is by its internal id, not its text.
• Your IP address reaches Google as part of any web request and is used to derive an approximate location. Google discards it rather than storing it against the measurement data.

The events we record are the ones that tell us whether the material is working: a page viewed, a lesson opened or read to the end, a practice question answered right or wrong, a mock exam started, submitted or abandoned, a tutor question asked, a theme switched, a code block copied, and the steps of a purchase. Each carries which certification it relates to, not who did it.

There is no cookie banner asking permission for this. What is collected is not used for advertising or personalisation — advertising storage and ad personalisation are switched off in the tag, independent of the analytics setting above — and it is not sold or shared with any marketing service. If that ever changes, this page changes in the same release.

If you would rather send nothing at all, any tracker-blocking extension or a browser with tracking protection will block the request outright — the site is built to work identically when it is blocked, and nothing on it checks whether analytics loaded.

An account exists so your progress survives closing the tab. Creating one means we store, in a Supabase-hosted Postgres database:

• Your email address, and a securely hashed password — handled by Supabase Auth. We never see or store your password in a readable form.
• Study progress — which lessons you have read, and a per-concept mastery estimate used to schedule reviews.
• Answer history — the questions you attempted, what you chose, whether it was right, and the mistakes you asked to keep in your mistake journal.
• Mock exam attempts — your answers and score for each full-length attempt, so a results page can be shown again later.
• Your exam target, if you set a date.
• Purchases — which certification or bundle you are entitled to, when it was granted, and the order it came from.
• Activity and rate-limit events — a timestamped log of significant actions, used to show your streak and to stop automated abuse of the question and tutor endpoints.

We do not ask for, and have no field to store, your real name, date of birth, address, phone number, employer or any government identifier.

If you have access to the AI tutor and ask it a question, that request is sent to Anthropic to generate the explanation. What is sent is the question you were working on, its answer options and explanation, the option you selected, and the question you typed. Your email address and account identifier are not sent.

We store a per-day count of your tutor requests so the daily limit can be enforced. We do not store the conversation itself.

Paid access is processed by Razorpay. Card details are entered on Razorpay’s own systems, inside their checkout, and are never transmitted to or stored by passgenai — we receive the confirmation that an order succeeded and the order identifier we record against your entitlement. Your email address and name are passed to Razorpay so the checkout can be pre-filled and a receipt sent.

We record that a purchase completed, its value and which product it was, in the analytics described above. That record carries the order identifier and no personal detail — it is what tells us whether the pricing page works, not who bought.

A purchase is also reported to analytics directly from our server, in case the confirmation page closes before it can report the same thing itself — the two are matched so neither counts a purchase twice. Making that match means reading the analytics cookie value your browser already had at checkout and keeping it in our own payment record alongside the order. It identifies a browser, not you by name, and it is used for nothing else.

These are the only third parties involved, and each is here because the site cannot function without it:

• Supabase — hosts the database and handles authentication. All account data described above lives here.
• Anthropic — generates AI tutor explanations, and only when you ask for one.
• Razorpay — processes payments, and only when you buy something.
• Google Analytics — measures page views and feature use; sets a cookie to recognise your browser across visits, and, signed in, your account id to recognise you across devices. Never your name or email, as described above.
• Google Fonts — serves the site’s typefaces to your browser.
• Our hosting provider — serves the pages and keeps short-lived operational request logs.

We do not sell your data, share it for advertising, or send it to any marketing service. Google Analytics is configured with advertising features and ad personalisation switched off, so nothing measured here is usable for targeting you elsewhere.

Account data is kept while your account exists. If you ask us to delete your account, we delete your progress, answer history, mock attempts and mistake journal, and we sever the link between your account and any anonymous identifier it absorbed.

There is one honest exception we would rather state than gloss over. Significant actions — the ones that decide whether an answer was graded correctly and whether you were entitled to see something — are written to an append-only activity log, which the database physically prevents anyone from editing or deleting, including us. That is a deliberate integrity guarantee: it is what makes a scoring or entitlement dispute resolvable, and a log that could be quietly rewritten would be worth nothing. Those rows hold timestamps and event types rather than anything you wrote, and after a deletion request they are no longer linked to your identity through any other table. But they are not erased, and we will not claim otherwise.

Records of a purchase are the other exception: we retain the minimum needed to evidence a transaction and meet tax and accounting obligations, even after an account is deleted.

Analytics data is a third case, worth explaining rather than glossing over. For most of what is measured, a deletion request cannot reach it — not because we refuse, but because we have nothing to hand Google to locate your specific rows, and no way to prove which measurement events were yours. Two exceptions exist and neither is hidden: a purchase's analytics cookie value is read once at checkout and kept in our own payment record, as described above; and signed in, your account id reaches Google as GA4’s User-ID, which — unlike the anonymous cookie — Google’s own tools can filter by. We do not run a process today that acts on either to erase analytics rows on request, and would rather say that plainly than promise a capability we have not built. It expires on a retention period set in Google Analytics, which we keep at the shortest setting that still allows a year-on-year comparison and which cannot exceed fourteen months for event data.

• Get a machine-readable copy of what we hold about you, including your full activity history.
• Correct anything that is wrong.
• Delete your account and its study data, subject to the append-only log described above.
• Withdraw consent by closing your account — the whole free corpus remains readable without one.

The first and third of these are built into the site rather than being a promise to act on an email: signed in, you can export your data and request deletion directly. If you would rather ask a person, or you can no longer sign in, email support@passgenai.com from the address on the account and we will act on it within 30 days. You can clear the browser keys described above yourself at any time by clearing site data.

Access to your data is enforced server-side. Correct answers and the question bank are never sent to the browser for content you have not unlocked, and every entitlement check runs on the server against the database rather than in client code.

No system is perfectly secure. If you believe you have found a vulnerability, email support@passgenai.com and please give us a reasonable chance to fix it before disclosing it publicly.

These are professional certification exams and the site is not directed at children. You must be at least 16 to hold an account, and we do not knowingly hold data about anyone younger. If you believe we have, email us and we will delete it.

If this policy changes materially we will update the revision date above. The data controller is the operator of passgenai; the operating legal entity is being formalised and this page will name it once that is complete.

Questions about this policy, or a request about your data, go to support@passgenai.com. See also our Terms of Use and Disclaimer.