Privacy
Last updated 26 September 2026.
This is a product concept built as a hiring assignment, not a commercial service. It is a working demonstration with a real sign-in and a real database, so it does store a small amount of data, and this page lists all of it.
If you never sign in
Nothing about you is stored in the database. The demo at /demo reads fixed sample data and writes nothing. The one exception is described under "Running an agent" below, and it stores no identifying information.
If you sign in with Google
Sign-in uses Supabase Auth with Google. No extra permissions are requested beyond the defaults, which are your name, email address and profile picture. Supabase stores those in its own managed auth.users table.
Two tables in this project's own database then hold data about you. Both have row level security, and every policy scopes every row to the user who owns it, so one account cannot read another's.
profiles
Your user id, and one preference: whether you chose the guided or the detailed view during onboarding. Nothing else.
projects
Your user id, and for each project you create: the name, the prompt you typed, and a status. The prompt is text you wrote, and it is stored. Do not put anything sensitive in it. Nothing else about a project is real: the build, agents, code and deploy screens all read fixed sample data.
Running an agent
Three agents in the demo make real calls to a decision model. Pressing "Run this agent" sends the text in that box to Vercel AI Gateway, which passes it to TypeSafe AI's Jev model. If you leave the box alone, a fixed sample sentence is sent instead.
Each call writes one row to a table called jev_calls, containing exactly six things:
- created_atwhen the call happened
- agent_idwhich of the three agents ran
- outcomewhether it was live, rate limited, capped, or failed
- latency_mshow long it took
- ip_hasha SHA-256 of your IP address plus a secret salt, kept only to enforce the rate limit
- ida random row identifier
The text you submit is not stored in that row, and neither is the answer. The IP hash is not reversible without the salt, which is a server-only secret, and no visitor can read that table: the anonymous role can add a row through a narrow function and cannot select from it.
Cookies
Two kinds, both necessary, neither for advertising or analytics. There is no analytics or tracking on this site at all.
- theme remembers whether you chose light or dark. Choosing Auto deletes it.
- Supabase sets session cookies once you sign in, so you stay signed in. Signing out clears them.
Who else handles this data
- Supabase hosts the database and runs authentication. It holds everything described above, and your Google account details.
- Vercel hosts the site and operates the AI Gateway that agent calls pass through.
- TypeSafe AI provides the Jev decision model, and receives the text you submit when you press "Run this agent".
- Google handles the sign-in itself, if you choose to sign in.
Nothing is sold, and nothing is shared with anyone beyond the four above.
Deleting your data
Email katkarabhi91@gmail.com and ask. Your account and every row belonging to it will be deleted, and the project rows go with the account automatically, because they are defined to cascade. Say which email address you signed in with, so the right account is removed.
Because this is a hiring assignment rather than a service, the whole database may be deleted after the assignment is reviewed.