Scope and How to Read This Register

This is Bleanx's single provider register for the Terms of Use, Privacy Policy and Schedule C of the Data Processing Addendum (DPA). It identifies provider services, processing roles, functions and relevant data, and processing locations. Each recipient receives only the data necessary for its stated function. Providers are not given general access to every account or Project merely because they are listed here.

A subprocessor processes Covered Personal Data on the Customer's documented instructions through Bleanx. A processor for Bleanx's independent controller purposes is not automatically a subprocessor under the DPA. A recipient acting for its own purposes remains separately qualified. The same provider can have different roles for different operations. The entries below distinguish those roles; independent uses remain confined to the exceptions in Section 4 of the Terms and the corresponding Privacy disclosures.

Bleanx ensures binding processing arrangements with the correct contracting entities, applicable onward-processing safeguards, and lawful transfer mechanisms under Privacy Section 4 and DPA Schedule D. Bleanx maintains the relevant legal identities, contacts, agreement versions and actual processing locations, makes required information available with the applicable processing disclosures and notices, and supplies copies of safeguards through support@bleanx.org. A primary deployment or sending region is not a promise that every backup, technical record or remote-access operation occurs there.

Application Infrastructure and AI

An external AI action requires the active permission of the user initiating it. Another author's personal AI setting does not, by itself, prevent their shared Project material from being used as permitted context for that action. Shared Project contributions may therefore be processed by the relevant AI provider for permitted actions initiated by other authorized participants even while the contributor's own AI permission is off. This rule does not expand context beyond Terms Section 1, automatically include other users' private histories, or override mandatory personal data processing requirements. The effects of withdrawing permission are described in Privacy Section 5.

Supabase

Role and function: subprocessor for database and object-storage operations involving Covered Personal Data; processor for Bleanx's independent account and operational records to the extent handled on its behalf. Data includes account records, Project materials, personal content, and necessary associated records within each operation's scope.

Location: United States — us-west-1, Northern California, for Bleanx's primary database and Storage deployment. This is the primary deployment, not an exclusive-location commitment for every backup, recovery copy or other operation. Backup and deletion arrangements are governed by Privacy Section 7 and DPA Schedule B6.

Fly.io

Role and function: subprocessor for application hosting and authorized request processing involving Covered Personal Data; processor for Bleanx's independent operational processing to the corresponding extent. Data is limited to the content and technical information necessary for those functions.

Location: United States — San Jose, California, for Bleanx's application servers. Network operations, technical records and remote access are not represented as exclusively confined to San Jose.

Anthropic

Role and function: subprocessor for the inputs, permitted context and generated results of authorized AI actions using its models. Only the provider used for the action receives that action's necessary data. Bleanx ensures the no-training and no-independent-product-development restrictions in Terms Section 4 and DPA Section 4.

Location: Anthropic describes storage in the United States. Its processing arrangements can also route traffic to selected countries in Europe, Asia and Australia under the applicable routing arrangements; United States storage does not mean exclusively United States processing.

OpenAI

Role and function: subprocessor for the inputs, permitted context and generated results of authorized AI actions using its models. Bleanx ensures the no-training and no-independent-product-development restrictions in Terms Section 4 and DPA Section 4.

Location: United States and other countries involved in OpenAI's infrastructure. Regional storage and inference depend on the API configuration, endpoints and supported features; regional controls for customer content do not necessarily cover system data. This entry does not promise a Bleanx-specific regional restriction.

Google — Gemini API, Paid tier

Role and function: subprocessor for the inputs, permitted context and generated results of authorized AI actions through Gemini API, managed through Google AI Studio with active linked billing. This is the Paid tier, not Vertex AI or the unpaid tier. Supplied prompts and responses are not used to improve Google's products under the applicable Paid Services terms; Bleanx also ensures the restrictions in Terms Section 4 and DPA Section 4.

Location: relevant transient storage and caching can occur in countries where Google or its agents maintain facilities. Paid tier does not establish a single-country restriction or zero retention.

Tavily

Role and function: provides optional external search. Processing to perform an authorized search and any independent use of transmitted queries are separately qualified. The search provider's own research, service-improvement and model-training uses are not processing solely on the Customer's instructions and are not authorized as subprocessing merely by this entry. The limited query exception and the safeguards for personal data in Terms Section 4, Privacy Section 2 and DPA Section 4.5 apply.

