Privacy, in plain words

What we save

• Your bot's sign-up. Its name, when it signed up, and which 29Court account it belongs to once you link it. Your key is never saved as-is: we save a scrambled fingerprint of it, plus its first few characters so you can recognise it. The full key is shown to you once.
• Your corrections and rules. What your bot sends when it saves a correction, and the rule made from it, with the kind of rule and the date. Rules keep their history (earlier wordings, edits, pauses, and retirements), so a rule can be traced and undone.
• Your description of your bot, if you fill one in. Who runs it, what it works with, and what it can do: the things you choose to write down so you can see them later and a rebuild can start from them.
• Draft checks. When your bot checks a draft against your rules, we save the result: the verdict, the score, and which rules were checked. The draft itself is saved only as a fingerprint, unless you chose to keep draft text.
• Your email address. Held by the 29Court accounts system, so you can sign in and receive sign-in links. If you ask us to email a setup message to your bot, the address is used to send it.
• Basic technical records. The network address and program name behind a request, plus rate-limit and alert records that stop spam. These keep the service running. They are not a profile of you.

What we never save

• Passwords. We never ask for your passwords or your bot's passwords. Never put a password in your bot description or anywhere else here: names of tools and accounts only.
• Login secrets for your other services. No API keys, tokens, or sign-in secrets for your other tools. Your bot's key here is the one exception, and even that is saved only as a fingerprint.
• Card numbers. Stripe's page takes your card. We never see your card number and do not save it.

Who can see what you save

• You. Signed in, you can see your bots, your corrections and the stories behind them, your rules, and your bot description.
• Anyone holding your rules link. The link shows your rules, their dates, and whether each rule is active. It does not show the corrections behind them; those stay in your signed-in pages. The link includes your key, so treat it like the key: share it only with people you want reading your rules.
• People at 29Court. Staff can reach saved records to run the service, fix problems, and carry out deletion requests. 29Court also gets a notice when a bot signs up and when a rule is saved, so a person can see the service working.
• The companies behind the plumbing. Cloudflare hosts the site and its database, Stripe handles payments, and an email service delivers sign-in and setup messages. They handle data only to run the service. Draft checks are done by 29Court's own services.
• Nobody else. We do not sell your corrections, your rules, or your bot description to anyone.

If you cancel

Cancelling stops future payments. Your plan stays live until the end of the month you paid for; when the plan ends, the key your bot uses stops working.

If a payment fails, nothing stops right away. There is a grace period while Stripe tries the payment again; the key stops only if the plan is actually cancelled.

If you come back later, you get a fresh key. What you made stays yours either way (next section).

What you keep

Your corrections, and the rules made from them, belong to you. You can read them, export them, change them, retire them, and have them deleted. We keep them so your bot can work by them; that is the whole purpose, and they never become ours to reuse for someone else. We never train anything on your corrections, your rules, or your bot's record — not our models, not anyone else's. When your bot checks a draft, our own checking service reads your rules only to check the draft against them: use to check, never use to train.

Deleting everything

Ask, and we delete. Email hello@29court.com from the address your plan lives under and say you want your record deleted. Signed in, you can also delete it from your account page. Deletion removes your bots' sign-up records, corrections, rules and their history, draft-check results, bot descriptions, and backups.

Copies already inside dated database backups stay there until those backups age out; we do not promise a date for that. One small receipt stays: it records only that a deletion happened, how much was removed, and the date. It holds no rule text, no corrections, and no bot description, so the deletion can be proven without the deleted material surviving in it.

Telling your bot to stop stops it saving new corrections from then on, but it does not delete what is already saved. For that, use one of the routes above.

Changes to this page

If what we save ever changes, this page changes with it, and the date at the top moves. Questions about anything here: hello@29court.com.