Skip to main content

​
Trust starts with transparency

The Tuteliq Trust Center at trust.tuteliq.ai is where you can verify our security posture, compliance status, and data handling practices — all in one place.

Visit Trust Center

View real-time security and compliance information at trust.tuteliq.ai

​
What you’ll find

Security Practices

Infrastructure security, encryption standards, access controls, and vulnerability management policies.

Compliance Status

Current compliance posture for enacted law — GDPR, EU Digital Services Act, UK Online Safety Act, and more — plus our coverage of the harm taxonomy in KOSA, still pending US federal legislation.

Sub-Processors

Full list of third-party sub-processors, their locations, purposes, and DPA links.

Data Handling

Retention policies, data minimization practices, and encryption-at-rest and in-transit details.

​
Key commitments

​
What we keep, what we don’t

We operate a content-out, metadata-in pipeline. The distinction matters because everything we say about your data flows from it.

​
What we never store

​
What we do store

One thing: the incident report. It is the model’s response, not your content. It exists so the moderation dashboard has something to show you, which is why it is entirely optional: set incident_moderation_enabled: false on the account or on any single call and nothing is written at all.
Two encryption levels, and the stronger one is yours to switch on. By default the incident record is encrypted at rest with server-side AES-256, which Tuteliq holds the key for. If you register a public key, incident fields are instead wrapped end-to-end so that only you can decrypt them and Tuteliq cannot — a cryptographic guarantee rather than a policy promise.In both cases the underlying content was already discarded, so what is being protected is the model’s assessment, never your users’ messages. And if you would rather nothing were written at all, incident_moderation_enabled: false does exactly that.

​
Your controls

  • Full deletion within 1 hour of a DELETE /account/data request
  • Encryption at rest (AES-256) for all stored metadata
  • End-to-end encryption (opt-in) — register an RSA public key and Tuteliq can no longer decrypt your stored rationales (see below)
  • EU data residency by default; US region on request
  • No cross-customer linking — deployer fingerprints scoped per request
The short version: your users’ content lives in your platform, not ours. Tuteliq holds the analysis outputs your team needs to review — nothing else.

​
End-to-end encryption for stored rationales (opt-in)

By default the metadata fields we retain — LLM rationale, visual description, source data — are encrypted at rest with a Tuteliq-held AES-256 key, then decrypted server-side when your dashboard requests them. This is fast and requires no setup on your side. For customers who want stronger separation, we support customer-managed end-to-end encryption: you generate an RSA keypair, register the public key with Tuteliq, and we use it to wrap every new incident’s metadata. From that point on we cannot decrypt those fields — only your dashboard, holding the matching private key, can. The scheme identifier (TLQ-HYBRID-RSA-OAEP-AES-256-GCM-v1) and key fingerprint are embedded in every encrypted record so you can verify integrity client-side. This is opt-in by design because losing the private key permanently strands every record encrypted under it — Tuteliq cannot recover them. Teams that don’t want that operational burden should stay on the default server-side AES at rest. Teams with stricter compliance requirements (or who want a verifiable cryptographic guarantee that Tuteliq cannot read their rationales) should register a key. Existing incidents written before you register a key remain readable under the server-side scheme; only new incidents use the hybrid scheme.

​
Compliance documentation

The following endpoints are publicly accessible and require no authentication: See the GDPR Compliance page for detailed data subject rights endpoints and consent management.

​
Independent penetration test

Tuteliq’s API was penetration tested by an independent third party (Workstreet) in February 2026, against the production surface at api.tuteliq.ai. Both low-severity findings were closed within two weeks and the fixes verified in production. The one informational finding we did not action was the public exposure of the OpenAPI specification, which is intentional: it is the documentation endpoint this site is built from. The full report is available under NDA. Contact security@tuteliq.ai.

​
Certification

Tuteliq also offers a free certification program for individuals and organizations who want to demonstrate their commitment to child safety. See the Certification page for details, or start directly at tuteliq.ai/certify.

​
Questions

For security inquiries, compliance questions, or to request the penetration test report under NDA, contact security@tuteliq.ai. Vulnerability reports are welcome at the same address; see /.well-known/security.txt.