Skip to content

Security and data handling

Last reviewed: 2026-11-08

Fillbook is a small, independent product. This page says what we do to protect your data and, just as plainly, what we have not done.

What a broker connection can and cannot do

Fillbook only reads your trades and does not place, change or cancel orders. A broker login can itself allow trading, so keep your credentials private, use keys with the narrowest permissions your broker offers, and remove Fillbook's access in your broker's own settings if you stop using it.

When you connect Tradovate with OAuth, we never see or store your Tradovate password. The access tokens and other connection secrets we hold, such as API keys or a Rithmic login, are encrypted before they are stored, and the keys are kept outside the database. Add-on keys and personal AI-assistant tokens are stored only as one-way hashes.

Who can see your data

Row-level security in our database means each signed-in account can read only its own records. It does not hide data from our own server code or from the small number of authorized people with dashboard access, who can technically reach stored data. Service keys are access-controlled.

Sign-in and the site

New passwords are checked against known data breaches: only the first five characters of a one-way hash leave your browser, and the password itself is never sent. The site uses HTTPS, an enforced content security policy and standard security headers.

Payments and AI features

Payments are handled by Stripe, and card details never reach Fillbook. AI requests go through our servers, so the AI provider key never reaches your browser. If you connect your own AI assistant with a personal token, a token expires within 90 days at most and you can revoke it in Settings.

Backups, logs and deleting your account

We make a daily encrypted backup of our database and keep it for up to about 90 days. Server logs are kept for about 30 days. Error reports go to Sentry with tokens, passwords and cookies scrubbed.

You can delete your account from Settings. It is then removed from the app database, but deleted data can remain in a backup until that backup ages out, and billing records stay with Stripe. Deleting your account does not revoke Fillbook's access at your broker, so remove it there too.

Delete your account · Privacy policy

What we have not done

Fillbook has not had a third-party security audit or penetration test, and we hold no security certification such as SOC 2 or ISO 27001. No system is completely secure.

Report a security problem

Email developer@fillbookhq.com. Our security contact is also published at /.well-known/security.txt.