01
Overview
A sub-processor is a third party we engage to process personal data on our behalf to provide TradersFlow. Each sub-processor is bound by contractual data-protection terms (including, where applicable, the UK Addendum and Standard Contractual Clauses for international transfers) and is selected for its security and compliance posture.
We may update this list when we add, replace or remove a sub-processor. Material changes are announced in advance by email or in-app notice to subscribed customers.
02
Current sub-processors
| Provider | Purpose | Categories of data | Location |
|---|---|---|---|
| Google LLC (Google Play Billing) | Subscription billing and payment collection inside the Android app, plus server-side purchase verification through the Google Play Developer API. Google acts independently for its store and payment services. | Google Play purchase token, order ID, subscription state, obfuscated Google account identifier (card details are entered into Google Play directly and never reach TradersFlow). | Global (Google Play operates globally; EU data protection terms apply). |
| RevenueCat, Inc. | Subscription infrastructure for the Android app — validates Google Play purchases, tracks entitlements, and notifies TradersFlow of subscription lifecycle events by webhook. | App user identifier linked to your TradersFlow account ID, purchase token, product/plan and entitlement identifiers, subscription status, purchase and renewal dates. | United States / global; applicable transfer safeguards depend on our current contract and data route. |
| OpenAI, L.L.C. / OpenAI Ireland Ltd | Generates the text for the AI features you choose to use: Ask TradersFlow answers, Automated Business Insights explanations, and Create with AI drafts. Requests are made server-side by TradersFlow over the OpenAI API. | The prompt or question you type, plus the limited business context needed to answer it — business and tax settings, finance totals, invoices, quotes, jobs, expenses, suppliers, purchases, stock figures and customer or supplier names. Customer contact details, bank details and tax identifiers are excluded. API content is not used to train OpenAI's models. | United States / Ireland; applicable transfer safeguards depend on our current contract and data route. |
| Supabase, Inc. | Managed database, authentication and file storage. | Account credentials (hashed), profile and business information, customer records, jobs, quotes, invoices, photos and documents, application logs. | Project-configured European region; underlying infrastructure details may change under the provider's terms. |
| Lovable (managed transactional email) | Delivery of transactional emails and delivery/engagement event reporting through Lovable's managed email API and its own disclosed providers. | Recipient email address, sender, subject, rendered email body, delivery and engagement events. | Location depends on Lovable's current managed-email infrastructure and subprocessors. |
| Lovable (hosting & deployment platform) | Application hosting, deployment, server runtime and Google OAuth brokering for web sign-in. | Application code, build artefacts, request logs, error traces. | Managed regional/global infrastructure under Lovable's terms. |
| Google Maps Platform / Places API (Google) | Address autocomplete when you type an address into the app. | The address characters you type, plus the IP address, device and browser information Google receives with the request. Google acts as an independent controller for this data. | Global (Google infrastructure). |
| Google LLC / Google Ireland Limited (Google Analytics for Firebase) | App analytics and conversion measurement in the TradersFlow Android app only. Disabled by default and enabled only after the user accepts the in-app analytics consent. Used to understand app usage, measure performance and conversions, and improve TradersFlow. | Firebase app-instance identifier, device model and OS version, app version, language, approximate location from IP address, standard automatic app events, and configured conversion events with product identifiers and a de-duplication reference. The Android Advertising ID is not collected; no names, email addresses, account identifiers, business records or financial figures are intentionally sent. | United States / global; governed by applicable Google data-processing and transfer terms. |
03
International transfers
Where a sub-processor stores or accesses personal data outside the UK or EEA, we rely on adequacy decisions or the UK International Data Transfer Addendum to the EU Standard Contractual Clauses to safeguard the transfer.
04
Questions
Questions about a specific sub-processor, or to request our Data Processing Addendum: privacy@tradersflow.co.uk.