Data minimization by design
PII never leaves your tenant in plaintext. Our engine tokenizes before processing — original values never touch external AI services.
How we protect your data and the PII you entrust to our engine.
PII never leaves your tenant in plaintext. Our engine tokenizes before processing — original values never touch external AI services.
Each key carries a role (admin / service / readonly) and is scoped to a single tenant. Keys are stored as bcrypt hashes — we cannot recover them.
Every mapping, audit log, and usage record is partitioned by tenant_id. Cross-tenant reads are structurally impossible at the database level.
Every API call is appended to a tamper-evident audit log with timestamp, tenant, action, and anonymized payload digest.
All traffic uses TLS 1.3. Databases use encryption at rest. Session cookies are encrypted and marked Secure + SameSite.
API endpoints are throttled per key to prevent abuse. Webhook endpoints verify Stripe signatures to reject forged payloads.
Python and PHP dependencies are scanned with automated tooling on every commit. Critical CVEs trigger immediate patching.
Found a vulnerability? Email [email protected]. We acknowledge within 48 h and aim to patch critical issues within 7 days.