Company
Security
Your pages are often unpublished work. This page tells you how Bublate keeps them private, what it sends to other companies, how to delete them and what we do not promise.
Table of contents
Where your data lives
Bublate runs on Cloudflare. The website and the app run as Cloudflare Workers. Your account, your workspace and your job records are in a Cloudflare D1 database. The pages you upload, the cleaned images, the lettering layers and the finished pages are files in Cloudflare R2 storage. Chapters process in Cloudflare Containers.
- All traffic to bublate.com uses HTTPS.
- Cloudflare encrypts the database and the stored files at rest.
- The removal of the original lettering from the art runs on our own processing service at Cloudflare, not at a model provider.
- While a job runs, the processing service keeps a working copy of the chapter. It deletes that copy when each step finishes.
Who can see your workspace
Your work is private to your account and to the people you invite to your workspace.
- Each request for app data must carry a valid session. The server checks that each series, chapter, file and job belongs to the workspace that asks for it.
- Image files get the same check. The server finds the workspace that owns the file and checks that you are a member of it.
- An invite link opens only for the email address that the owner invited.
- Roles limit what each member can do. The owner manages members, billing and deletion. Translators and letterers upload, start and edit chapters. Reviewers read, flag and comment, and cannot edit.
Our staff look at your work only to run the service, to give support that you ask for, to handle a rights complaint or a legal request, or to protect the service. Admin access is checked on the person who is signed in, never on a workspace. Each admin action goes into a log with the email address of the admin and a note.
Model providers and training
To read and translate a chapter, Bublate sends page images, crops of sound effects, the text read from the pages, draft translations, the series bible and your translation notes to model providers through OpenRouter. The Privacy Policy names each provider.
- Each request to OpenRouter carries the setting
data_collection: deny. With this setting, OpenRouter sends the request only to providers that do not collect user data. - We do not use your pages to train models. We do not sell personal data.
- We do not send your name, your email address or your payment data to model providers.
OpenRouter and each provider process the requests under their own terms. These terms can let them keep request data for a limited time, for example to check for abuse.
How to delete your data
- A chapter or a series. The owner of the workspace deletes it in the library, with Delete chapter or Delete series. The database records go at once, and the files leave our storage within minutes.
- Your account. Open Settings, Delete account, and type your email address to confirm. This deletes every series, chapter, version, folder, saved style, comment, membership, invite, API key, webhook, workspace font and translation memory line. The files of your work leave our storage within minutes.
- By email. Send a request to privacy@bublate.com from the address of your account. We delete the data within 30 days.
Some records stay after a deletion. Credit and purchase records stay because tax and accounting law requires them, and the account record stays with its name and email address cleared. The translation memory of a workspace stays when you delete one chapter, and the owner clears it in Settings, Translation memory. A series under a takedown stays as evidence. Cloudflare keeps request logs for a few days and then deletes them.
Sign-in, payments and the API
- Clerk runs accounts and sign-in, with an email address and a password or with Google. Clerk keeps your password in hashed form. We never see it.
- A password needs at least 8 characters. Clerk asks for a code from your email when you sign in on a new device, and it checks new sign-ups for bots.
- Clerk records the IP address and the device of each sign-in, to keep accounts safe.
- Polar takes payments as the merchant of record. We do not receive your card number. Payment events from Polar must carry a valid signature.
- For the publisher API, we store only a SHA-256 hash of each key, not the key. Each webhook carries an HMAC SHA-256 signature, so your server can check that it came from Bublate.
Rights reports and takedowns
A rights holder can report a series under our Copyright Policy. A takedown closes the series for its owner and members, and holds its queued jobs. It deletes nothing, so the record stays for the claim and for a restore.
What we do not promise
No system is fully secure, so we cannot promise that your data is never exposed. Bublate has no security audit and no certification, such as SOC 2 or ISO 27001. If a breach puts your personal data at risk, we tell you and the authorities as the law requires.
Organizations that need a written agreement can sign our Data Processing Agreement.
How to report a security problem
Email security@bublate.com with "Security" in the subject. Our contact is also in security.txt. Tell us what you found, the steps to see it again, and the page or the request it affects.
- Test only with your own accounts and your own data.
- Do not read, change or delete the data of other people.
- Do not run denial of service tests and do not send spam.
- Give us time to fix the problem before you publish it.
We do not run a paid bug bounty.