AI Optimization Platform
Security & privacy

Designed for multi-tenant production from day one.

A summary of the controls built into the platform today. We describe what exists — certifications such as SOC 2 are on our roadmap, not claimed.

Tenant isolation

Every project-scoped request is resolved through organization membership. Cross-tenant access returns “not found” so existence isn’t leaked — covered by automated tests.

Role-based access

Owner, admin, developer, analyst and viewer roles; a separate platform super-admin. At least one owner is always retained.

Authentication

Argon2id password hashing; short-lived signed sessions in httpOnly, SameSite cookies; secure cookies in production.

API keys

Publishable keys for ingest/config, secret keys for server APIs. Keys are stored as keyed hashes, shown once, rotatable and revocable, with last-used tracking.

Secrets at rest

Provider credentials and webhook secrets are encrypted and never returned by the API after saving.

Encryption in transit

TLS terminated at the edge in production with HSTS; encryption at rest delegated to managed database and disk encryption.

Rate limiting

Token-bucket limits per key and IP on ingest, config, authentication, audit and contact endpoints.

Secure uploads

CSV/XLSX allowlist, size cap, in-memory parsing, never executed. URL checks block private and loopback addresses (SSRF protection).

Audit logging

Authentication, key, approval, experiment, rollback and admin actions are logged with actor, target and details.

Retention & deletion

Per-project retention, retention purges and per-user erasure (GDPR Art. 17) — admin-only and audit-logged.

Child safety

Child-directed projects disable personalized offers, require human approval for monetization changes and hard-block dark-pattern content.

Production guardrails

The API refuses to start in production with default secrets, a development database or debug mode enabled.
Data minimization

We’d rather not have your users’ personal data

  • • Pseudonymous IDs only; PII-looking event properties are stripped on ingest.
  • • No payment card data is accepted anywhere.
  • • Events without analytics consent are discarded.
  • • AI prompts use aggregates only; cloud AI is off by default and requires opt-in.
Responsible disclosure

Found a vulnerability? Please report it through the contact form with the subject “Security”. Please don’t access other customers’ data or degrade the service while testing.