Your contracts are private. Here is exactly how.

We store your contract text

Your contract text is stored in your account, as version history. We are saying this first because some tools claim to discard it, and we do not.

A contract tool that throws away your contract cannot show it back to you, let you edit it, compare two drafts, or re-check it after a change. Storing it is what makes those work. It is yours: we do not sell it, share it, or use it to train AI models.

What we hold

• The contract text, as every version of it — so you can read, edit, diff and re-review.
• The analysis derived from it: risk flags, clause summaries, suggested wording.
• The details you add — counterparty, dates, value, notes.

We do not store passwords or card numbers. There are no columns for either: sign-in is handled by Clerk and payment by Stripe, and neither hands us the credential.

Who can reach it

Row-level security is enabled on every table in the database — all 25 of them. And there is no path from a browser to the database: the application has no database client in it at all, so the API is the only way in, and the API checks who you are on every request.

Verified against production, September 2026.

Deleting things

Delete a contract and its text goes with it — every stored version, along with its comments, deadlines, share links, approval requests and signature records. This is enforced by the database itself rather than by cleanup code that might miss something.

Closing your whole account is not yet something you can do yourself in the app. We are building it. In the meantime, write to privacy@contractclerk.com and we will handle the request. We would rather tell you the button does not exist than imply that it does.

Verified against production, September 2026.

Where it runs

• Database — Supabase Postgres, hosted in the United States (AWS us-east-2).
• Application — Vercel (frontend) and Railway (API).
• In transit — HTTPS everywhere; the API accepts nothing else.

Who else is involved

• Clerk handles sign-in. Your password never reaches us.
• Stripe handles payment. Your card details never reach us.
• Anthropic provides the Claude model that reads your contracts. Under Anthropic’s API terms, content sent through the API is not used to train their models.