Sub-Processor Register
Last updated: 13 November 2026
This working inventory identifies third-party routes found in Ask Brigid and MyBrigid, including routes that are switched off, historical or awaiting evidence. Each row says whether its route is enabled or switched off. A route marked enabled is authorised for a clinic as Data Processing Agreement clause 6 provides; a route marked switched off, retired or a candidate is not authorised.Ask Brigid is the staff-facing product and MyBrigid is the patient product; they are product names, not legal entities. Processor: DJG Media Limited, CRO No. 762838, Coliemore House, Coliemore Road, Dalkey, Dublin, Ireland. This register is the list that clause 6 of the Data Processing Agreement refers to, under GDPR Article 28(2).
The clinic contract and DPA commit us to at least 30 days' written notice before adding or replacing a sub-processor that processes your data, with a written objection right and a termination remedy if an objection cannot reasonably be accommodated. A route marked enabled is authorised for a clinic from the date it accepts the Data Processing Agreement version in force, unless its executed order form lists the suppliers and omits it. The notice period, objection right and termination remedy are in clause 6 of the Data Processing Agreement.
The transfer-mechanism column records the safeguard each route relies on. A row that says instrument not yet captured means exactly that: the safeguard is named, but no copy of the operative text is on file in our Article 28 register. Where a row says an agreement or evidence is still being captured, that is stated in the row; it does not suspend or extend the authorisation. A mailbox, calendar or import source system a clinic connects itself is the clinic's own supplier, not a sub-processor of ours, and is listed so you can see what we read on your authorisation.
AI & inference
| Sub-processor | Purpose | Data processed | Location | Transfer mechanism |
|---|---|---|---|---|
| Google Vertex AI (Gemini) | Status: enabled. Note and letter drafting from the transcript, the clinician's own words and, when asked, the chart; and the administrative routes: pre-consultation chart summary, document-filing scan, mailbox sorting (an order for the mailbox, not a statement about a patient) and emailed-document filing, the onboarding assistant and the staff assistant. Consultation and dictation transcription runs first on Google’s Gemini transcription model on Vertex AI in the EU, with Google Cloud Speech-to-Text as the fallback (next row). Ask Brigid Live, the staff voice assistant, sends speech to Google’s Gemini Live on Vertex AI in the EU with administrative tools only; reading patient records by voice is switched off for every practice. Every draft stays a draft until a clinician signs it. Clinical decision support (diagnosis, triage, urgency grading, treatment recommendations) is switched off. The Google Cloud CDPA is on file; each enabled purpose, project/account, service terms, logging, caching and retention must be verified. | Prompts and records used by the authorised workflow: transcripts, clinician notes, chart extracts, documents and emails. This can include identifiable health information and remains subject to health-data protections. | EU — Google Cloud Vertex AI EU multi-region (Google’s Gemini models, processed within the EU member states); the pre-consultation chart summary may fall back to Frankfurt, Germany (europe-west3); embeddings in europe-west4 (the Netherlands) | EEA — no Art. 46 transfer for inference. The applicable Google Cloud terms cover support access and onward transfers |
| Google Cloud Speech-to-Text v2 | Status: fallback. Consultation recording and dictation are transcribed first by Google’s Gemini transcription model on Vertex AI in the EU (row above); Google Cloud Speech-to-Text (Chirp 3) on an EU endpoint is the fallback, with no US route. The Cloud CDPA is captured; account/service coverage, logging and retention are verified per clinic. | Consultation audio and transcripts, including special-category health data. Original audio is deleted within 24 hours after the clinician accepts the note, and no later than seven days after it was recorded, unless the clinic instructs a different period in writing. Recordings saved before 8 October 2026 or outside the standard route are being brought under this schedule; until then some may be kept longer | EU regional endpoint | EEA — no Art. 46 transfer; the applicable Google Cloud terms cover support access and onward transfers |
| Google Cloud Document AI | Status: enabled, where a processor is configured, for the document-filing scan: OCR and form parsing of uploaded and emailed documents so they can be identified and filed. Service-specific contract, purpose and region evidence is verified per clinic | Document content (may include PHI) | EU | EEA — no Art. 46 transfer; the applicable Google Cloud terms cover support access and onward transfers |
| Google Cloud Platform — supporting services | Status: reCAPTCHA Enterprise is built in to the public booking-request form but switched off. Cloud Healthcare API (FHIR), Healthcare Natural Language, Translation, DLP de-identification, Vision OCR, Text-to-Speech, BigQuery analytics and Contact Center AI Insights are switched off unless a service is individually classified and evidenced for the clinic | Clinical documents and text for the healthcare services; technical signals for the utility services | EU — “eu” multi-region / europe-west4 | EEA — no Art. 46 transfer; the applicable Google Cloud terms cover support access and onward transfers |
| Google Maps Platform (Places address lookup) | Status: enabled in the clinic app. Address suggestions as staff type an address in patient registration, patient edit and practice setup. Provided by Google; the Maps JavaScript API loads in the browser | The address text a user types and the user's IP address, sent from the browser to Google. This can be a patient's address | Global — Google may process it outside the EU | Google Cloud Data Processing Addendum (captured; Google Maps Platform is in its service list), with Google’s processor-to-processor Standard Contractual Clauses (Module Three) for processing outside the EEA |
| ElevenLabs | Status: switched off (both ElevenLabs launch switches are off). Historical speech-to-text and outbound voice-agent routes, excluded for patient and clinical content. The captured account review identified sensitive-data, retention and residency gaps. | Audio and outreach information if a route is used; excluded from the approved launch scope | Account-specific residency and access arrangements not approved | Acceptable sensitive-data terms and transfer safeguards remain outstanding; inventory inclusion does not authorise use |
Telehealth, recording & meeting capture
| Sub-processor | Purpose | Data processed | Location | Transfer mechanism |
|---|---|---|---|---|
| Daily.co | Video visits between a clinician and a patient. Status: enabled. Nothing is recorded, transcribed or summarised, and recording of video visits stays switched off. The invitation carries the patient's first name, the clinician's name and a link | Live video and audio of the visit (which can include special-category health data), and room and usage details. No recording or transcript is kept | The call server is in Frankfurt, Germany (eu-central-1); account, room and usage details are processed in the United States. Daily offers no EU data-residency option on our plan | Daily’s Data Processing Addendum (last updated 1 May 2025), incorporated in Daily’s Terms and captured 25 October 2026; EU-US Data Privacy Framework first, with Standard Contractual Clauses (Module Three) as the fallback; it covers special-category data in call streams |
| Recall.ai | Status: switched off (the meeting-bot capture switch is off). Meeting bots and transcripts: excluded from launch pending purpose approval, applicable terms, configuration and verification of deployed restrictions. | Meeting audio, recordings and transcripts, potentially health data | EU route proposed; storage and access require service-specific evidence | Article 28 and any applicable transfer safeguards remain to be established before use |
Infrastructure & data storage
| Sub-processor | Purpose | Data processed | Location | Transfer mechanism |
|---|---|---|---|---|
| Supabase | Status: enabled. PostgreSQL database, authentication, file storage and edge functions hosting. Core route hosted in AWS Dublin (eu-west-1); the DPA and incorporated transfer terms are captured. Account/service coverage and current security, backup, access and logging evidence remain release conditions | All PHI/PII — patient records, clinical notes, voice recordings, audit logs | EU — Ireland (eu-west-1) for the database, file storage and server functions | Art. 46 SCCs — Module Three (processor to sub-processor), in force by incorporation. Data is stored in Ireland, but Supabase Pte. Ltd. is a Singapore company with administrative access, so Chapter V applies |
Communications & messaging
| Sub-processor | Purpose | Data processed | Location | Transfer mechanism |
|---|---|---|---|---|
| Twilio | Status: SMS reminders, campaigns and notifications are switched off. Twilio is still used to deliver sign-in codes by text to staff who chose that method. Live-account scope, terms, region, retention and webhook evidence are verified before SMS to patients is switched on | Phone numbers and one-time codes for staff sign-in by text; delivery metadata. No appointment or patient message content while SMS outreach is off | EU + US routing | Art. 28 DPA + SCCs + EU-US Data Privacy Framework |
| Healthmail (HSE) | Secure clinical email to the HSE Healthmail network (referrals, clinical letters) — sent only at your direction. Status: switched off; no Healthmail production authorisation or route evidence is on file | Clinical correspondence (special-category health data) | Ireland — HSE secure network | EEA — no Art. 46 transfer; controller-directed transmission |
| Microsoft (Graph / Outlook) | Status: in use, only for a practice that has connected a Microsoft 365 mailbox or calendar. Microsoft is the clinic's own supplier, not a sub-processor of ours: we read the connected account only on the clinic's authorisation. Connected accounts sync, and mailbox sorting reads them. | Connected mailbox/calendar content and metadata, potentially health data | EU data centres, depending on the connected account's Microsoft tenant | The clinic's own agreement with Microsoft governs Microsoft's processing (Data Processing Agreement clause 6) |
| Google Workspace APIs (Gmail / Calendar) | Status: in use, only for a practice that has connected a Gmail or Google Calendar account. Google is the clinic's own supplier for that account, not a sub-processor of ours: we read the connected account only on the clinic's authorisation. Connected accounts sync, and mailbox sorting reads them. | Connected mailbox/calendar content and metadata, potentially health data | EU or global, depending on the connected Google account | The clinic's own agreement with Google governs Google's processing of that account (Data Processing Agreement clause 6) |
| Import source systems (for example Cliniko, or an iMedDoc transfer link) | Status: in use only when a clinic instructs an import. The source system is the clinic's own supplier, not a sub-processor of ours: we read the records from the clinic's own account or transfer link on the clinic's authorisation | Patient records being imported, potentially health data | Where the source provider holds the clinic's account | The clinic's own agreement with that provider governs its processing (Data Processing Agreement clause 6) |
| Apple | Status: enabled. Push notifications (APNs) for the MyBrigid app and for the Ask Brigid clinician iPhone app, and optional read-only iCloud calendar sync (CalDAV) where a clinician connects it. Any identity service requires a separate assessment. | APNs device tokens and a notification category; payloads are kept minimal, and for MyBrigid never carry clinical detail. Calendar entries where iCloud sync is connected. | Global (Apple's push network) | Apple Developer Program License Agreement, which covers APNs; Apple offers no separate data processing agreement for it. Captured 29 September 2026; the developer account is held by the director personally until it moves to DJG Media Limited — route enabled |
| Browser push services (Google, Mozilla, Apple, Microsoft) | Status: enabled. Notifications to a browser where a member of staff or a patient has turned them on. Each notification goes through the push service of the browser's vendor | A device or browser push address and an encrypted notification that names the kind of update. The push service sees the address and the timing, not the content | Global (each browser vendor's push network) | Each browser vendor's own terms apply; no separate data processing agreement is held. The notification content is encrypted for the receiving browser |
Billing & identity
| Sub-processor | Purpose | Data processed | Location | Transfer mechanism |
|---|---|---|---|---|
| Stripe | Status: enabled. Clinic subscription billing, payments, and Stripe Identity, the document-and-selfie check used to verify a MyBrigid account holder. The DPA is captured. Confirm service-specific roles, current account settings and the agreed order particulars. | Billing identity, payment tokens and metadata. For an identity check: an image of an identity document and a live selfie, processed as biometric data with the person's explicit consent on Stripe's own screen. We ask Stripe to delete the session after the check and keep only the outcome and a reference; Stripe keeps some verification data as an independent controller. From 24 October 2026 clinical details are excluded from payment descriptions and product names; earlier items are not rewritten. | EU contracting arrangements and global payment networks, depending on service | Service-specific controller/processor roles and applicable DPA/transfer terms; EU establishment does not settle all onward transfers |
Support, monitoring & hosting
| Sub-processor | Purpose | Data processed | Location | Transfer mechanism |
|---|---|---|---|---|
| Sentry | Status: enabled. Application error monitoring: error reports, a 10% sample of performance timings and diagnostic log lines. In the clinic web app (not MyBrigid) about one error in ten may attach a masked recording of the minute before the error: every piece of text and every input is masked; media, documents, scans, signatures and uploads are blocked; link addresses and file names are masked again before sending; no network bodies or headers are recorded and there is no whole-session recording. Health data and direct identifiers are scrubbed before anything leaves the application. Since 25 October 2026 the account is contracted directly with Sentry (EU region), and its DPA (version 5.1.0) was accepted that day; retention, access and authenticated production scrubber evidence remain release conditions | Stack traces and error context, performance timings, log lines and masked error replays — PHI scrubbed and masked before transmission (sendDefaultPii: false, custom scrubber) | EU — Frankfurt (Sentry EU region) | Art. 28 DPA + SCCs Module Three + EU-US Data Privacy Framework. Errors are stored in the EU; the importer, Functional Software, Inc., is US-established |
| Slack | Internal support alerting. Status: switched off — the support notification route is off unless a deployment switch is set, and stays off pending executed terms and minimised-field configuration evidence; instrument not yet captured | Support ticket metadata — no clinical records | US + EU | Art. 28 DPA + SCCs + EU-US Data Privacy Framework required; instrument not yet captured — route disabled |
| Google Analytics 4 | Provided by Google Ireland Limited and loaded through Google Tag Manager. Website analytics only — never loaded by the Ask Brigid or MyBrigid apps, whether or not someone is signed in, and never before you opt in. Status: enabled on askbrigid.com from 22 September 2026 behind the cookie choice: nothing is requested from Google until you choose “Accept all” or switch on Analytics, and withdrawing the choice reloads the page without it. Google Consent Mode v2 starts every signal as denied. No advertising, remarketing or audience feature is configured. The Google Ads Data Processing Terms (which govern Analytics) are accepted in the Analytics account; the capture of that acceptance is being added to the register | Website page views, the pages that led to a request, and Google’s analytics identifiers (_ga). No patient or clinical data; no page may be used to infer anyone’s health | EU entity; data may be processed in the United States | Art. 28 terms incorporated in the Google Ads Data Processing Terms; Art. 46 SCCs (Module Two) for any US processing; Google LLC is EU-US Data Privacy Framework certified |
| Lovable Technologies (connector gateway) | Intermediary through which the Slack support notification above is sent — so anything reaching Slack by that route passes through this gateway first. Status: switched off by the same source-level gate as the Slack route (SUPPORT_SLACK_ENABLED defaults off). Legal entity, terms, sub-processors, processing location and retention are not yet evidenced, and the route stays off until they are; instrument not yet captured | The same support-ticket metadata sent to Slack, plus connection metadata | Not yet evidenced | Art. 28 terms required (entity and location not yet evidenced, so the transfer module cannot yet be named); instrument not yet captured — route disabled |
| Cloudflare | Provided by Cloudflare, Inc. Web hosting and delivery for the marketing site and the clinic and patient web apps (Cloudflare Workers), and DNS for our domains. The apps are client-side: clinical data (PHI) is exchanged directly between the browser and Supabase (EU), not intentionally routed through Cloudflare. The website’s enquiry forms pass through it to Supabase (EU). Request logging is on. No Cloudflare cookies or analytics are in use. In use since 25 October 2026, replacing Vercel. Also transactional email: since November 2026 every email Ask Brigid sends (sign-in codes, appointment and clinic emails) goes through Cloudflare Email Sending, replacing Resend. Also the off-site backup: a private copy of the files stored in Ask Brigid, kept in Cloudflare R2 under its EU jurisdiction so that the copy is stored only in the EU. Only Ask Brigid’s own systems write it, and a copy is deleted once its original is deleted. Status: hosting is in use, but deployment, access, WAF and log evidence must cover the intended clinic and clinic-linked adult patient release. The backup store was created on 13 November 2026; copying starts after this change’s notice period | App and page delivery and request metadata (IP address, page address, browser details and timing), and the details entered in the website’s enquiry forms, in transit. In the clinic app the page address can contain an internal record reference, never a name or clinical content. Email: recipient address, message content and delivery metadata, in transit; clinical content depends on the authorised template. The backup holds copies of the files a clinic stores in Ask Brigid: patient documents, letters, recordings, attachments and profile pictures | United States + Cloudflare global network; backup copies stored in the EU only | Art. 28 DPA incorporated in the Cloudflare self-serve terms (version 6.4, 3 April 2026); EU-US Data Privacy Framework, with Art. 46 SCCs Module Three as the fallback |
| Mapbox | Status: enabled. Map display and place search in the MyBrigid clinic finder, and address and Eircode search in a clinic's public-listing settings. Provided by Mapbox, Inc. | The visitor's IP address and the map area being viewed; in a clinic's settings, the address or Eircode being placed on the map. No patient record is sent | United States | Mapbox Customer DPA, incorporated in the Mapbox terms, with Standard Contractual Clauses deemed signed; captured 29 September 2026 — route enabled |
Services that receive no personal data
| Provider | Purpose | Data processed |
|---|---|---|
| DigiCert (Timestamping Authority) | RFC 3161 timestamp candidate for the audit chain. Status: not scheduled — the weekly anchor job is not on the production schedule and runs only after operational review; historical anchor records exist. No personal data leaves, so no Article 28 instrument is required; the provider's terms are not yet captured on file. Source and production proof required before any assurance claim | A cryptographic hash only — no personal data |
| Anthropic — not a sub-processor for any clinic | None for any clinic. Listed here because the question is a fair one. Since 23 October 2026 the Ask Brigid assistant calls Anthropic’s API (United States) as a test route for two of our own internal test practices, which hold only made-up patients. No clinic’s data goes to Anthropic. Several endpoints and files in our system still carry Anthropic names from an earlier architecture, including one endpoint, secure-anthropic-proxy; the names were kept so the front end did not have to redeploy in lockstep. Our browser Content-Security-Policy does not permit a connection to Anthropic from a browser. Claude models are also offered through Google Vertex AI in one EU region (Belgium); none is set to a clinic route today. If one is ever set, the processor is Google, with Anthropic appearing on Google’s own sub-processor list rather than on ours | No clinic data of any kind is sent to Anthropic; the test practices hold made-up patients only |
| OpenAI | Marketing blog hero-image generation (a fallback when Gemini image generation is unavailable) and administrator “AI connection test” diagnostics — never used for clinical processing. Status: the diagnostics route is disabled by the unclassified-AI launch boundary; the blog image fallback is enabled and scheduled with the blog generator. No personal data is sent, so no Article 28 instrument is required; the provider's terms are not yet captured on file | A synthetic test prompt and a blog image prompt — no patient or user data |
| Public medical reference services | Status: NCBI PubMed, Europe PMC, openFDA and DailyMed are switched off since 2 October 2026 (the assistant refuses medical-literature and drug-label lookups). The US NPI registry and SNOMED and ICD terminology servers can still be queried when staff ask the in-product assistant to look a code up. These are public services with no contract with us, so no Article 28 instrument applies. Patient identifiers are not authorised in a search | A search term only (a condition, a drug name or a code) — no patient record is sent |
Retired routes
Providers we have stopped using. They are listed because a provider that once held data is part of your record even after the route closes, and silence would read as “never used”.
| Provider | Former purpose | Retired |
|---|---|---|
| Anthropic (direct API) | Clinical reasoning and triage, before the move to Google | 2 June 2026 for clinic data — see the note in the table above, which also describes the test route for internal practices |
| Wispr AI | Audio transcription, superseded by Google Speech-to-Text | 8 May 2026 |
| Composio | Third-party tool and OAuth bridge, and a WhatsApp route | 24 August 2026 — the five former endpoints now return HTTP 410 |
| Airtable | Support-ticket mirror | Retired; the endpoint is a tombstone and makes no vendor call |
| Vonage (formerly Nexmo) | Inbound SMS and voice webhooks, and WhatsApp messaging. It was never switched on for a practice: no message or call went through it. Text messages go through Twilio | 29 September 2026 — two of the three former endpoints have been removed and one returns HTTP 410 |
| Google AI Studio / Gemini Developer API | Global (US) transport for Gemini text, Live audio and transcription, before the move to Vertex AI in the EU | 7 September 2026, as a transport for practice or patient data: the transport selector now resolves to Vertex AI (EU) unconditionally and every request builder refuses the Developer API. One caveat, stated so that silence does not read as “gone”. The transcription bundles deployed on 28 August 2026 still carry the previous selector until the next deployment — their request builders already refuse the Developer API, so the path is dead there too |
| Vercel | Web hosting for the marketing site and the clinic and patient web apps | 25 October 2026 — every site moved to Cloudflare; Vercel serves no domain |
| Resend | Transactional email | 13 November 2026 — every email is sent through Cloudflare; the Resend key was removed from Ask Brigid |
Changes to this register
This is a working, version-controlled route inventory. Before approval, the controlled production schedule must be reconciled to the release fingerprint and attached to the executed clinic DPA. If you are an Ask Brigid customer and would like to raise a concern about a proposed processor-route change, please email privacy@askbrigid.com. The notice period, objection procedure and any termination right are those in your executed clinic contract and DPA, not this public page.
Related documents
Data Processing Agreement · Privacy Policy · Compliance Overview · Terms of Service
Download compliance documents