Privacy
Exactly what moves where
Holdout reads your trade history to test your rules. This page lists every place that data goes.
Bitget CSV export
Your browser only
Parsed in a Web Worker on your device. The file is never uploaded.
API sync, secret key
Your browser only
The browser signs each request with WebCrypto (HMAC-SHA256). The secret never leaves the browser.
API sync, key and passphrase
Our edge function, in memory
The signed request goes through /api/sync, which forwards it to Bitget. The access key and passphrase headers pass through in memory. Nothing is logged or stored.
Ledger and results
IndexedDB in your browser
Stored locally. Delete my data clears it.
Saved rulebooks and aggregates
Supabase, only if you opt in
Rule text and aggregate statistics only, keyed to an anonymous device id. Fills are never stored there.
Rule text and aggregates for the AI layer
The model provider
The model sees rule text, the rule schema, aggregates and tool results. It never sees raw fills or keys.
Read-only keys
Use a read-only key. If the Bitget API exposes the key's permissions, Holdout reads them and refuses a key with trade or withdraw permission. It never attempts anything write-shaped.
Orders
Holdout never places orders. The product has no code path that does.