Privacy

Faircopy is a personal project run by one individual, published as a portfolio piece. There is no company behind it and no team with access to your data. This page describes what it actually stores, in plain terms, rather than reciting a compliance programme it does not have.

Everything below lives in a Supabase (PostgreSQL) database:

• Your email address and a hashed password, if you create an account. Authentication is handled by Supabase Auth.
• The client briefs you paste — including any names, company details or figures you put in them.
• The proposals generated from those briefs, plus any client records and saved templates you create.
• A timestamped row per generation, used as an audit trail against abuse. It records that a generation happened and by whom, not its contents.

Row-level security in the database restricts every one of those rows to the account that created it.

This is the most sensitive thing the app touches, so it gets its own section.

• Your key is stored in your own browser — this tab's session storage by default, or this device's local storage if you tick “remember it on this device”. You can remove it at any time from the account page.
• It is sent with each generation request to this app's server, used for that single call to Anthropic, and then discarded. There is no column for it in the database.
• It is never written to a log, and never shared with anyone.
• The honest caveat: anything that can run JavaScript on this page could read it. That is inherent to any browser-based bring-your-own-key tool. Use a key with a spend limit, and revoke it when you stop using this.

Two processors, both because the app cannot work without them:

• Anthropic — the brief you generate from is sent to the Claude API using your own key. What Anthropic does with it is governed by your agreement with them, not by this page.
• Supabase — hosts the database and authentication.

Nothing is sold, and there is no advertising, no analytics script and no tracking cookie on this build. The only cookies set are the session cookies that keep you signed in.

The account page has a delete button. It removes your account and cascades to every proposal, client and template attached to it. It is immediate and cannot be undone.

If you would rather not create an account at all, the demo stores nothing and needs no sign-up.

Questions about any of this, or a request to remove something: open an issue on GitHub.