Skip to content

Security

Your data sits in Germany, and nothing trains on it.

Every agent runs in its own sandbox, every Company on its own storage. What follows is the detail — including the certifications we have not been issued yet.

Data handling

We do not train models on your data. Agent conversations are forwarded to the model provider you selected in order to generate a response, and nothing else happens to them.

If you bring your own API key, we use it only to route your request to the provider you chose. That content is not trained on, not resold, and not used anywhere outside the request path and your own Company history.

Isolation

Each quest runs in its own git worktree. Tool calls execute inside a per-agent sandbox (bwrap on Linux) against an explicit allow-list of filesystem, network, and process access. Agents from different Companies share no working directory and no execution context.

Traffic is encrypted in transit with TLS 1.2 or better, and managed databases are encrypted at rest. Companies run on dedicated workspace storage — there is no shared tenancy at the data layer.

Authentication

Sessions are short-lived JWTs that expire on their own. Passkeys (WebAuthn) are on the 2026 roadmap. SAML SSO and SCIM provisioning are available to enterprise customers on request.

Subprocessors

These third parties process data on your behalf so the platform can run: Hetzner, Stripe, OpenRouter, Resend, and Plausible (self-hosted). What each one does, which region it processes in, and exactly what of yours reaches it are published on Subprocessors — a stable URL your data processing agreement can cite and your team can watch for change.

Compliance

GDPR today, with a DPA available on request for paid plans. Hosting is in Germany, and EU data residency and private deployment are both available to teams with stricter requirements.

SOC 2 and ISO 27001 are in flight but have not been issued. We will publish the report dates here when they exist and not a day before — if a badge appears on this site, it is a fact rather than an intention. If your procurement process needs one of them today, write to us and we will scope the deployment path that works instead.

DPAs, security questionnaires, and subprocessor questions: luca@aeqi.ai.

Private deployment

Hosted early access is the default path. A private deployment keeps agent state, event logs, and model traffic inside infrastructure your own Company has approved.

On-chain data

Tokenized cap-table state is written to a public chain. It is immutable and cannot be redacted afterwards, so tokenize only what you are content to make public permanently.

Reporting a vulnerability

Send it to luca@aeqi.ai with reproduction steps and your estimate of severity. First response within two business days. Please hold off on publishing until a fix has shipped.

Cookies for sign-in and analytics. No third-party tracking.