CreatorsTranslatorsPublishersResourcesPricing
Log inContact salesGet started for free

Legal and privacy

The terms and policies that cover your use of Bublate and the pages you upload.

Terms
  • Terms of Service
  • Acceptable Use Policy
  • Affiliate Terms
Privacy
  • Privacy Policy
  • Cookie Policy
  • Data Processing Agreement
Copyright
  • Copyright and takedown

Data Processing Agreement

Effective date: 2026-11-20

This Data Processing Agreement ("DPA") is part of the Terms of Service between Bublate and the customer that uses Bublate for its own work. It applies when Bublate processes personal data for the customer under the GDPR, the UK GDPR, the Swiss Federal Act on Data Protection or a similar law. To get a signed copy, email privacy@bublate.com.

1. Parties and definitions

1.1. Parties. "Customer" means the organization that accepts this DPA. "Processor" means Bublate, 30 N Gould St Ste R, Sheridan, WY 82801, United States, privacy@bublate.com.

1.2. Data protection law. "Data Protection Law" means every data protection law that applies to the processing under this DPA, including Regulation (EU) 2016/679 (GDPR), the GDPR as it applies in the United Kingdom (UK GDPR) and the Swiss Federal Act on Data Protection.

1.3. Other terms. "Personal data", "processing", "controller", "processor", "data subject" and "personal data breach" have the meaning that the GDPR gives them. "Customer Personal Data" means personal data in the content that the Customer uploads to Bublate or makes with it. "Subprocessor" means a third party that the Processor engages to process Customer Personal Data.

2. Roles and instructions

2.1. Roles. The Customer is the controller of Customer Personal Data, and the Processor is its processor. If the Customer is itself a processor for a third party, the Processor is its subprocessor.

2.2. Instructions. The Processor processes Customer Personal Data only on the documented instructions of the Customer. The Terms of Service, this DPA and the settings that the Customer uses in Bublate are those instructions. If the law requires other processing, the Processor tells the Customer first, unless the law forbids it.

2.3. Unlawful instructions. If the Processor thinks an instruction breaks Data Protection Law, it tells the Customer at once.

2.4. Customer duties. The Customer makes sure that it has a legal basis for the processing, and that it gives data subjects the notices that the law requires.

3. Details of the processing

ItemDescription
Subject matterThe Bublate service: reading, translating, cleaning and lettering comic pages, and storing them for the Customer.
DurationThe term of the Terms of Service, and after it until the Processor deletes the data as clause 9 says.
Nature and purposeStorage, text recognition, machine translation, image editing, lettering, display in the editor and export, only to give the Customer the service.
Types of personal dataPersonal data in the pages and the text on them, such as names in credit lines and in the story. Names and email addresses of the users of the Customer's accounts. Records of jobs and credits.
Special categoriesNone are intended. The Customer must not upload special categories of personal data unless it has a legal basis to do so.
Data subjectsUsers of the Customer's accounts, and people named or shown in the Customer's pages.
FrequencyContinuous, while the Customer uses the service.

4. Confidentiality

4.1. People. The Processor lets only people who need it for the service get to Customer Personal Data. Each of them is bound by a duty of confidentiality.

4.2. No training. The Processor does not use Customer Personal Data, or any other Customer content, to train machine translation models or any other models.

5. Security

5.1. Measures. The Processor uses the technical and organizational measures in Annex 1. These measures take into account the risks of the processing, as Article 32 of the GDPR requires. The Processor can change the measures, but not in a way that lowers the overall level of security.

6. Subprocessors

6.1. General authorization. The Customer gives the Processor a general authorization to engage Subprocessors. Annex 2 lists the current Subprocessors.

6.2. Changes. The Processor tells the Customer at least 30 days before it adds or replaces a Subprocessor, by email or by an update to this page. The Customer can object for reasonable data protection reasons within that time, by email to privacy@bublate.com. If the parties cannot agree, the Customer can end the service, and the Processor refunds the credits that the Customer bought and did not use.

6.3. Same duties. The Processor puts data protection duties in a written contract with each Subprocessor that are not less protective than this DPA. The Processor stays liable to the Customer for the work of its Subprocessors.

7. Help to the Customer

7.1. Data subject requests. The Processor helps the Customer answer requests from data subjects to use their rights. If a data subject sends a request to the Processor, the Processor sends it to the Customer. The Processor does not answer it alone, unless the law requires it to.

7.2. Other help. The Processor helps the Customer with its duties under Articles 32 to 36 of the GDPR, as far as the information it has allows. These duties cover security, breach notices, impact assessments and prior consultation.

8. Personal data breaches

8.1. Notice. The Processor tells the Customer without undue delay after it becomes aware of a personal data breach that affects Customer Personal Data. The notice describes the breach, the likely effects and the steps taken, as far as the Processor knows them.

8.2. Steps. The Processor takes reasonable steps to stop the breach and to limit its effects. It gives the Customer the information it needs to notify authorities and data subjects.

9. Deletion and return

9.1. During the service. The Customer can export its lettered pages from the editor at any time. To get any other Customer Personal Data, or to delete a chapter, a series or an account, the Customer emails the Processor. The Processor does it within 30 days.

