How we protect your account and your work

What protects you today

• Signing in

  Passwords go straight from your browser to our sign-in provider, which keeps only a salted hash; our own code never receives them. You can sign in with Google instead. Requests from your account carry a signed session token, which our servers check before anything is read or changed.

• Your projects stay yours

  The API checks every request against the account that made it before it touches a project, a credit balance or a payment. Underneath, row-level security is on for every table the application stores data in, and a test fails our build if a new table ships without it.

• Files and links

  Uploads and renders are stored at long, unlisted addresses that include your account’s random ID. Nothing lists or indexes them, but a link opens for whoever has it, like an unlisted video, so share links only with people you trust. Downloads use signed links that expire within an hour.

• In transit

  The site and the API are served only over HTTPS, and browsers are told to refuse plain HTTP to us for a year. Other sites cannot show our pages inside a frame.

• Payments

  Card payments are taken on our payment partner’s checkout. Card numbers never reach our servers: we keep the last four digits and the partner’s reference.

• Your content is not training data

  We do not use your scripts, uploads, voices or renders to train AI models, and we do not share them with third parties.

• Access on our side

  Our admin tools need an admin role that the API checks on every call. Credit changes, refunds, account bans and settings changes are written to an audit log with who made them.

• Abuse protection

  Free credits arrive only once an email address is confirmed, sign-ups from throwaway email domains are refused, and the API limits how fast any one client can call it.