Privacy

What we store

Your account: an email address and a magic-link or password sign-in, handled by Supabase Auth.

• The people you've added and their answers to the seven EMPOWER questionnaires (Empathy, Morality, Personality, Orientation, Workstyle, Entrepreneurship, Reasoning)
• The written readings generated from those answers (module reports, advisor briefings, persona matches)
• If you invite a real partner to link accounts: the invite itself (their email, its status) and a placeholder row pointing at their account — never their answers directly, see "Partner linking" below
• If you connect your own model key (BYOK): the endpoint and model name you specify, and the key itself, encrypted in Supabase Vault

Where it lives, and who can see it

Everything above lives in our Supabase project's Postgres database, in tables scoped by row-level security to exactly one owner: you. No table grants any account read access to another account's raw answers, assessments, or reports. This isn't a policy we promise to follow — it's enforced by the database itself, and it's the thing we verify first whenever we change anything in this area.

The one exception is deliberate and narrow: if you link with a real partner, the comparison we compute (which scales you're alike or different on, and the counsellor's or adviser's read on that) is visible to both of you once you've both accepted. Your raw answers are never readable by your partner's account, and theirs are never readable by yours — only the comparison output crosses that boundary, and only after mutual consent.

Partner linking, specifically

When you invite someone, we store their email and an invite state (pending, accepted, declined, or revoked). Accepting creates a placeholder record in each of your accounts pointing at the other — no answers move. Every comparison you see afterwards is computed at the moment you view it, from each person's own answers, read under a system role that exists only inside that one computation. Revoking a link stops new comparisons immediately; anything you already generated and saved stays exactly where it was, since it never contained the other person's raw answers to begin with.

Bring-your-own-key (BYOK) models

By default, every reading is written entirely on our servers with no external call. If you add your own model key in Settings, your answers are sent to the endpoint you specified only when you explicitly ask for a rewrite — never automatically, never as a side effect of anything else. The rewrite is asked to keep the same evidence and disclaimer as the original, and we check the result against that before showing it to you.

Your key itself is encrypted at rest in Supabase Vault. We do not read it, log it, or use it for anything other than the rewrite you requested.

What we don't do

• We do not sell your data, to anyone, ever.
• We do not use your answers, scores, or readings to train any model.
• We do not currently run any third-party analytics, advertising pixel, or tracking script on this product.
• We do not use your psychometric data — yours or your partner's — to make or inform any decision about hiring, promotion, lending, insurance, or anything else with a legal or similarly significant effect on a person. See Responsible use.

Deleting your data

Settings → "Delete your account" removes your account and everything it owns: every person you added, every answer, every report, any partner links (both sent and received), and your model key. This runs immediately, is not a soft delete, and cannot be undone from within the product. If you were linked to a partner, their account and their own answers are entirely unaffected — deleting your account only ever removes what your account owns.

One known limitation, stated plainly rather than hidden: if you configured a BYOK model key, its underlying encrypted secret is deleted as part of account deletion; we verify this in our own testing rather than assuming it. Deleting a single person from within the product (rather than your whole account) removes that person's answers and reports the same way, immediately.

Cookies

Supabase Auth keeps your session in your browser's local storage, not a cookie. We don't set any analytics or advertising cookies.

Changes to this policy

If this policy changes in a way that matters to what's already stored about you, we'll say so clearly rather than quietly updating the date at the top.