Privacy Policy
Effective date: 2026-11-20
This Privacy Policy says what personal data Bublate collects, why, who gets it, how long we keep it and what rights you have. Words with a capital letter, such as "Pages", "Output" and "Your Content", have the meaning that the Terms of Service give them.
1. Who we are
1.1. Controller. Bublate is the controller of the personal data in this policy. Contact: Bublate, 30 N Gould St Ste R, Sheridan, WY 82801, United States, privacy@bublate.com.
1.2. When we are a processor. If an organization uses Bublate for its own work and signs our Data Processing Agreement, that organization is the controller of the personal data in its content. We process that data for it, as that agreement says.
2. What we collect
2.1. Account data. Your name and email address. Clerk, our sign-in provider, holds your password in hashed form. We never see it. If you sign in with Google, LINE or Kakao, that service gives Clerk your name, email address and profile picture. Our database keeps your account ID, name, email address and the date you joined. We use your email address to sign you in, to send the emails in section 2.12 and to answer you. Free credits come once per email inbox (Terms 2.5), so we also keep a one-way code made from your address with a secret key. The code cannot be turned back into the address. We use it only to see whether an inbox already had free credits.
2.2. Your Content. The Pages you upload, the text that the Service reads from them, the translations, the cleaned images and lettering layers, the series bible (with the character pictures you add to it and the notes you paste to import into it), your edits, notes you write for a chapter or when you translate a line again, images you place or replace, series and chapter titles, credit lines, folder names and saved text styles. Pages can contain personal data, for example a name in a credit line.
2.3. Credit and payment records. Your credit balance, your free credits left, and a record of each chapter you start with its price in credits, each refund and each purchase. For each purchase, Polar tells us the order number, the product, the number of credits, the amount and the currency. Polar collects your payment details. We do not receive your card number.
2.4. Job records. For each translation: the languages, the status, the progress, error messages, the review state and records of the requests to model providers (which model ran and what it cost).
2.5. Technical data. Cloudflare logs each request to bublate.com: the IP address, the browser, the address of the page and the time. The app writes error messages to these logs, and it sends error reports to Sentry and PostHog (section 2.10). Clerk records the IP address and device of each sign-in, to keep accounts safe.
2.6. Team data. If you invite people to your workspace, we keep the email address of each invite, the role of each member, comments and mentions, page assignments and the steps each member marks done.
2.7. Messages and feedback. If you email us, we keep the email and our reply. From time to time the app asks how Bublate works for you. If you answer, we keep your rating, what you write, how many chapters you had finished and the chapter you had open, so we can improve the Service. If you close the request, we keep only that you closed it. We delete your feedback when you delete your account.
2.8. Website analytics. On the marketing pages of bublate.com (not in the app), we count visits with PostHog, without cookies and without browser storage. The page sends its address (without the query, except campaign tags such as utm_source), the referring site, the browser, the device type, the page language and the country (from Cloudflare). It also sends a click on a sign-up button, with the name of the page. Your IP address goes to PostHog only to compute a visitor count that resets every day, and PostHog does not store it. Do Not Track and Global Privacy Control turn this off. We use these counts to see which pages people read and which ones lead to sign-ups.
2.9. Product analytics in the app. In the app, we record the steps you take with PostHog, so we can see which features people use and where they get stuck. An event names the step (for example "upload completed" or "export completed") and carries counts, sizes, formats, languages and times. It is linked to your Bublate account id, not to your name or email address. It never holds your pages, the text on them, a translation, a file name or your email address. The app sends the events through bublate.com and stores no cookie and nothing in your browser for this. Do Not Track and Global Privacy Control turn these events off.
2.10. Error reports. When something fails in the website, the app or our servers, we send an error report to Sentry and to PostHog, so we can find and fix the fault. A report holds the error and the place in our code where it happened, the page address, the browser and device, the IP address and request headers, and your account id when you are signed in. A report never holds your pages, the text on them or a translation. Error reports are needed to keep the Service working, so Do Not Track does not turn them off.
2.11. What we do not collect. We use no tracking pixels and no advertising cookies, and we record no sessions. We do not follow you across other websites. The only data an ad network gets from us is in section 2.18. Our Cookie Policy lists every cookie we use.
2.12. Emails we send. We email you when your account starts, when chapters are ready or fail, when a teammate mentions you, when credits reach your account and when you delete your account. We email an invite to the address a workspace owner enters. We also send a few tips and reminders about your own use of Bublate, each at most once: a day after sign-up if you have not uploaded a chapter, 3 days after sign-up if your free credits are unused, 2 days after your first chapter is ready if you have not exported it, a day after a chapter if your credits are low, when your monthly plan ends, and after 30 days without a visit, with what changed in Bublate. To send them, we use your account dates, your credit balance, your plan and whether you exported a chapter, and we keep a record of which of these emails we sent. An email holds names, chapter titles and, for a mention, the comment. It never holds your pages or their text. You can turn off the chapter and mention emails, and the tips and reminders, in Settings, Account. Each tips and reminders email also has a link to unsubscribe.
2.13. Sales enquiries and newsletter. If you send the sales form, we keep your name, email address, company, what you need, your chapters a month, your languages, your message and the page you sent it from. If you subscribe to the newsletter, we keep your email address, the page and the time. We then email you a link to confirm, and you get the newsletter only after you click it. We keep the time you confirmed as a record of your consent, and which newsletters we sent you. We email each sales form, and each confirmed subscriber, to our own sales, billing or general address so we can answer it. To stop spam, we also keep a one-way code made from your IP address, which we use only to limit how many forms one address can send in an hour. We use this data only to answer you and, for subscribers, to send the newsletter. Every newsletter has a link to unsubscribe, or email us to remove your address.
2.14. Invites, partners and gifts. If you sign up through an invite link or a partner link, we record which account or partner the link belongs to, its code and the free credits it gave. The person who invited you sees only how many people joined and how many were rewarded, never who. If you apply to the affiliate program, we keep your name, email address, the link to your site or channel, what you wrote about your audience, our decision and, to stop spam, the one-way code of your IP address from section 2.13. For an approved partner, we keep a record of each paid order of the accounts they brought (its date, the amount and the commission) and of each payout. To pay a partner, we give their name and payment account to Wise or PayPal. The partner sees these dates and amounts, never a name or an email address. If you buy credits as a gift, we keep the email address you enter and send one email to it, with the gift link and your name. The person who adds the gift to an account becomes its holder.
2.15. Share links. If you turn on a share link for a chapter, we keep a copy of its translated pages and a preview image, the link, who turned it on, when that person confirmed the rights to show the chapter publicly, the end date and a count of views. Anyone with the link can see the pages, the series and chapter titles, the language and the series credit line. The link does not show your name or email address. For people who open a link, we count the view and the click on the sign-up button. These events go to PostHog with the link id, not with an id for the reader, and Cloudflare logs the request as section 2.5 says. The page uses no cookies and no scripts.
2.16. Assistants and tools you connect. You can connect an assistant (such as Claude or ChatGPT) or an automation tool (such as Zapier or n8n) to your account through our MCP server or our API. With an assistant, you sign in through Clerk, and Clerk records which app you allowed and gives it a token for your account. With a tool, you give it an API key. The app or tool then sends us the requests you ask for, and we answer with data from your account: series and chapter titles, page counts, status, prices, your credit balance and download links that work for one hour. The privacy policy of the assistant or tool covers what it does with our answers. If you give us links to pages, we fetch those images from the addresses you give and keep them as Your Content. We record each request in our product analytics (section 2.9) with the name of the step, its result, its duration and the name the app gives for itself. To disconnect, remove Bublate in the assistant, or revoke the key in the app under API and webhooks.
2.17. First touch. When you create an account, we keep where your visit to bublate.com started: the first page you opened, the campaign tags in its address (such as utm_source and from), the name of the website that sent you (only its host name, such as google.com, never the page), the sign-up button you used, the country of your visit (from Cloudflare) and, if an ad sent you, the ad click id in the address (such as gclid from Google, fbclid from Meta, ttclid from TikTok or rdt_cid from Reddit). Your browser keeps this in memory while you move between our pages, with no cookie and nothing stored in the browser, and sends it only when you create the account. If you are in the European Economic Area, the United Kingdom or Switzerland, the sign-up form asks first with a box that is not ticked, and if you do not tick it we keep none of this. We use it to see which pages, websites and ads bring people who sign up and buy, and we add your first page and its channel to the product events of section 2.9.
2.18. Ad measurement. If an ad on Google, Meta (Facebook and Instagram), TikTok or Reddit sent you to us, we tell that ad network, from our server, when you sign up and when you pay. We send the ad click id from section 2.17, the kind of event, an event number, the amount and currency of a payment, and one-way SHA-256 codes made from your email address and your account id. We send nothing to a network that did not send you, and no browser pixel or ad cookie runs on our pages. The network uses this to count which of its ads bring customers, under its own terms. We do not send it if you turned off Ad measurement in Settings, Account, if your browser sends Global Privacy Control, or, in the European Economic Area, the United Kingdom, Switzerland, South Korea, Japan, China and Turkey, if you did not tick the box when you signed up.
3. Why we use it
| Purpose | Data | Legal basis (GDPR and UK GDPR) |
|---|---|---|
| Run your account and sign you in | Account data, technical data | Contract |
| Read, translate and letter your Pages, and keep them in your library | Your Content, job records | Contract |
| Count free credits, charge credits, give credits back when a job fails | Credit and payment records | Contract |
| Sell credits and keep accounting records | Credit and payment records | Contract, legal obligation |
| Keep the Service secure, stop abuse of free credits, fix errors | Account data, technical data, job records, error reports (section 2.10) | Legitimate interests |
| Count visits to the marketing pages and see which pages lead to sign-ups | Website analytics data (section 2.8) | Legitimate interests |
| See which features of the app people use and where they get stuck | Product analytics data (section 2.9) | Legitimate interests |
| Send tips and reminders about your own use of Bublate (section 2.12) | Account data, credit and payment records, job records | Legitimate interests (you can turn them off at any time) |
| See which pages, websites and ads bring people who sign up and buy | First touch (section 2.17) | Consent in the European Economic Area, the United Kingdom and Switzerland. Legitimate interests elsewhere |
| Tell an ad network that its ad brought a sign-up or a payment | Ad measurement data (section 2.18) | Consent where section 2.18 names the place. Legitimate interests elsewhere, and you can turn it off |
| Send the newsletter (section 2.13) | Email address, confirm and send records | Consent (you confirm by email, and you can unsubscribe at any time) |
| Give invite credits, pay partners their commission and deliver gifts (section 2.14) | Account data, credit and payment records, affiliate applications | Contract, legitimate interests |
| Answer your messages and give support | Messages, and the data the question is about | Contract, legitimate interests |
| Handle rights complaints and legal requests | The data the complaint or request is about | Legal obligation, legitimate interests |
3.1. No training. We do not use Your Content to train machine translation models or any other models.
3.2. No sale. We do not sell personal data. The only data we share for advertising is the ad measurement in section 2.18, and you can turn it off.
3.3. Who sees Your Content. Your Content is private to your account and to the members you invite to your workspace. The owner of a workspace and its members can see the work, the comments and the names and email addresses of the other members. If you turn on a share link (section 2.15), anyone with the link can read that chapter until the link ends. Our staff look at it only for these reasons: 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.
4. What the model providers get
4.1. What we send. To read and translate a chapter, the Service sends parts of your Pages to model providers through OpenRouter. This includes page images, close crops of sound effects, a few key panels for the series bible, the text read from the pages, draft translations, the series bible with its character pictures, notes you write for a chapter or a translation, and the notes you paste to import into the series bible.
4.2. What we do not send. We do not send your name, your email address or your payment data to model providers. The removal of the original lettering from the art runs on our own processing service at Cloudflare, not at a model provider.
4.3. Their terms. OpenRouter and each model provider process the data under their own terms. These terms can let them keep request data for a limited time, for example to check for abuse.
5. Who gets your data
We give personal data only to the service providers below, and only so they can do their part of the Service.
| Provider | What it does for us | Data it gets | Where |
|---|---|---|---|
| Cloudflare, Inc. | Hosting of the website and the app (Workers), page processing (Containers), the account database (D1), file storage (R2) and sending our emails (section 2.12) | All data in this policy | Global network, United States |
| Convex, Inc. | Runs our email system, which hands each email to Cloudflare to send (section 2.12). It keeps send counts, not the emails | Your email address and the email, while it is sent | United States |
| OpenRouter, Inc. | Sends each model request to the model provider that runs the model | Page images, text read from the pages, translations, series bible, notes you write for a translation | United States |
| Google LLC | Gemini models: find and read text, read sound effects, check lettering | Page images and text, as above | United States |
| OpenAI, L.L.C. | GPT models: read text, translate, check lettering | Page images and text, as above | United States |
| Anthropic, PBC | Claude models: series bible, translation, editing, review | Page images and text, as above | United States |
| Alibaba (Qwen models) | Backup model for reading text, used only when the main model fails. OpenRouter can send these requests to Alibaba Cloud or to another host of the same model. | Page images and text, as above | Depends on the host |
| Clerk, Inc. | Accounts, sign-in, verification emails, sign-in for assistants you connect (section 2.16) | Name, email address, password (Clerk stores it in hashed form), Google, LINE or Kakao profile if you sign in with one, IP address and device data for security | United States |
| PostHog, Inc. | Website analytics for the marketing pages, without cookies (section 2.8). Product analytics in the app (section 2.9). Error reports (section 2.10) | Website: page address without its query (campaign tags kept), referring site, browser, device type, language, country, and the IP address only to compute a daily visitor count (PostHog does not store it). App: your account id, the steps you take and their counts, sizes, languages and times. Error reports: as for Sentry below | United States |
| Functional Software, Inc. (Sentry) | Error reports from the website, the app and our servers (section 2.10) | The error and the place in our code where it happened, the page address, the browser and device, the IP address and request headers, and your account id when you are signed in | United States |
| Polar | Payments, as merchant of record (polar.sh) | Name, email address, billing address, payment details, purchase history | Polar's own locations, see polar.sh |
5.1. Other cases. We also share data when the law requires it or to answer a valid legal request. We share it to protect the rights and safety of people or of the Service. We can also share it as part of a merger or a sale of the Service. In a sale, the buyer must follow this policy for the data it gets.
5.2. Ad networks. Google LLC, Meta Platforms, Inc., TikTok and Reddit, Inc. get the data in section 2.18, only when their ad sent you and only as that section says. They are not our service providers: each one uses the data as a separate controller under its own privacy policy.
6. Transfers out of your country
6.1. United States. We are a United States company, and most of our providers process data in the United States. If you are in the European Economic Area, the United Kingdom or Switzerland, we transfer your data under the Standard Contractual Clauses of the European Commission and the UK Addendum. Where a provider takes part in the EU-US Data Privacy Framework, the transfer can also rely on that framework.
7. How long we keep it
7.1. While your account is open. We keep your account data, Your Content and your job records while your account is open. The Service does not delete them by itself.
7.2. Deletion. The owner of a workspace can delete a chapter or a whole series in the library (Delete chapter, Delete series), and you can delete your whole account in Settings, Delete account. The database rows go at once, and the files of the deleted work leave our storage within minutes. You can also email privacy@bublate.com from the address of your account, and we delete the data within 30 days. Records we must keep stay, as section 7.4 says.
7.3. Temporary copies. While a job runs, the processing service keeps a working copy of the chapter. It deletes that copy when each step finishes.
7.4. Records we keep longer. After an account closes, we keep purchase records for as long as tax and accounting law requires. We keep records of rights complaints and of breaches of our Acceptable Use Policy for as long as we need them to handle claims and repeat infringers.
7.5. Logs. Cloudflare keeps request logs for a few days and then deletes them.
7.6. Analytics and error reports. Sentry keeps error reports for 30 days. PostHog keeps product analytics events and error reports for up to 7 years. These records hold your account id, not your name or email address. To have them deleted, email privacy@bublate.com.
7.7. Sales enquiries and newsletter. We keep a sales enquiry for up to 3 years after our last contact with you. We keep a newsletter address while you are subscribed. When you unsubscribe, we stop at once and keep only the address and the time you unsubscribed, so no later newsletter reaches it. A sign-up that you never confirm gets no newsletter. To have your address deleted completely, email privacy@bublate.com.
7.8. Free credit codes. We keep the one-way code from section 2.1 after an account closes, so a deleted account cannot sign up again for more free credits. It holds no address and no account id.
7.9. Invites, partners and gifts. We keep invite records after an account closes. They hold account ids and credit counts, not names or addresses, and they stop a closed account from earning a second reward. We keep partner records, commissions, payouts and gifts as payment records for as long as tax and accounting law requires. We keep a rejected affiliate application for up to 1 year, then we delete it.
7.10. Share links. When you turn off a share link, we delete its copy of the pages within minutes. We keep the record of the link (who turned it on, when, and the rights confirmation) while the chapter exists, because it can matter for a rights complaint. When you update a link, we delete the copy it showed before. Deleting the chapter or the account deletes the link and its pages.
7.11. First touch and ad measurement. We keep the first touch from section 2.17 while your account is open and delete it with the account. We delete ad click ids 90 days after you sign up. We keep a record of each event sent to an ad network, so we never send it twice, and delete it with the account. When you sign up, the first touch also passes through Clerk, and we remove it there once our database has it.
8. Security
8.1. What we do. All traffic to bublate.com uses HTTPS. Each request for app data must carry a valid session. The app checks that each chapter, file and job belongs to the account that asks for it. Cloudflare encrypts the database and stored files at rest. Payment events from Polar must carry a valid signature. No system is fully secure, so we cannot promise that your data is never exposed.
8.2. Breaches. If a breach puts your personal data at risk, we tell you and the authorities as the law requires.
9. Your rights
Depending on where you live, you can ask us to:
- tell you what personal data we hold about you, and give you a copy.
- correct data that is wrong.
- delete your data.
- give you your data in a common machine-readable format, or send it to another service.
- stop or limit some uses of your data, and object to uses that rely on our legitimate interests.
9.1. How to ask. Email privacy@bublate.com from the address of your account. We answer within 30 days. We may need to check that the request comes from you. We do not charge for a request, unless it is clearly excessive.
9.2. Complaints. If you are in the European Economic Area or the United Kingdom, you can complain to the data protection authority where you live. Please talk to us first, so we can try to fix the problem.
9.3. California and other US states. California residents have the right to know, delete and correct their personal information, and to not be discriminated against for using these rights. We do not sell personal information. The ad measurement in section 2.18 can be "sharing" for cross-context behavioral advertising under the California Consumer Privacy Act, and "targeted advertising" under the laws of other US states. To opt out, turn off Ad measurement in Settings, Account, or use Global Privacy Control: we treat it as an opt-out for your browser and your account, and Settings shows when it turned ad measurement off. You can also email us.
10. Children
10.1. Age. Bublate is not for children under 16. We do not knowingly collect personal data from children under 16. If you think a child gave us personal data, email us and we will delete it.
11. Changes
11.1. Updates. We update this policy when what we do with data changes. We show the effective date at the top. If a change is material, we tell you by email or in the app before it takes effect.
12. Contact
Bublate, 30 N Gould St Ste R, Sheridan, WY 82801, United States. Email: privacy@bublate.com.