Data: for supported Section generation, the purpose-limited query prepared from general business context, not the entire Project or full AI context. For Ask with web search, Bleanx may clean up and shorten the question when preparing the search query, and external search is not performed for every question. When a search is performed, the provider receives the query actually prepared and transmitted. This preparation does not guarantee anonymization or removal of all personal or confidential information. Do not include personal or confidential information in questions for web search. Search results may be processed by the selected AI provider. Bleanx explains the recipient, transmitted data and independent uses before search is enabled and requires the initiating user's active AI and search permissions. The independent-use exception is limited to the search queries actually transmitted.

Location: Tavily describes processing in the United States. This is not an exclusive United States restriction on every operation or further provider involved in retrieving search results.

Email and Support

Resend / Amazon Web Services, including Amazon SES

Role and function: Resend, provided by Plus Five Five, Inc., processes delivery of Bleanx's necessary service emails on Bleanx's behalf. Bleanx is controller for its account, contractual, security and complaint-related communications. AWS, including Amazon SES, participates through Resend's infrastructure chain, not as a separate direct Bleanx email provider. This administrative flow is not automatically subprocessing of Covered Personal Data under the DPA.

Data: necessary sender and recipient addresses, message content and delivery information. Service emails do not contain Project materials. Independent provider use is confined to the sender and recipient addresses, delivery statuses, bounces, delivery failures and technical transmission metadata specified in Terms Section 4; it does not cover message subjects, bodies, attachments or information extracted from them beyond necessary delivery. Open and click tracking are not authorized.

Location: Bleanx's sending region is us-east-1, Northern Virginia, United States. Resend describes United States storage of account data, including email metadata, logs and API records. The sending region determines routing and dispatch, not every aspect of storage or access. Any operation involving Covered Personal Data on Customer instructions requires its applicable subprocessor authorization and safeguards before it begins; this entry does not introduce an additional email feature.

Google Workspace — Business Starter, Gmail support mailbox

Role and function: processor for correspondence at support@bleanx.org where Bleanx administers support, complaints and contractual or statutory notices as controller. Google is a subprocessor for the particular support operations involving Covered Personal Data on Customer instructions, including necessary assistance with content issues or data-subject requests. This role is separate from Google sign-in and Gemini API.

Data: supplied correspondence and attachments, sender and recipient details, necessary headers and transmission information. Attachments may contain Project materials; this does not give access to all Projects or private histories. The Resend delivery-metadata exception does not apply. The Google Workspace processing agreement, including its Cloud Data Processing Addendum, covers the entrusted mailbox processing; Bleanx ensures that other enabled services do not circumvent the agreed limits on purposes and data use.

Location: Business Starter without an applicable Data regions policy or a customer-selected regional restriction. Correspondence, backups and associated records use Google's international infrastructure; no exclusive United States or European Union location is promised.

Diagnostics and Public Website

Sentry — Functional Software, Inc.

Role and function: processor for Bleanx's necessary technical error diagnosis and subprocessor to the extent a diagnostic operation involves Covered Personal Data on Customer instructions. The integration covers bleanx.ai only, not the macOS application or bleanx.com. It does not use Session Replay, recording of users' actions or behavioural analytics.

Data: only error reports and associated technical information necessary to diagnose and correct errors. Bleanx excludes excessive Project and Section content, full AI context, personal correspondence and active secret credentials from diagnostic events and does not use them for model training or independent product development. Retention, access and deletion follow Privacy Sections 7–8 and the applicable processing agreement.

Location: United States for Bleanx's error-report storage. This identifies the storage region, not an unsupported restriction covering every support-access location.

Webflow

Role and function: processor for hosting bleanx.com and the technical information necessary to deliver the public website, for which Bleanx acts as controller. This does not make Webflow a subprocessor of application Project content.

Location and limits: Webflow describes hosting and processing in the United States and other countries. Google Analytics, Webflow Analyze, behavioural analytics and advertising tracking are not used on Bleanx's website.

Payment and Authentication Roles

Stripe — direct web payments

