Privacy policy

What we collect

• Account details — your name, email address and a salted hash of your password (never the password itself), your organisation and role.
• What you configure — store addresses, test plans, alert channels, and any test-account credentials you store for a protected store. Stored credentials are encrypted at rest and never shown back in full.
• Run evidence — pages our agents fetched, screenshots, DOM snapshots, step traces and the reports built from them, for the sites you test.
• Traffic events you send — if you connect monitoring ingest, the request metadata your edge forwards (paths, user agents, outcomes). We ask you not to send personal data of your shoppers; configure your feed accordingly.
• Public scans — the URL submitted and a one-way hash of the requester's IP address, used only for rate limiting.
• Billing — handled by Stripe; we store the plan and Stripe's customer and subscription identifiers, not card numbers.
• Technical data — server logs (IP address, user agent, timestamps) kept for security and debugging, and, only if enabled on this deployment, product analytics and error reports.

Why we use it

To provide the Service you signed up for (contract), to keep it secure and prevent abuse (legitimate interest), to bill you (contract), to send service emails such as sign-in links, invites and alerts you configured (contract), and to meet legal obligations. We do not sell personal data and do not use your data or your sites' content to train models.

Who processes it for us

• Cloud hosting and database providers that run the Service.
• Model providers (for example Anthropic, OpenAI or OpenRouter, depending on configuration) — page content from the sites you test is sent to them so simulated agents can act. Your account details are not.
• Stripe, for payments.
• An email delivery provider, for sign-in links, invites and alert emails.
• Slack, when you connect a webhook — alerts are posted to the channel you chose.
• PagerDuty, or a webhook URL you supply, when an alert rule names one — the alert is sent there.
• If enabled on this deployment: PostHog (product analytics) and Sentry (error reports).

Cookies

The dashboard sets an httpOnly session cookie (or an API-key cookie, if you sign in with a key) that is required to keep you signed in. Optional analytics, where enabled, may set their own cookies or local storage; nothing is used for advertising.

How long we keep it

Account data for as long as the account exists. Run evidence and reports for the life of the project unless you delete them; raw monitoring events are pruned on a rolling retention window. Public scan results expire after a short period. When you delete an organisation we delete its data within 30 days, except backups, which roll off on their normal schedule, and records we must keep by law (such as invoices).

Your rights

Depending on where you live you may ask to access, correct, export or delete your personal data, or object to its use. Write to [email protected] and we will answer within 30 days. You may also complain to your local data-protection authority.

Security

Credentials are held server-side and never exposed to browser scripts, stored secrets are encrypted, and access to production systems is restricted. No system is perfectly secure; if we learn of a breach affecting your data we will tell you without undue delay.

Changes

We will post changes here and, for material ones, notify account owners by email before they take effect.