Sub-Processors

Neon

• Purpose: managed PostgreSQL database — the primary store for the Service.
• Data: all account, profile, brand, collaboration, payment, brief, and billing records, and the Gmail message content matched by your keywords, including message bodies.
• Location: European Union — AWS eu-central-1 (Frankfurt).

Upstash

• Purpose: managed Redis, used as the background job queue and for synchronisation locks.
• Data: transient job payloads and identifiers, which can briefly include references to email messages while a job runs. Not a long-term store.
• Location: [UPSTASH REGION — SELECT AN EU REGION TO MATCH THE DATABASE].

[HOSTING PROVIDER]

• Purpose: the virtual server running the application, background workers, and web server.
• Data: all data in transit through the application, plus server logs.
• Location: [DATA CENTRE REGION].

Cloudflare

• Purpose: DNS, TLS termination, network protection, and routing of inbound email sent to our support address.
• Data: IP addresses, request metadata, and the content of email you send to our support address.
• Location: global edge network.

GitHub

• Purpose: source code hosting and the container registry we deploy from.
• Data: application code and build artefacts only. No customer personal data.
• Location: global.

These process data only if you choose to connect them, and stop when you disconnect.

Google — Gmail API and Cloud Pub/Sub

• Purpose: reading inbound messages that match your keywords, sending replies from your address, and delivering push notifications so new mail is picked up promptly.
• Data: Gmail message content and metadata, your Google account identity, and message identifiers in notification payloads.
• Location: global (Google Cloud). Our use of this data is governed by the Limited Use commitments in our Privacy Policy.

Notion

• Purpose: reading the pages you link to a collaboration. Read-only — we do not write to your Notion workspace.
• Data: the content of pages you authorise, and workspace and page metadata.
• Location: global.

Google — Gemini API

• Purpose: extracting collaboration details from a matched email or a submitted brief, and drafting Smart Reply responses.
• Data: the subject and body of a matched email (truncated to roughly 12,000 characters), and the labels and values of submitted brief answers with the brand name where known.
• Location: global (Google Cloud).
• Restrictions: processed as our service provider. Not used to train generalised AI or machine learning models, and not used for advertising. We do not fine-tune models on your data.

This sub-processor is engaged only when AI features are active on your account. Leaving Smart Reply disabled means your email content is not sent to a model.

Dodo Payments

• Purpose: merchant of record, checkout, subscription management, and tax handling for paid plans.
• Data: name, email address, billing and country information, transaction and subscription records. Card details are collected directly by the provider — they never reach our servers.
• Location: global.

Resend

• Purpose: delivering transactional email from CollabFlow, such as billing notices and account notifications.
• Data: your email address and the content of the notifications we send you. This is separate from replies sent through your own Gmail account, which go via Google.
• Location: global.

The public website is separate from the application and handles far less data. It runs no analytics, advertising, or session-recording tools.

Supabase

• Purpose: storing early access waitlist sign-ups.
• Data: email address, whether you consented to product updates, and the sign-up date. Nothing else.
• Location: [SUPABASE PROJECT REGION].

Lovable

• Purpose: hosting and serving this website.
• Data: standard web request logs, including IP address and user agent.
• Location: global.

We update this page whenever the list changes. Before a new sub-processor begins processing personal data on our behalf, we will:

• update this page and the date at the top of it; and
• give account holders at least 30 days' notice by email or in-app notice where the change is material — for example a new vendor that would handle your email content or a change to where your database is hosted.

If you have a reasonable, good-faith objection to a new sub-processor on data protection grounds, tell us during the notice period. We will try to offer an alternative, and if we cannot, you may cancel your subscription and receive a pro-rata refund of prepaid fees for the unused period.

We may engage a replacement for an existing sub-processor immediately where necessary to keep the Service running or secure, and will update this page as soon as we do.