Data processing agreement
Last updated 31 July 2026 · forms part of the Terms
Applies when your Mycel business processes personal data belonging to your customers. You are the controller. We are the processor. Signed copy on request: legal@mycelai.dev.
Scope
| Subject matter | Running the AI service business you configure. |
| Duration | The life of your account, plus 30 days. |
| Nature | Storage, retrieval, model inference, and outbound actions you approve. |
| Data types | Whatever your wedge handles — typically names, contact details, and business records such as invoices or transactions. |
| Data subjects | Your customers and their staff. |
Our obligations
- Process only on your documented instructions — which, in practice, are the wedge and schedules you configure.
- Keep anyone with access under confidentiality.
- Apply the measures below.
- Not engage a sub-processor without 30 days' notice, and you may object.
- Help you answer data-subject requests. Export and deletion are API calls, so you mostly won't need us.
- Notify you of a breach within 72 hours of awareness.
- Delete or return everything on termination.
Security measures
Specific rather than reassuring, because a list of adjectives isn't auditable:
- Credentials encrypted at rest with AES-256-GCM under a key held outside the database. A stolen database dump yields ciphertext. Verified by inspecting a real dump.
- Credentials never reach the model. The agent runs in a sandbox and receives opaque handles; our harness holds the secrets and makes every privileged call.
- Tenant isolation enforced at a single code path that fails closed, with tests that attempt cross-tenant access and assert refusal.
- Per-customer isolation — a credential belonging to one of your clients cannot be used on another's work, and naming it explicitly does not override that.
- Tamper-evident audit — hash-chained and append-only. Editing history breaks the chain and a verify endpoint reports where.
- Encryption in transit — TLS 1.2+ everywhere.
- Least privilege — the database is reachable only by the kernel; the kernel is not reachable from the internet.
These are properties of the open-source kernel, so you can read them rather than take our word: github.com/mycelhq/mycel.
Sub-processors
Listed in the privacy policy, with location and purpose.
International transfers
Customer data rests in the UK — AWS and Supabase, both London. London is eu-west-2 by name and outside the EEA in law, so we say UK rather than EU. Model inference, the run sandbox, brokered connections, transactional email, crash reporting and — if the visitor accepts the cookie banner — marketing-site analytics are US providers; those transfers rely on the EU-US Data Privacy Framework, Standard Contractual Clauses and the UK Addendum. Analytics never carries customer data: it sees a page path and a setup step against an internal id, and it is switched off entirely unless consent is given. If you need inference or the sandbox to stay in the UK or the EEA, that is a configuration change — ask us.
Audits
Once a year on 30 days' notice, or sooner if a regulator requires it. We'll answer questionnaires, and the kernel being open source usually answers most of them faster than we can.
What we are not built for
Mycel has no data classification layer. Nothing distinguishes a health record from a shipping address, so there is no field-level redaction and no per-field residency. Do not use it for special-category data. We would rather lose the deal than have you assume otherwise.