Accounts
Workbench accounts use their own sessions. Plans are tied to a single account and can only be activated by a confirmed payment or a verified administrator action with a unique payment reference.
Data and APIs
Passwords are hashed with bcrypt, sign-in cookies are HttpOnly, and write requests check that they come from this site. Reading, deleting and exporting records checks account ownership. Credit deductions use conditional database updates inside transactions, so a repeated request is never charged twice. Model and payment credentials stay on the server.
Usage limits
Input length, image size, output tokens and request rates are all capped. Failed runs are refunded, and a model without vision support never pretends to have looked at an image. There's no promise of unlimited AI, zero risk or end-to-end encryption.
Current limitations
MFA, email recovery and Etsy OAuth aren't offered. Payments are handled by Stripe; we never see or store card numbers. Account and data requests are verified and handled manually. To report a security issue, contact support — never send passwords, tokens, cookies or customer data.