9.2. At the end. When the service ends, the Processor deletes Customer Personal Data within 30 days, unless the law requires it to keep a copy. If the Customer asks before the end, the Processor first gives back the Customer's files.

10. Audits

10.1. Information. The Processor gives the Customer the information it needs to show compliance with this DPA and with Article 28 of the GDPR.

10.2. Audits. If that information is not enough, the Customer can audit the Processor once a year. An independent auditor bound by confidentiality can do the audit for the Customer. The Customer gives at least 30 days of notice, and the audit takes place in normal working hours. The Customer pays its own costs. The Processor can meet a request with reports from its Subprocessors where those reports cover it.

11. International transfers

11.1. Transfers. The Processor is in the United States, and its Subprocessors process data in the United States and other countries. This section applies when Customer Personal Data moves from the European Economic Area, the United Kingdom or Switzerland to a country without an adequacy decision.

11.2. Standard Contractual Clauses. The Standard Contractual Clauses of the European Commission (Decision 2021/914), Module 2 (controller to processor), are part of this DPA. Where the Customer is a processor, Module 3 (processor to processor) applies instead. The Customer is the data exporter and the Processor is the data importer. For the clauses:

  • Clause 7 (docking clause) applies.
  • Clause 9: option 2 (general authorization) applies, with the notice time in clause 6.2 of this DPA.
  • Clause 11: the optional language does not apply.
  • Clause 17: option 2 applies. The clauses are governed by the law of the EU Member State where the data exporter is established. If that law does not allow for third-party beneficiary rights, the law of Ireland applies.
  • Clause 18: the courts of that same Member State.
  • Annex I: section 1 and section 3 of this DPA. The competent supervisory authority is the one of the Member State where the data exporter is established.
  • Annex II: Annex 1 of this DPA. Annex III: Annex 2 of this DPA.

11.3. United Kingdom. For transfers from the United Kingdom, the International Data Transfer Addendum of the UK Information Commissioner (version B1.0) amends the clauses above. Its tables use the details in this DPA.

11.4. Switzerland. For transfers from Switzerland, the clauses above also apply. References to the GDPR mean the Swiss Federal Act on Data Protection, and the competent authority is the Swiss Federal Data Protection and Information Commissioner.

11.5. Order of precedence. If this DPA and the Standard Contractual Clauses conflict, the Standard Contractual Clauses apply.

12. General

12.1. Precedence. If this DPA and the Terms of Service conflict about personal data, this DPA applies.

12.2. Liability. The limits on liability in the Terms of Service apply to this DPA, to the extent Data Protection Law allows.

12.3. Term. This DPA applies for as long as the Processor processes Customer Personal Data.

Annex 1. Security measures

  • Encryption in transit. All traffic to bublate.com uses HTTPS. The processing service reaches the file storage and the model providers over HTTPS. The app reaches the processing service inside the Cloudflare network.
  • Encryption at rest. Cloudflare encrypts the database (D1) and the file storage (R2) at rest.
  • Access control. Each request for app data must carry a valid session from Clerk. The app checks that each chapter, file and job belongs to the account that asks for it.
  • Service credentials. Each call from the app to the processing service carries a secret token. Keys and tokens are kept as platform secrets, not in the source code.
  • Signed payment events. The app accepts payment events from Polar only with a valid signature that is less than 5 minutes old.
  • Temporary copies. The processing service deletes its working copy of a chapter after each step.
  • Data minimization. Model providers get page images and text, not account names, email addresses or payment data.
  • One job per instance. The processing service runs on container instances, and one instance runs one translation job at a time.
  • Staff access. Only people who need it for the service can get to Customer content.

Annex 2. Subprocessors

SubprocessorServiceDataLocation
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 policyGlobal 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 emailsYour email address and the email, while it is sentUnited States
OpenRouter, Inc.Sends each model request to the model provider that runs the modelPage images, text read from the pages, translations, series bible, notes you write for a translationUnited States
Google LLCGemini models: find and read text, read sound effects, check letteringPage images and text, as aboveUnited States
OpenAI, L.L.C.GPT models: read text, translate, check letteringPage images and text, as aboveUnited States
Anthropic, PBCClaude models: series bible, translation, editing, reviewPage images and text, as aboveUnited 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 aboveDepends 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 securityUnited 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 belowUnited 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 inUnited States
PolarPayments, as merchant of record (polar.sh)Name, email address, billing address, payment details, purchase historyPolar's own locations, see polar.sh

Bublate

Product

  • Lettering
  • Sound effects
  • Editor
  • Pricing
  • Release notes

Use cases

  • Manga translation
  • Manhwa translation
  • Webtoon translation
  • Manhua translation
  • Comic lettering
  • Sound effect translation
  • Localization
  • Manga typesetting
  • Manga cleaning
  • Comic translation

Resources

  • Resource library
  • Blog
  • Research
  • Guides
  • Sound effect dictionary
  • Glossary
  • Languages
  • Alternatives
  • Free tools

Company

  • About
  • For creators
  • For translators
  • For publishers
  • Help center
  • Security
  • Press
  • Affiliates
  • Contact sales
  • Contact
© 2026 BublateTermsPrivacyCookiesCopyrightCreditsSitemap