Privacy
Caesura is built to see as little as possible. On a store page it reads only the visible product details, and never anything from the checkout.
This is a pre-beta draft, written in plain language and pending legal review. It describes how Caesura works today.
What Caesura reads and stores
- The product title
- The merchant name and domain
- The product web address, with unnecessary tracking parameters removed where possible
- The product image address
- The displayed price, currency, and quantity
- Your own notes, bag choices, spend type, decisions, and outcomes
- Which merchant adapter ran, its version, and how confident the extraction was
What Caesura never reads or stores
- Raw page HTML or the page structure
- Screenshots of retailer pages
- Anything typed into a checkout form
- Card numbers, security codes, or bank credentials
- Passwords
- Shipping or billing addresses
- Keystrokes
- Browsing history unrelated to a saved item
- Personal messages
Your data, your call
Every bag is private. You choose which stores Caesura runs on, one at a time, and can turn any of them off. You can download everything Caesura holds for you from Settings, and deleting your account removes your profile, bags, items, and decision history for good.
Where it lives
Your data is stored in a managed Postgres database (Supabase) with row-level security, so one account can only ever reach its own rows. Anonymous, aggregate usage analytics may be recorded to see what is working; item titles, prices, and retailers are never part of that.
Questions
Write to us and we will answer plainly. support@heycaesura.com