Privacy Notice
Applies to correctover.com and the hosted evidence control plane. Last updated 7 November 2026.
The control plane exists to hold evidence about what your agents did. That means we necessarily store some data about your workspace and the receipts you submit. This page states exactly what is stored, why, for how long, and who else touches it.
1. What we collect
| Category | Content | Why |
|---|---|---|
| Workspace identity | Email address you enter at checkout, plan, subscription status, quota, counters. | Bind receipts to an owner, enforce quota, support key rotation. |
| API credentials | A SHA-256 hash of your API key, plus a short display prefix. The full key is held only long enough for you to reveal it once after payment. | Authenticate requests without keeping a usable copy of the secret. |
| Receipt payloads | Whatever your integration posts: verdict, tool name, correlation id, and any fields you choose to include. | Provide the audit log and usage accounting you subscribed to. |
| Billing records | Customer and subscription identifiers from Stripe, payment status, invoice references. Card numbers never reach us. | Charge the subscription and reconcile entitlements. |
| Operational logs | Request paths, timestamps, status codes, coarse network metadata from our edge provider. | Run the service, detect abuse, debug failures. |
We do not run advertising trackers, we do not sell data, and we do not use receipt contents to train models.
2. What you should not send us
Receipts are evidence records, not a secrets store. Do not put credentials, private keys, full prompts containing personal data, or regulated data categories into a receipt payload. Send a correlation id and a decision, and keep the sensitive artefact on your side.
3. Legal basis and role
For workspace and billing data we act as the party providing the service you subscribed to. For the contents of receipt payloads we act as a processor on your instructions: you decide what to send, we store and return it. Where the law requires a basis for processing, we rely on performance of the subscription contract and on our legitimate interest in operating a secure service.
4. Who else processes data
- Cloudflare — edge delivery, request routing, and the key-value store that holds workspace records and receipts.
- Stripe — card payment, subscription billing, receipts and invoices. Stripe is the merchant of record for card data.
- Email providers — delivery of transactional and support email to the address on the workspace.
We do not share receipt data with third parties for their own purposes. If we are compelled by a lawful order to disclose data, we disclose the minimum required and, where permitted, tell the workspace owner.
5. Retention
- Receipts: retained for the life of the workspace, subject to the retention window of your plan. Deleting the workspace deletes its receipts.
- Workspace record: kept while the subscription is active and for as long as needed to handle billing disputes afterwards.
- API key material: only the hash and display prefix are kept. The revealable key expires 24 hours after issuance.
- Operational logs: short-lived, retained for security and debugging purposes only.
6. Your controls
- Read your own workspace data through
GET /api/v1/receiptswith your API key. - Request export or deletion of a workspace by writing from the account email address.
- Request key rotation from the account email address; rotation invalidates the old key.
7. Security
Traffic is served over TLS. API keys are stored hashed. Workspace records are keyed by email and API key lookups resolve through the hash, so possession of the key is required to read receipts. No system is perfect: if you discover a weakness, report it to the address below rather than testing against other tenants.
8. International transfers
The service runs on a global edge network, so records may be stored or served outside your country. Where that happens, the transfer is covered by the processor terms of the infrastructure providers listed above.
9. Changes
If this notice changes in a way that materially affects what is stored or who receives it, the change is announced on this page and, for active workspaces, by email before it takes effect.
10. Contact
Privacy questions, export requests and deletion requests: [email protected]. We answer from the operator address, and we will ask you to confirm control of the workspace email before acting on a request.
Correctover is an independent project operated by Guigui Wang. It is not affiliated with, endorsed by, or acting on behalf of any standards body.