Short, because there is not much to describe
What this site knows about you.
Close to nothing, and the reasons are structural rather than promised. Here is exactly what happens.
The interview
The nine answers never leave your browser. There is no form submission, no request to a server, and no database attached to this site to store them in. When you reach the manifest, your answers have been turned into nine characters in the address bar — that is the whole mechanism, and it is why a manifest link works when you reload it or send it to somebody.
If you share a manifest link, you are sharing those nine answers with whoever you send it to. Nothing else travels with it.
Credentials
This site never asks for one and has nowhere to keep one. No password, no API key, no OAuth token for GitHub, Stripe, Google or anything else. The manifest describes which permission each service wants; you grant it on that vendor’s own screen, to your own assistant.
Analytics and cookies
No analytics are running. The measurement code exists and renders nothing at all unless a measurement ID is configured, and none is. That means no third-party script, no tracking cookie, and no consent banner — a banner asking permission for a tracker that is not running would be theatre.
If that changes, it will be Google Analytics 4 with IP anonymisation, and this paragraph will say so instead of this one.
Hosting and logs
The site is served by a hosting provider that keeps ordinary access logs — an IP address, a timestamp, a path, a user agent — for its own operational purposes. That is true of every website you visit, it is not under this site’s control, and pretending otherwise would be the one dishonest sentence in an otherwise short document.
If you email
Then I have your email and whatever you wrote, in an ordinary mailbox, for as long as the thread is useful. Every message gets a reply within two working days. Ask for it to be deleted and it is deleted.
chigoemeagha@gmail.comChanges
If this site gains accounts, it gains a database, and this page will be rewritten before that ships rather than after. The things that would arrive with it — row-level security, scoped session cookies, hashed passwords — are already described on the standard page as not yet built.
The claims here are meant to be checkable rather than trusted. If one of them does not match what the site does, that is a bug worth reporting.