Privacy Policy

What we collect

Data	Why
Email address	To identify your account, verify it, reset a password, and tell you when something needs your attention.
Password (hashed)	To sign you in. Stored as a one-way hash — we cannot read it.
Two-factor secret and recovery codes	To protect the account. Recovery codes are stored hashed.
Broker API credentials	To place orders on the account you connected. Encrypted — see below.
Trading records	Positions, closed trades, balances and the activity feed, so you can see what was done and why.
Account settings	Risk controls, watchlist and plan.
Security log	Sign-ins, settings changes and administrative actions, with the IP address they came from. Append-only; we cannot edit or delete entries from the console, including our own.
Billing identifiers	A Stripe customer and subscription reference. Card numbers are handled by Stripe and never reach our servers.

We do not use advertising trackers, we do not sell data, and there is no third-party analytics script on these pages.

How your broker credentials are protected

Each account's credentials are encrypted with a key unique to that account, which is itself encrypted with a master key that exists only in the server's environment — never in the database, never in the code, and never in a backup of the database alone.

The practical consequences, which are the point:

Nobody at CurmyBot can read your API keys from the admin console. The console shows whether a key works, not what it is.
They are excluded from your data export by construction. An export that handed out API keys would be a breach dressed as a courtesy.
They are redacted from logs and from error messages.
If someone obtained a copy of our database alone, the credentials in it would be unreadable.

You can revoke them at your broker at any time without asking us. That is the strongest control available to you, and it does not depend on us doing anything.

Who else processes your data

Who	What they see
Your broker	The orders we place with the keys you gave us.
DigitalOcean	Hosts the server and its backups.
Stripe	Your payment details and billing history, under Stripe's own policy. We never see your card number.
Our email provider	Your email address and the contents of messages we send you.
Anthropic	Only if you switch on the optional AI features. Off by default; when off, nothing about your account is sent.

How long we keep it

While your account is open, so the record stays complete. When you delete an account, we delete its trading history, positions and settings. When you close your CurmyBot account, we delete your accounts and your personal data.

Two things survive deletion, and you should know which:

Billing records, which we are required to keep for tax and accounting purposes.
Server backups, which are taken daily and age out on their own cycle. A deletion is not instantly erased from a backup taken before it.

Your rights

Get a copy. Download everything we hold about you, as readable JSON, from your settings — no request, no wait.
Correct it. Email and settings are editable in the product.
Delete it. From account settings. Deleting does not sell or touch anything you hold at your broker.
Object or complain. Contact us through support. If you are in a jurisdiction with a data protection authority, you may complain to it.

Breach

If we discover a breach affecting your data, we will email you and say what happened, what was exposed and what to do — including telling you to revoke your broker keys. We will do that whether or not a regulator requires it.

Contact