Data Processing Agreement
Last updated: 25 October 2026 · Takes effect: 25 October 2026
Version: 2026-10-25_v8 (supersedes 2026-10-25_v7) Effective: 25 October 2026 Application: This version is offered for acceptance from its effective date. A Controller that accepted an earlier version remains bound by that version until it accepts this one (clause 13). Processor: DJG Media Limited, CRO No. 762838, Coliemore House, Coliemore Road, Dalkey, Dublin, Ireland, which provides Ask Brigid and MyBrigid Governing law: the laws of Ireland · Supervisory authority: Data Protection Commission (dataprotection.ie)
This Agreement is made under Article 28 of Regulation (EU) 2016/679 (GDPR) and the Data Protection Act 2018 (Ireland). It is concluded in electronic form, which Article 28(9) permits, and takes effect when an authorised representative of the Controller accepts it and the Controller's legal identity is recorded. Schedule 1 (technical and organisational measures) and Schedule 2 (retention of working copies) form part of it.
1. Parties and roles
Controller: the legal entity named in the acceptance record, being the clinic or practice subscribing to Ask Brigid.
Processor: DJG Media Limited, CRO No. 762838, of Coliemore House, Coliemore Road, Dalkey, Dublin, Ireland.
The Controller determines the purposes and means of processing patient personal data. The Processor processes that data only on the Controller's behalf.
1A. Processing for the Processor's own purposes
The Processor is a controller, under its Privacy Policy, for: (a) the account, sign-in and billing data of the Controller's users, to the extent needed to administer the subscription and secure sign-in; (b) platform security logs and usage data that contain no patient name, note text or message text; (c) its websites, enquiries and marketing; and (d) a patient's MyBrigid account, as the Terms of Service describe. The Processor does not use personal data it processes on the Controller's behalf for any other purpose, including to train or improve an AI model, to build profiles or for advertising, and does not sell it or disclose it except to sub-processors under clause 6 or as law requires.
2. Subject matter, duration, nature and purpose (Art. 28(3))
Subject matter: provision of the Ask Brigid practice platform and the clinic-linked MyBrigid patient app.
Duration: for the term of the subscription and until the data is returned or deleted under clause 10, plus any longer period the Controller instructs or the law requires. Each record category follows the retention the Controller sets; working copies follow Schedule 2. This Agreement does not impose one universal period on clinical records.
Nature and purpose: storing, organising, retrieving and transmitting patient and staff records so the Controller can deliver and administer healthcare, including connected patient and authorised-representative access through MyBrigid. Transcription, preparation of draft notes and letters for the clinician to review and sign, factual summaries, patient administration and mailbox processing are included to the extent the Controller uses them. The published sub-processor register describes each of these routes, the provider it uses and whether it is switched on. This Agreement does not itself determine a product's regulatory classification.
Types of personal data: identification and contact data; special-category health data including clinical notes, medications, allergies, conditions, results, referrals and prescriptions; billing data; clinician and staff records; and, where the Controller uses the feature, consultation audio and transcripts, clinic correspondence and attachments, patient submissions, consent and choice records and authorised-representative records.
Categories of data subjects: the Controller's patients (including children where the clinic treats them), their authorised representatives, clinicians, administrative staff, and correspondents whose information is processed for the clinic's purposes.
3. Processing only on documented instructions (Art. 28(3)(a))
The Processor processes personal data only on the Controller's documented instructions, including as to transfers to a third country, unless required to do otherwise by Union or Member State law. Where such a legal requirement applies, the Processor informs the Controller before processing, unless that law prohibits it on important grounds of public interest.
The Controller's use of the platform in the ordinary course constitutes documented instructions. Where an order form is executed with the Controller, that order and its schedules are also documented instructions and prevail over this clause to the extent they are more specific. Further instructions may be given in writing. A user action does not expand the purposes in clause 2, add a provider not authorised under clause 6, or override a patient's recorded choice or applicable law.
The Processor's systems check a patient's recorded choice about AI before an AI model reads that patient's record, and do not use the record with AI where the patient has refused or withdrawn that choice. Dictation by a clinician (a clinician speaking, not a consultation recording) is the one exception: speech-to-text and optional clean-up of dictated text run whether or not the patient has recorded a choice. Consultation recording keeps the check.
The Processor immediately informs the Controller if, in its opinion, an instruction infringes the GDPR or other data protection law.
4. Confidentiality of personnel (Art. 28(3)(b))
The Processor ensures that every person it authorises to process personal data — employee, contractor, or sub-processor personnel — is bound to confidentiality before access is granted, either by a written undertaking in the form published by the Processor or by an appropriate statutory or professional duty of confidence. The Processor maintains a register of the persons so authorised and of the instrument binding each, and makes that register available to the Controller on request.
Access is granted only where necessary for that person's role, is withdrawn when the role changes or ends, and is logged. The confidentiality obligation survives the end of that person's engagement and the end of this Agreement.
5. Security of processing (Art. 28(3)(c), Art. 32)
The Processor implements and maintains appropriate technical and organisational measures, having regard to the state of the art, implementation costs, the nature, scope, context and purposes of processing and the risks to individuals. The measures include encryption in transit and at rest, tenant isolation, individual accounts and role and record access controls, audit logging, confidentiality of personnel, incident handling and tested recovery arrangements.
Schedule 1 sets out the measures as they stand on the effective date: where the data is held, the database and file-backup arrangements, the restore test, and which measures are in place and tested, in place, or planned. A database backup is not represented as a backup of separately stored files. The Processor updates Schedule 1 when a measure changes and tells the Controller when a change reduces protection.
The Processor regularly tests, assesses and evaluates the effectiveness of the measures and records the method, scope, date and result. It makes that record available to the Controller on request, including material unresolved limitations. Independent testing may supplement internal assessment; a planned external assessment does not replace the duty to maintain appropriate security from the start of processing.
6. Sub-processors (Art. 28(2), 28(3)(d), 28(4))
The Controller grants general written authorisation for the Processor to engage sub-processors, subject to this clause.
The Processor publishes a versioned sub-processor register at askbrigid.com/sub-processors. Each version shows, for every route, whether it is enabled, switched off or retired, the data it receives, its location and its transfer mechanism. The providers authorised for a Controller are those the register shows as enabled in the version in force on the date the Controller accepts this Agreement, which the acceptance record identifies, together with any provider added later under this clause. A provider shown as switched off, retired or a candidate is not authorised. Where an executed order form lists the providers authorised for that Controller, a provider not listed there is not authorised for that Controller.
The Processor gives the Controller at least 30 days' written notice before adding or replacing a sub-processor that will process its personal data, by email to the Controller's recorded privacy contact or, failing that, its account owner. The notice names the provider, the purpose, the location and the transfer mechanism. Updating the public register is not itself notice. The Controller may object in writing within that period on reasonable data protection grounds. Where an objection cannot reasonably be accommodated, the Controller may end the affected subscription by written notice without penalty, and the Processor refunds the fees paid for any period after the subscription ends. Where a replacement is needed urgently to protect the security or continuity of the service, the Processor gives as much notice as it can, which may be less than 30 days, states the reason, and the Controller's right to object and end the subscription runs from the date of that notice.
The Processor imposes on each sub-processor, by contract or other legal act under Union or Member State law, the data protection obligations Article 28(4) requires, in particular sufficient guarantees to implement appropriate technical and organisational measures. Where a provider contracts only on its standard data processing terms, those terms are that contract and the register records which. The Processor remains fully liable to the Controller for the performance of a sub-processor's obligations. A mailbox, calendar or other service the Controller connects with its own account, and a source system the Controller instructs the Processor to import from, is the Controller's own supplier and not a sub-processor of the Processor: the Processor accesses it only on the Controller's authorisation, and the Controller's agreement with that provider governs the provider's processing.
7. Assistance with data subject rights (Art. 28(3)(e))
Taking into account the nature of the processing, the Processor assists the Controller by appropriate technical and organisational measures, insofar as possible, in fulfilling the Controller's obligation to respond to requests to exercise data subject rights under Chapter III — access, rectification, erasure, restriction, portability and objection.
Where the Processor receives such a request directly from a data subject, it does not respond substantively but refers the data subject to the Controller and informs the Controller without undue delay. This clause concerns data processed on the Controller's behalf; the Processor handles requests about processing for which it is itself a controller under its own duties.
8. Assistance with Articles 32 to 36 (Art. 28(3)(f))
The Processor assists the Controller in ensuring compliance with the obligations in Articles 32 to 36, taking into account the nature of processing and the information available to it. This includes security of processing, personal data breach notification, communication to data subjects, data protection impact assessments, and prior consultation.
9. Personal data breach (Art. 33(2))
The Processor notifies the Controller without undue delay, and in any event within 24 hours, after becoming aware of a personal data breach affecting personal data processed on the Controller's behalf. Notice is given by the Processor's named incident lead or deputy to the contacts the Controller has recorded for this purpose or, failing that, to the email address of the practice's account owner. The Processor maintains a written breach-response procedure that names an incident lead and a deputy, tests the route by which they are reached at least once a year, and records each test.
The notification describes the nature of the breach, the categories and approximate number of data subjects and records concerned, the likely consequences, and the measures taken or proposed. Where information is not available at once, it is provided in phases without further undue delay.
10. Deletion or return of data (Art. 28(3)(g))
At the end of the provision of services, the Controller chooses whether the Processor deletes or returns the personal data processed on its behalf. The Processor acts on that instruction and deletes existing copies, except to the extent that Union or Member State law requires continued storage. If the Controller has not told the Processor whether to return or delete its data by the end of the export window, the Processor deletes it under this clause.
Unless an executed order form sets different periods:
- Export window. For 30 days after the subscription ends, the Controller can export its data, with no fee. The Controller can also export its data at any time during the subscription.
- Deletion from the active system. The Processor deletes the Controller's data from the active system within 90 days after the export window closes, or sooner on the Controller's written instruction, and confirms the deletion to the Controller in writing.
- Backup expiry. Backup copies expire on the backup rotation in Schedule 1, and in any case within 90 days after deletion from the active system. A backup is not edited selectively; it expires.
Cancelling a subscription does not by itself delete data; deletion follows this clause. Data returned is provided in a structured, commonly used, machine-readable format. Where law requires retention beyond these periods, the Processor tells the Controller which data is retained, on what legal basis, and for how long.
11. Audit and inspection (Art. 28(3)(h))
The Processor makes available to the Controller all information necessary to demonstrate compliance with Article 28, and allows for and contributes to audits, including inspections, conducted by the Controller or its mandated auditor.
Routine audits are ordinarily arranged on reasonable notice, during business hours and no more than once in twelve months. Those arrangements do not prevent an additional audit or inspection reasonably necessary to verify compliance, including following credible indications of non-compliance, material processing changes, a personal data breach or a competent authority's requirement. Urgency may require shorter notice.
The parties agree proportionate arrangements that protect other customers' information and maintain confidentiality without preventing the Controller from exercising these rights. Reports or certifications may assist an audit but do not replace the Controller's rights under this clause.
The Controller's auditor must be bound by written confidentiality obligations and must not be a competitor of the Processor. An audit does not extend to other customers' data. The Processor may first meet a request by documents, a written questionnaire or a remote session, provided that does not prevent the Controller from exercising its rights under this clause. Each party bears its own costs. The Controller reimburses the Processor's reasonable and documented costs of an audit beyond one in twelve months that does not follow a personal data breach or a finding of non-compliance.
12. International transfers (Chapter V)
The Controller's records are stored at rest in the European Union: the database, authentication and file storage run in Ireland (AWS eu-west-1), and AI processing runs in Google Cloud regions in the European Union. Server functions called from the web apps are pinned to Ireland. Server functions called from the Ask Brigid iPhone app, a scheduled job or a supplier's webhook run in the region the platform selects nearest the caller, which may be outside the European Union; they read and write the Controller's data in Ireland and hold it in memory only while they handle the request (Schedule 1, item 1).
The following routes, used for every Controller, involve processing or storage outside the European Union. The Controller authorises them by accepting this Agreement:
- remote support and administrative access by Supabase (Singapore) and by Google Cloud support staff outside the European Union, under the Standard Contractual Clauses (Module Three) in each provider's data processing terms;
- server functions that run outside the European Union as described above (Supabase);
- transactional email (Resend, United States): the recipients and content of the emails the platform sends;
- sign-in codes by text message, for staff who choose that method (Twilio, European Union and United States routing);
- push notifications to the Ask Brigid and MyBrigid apps (Apple Push Notification service) and to browsers (the push services of Google, Mozilla, Apple and Microsoft): a device or browser address and an encrypted notification that names the kind of update;
- subscription billing and card payments (Stripe);
- maps and place search (Mapbox, United States): the address or place a user searches for, the map area and the user's IP address;
- address lookup (Google Maps Platform): the address text a user types when registering or editing a patient or setting up the practice, and the user's IP address, sent from the browser to Google, which may process them outside the European Union;
- video visits (Daily, Co., United States): the call is carried by a server in Frankfurt, and the account, room and usage details of each call are processed in the United States. Nothing is recorded, transcribed or summarised. The invitation carries the patient's first name, the clinician's name and a link;
- web hosting (Cloudflare, United States; its global network): the apps are delivered from it, so it handles the network details of each request, such as the user's IP address and the page address, which can include an internal reference to a patient record but no name or clinical content; clinical data is exchanged between the browser and the database in Ireland and is not intentionally routed through it;
- error monitoring (Sentry): error reports, a sample of performance timings, diagnostic log lines and, for about one error in ten in the clinic web app, a masked recording of the minute before the error (every piece of text and every input is masked, and media, documents and uploads are blocked), with health data, direct identifiers and record references removed before they leave the application, stored in the European Union by a United States-established provider.
A service the Controller connects itself, such as a Microsoft 365 or Google mailbox or calendar, or a source system the Controller instructs the Processor to import from, is the Controller's own supplier (clause 6) and processes data where that provider holds the Controller's account. Any other route outside the European Union is added only under the notice procedure in clause 6.
For each transfer to a third country, the Processor ensures an appropriate transfer mechanism under Chapter V — an adequacy decision, Standard Contractual Clauses, or another lawful mechanism — together with any supplementary measures required, and records the basis for each transfer. The sub-processor register shows, for each route, its location and the mechanism relied on.
13. Precedence and variation
This Agreement forms part of the subscription between the parties. In the event of conflict between this Agreement and the Terms of Service in respect of the processing of personal data, this Agreement prevails.
The Processor may issue a new version of this Agreement on reasonable notice. Continued use of the service after a new version takes effect does not by itself constitute acceptance of that version where the change materially reduces the Controller's protections; in that case the Processor asks an authorised signatory of the Controller to accept the new version.
This Agreement is governed by the laws of Ireland. The courts of Ireland have exclusive jurisdiction over disputes between the parties arising from it. Nothing limits a data subject's rights under Articles 77, 79 and 82 GDPR.
13A. Liability
Nothing in this Agreement limits the rights of a data subject under Article 82 GDPR, or liability for fraud, for death or personal injury caused by negligence, or any other liability that cannot lawfully be limited. As between the parties, the Processor's total liability to the Controller arising under or in connection with this Agreement in any period of twelve months is limited to the limit in the executed order form or, where there is none, to the greater of €50,000 and the fees paid in the twelve months before the first event giving rise to the claim. A party that has paid compensation for damage to a data subject for which the other party is responsible may recover from the other party the share of the compensation that corresponds to the other party's responsibility (Article 82(5)).
14. Execution
Accepted in electronic form under Article 28(9). The acceptance record identifies the Controller's legal entity, its registration number and registered address, the name and role of the authorised signatory, the date and time of acceptance, and the version of this Agreement accepted.
Schedule 1 — Technical and organisational measures (Article 32)
Each measure is marked in place and tested (a dated test is recorded), in place (running, with no dated test recorded) or planned. A planned measure is not represented as in place.
| # | Measure | Status | |---|---|---| | 1 | Location. The production database, authentication and file storage run in one Supabase project in Ireland (AWS eu-west-1, Dublin). Server functions called from the web apps and from other server functions are pinned to the same region; a function called from the Ask Brigid iPhone app, a scheduled job or a supplier's webhook runs in the region the platform selects nearest the caller, and reads and writes the data in Ireland. | In place | | 2 | Encryption of personal data in transit (TLS) and at rest. | In place | | 3 | Tenant isolation at the database layer: row-level security on every table holding patient data, so one Controller's users cannot read another Controller's data. | In place | | 4 | Individual accounts and role-based access. Every user has their own account; what they can see and do follows their role in the practice, and access to a patient record follows the care relationship. The Processor's platform-administrator accounts can reach every practice, for support and security; their use is logged. | In place | | 5 | Second sign-in step for staff. Every clinic staff account, and each of the Processor's platform-administrator accounts, must enter a code sent to the account's own email address on each new browser, and again at least every 30 days. The Ask Brigid iPhone app does not yet have a code screen; one App Store review account, which holds only sample data, is exempt until it does. | In place since 1 October 2026 | | 6 | New sign-in alert. A member of staff is emailed when their account signs in from a new browser. | In place | | 7 | Audit logging of access to patient records and of consequential actions, with the limits described in the Terms of Service. | In place | | 8 | Database backups. One full backup a day, eight kept (about eight days). Point-in-time recovery is not enabled, so a restore can lose up to about 24 hours of records. | In place | | 9 | Database restore. A daily backup was restored into a separate project in the same region; every compared table count and identifier fingerprint matched. | In place and tested, 1 October 2026 | | 10 | File backups. Stored files in the twelve clinical and practice storage areas are copied every 15 minutes into backup storage in the same project and region. Import holding files are not copied. A database backup does not include these files. Because the copies sit in the same project, they protect against a file being deleted or overwritten, not against the loss of the project. | In place | | 11 | Backup copies of deleted files are removed by a nightly job once the original has gone. | In place | | 12 | File restore. A restore of a stored file from backup storage has not yet been rehearsed and recorded. | Planned | | 13 | Retention of working copies under Schedule 2, by nightly and daily jobs. | In place | | 14 | Breach notification to the Controller within 24 hours of becoming aware (clause 9), through a named incident lead or deputy. The route to the incident lead was tested on 1 October 2026; the route to the deputy has not yet been tested. | In place; lead route tested 1 October 2026 | | 15 | Independent security testing (penetration test). Scope prepared; not yet commissioned. | Planned | | 16 | Patient AI choice. The server checks the patient's recorded AI choice before an AI model reads a patient's record (clause 3). The check runs on note and letter drafting and on reading an uploaded document to file it; it is being extended to every other route that reads a patient's record with AI, and where it is not yet automatic, staff must check the patient's choice before using AI. | In place on two routes; planned for the rest | | 17 | Web-host request logs. Request logging for the clinic app is limited so that the page addresses the web host records do not carry patient-record references. | Planned |
Limits the Controller should know. Up to about 24 hours of records could be lost if the database had to be restored (item 8). The file backups are not independent of the production project (item 10), and no file restore has been rehearsed (item 12). No independent test of these measures has yet been carried out (item 15). The patient AI choice check does not yet run on every route (item 16), and the web host's request logs for the clinic app can still contain page addresses with an internal patient-record reference (item 17).
Schedule 2 — Retention of working copies
Ask Brigid makes working copies of the Controller's data to do its job: recordings before they become a note, an import's files before they are filed, searchable summaries, chat threads. A working copy is not the clinical record, which follows the retention the Controller sets. This schedule is the Processor's standard for working copies. Accepted with this Agreement, it is the Controller's documented instruction on these periods; the Controller may instruct a shorter or longer period for any item in writing, and the Processor confirms in writing when that instruction is in effect.
| # | Working copy | Kept until | |---|---|---| | 1 | Raw consultation audio linked to a consultation record | 24 hours after the clinician accepts the note made from it, and in any case 7 days after recording, whichever comes first. The checked transcript and the note are the record and are not affected. Older audio files that are not linked to any record are found and deleted on the Controller's confirmation. | | 2 | Import holding files of an import that was cancelled or failed | 7 days after the import ended. A backlog of files from imports cancelled before 1 October 2026 is being deleted nightly and is expected to clear by 31 December 2026. | | 3 | Import holding files of a finished import | 30 days after that import's documents have left the Needs Filing folder, and never later than 90 days after the import finished. | | 4 | An import left unfinished | Cancelled after 14 days with no activity; item 2 then applies. | | 5 | The only copy of a document still waiting for a person in an import's review queue | Kept until a person at the clinic files or releases it, whatever items 2 to 4 say. | | 6 | Import working rows (paths inside the archive, identities read from documents, match candidates) | Removed with that import's holding files. The file's fingerprint, its status and the patient it was filed to are kept as a record of the import. | | 7 | People waiting in import review | A decision deadline of 90 days from entering review; after it, their identifying and clinical details are removed and the entry is closed. | | 8 | People the Controller declined at import | Identifying details removed 30 days after the decision. The fact of the decision and its reason are kept. | | 9 | Searchable copies of patient content (summaries and excerpts of documents, emails, tasks, alerts and outreach), summaries of staff conversations with the assistant, and any other searchable copy not listed in items 10 and 11 | 90 days from when the copy was last written or refreshed; some kinds for less. | | 10 | Searchable copies of the Controller's reference material (policies, services, templates, staff details) | 1 year from when it was last indexed. | | 11 | Staff members' saved assistant notes | 1 year. | | 12 | Staff chat threads with the assistant | 90 days from the last message. | | 13 | A full practice export prepared for download | 30 days after it is prepared. | | 14 | Copies in backups | Database backups rotate as Schedule 1 item 8 sets out, so a deleted record survives in backups for up to about eight days. A backup copy of a file whose original has been deleted is removed by the nightly job in Schedule 1 item 11. | | 15 | Unfiled transcripts, patient messages, submissions and uploads | 30 days after they were made, unless the Controller files them to the clinical record first or instructs a different period in writing, and in any case under clause 10. | | 16 | Video visit rooms and call details (Daily) | The room expires at the end of the join window, four hours after the appointment ends. Nothing is recorded, transcribed or summarised. Daily deletes its call usage data after the retention period Daily sets under its Data Processing Addendum. |
When the Controller erases a patient's identity in Ask Brigid, that patient's searchable copies (items 9 and 10) are deleted at the same time. On the Controller's written instruction, the Processor keeps a named working copy past its period until a stated date, and records the scope, date and reason. Where law requires a working copy to be kept longer, clause 10 applies.
This page renders the agreement text itself, not a summary of it. The version accepted by a clinic is fingerprinted, so the exact wording agreed can always be established:
SHA-256: e34900376e413dfed982ad047491d2be0e4e6ec8482941112eeffd3966bbb2a2
Source: docs/legal/DPA_2026-10-25_v8.md
Download compliance documents