Trust is earned.
We accept it in $5 increments. This page describes how BRAIAIN Laboratories protects your data, which is easy, because we have almost none of it.
Compliance
None of these are real certifications. The security facts below are.
Security, honestly
- No servers. The site is static files on GitHub Pages. There is nothing running for anyone to break into.
- No accounts and no passwords. You cannot sign in, so your password cannot leak.
- The chat runs in your browser. brAIAIn is rebuilt on your device from public files. Nothing you type is sent to us.
- Payments are handled by Stripe. We never see your card. Stripe keeps your email for the receipt; the public site stores only your sentence and the credit name you chose.
- Everything else is public on purpose. The code, the model and the training data are public domain, so anyone can audit every line. Several people could.
Subprocessors
| Service | Used for |
|---|---|
| GitHub | Hosting the site, and running the training job |
| Stripe | Payments and receipts |
| Google Analytics | Counting visits (two cookies) |
| Google Fonts | The typeface |
| Hugging Face | A public mirror of the model, its training data and a chat demo |
| Gmail | Operational email, such as review notices |
Penetration testing
Our most recent penetration test was conducted by Gerald Honk, Chairman, who walked across the keyboard. No vulnerabilities were found. Several files were renamed.
Uptime
Our uptime is GitHub's uptime. The training job is scheduled every ten minutes and sometimes runs late. Live numbers are on the Status page, which is honest about what it has not checked.
Compliance documents
Enterprise customers may request our SOC 0 report by emailing hello@braiain.com. It is a blank page, signed by the board.
Responsible disclosure
Found a real security problem? Email hello@braiain.com. We will fix it, thank you, and credit you in the next release notes if you want.