Privacy Policy
Last updated: October 2026
1. What we collect
| Data | Where it comes from |
|---|---|
| Account info (email, hashed password, company name) | Signup / team invites |
| Issue reports (page URL, description) | The embeddable widget |
| Screenshots of the reported page | Captured client-side by the widget at submission time |
| Page content the agent reads while investigating | The agent's own page fetch/Playwright reproduction, at the time it processes a report |
| Integration credentials (WordPress, Jira, Trello, Asana, Slack) | Settings — encrypted at rest, never sent to Claude |
| Usage/cost data (tokens, estimated spend) | Generated internally per request, for the budget feature |
| Billing details (name, billing email, country, order history) | Checkout — card details are collected by Paddle and never reach our servers |
2. How it's used, and who sees it
Issue reports, screenshots, and page content are sent to Anthropic's Claude API so the agent can classify the report and draft a response — Claude acts as a subprocessor for this purpose only, under Anthropic's own API data handling terms. Drafted content/price changes and their originating screenshot are shown to whichever of your teammates has Manager or Admin access, so they can review and approve or reject them.
Payments are handled by Paddle.com, our reseller and Merchant of Record. Paddle collects your payment details and billing address directly at checkout and processes them under its own privacy policy; we receive only the subscription status, plan, and invoice details we need to run your account. We don't sell your data or share it with any other third party.
3. Cookies
WebOps Agent sets exactly one cookie: a signed session cookie that keeps you logged in after you sign in. It's strictly functional — there is no third-party analytics or advertising cookie on this site.
4. Retention and deletion
Your tenant's data is kept for as long as your account exists. From Settings → Danger Zone, an Admin can export everything under your tenant as JSON at any time, or permanently delete the tenant and everything under it (requests, drafts, approvals, integrations, audit log) — this is irreversible.
5. Security
Passwords are hashed (bcrypt), integration credentials are encrypted at rest (Fernet), and every database row is scoped to your tenant — other tenants cannot see your data. Sessions are protected by a signed cookie; we support two-factor authentication (TOTP) for logging in.
6. Your rights
You can access, export, or delete your tenant's data at any time (Settings → Danger Zone) without contacting us. If you have a question we haven't answered here, reach out — see below.
7. Contact
Questions about this policy: echos.solutions@gmail.com