This page describes only what the application actually stores, checked against the database schema. It is not yet a complete privacy policy: it does not state retention periods, legal bases, jurisdiction, or how to exercise formal data rights. Those are being prepared.
Each item below is a table in the database, listed with the columns it holds and who can read them.
The email address and password you sign up with. These are held by Supabase Auth, the service that signs you in — not in a table this app writes to.
What you tell onboarding about yourself: the background you picked, your state, your sector, how much experience you have, and where you are on the 13-phase journey.
The question you typed and the answer you were given, with the time it happened, so you can find it again.
When you’re signed in, we save the questions you ask, Chiefy’s answers, the date and time of each, and the names of any files you attach, so you can come back to them. We keep them until you delete a chat or close your account. If you’re not signed in, your chats aren’t saved.
A record that a term was opened, against your account if you are signed in or an anonymous session identifier if you are not. It is used to show what is most read, and to suggest related terms.
If you join the waitlist: your name, email, organisation type, and optionally your organisation, role and a short note.
A PDF, an image or a Word file you attach to a chat question, and a record of when you attached it. Each file is held in the app’s own file storage, in a folder private to your account, and is read back only to answer the question you attached it to.
Page views and a few interaction events are counted through Vercel Analytics, which is cookieless and receives no names, emails or account identifiers.
Write to matt@chiefy.ai.