Role and function: direct web payment processing, recurring billing and authorized payment retries, Subscription and invoice administration, purchase verification, refunds, and Stripe-operated failed-payment notices with links to update payment methods or pay outstanding invoices. Those billing emails are sent through Stripe separately from Bleanx's Resend service emails. Stripe has independent responsibilities and purposes for relevant payment processing, including fraud prevention and improvement of payment services; operations performed on Bleanx's behalf retain their separate qualification. Stripe is not a subprocessor of Project content merely because it processes a purchase.

Data and limits: necessary purchaser contact details (including email address), payment-method and transaction information, Subscription and invoice identifiers and statuses, payment-attempt timing and results, and data needed for related Stripe billing notices. Bleanx does not receive or store full card details. The payment exception does not include Project materials, User Content, Output, personal conversations or Bleanx's allowance and consumption records. Purchase records are not records of how AI, search or resources are used.

Location: United States and other jurisdictions involved in Stripe's international operations and processing chain. Its processing agreement addresses transfers to the United States and onward transfers, not exclusive United States processing.

Apple — App Store purchases

Role and function: independent payment and store-related processing under Apple's applicable arrangements, and provision of necessary transaction and entitlement information to Bleanx. Listing Apple does not authorize subprocessing of Project content. The same limited payment-data boundaries apply; Bleanx does not receive card details for these purchases. Apple Send Consumption Information is not used.

Location: Apple describes international processing; personal data collected by Apple and its affiliates is generally stored by Apple Inc. in the United States. The responsible entity can depend on the service and jurisdiction; its place of establishment does not by itself identify physical storage. This entry applies to purchases in applications actually made available and is not a statement that every platform version has been released.

Apple — Sign in with Apple

Role and function: authentication and provision of the account information permitted for the chosen sign-in method, including an Apple private relay address where selected. Apple's own account and authentication processing is separate from processing by Bleanx and from Apple's payment role; this is not authorization to process Project content as a subprocessor.

Location and limits: Apple's international sign-in arrangements apply; no Bleanx-specific single-country restriction is promised. Sign-in does not give Apple general access to Project materials or private histories.

Google — sign-in provider

Role and function: authentication and provision of permitted profile and account information. Google's own external-account processing is separately qualified; it is not subprocessing of Project content merely because the user signs in. This flow is separate from Gemini API and Google Workspace.

Location and limits: Google processes information on servers in different countries, potentially outside the user's country. Settings or agreements for Gemini or Workspace do not automatically restrict Google sign-in geographically. Sign-in does not give Bleanx access to the user's Gmail, calendar or cloud files.

Provider Rules, Changes and Safeguards

For AI and search, Bleanx identifies the provider used for the relevant feature, including a default model, and makes that provider's applicable acceptable-use rules, material use restrictions and privacy information available before use. Those use restrictions have only the scope stated in Terms Section 4; the providers' entire commercial agreements are not incorporated into the user's contract. More permissive provider terms do not override Bleanx's restrictions or enlarge the three narrow independent-use exceptions.

Bleanx maintains this register with its version and effective date and retains prior versions. Adding or replacing a subprocessor follows DPA Section 6, including written notice to the Customer at least 14 calendar days before the proposed provider first processes the affected data, an opportunity to object, and any longer or stricter applicable requirement. Publication of an updated list alone is not that notice. An independent recipient's inclusion does not mean the subprocessor notice procedure authorizes all of its activities.

An inventory-only update need not alter unchanged Terms, Privacy or DPA rules. It cannot introduce a new purpose, expand permissions or independent uses, reduce protections, or bypass a required contractual change, notice, express acceptance or consent. Terms Section 22, Privacy Section 14 and the DPA continue to govern changes within their respective scope. Applicable transfer assessments, supplementary safeguards and suspension of an inadequately protected flow are required under Privacy Section 4 and DPA Schedule D.

Questions, applicable processing information and copies of safeguards: support@bleanx.org. You do not need an account to ask about your personal data. This route supplements information Bleanx must provide proactively under applicable law.

AI and Search Provider Documents

The following official documents provide the rules and notices referenced above. Their scope is limited by Terms Section 4; linking them does not incorporate every provider commercial term or replace Bleanx's own obligations and disclosures.

Anthropic — Commercial Terms | Usage Policy | Privacy Policy

OpenAI — Services Agreement | Usage Policies | Privacy Policy

Google Gemini API — API Terms | Prohibited Use Policy | Privacy Policy

Tavily — Service Terms | Acceptable Use Policy | Privacy Policy