Privacy foundation and safeguards
What we store, where it lives, what a database leak would and would not reveal, and the limits of the claim. Written to be checked, not to be trusted.
Who pays is one question. How you feel is another. We keep them in separate rooms, on purpose.
What we store, and where
Three separate records, each answering one question and never two.
billing — who pays
Never your email in plain text. A scrambled version for checking sign-in, one fingerprint for finding your row, and one encrypted copy for receipts. A stolen copy of this table is noise without our key.
pop-ins — how you feel
Three scores, an optional note, a timestamp, and a random id. No email, no name, nothing that points back to a person.
research — what we learn
Averages only. No ids, no rows that link to the other two, nothing that can be traced back to one person.
The one thread between them
There is exactly one link between your account and what you write: a single encrypted value. The key that opens it lives in the running service, not in the database.
So what does that mean? If someone steals a copy of the database — a dump, a backup, an insider with access — they get scrambled email, anonymous scores, and one unreadable value. They cannot connect a name to a bad week.
And what it does not mean: the running service can open that value when it needs to — to show you your own history, to export it, to delete it. Only you can ask for that, and only from your own account. This protects you from a leak. It is not a promise that no human here could ever look.
One weakness, said out loud: when an admin views an account's email, the action is behind a login but is not yet written to an audit log. We would rather you read that here than discover it.
What we do to keep it true
- Your email is never stored readable — not in logs, not in research, not in backups.
- Backups are encrypted before they leave the machine, and the key is not on the server's disk.
- If the keys are missing, the app refuses to start — it will not quietly save addresses in the clear to keep running.
- No third-party requests on these pages — the fonts are ours, so reading this does not hand your IP to a font company.
- Nothing personal goes to a model without your consent — no endpoint, no key, or no consent means it stays on the server.
- Delete means delete, in the safe order — your pop-ins go first, then the account. A failure in the middle cannot leave your words behind without your name.
- An employer sees trends, never names — population numbers with a cohort floor. A manager can never see who is declining.
What we do not do
- No ads, and nothing sold. There is no third party to sell it to.
- No tracking pixels or client-side analytics on these pages.
- No diagnosis, no treatment claims, no prediction about you.
- No score deciding which content you are shown.
The limits of the claim
Agellia is not a crisis service and not clinical care. Three sliders are what you tell us, which is not a measurement of illness. What you get is early sight of your own pattern — in the stretch of time between noticing something is wrong and being able to get help.
If any of the above stops being true, this page changes before the claim does.