Privacy
A plain description of what this service stores. Draft, pending legal review before any customer data is processed.
What we store
- Account data: your name, email, a hashed password or the identity provider you signed in with, and session records.
- Workspace data: alerts, customer profiles, transactions and decisions you upload or create, plus the agent's runs and the audit log.
- Pilot requests: the details you submit on the pilot form.
- Billing: handled by Stripe. We store the Stripe customer and subscription IDs, never card numbers.
- Page views: the minimal, cookie-free counts described under Analytics below.
Demo workspaces
The public demo uses synthetic data only. On the server edition, each demo workspace is tied to a browser cookie and deleted after 24 hours.
The in-browser demo keeps its state in your browser's local storage so a refresh does not wipe your work, and sends no alert data to us. If you paste your own model key into it, the key stays in your browser and is sent only to the provider you chose.
Cookies
A session cookie when you sign in, and a demo cookie when you open the server-edition demo. No advertising or cross-site tracking cookies, and no cookies for analytics.
Analytics
This site counts page views with its own first-party code. There are no cookies, no third-party scripts and no advertising identifiers involved. For each page view, the server stores:
- the path of the page, such as /pricing;
- the host name of the site that referred you, if any, never the full referring URL;
- a coarse device class, worked out from the width of the browser window;
- a visitor hash that rotates every day. It is salted, so the server cannot reverse it to identify you, and because it changes daily it cannot link your visits across days.
Clicks on a few labeled buttons, such as the demo button, are counted the same way. No IP address is stored. If your browser sends Do Not Track or Global Privacy Control, the page sends nothing at all.
The GitHub Pages edition of this site sends these events, and pilot requests, to a small Assay API running as a Neon Function in AWS US East (Ohio), with the data stored in Neon Postgres in the same region. The demo itself sends nothing: alerts, decisions and any model key you add stay in your browser.
Who processes data
The hosting provider and database provider chosen by the operator of this deployment, Stripe for billing, and, only when a workspace enables a live model, that model provider (Anthropic, OpenAI or Microsoft Azure OpenAI). Enterprise deployments run in the customer's own cloud subscription. The full list is on the security page.
Production data
Do not upload real customer data on the Sandbox plan. Production data is processed only under a signed data processing agreement.