Skip to content
aidramabuilder

Legal

Security

Last updated Nov 8, 2026

Your scripts and unreleased episodes are commercially sensitive. This page describes what we do to protect them, in plain terms, and what we do not claim.

1. Account protection

Passwords are stored as PBKDF2 hashes with a per-user salt; we never store or log plaintext passwords.

Sessions use HttpOnly, Secure, SameSite cookies with signed payloads, and are invalidated on password change.

Administrative access requires a separate token and is rate-limited and audit-logged.

2. Data in transit and at rest

All traffic is served over TLS 1.2 or above; HTTP is redirected and HSTS is enabled.

Assets are stored in object storage with per-account path isolation. Signed URLs expire, so a shared link cannot be used indefinitely.

Database backups are encrypted at rest and retained for 30 days.

3. Isolation between customers

Every query is scoped to the authenticated account. There is no shared project namespace.

Generation providers receive the minimum input required for a job — shot prompt and reference images — not your account identity or billing data.

Your content is not used to train models unless you explicitly enable it in account settings.

4. Payments

Card data never touches our servers. Checkout is hosted by Creem or Paddle, both PCI-DSS compliant, and we receive only a transaction reference and status.

Crypto payments are verified on-chain against a per-order address and amount; we do not custody your funds.

Webhook payloads are signature-verified before any credit is granted.

5. What we do not claim

No service is perfectly secure. We do not claim ISO 27001 or SOC 2 certification.

We do not offer a contractual uptime SLA on the self-serve plans. Enterprise agreements can include one.

We cannot protect content you publish publicly or share via an expiring link that someone else has already downloaded.

6. Reporting a vulnerability

Email [email protected] with reproduction steps. We acknowledge within two business days.

Please do not test against other customers’ accounts, run denial-of-service tests, or access data that is not yours.

We do not currently run a paid bounty programme, but we credit researchers who report in good faith.

Questions about this document? Write to [email protected]. This page is provided in English; translations are offered for convenience and the English version prevails.