Privacy Policy
Last updated: 25 October 2026
Version: 2026-10-25_v23 (supersedes 2026-10-25_v22) Effective: 25 October 2026 Last updated: 25 October 2026 Provider: DJG Media Limited, CRO No. 762838, Coliemore House, Coliemore Road, Dalkey, Dublin, Ireland, which provides Ask Brigid and MyBrigid Governing law: Ireland
1. Introduction
Welcome to Ask Brigid and MyBrigid. We are committed to protecting your privacy and handling your personal data in an open and transparent manner. This Privacy Policy explains how we, DJG Media Limited, CRO No. 762838, collect, use, share, and protect your personal data when you visit our website (askbrigid.com), use Ask Brigid or MyBrigid (released earlier under a different name), or use an enabled Ask Brigid feature. The features that are switched on, the ones that are switched off, and your optional AI choices are explained in section 6. Where a feature processes patient information, the applicable clinic instructions, lawful basis and access and permission checks apply. These are product names, not separate legal entities.
This policy is designed to help you understand your privacy rights and how you can exercise them.
In short. For our website, our accounts, our sales contacts and our own business records, we are the controller (sections 3, 4 and 10 to 12). For a clinic's patient records, the clinic is the controller and we are its processor (section 2). The AI features, what is switched on and what is switched off, and your AI choices are in section 6. MyBrigid is in section 14. Your rights, our Data Protection Officer and how to complain are in section 10.
2. Who We Are and Our Roles
We are DJG Media Limited, CRO No. 762838, a company registered in Ireland with our registered office at Coliemore House, Coliemore Road, Dalkey, Dublin, Ireland. For the purposes of the General Data Protection Regulation (GDPR), our role depends on the context of our interaction with you:
- When you visit our website, contact us directly, request a demo or early access, or create an account for Ask Brigid: DJG Media Limited is the Data Controller. We determine the purposes and means of processing your personal data.
- When a healthcare provider (our "Customer") uses Ask Brigid to manage patient information: The Customer is the Data Controller of the patient data, and DJG Media Limited is the Data Processor. We process this data on behalf of and under the instruction of the Customer, as governed by the Data Processing Agreement (DPA) we have with them.
This distinction is important. If you are a patient of one of our Customers, you should direct any privacy-related questions to your healthcare provider in the first instance.
Our Data Protection Officer can be contacted at mark@askbrigid.com.
3. What Data We Collect
We collect different types of data depending on your interaction with us:
- When you visit our website: We collect technical data such as your IP address, browser type, and operating system, as well as information about your browsing activity (our "Website Data"). Optional analytics run only if you opt in, as described in the Cookie Policy. We also keep a record of your cookie choice: a random visitor ID, your choices, the time, and your browser's description of itself.
- When you contact us or sign up: We collect your name, email address, and any other information you provide in your communications with us (our "Communication Data"). On the early-access form that is your name, work email, your role and an optional phone number; on the demo form it is your name, work email and anything you choose to tell us. With each request we also keep where the visit began, so we can see which link or page worked: the campaign details in the link you followed, the site that referred you, the first page you landed on, the page you were on when you sent the form, and your country (worked out from your IP address). We use your IP address to slow down repeated submissions, and keep only a one-way hash of it for that purpose, not the address itself. We use these details to reply to you or ring you, and to understand which of our own pages and campaigns lead people to ask. We do not add you to a newsletter or a mailing sequence because you sent a request.
- If you subscribe to product updates: on our changelog page you can give your email address to receive product updates. We keep the address and the page you subscribed from, send you the updates, and stop when you unsubscribe, which every message lets you do.
- When you use our platform: We collect account information such as your name, email address, role, and payment information (our "Account Data"). We also collect data on how you use the platform (our "Usage Data"): with each event, the Ask Brigid app records your account and practice, the page address with every patient or record reference replaced by a placeholder, the feature or action used, how long it took, whether it succeeded or what kind of error stopped it, page-speed measurements and the kind of device (desktop, tablet or phone). Each event can carry only properties from a fixed list, so it holds no patient name, no note or message text, no search text and no error message. We use it to keep the product fast and working and to see which features are used. MyBrigid does not send these events. We also maintain detailed logs for security and auditing purposes (our "Log Data").
- When we process data for our Customers: We process patient demographic and clinical data on behalf of our Customers (our "Patient Data"). This is special category data and is protected by the technical and organisational measures set out in our DPA.
Data we hold that did not come from you
Four datasets are not collected from the people they concern, and Article 14 of the GDPR requires us to say so.
1. Irish pharmacies. We maintain a directory of Irish pharmacies — name, address, telephone, opening hours, and in some cases an email address — so that patients can find and contact their pharmacy, and so that clinic staff can look one up when arranging a prescription. It is built from two public sources: the statutory register of retail pharmacy businesses maintained by the Pharmaceutical Society of Ireland, and OpenStreetMap. Where the PSI register names the owner of a pharmacy, that name is held with the entry.
We rely on Article 6(1)(f) — our legitimate interest, and that of patients, in an accurate pharmacy directory. We have not written to each pharmacy owner individually, relying on Article 14(5)(b): the information concerns businesses, it is drawn from a public register those businesses are already listed in, and individual notification would be a disproportionate effort. Publishing this section is the measure we take instead.
If you are a pharmacy owner and would rather your details were not held here, write to privacy@askbrigid.com and we will remove the entry.
2. Emergency contacts and next of kin. When a patient (or a clinic, for a patient) records an emergency contact or next of kin, we hold that person's name, relationship to the patient and telephone number, and nothing else about them. The patient or the clinic gave us those details; the person named did not. They are held so the clinic can reach someone if the patient's care requires it. Where the patient's record belongs to a clinic, the clinic is the controller and we process the details for it. We rely on Article 6(1)(f) — the legitimate interest of the patient and the clinic in being able to reach someone in an emergency. We do not write to each person named: the details are given to protect the patient, we hold nothing else about the person, and notifying each one would be a disproportionate effort (Article 14(5)(b)). Publishing this section is the measure we take instead. The details are used only to contact that person about the patient, and are not used for marketing. If you are named as someone's emergency contact and would like the details removed or corrected, tell the patient or their clinic, or write to privacy@askbrigid.com and we will pass your request to the right controller.
3. People a patient invites to a family link. In MyBrigid an account holder can invite only an adult who already has a MyBrigid account, by that person's MyBrigid ID; inviting someone by email address alone is switched off. We record the invitation and the relationship the account holder chose, and tell the person with a MyBrigid alert that names nobody and carries no health detail (their notification settings may also send it as a push notification or an email). Opening it shows who asked, and nothing is shared unless they accept. A request about a child under 16 goes to the child's clinic, which confirms parental responsibility first (section 14).
4. Doctors and practices we may write to. DJG Media Limited keeps a business contact list of private consultants and practices in Ireland that we may contact about Ask Brigid. For each person it holds their name, job title and practice, a work email address or phone number where one is public, the address of their public LinkedIn profile, where we found them, and a record of our contacts and follow-ups. We took most of it from public LinkedIn profiles and public listings, not from you. We use it to introduce Ask Brigid and to follow up, and we rely on Article 6(1)(f), our legitimate interest in telling private consultants about software built for them. Only members of our team can see the list, and it is held in our database in Ireland. We keep an entry for 24 months from our last contact with you. You can object at any time, including to direct marketing, and we will stop at once: write to privacy@askbrigid.com. We do not rely on Article 14(5)(b) for this list: we tell you where we got your details when we first contact you.
Letters to practices. DJG Media Limited also writes by post to private practices in Ireland to ask for their help with Ask Brigid. Each letter is addressed "Dear Doctor" to the practice at its business address, taken from public listings. The printing service, Cardly, receives only the practice's name and business address and the text of the letter, and no person's name. We do not write to a practice that trades under an individual's name. If you want us to stop writing to your practice, email privacy@askbrigid.com and we will record that.
Children and family access. Own MyBrigid accounts and clinic staff accounts require age 18 or over for this release. Clinics may hold children's information to provide healthcare, subject to the clinic's lawful basis, confidentiality and safeguarding duties. An authorised parent or guardian can request access to a child under 16 through an adult account; the clinic verifies the authority and approves the permitted access before information is shared. A family relationship alone does not confer access. The guardian link ends when the child turns 16. For ages 16–17, contact the clinic about record access; the app does not create an independent under-18 account or continue the guardian link automatically. These product rules do not replace the applicable law on children's data, capacity or confidentiality.
4. Lawful Bases for Processing
We only collect and process your personal data when we have a legal basis to do so. The purposes for which we use your data include:
- Contract fulfilment: To provide and manage the service.
- Legitimate interest: To secure and monitor our platform, communicate with you, understand which of our pages and campaigns lead people to contact us, and improve our services. You may object to processing based on legitimate interest at any time (section 10).
- Consent: For marketing and cookies (where required).
- Legal obligation (Art. 6(1)(c)): Where retention or processing is required by law — for example tax and accounting records retained under Irish Revenue rules.
In more detail, by purpose:
What we do | Our legal basis |
|---|---|
Reply to early-access, demo and support requests, and see which pages and campaigns led to them | Art. 6(1)(b), steps you ask for before a contract; Art. 6(1)(f), understanding which of our pages and campaigns work |
Run Ask Brigid and MyBrigid accounts and take payment | Art. 6(1)(b) |
Keep tax and accounting records | Art. 6(1)(c) |
Usage Data, security and audit logs, error monitoring | Art. 6(1)(f), keeping the product secure, fast and working |
Send product-update emails | Art. 6(1)(a), your consent |
Keep cookie-choice records | Art. 6(1)(c) and (f), so that we can show a choice was made |
Keep a business contact list and write to practices (section 3) | Art. 6(1)(f) |
Check the identity of a MyBrigid account holder | Art. 9(2)(a), explicit consent (section 14) |
Process patient data for a clinic | The clinic's own Article 6 basis and Article 9 condition. We are the clinic's processor. |
5. Health Data Processing (Special Category)
Your medical record is "special category personal data" under GDPR Article 9. Where applicable, the Irish Data Protection Act 2018 §36 requires suitable and specific safeguards, while §52 addresses health and social-care processing and §53 addresses public-health processing. For patient data held for a clinic, these are the clinic's conditions: the clinic is the controller and we are its processor (section 2). The relevant bases include:
- Explicit consent — GDPR Art 9(2)(a) — used only for optional processing that genuinely relies on consent, such as certain recording, sharing, and research choices. Consent can be withdrawn without affecting prior lawful processing.
- Healthcare delivery — GDPR Art 9(2)(h) + Irish DPA 2018 §52 — permits processing necessary for medical diagnosis, the provision of health or social care or treatment, or management of health systems.
- Public interest in the area of public health — GDPR Art 9(2)(i) — applies to specific public-health functions (e.g. notifiable disease reporting).
The platform records security and access events defined in the clinic's approved logging specification. Logging coverage, access to log data and retention are documented in the clinic agreement and evidence pack; this notice does not claim that every database event is captured. You may request access to personal data held in those logs under GDPR Article 15, subject to the rights of other people and applicable restrictions.
What we do NOT do with your health data: we never sell it or use it for advertising, and DJG Media Limited does not use it to train its own AI models. Provider processing, retention and training restrictions differ by service and are disclosed in our Sub-Processor Register; we do not describe every provider as zero-retention.
6. What Ask Brigid Does, What Is Switched Off, and Your AI Choices
Ask Brigid is practice-management software with AI built in. Its AI assistant is called the Ask Brigid assistant, and "the assistant" below. The AI helps the clinic prepare its work. A clinician or other responsible staff member reads the source and approves a draft before it is signed, sent, filed or relied on, and a draft stays a draft until then. AI can make mistakes and leave things out. The assistant is not intended to provide diagnosis, clinical triage, medical risk scores, treatment recommendations or autonomous clinical decisions. This section lists what is switched on today. If a clinic has not enabled a feature, it does not run for that clinic. The check of a patient's AI choice is automatic on some paths and is being extended to the rest; where it is not yet automatic, the clinic's staff must check it (see "Patient-linked AI and transcription" below).
Switched on:
- Recording and speech-to-text. A clinician can record a consultation or dictate a note. The audio is turned into text by Google Cloud on an EU endpoint: Google's Gemini transcription model on Vertex AI, with Google Cloud Speech-to-Text as the fallback. The clinic's recording notice and permission procedure apply. The original audio is kept only briefly (section 11).
- Note and letter drafting. The assistant drafts a clinical note or a letter from the transcript, from what the clinician dictated or typed, and, when the clinician asks, from the patient's chart. It can also tidy dictated text and draft one section of a note again. This uses Google's Gemini models on Google Cloud Vertex AI, processed inside the EU. Drafted text is labelled as drafted by AI. It is a draft: the clinician reads it, edits it and signs it, and the assistant does not file, sign or send it. The assistant is instructed to write down only what was said and what is already recorded, and not to diagnose, grade urgency or risk, triage, assign clinical codes, or recommend investigations, treatment or follow-up that was not already stated. When a draft is made for a patient, the patient's AI choice below is checked first.
- Administrative helpers. A factual summary of the chart before a consultation; reading an uploaded document to work out what it is and file it in the right place (using Google Cloud Document AI and Gemini in the EU); reading a blank form to find the places to fill in; reading the documents in an imported archive to file each one to the right patient's chart; mailbox sorting, which puts each of the clinic's own emails in an order for how soon staff should open it (it is an order for the mailbox, not a statement about a patient), and filing emailed attachments to the right chart; the onboarding assistant; and an in-product assistant for staff that runs administrative tasks and can look up public code services on request, namely SNOMED and ICD codes and the US NPI registry (see section 12).
- Ask Brigid Live (voice). Staff can talk to the assistant. Speech goes to Google's Gemini Live on Vertex AI in the EU. It uses administrative tools only. Reading a patient's records by voice is switched off for every practice. Before the microphone opens, the user is told they are talking to an AI and acknowledges how it works.
- Video visits. A clinic can book a video visit, or a patient can ask for one in MyBrigid. The call is carried by Daily (Daily, Co., United States) and the invitation carries the patient's first name, the clinician's name and a link. Nothing is recorded, transcribed or summarised: it is a plain live call. Recording of video visits stays switched off. Where Daily is based and the safeguard we rely on are in section 12.
- The assistant's searchable memory. So that staff can find earlier work again, the assistant keeps searchable copies of short summaries and excerpts: of documents and notes filed to a patient's record, of the clinic's email and the tasks taken from it, of follow-up alerts, of the results of the clinic's outreach to patients, and of staff members' own conversations with the assistant. It also keeps the practice's own reference material, such as its policies, services, templates and staff details. A copy taken from a patient's document or task is kept only when it is linked to that patient's record or to the member of staff who made it. A copy of an email is kept only when it is linked to the patient, or to the member of staff whose mailbox it came from. Copies made before 1 October 2026 without such a link are no longer used, and are deleted on the dates in section 11. These copies are not used to answer general questions, and a copy linked to one patient is not used when staff are working on someone else. To make the copies searchable, Google's embedding model on Google Cloud Vertex AI turns each one into numbers, in the Netherlands (europe-west4). How long each kind of copy is kept is in section 11.
- Clinical follow-up reminders. The assistant checks the practice's own records for three things: a clinical note left unsigned for more than a day, a test result that nobody has marked as reviewed, and a referral that has not moved on in the expected time. It shows the practice's clinical staff how many there are and which records they are in, so they can be followed up. No AI model is used for this. It does not change the record, and it does not contact patients or anyone outside the practice.
- Clinic email and calendar. Where a clinic connects a Google Workspace (Gmail, Google Calendar) or Microsoft 365 (Outlook) account, authorised staff may use the connection, including attachments, for the clinic's documented purposes. The clinic must explain that processing and establish its own lawful basis and any required permission. Email and attachments that are not linked to a patient are not automatically checked against an individual patient's AI choice.
Switched off for this release: AI that diagnoses, triages patients, ranks patients or results by clinical urgency, scores risk or recommends treatment; medical-literature search and drug-interaction or drug-label lookups (refused in code since 2 October 2026); a live "copilot" during a consultation; reading a patient's records by voice in Ask Brigid Live; video-consultation recording; meeting-bot and browser-extension capture; ElevenLabs speech and voice-agent calls; SMS and WhatsApp outreach to patients; automatic AI replies to patients who answer an outreach email (switched off on 2 October 2026; the last was sent on 25 May 2026); and any AI that writes to a patient on its own or starts a conversation with one. Consent does not switch any of these on.
Correction. Until 1 October 2026 the staff assistant had two functions outside its intended purpose: a risk label for a patient, and a suggestion made from a clinical photograph. Both are now switched off. Our records show the risk label was used 6 times, all on our own test accounts and none on a clinic's patients, and the photograph function was never used. Until 24 October 2026 the staff assistant also had a "find the problem" chat mode that gave diagnosis-style answers. It was removed on 24 October 2026. Four earlier conversations in that mode, all on our own test accounts, remain stored. They are not read, and they are included in a patient's access request.
In MyBrigid. The MyBrigid app does not currently offer you an AI chat, a symptom checker or an AI-written reply. AI touches your information only through the clinic's staff, in the ways listed above and, apart from your clinician's own dictation (below), only if you have not refused it.
Patient-linked AI and transcription. Staff must have permission to access the record and must check the patient's applicable AI choice before using patient information with AI. A consultation recording also follows the clinic's recording notice and permission procedure. General administrative recordings must contain no patient information.
Where the check is automatic. The server checks the patient's AI choice automatically, before anything is sent to the model, on these paths:
- drafting a note or letter for a patient;
- reading an uploaded document to work out what it is and file it;
- recording a consultation.
We are extending the same check to every route that reads a patient's record with AI. Until it is in place and verified, on the other routes the clinic's staff must check the patient's choice before using them, and must not use them against a refusal or withdrawal. Those routes are:
- the staff assistant, when it reads a patient's chart to answer a question or do a task;
- the assistant's searchable memory, when it keeps a copy about a patient or finds earlier copies about a patient;
- mailbox sorting and email or document reading that is not yet linked to a patient;
- patient notes and chat outside the drafting route.
Dictation is a deliberate exception. When a clinician dictates (⌘D, or Dictate in a note), speech-to-text and, if "Cleaned up" is selected, the tidying of the words by a model run whether or not the patient has said yes to Clinical intelligence. That is the clinician speaking, not a consultation being recorded. The clinic's own lawful basis for care applies, and the clinician needs access to the record. Only the dictated words are sent for tidying, and nothing is diagnosed or added. A letter written without the chart is treated the same way. Recording a consultation keeps the patient's choice check.
If you believe your choice has not been honoured, contact your clinic or privacy@askbrigid.com so the processing and your request can be investigated. We will update this notice when each remaining check is in place and verified.
Your choice. The Clinical intelligence choice is optional, off unless enabled through the applicable patient process, and withdrawable without loss of non-AI care. In MyBrigid you can turn it on or off at any time in Me → Data & privacy. Refusal or withdrawal means further processing covered by that choice must stop. It does not retrospectively invalidate lawful processing or automatically erase a clinical record. Sharing between clinics and non-clinical product updates have separate choices. Account or terms acceptance is not consent to all optional processing.
Chat history. Patient-linked chat and retrieved records require the applicable permission and access checks when reused. We do not claim to identify every patient's identity from arbitrary text.
Consent settings do not by themselves establish every lawful basis or enable an unavailable feature. The clinic must document the relevant Article 6 basis, Article 9 condition and DPIA where required. No patient choice overrides provider terms or applicable law. Medical-device and AI Act classification is assessed separately against the actual functions and intended use. Under the EU AI Act, you are told when you are dealing with an AI system and AI-written text is labelled before anyone relies on it.
7. Cross-Clinic Data Sharing & Record Portability
Cross-clinic record sharing is offered to you in the MyBrigid app as an explicit choice — presented as Share your records, off unless you turn it on, and withdrawable at any time in Me → Data & privacy. Choosing what a particular clinic may see asks for this choice first; it is never recorded for you in the background. Turning it off is intended to prevent further access through the sharing permission. It does not automatically erase a copy already lawfully received by another clinic: that clinic handles its copy under its own responsibilities. The current release must verify the applicable database and sharing-path enforcement before relying on that control.
Before any clinic is enabled to receive a share, its controller must have approved the purpose, Article 6 basis, Article 9 condition, recipient verification, access and revocation behaviour, transparency text and any required DPIA. Your permission does not substitute for that approval; both are required.
- No blanket pre-consent — a general toggle will not authorise any clinic to read the complete record.
- No implied lawful basis — a patient action is recorded, but the relevant controller must still identify and document the lawful basis and safeguards.
- Fail closed — no production share may open until recipient identity, expiry, revocation, logging and deletion tests are in the release evidence.
8. Marketing & Outreach Communications
Marketing messages sent by DJG Media Limited require a valid permission or another applicable ePrivacy route and a working opt-out. A clinic is responsible for determining and documenting the lawful basis and ePrivacy rule for its own patient communications. SMS and WhatsApp outreach to patients are switched off. The assistant does not write to patients on its own: an outreach email is sent only after the clinic's staff approve it, and replies are not answered automatically (section 6). An outreach email goes only to a patient whose record shows an explicit permission for email; where the permission is blank or cannot be read, nothing is sent. A message asking a patient to come back or to give feedback is treated as direct marketing and needs that explicit permission with no exception. Every outreach email carries an unsubscribe link. The only SMS we send is a sign-in code to a member of staff who chose to receive codes by text.
- We do not sell your contact details. Where needed to provide a requested service, we disclose them to authorised service providers described in this notice and the applicable supplier information. Marketing use requires the applicable legal basis or permission and an effective opt-out.
- Appointment or care-related reminders are not automatically marketing, but the clinic must classify each purpose and document its GDPR and ePrivacy basis; this policy does not assign one blanket basis to every reminder.
- One-tap unsubscribe links appear on every marketing message; you can also globally opt out using the instructions supplied with the communication or by contacting the sender.
- Our letters to practices are described in section 3. They are postal letters to a practice's business address, not electronic marketing.
9. Research Use
No patient-data research programme is authorised for the first-clinic release. We will not describe data as anonymous merely because direct identifiers have been removed.
- Any future research use requires a separately documented protocol, controller decision, Article 6 basis, Article 9 condition, data-minimisation and disclosure analysis, and any required ethics or DPIA approval.
- A future notice will distinguish anonymous information from pseudonymised personal data and explain withdrawal or objection rights for the approved study.
10. Your Data Protection Rights
Under GDPR, you have several rights in relation to your personal data:
- Right to Access: Request a copy of the data we hold.
- Right to Rectification: Correct inaccurate or incomplete data.
- Right to Erasure: The "Right to be Forgotten".
- Right to Data Portability: Transfer data to you or a third party.
- Right to Object: Object to processing in certain cases, including processing based on our legitimate interest.
- Right to Restriction: Ask us to pause processing while a dispute is resolved.
- Right to Withdraw Consent: Where we rely on consent (marketing, optional cookies) you may withdraw it at any time without affecting earlier processing.
A copy of your data from your clinic includes Ask Brigid's searchable copies about you (section 6), including any copy that names you but had not been linked to your record. If your clinic erases your identity from its records, Ask Brigid's copies about you are deleted at the same time.
We respond within one month, extendable by two months for complex requests, in which case we tell you. Providing your name and email for a staff account or the early-access list is needed to provide that service; you are not otherwise obliged to give us data. We do not make decisions producing legal or similarly significant effects about you by solely automated means.
Our published privacy contact is privacy@askbrigid.com. Our Data Protection Officer can be contacted at mark@askbrigid.com. To exercise any of these rights, contact us at privacy@askbrigid.com. You may also lodge a complaint with the Data Protection Commission at dataprotection.ie (GDPR Article 77). Current postal and online contact details are available on the DPC contact page.
11. How Long We Keep Your Data
Retention periods depend on the category of data (GDPR Art. 13(2)(a)):
- Account and billing data — for the duration of your contract, then handled under the signed contract and approved retention schedule after termination. Irish tax and accounting records are generally kept for six years, subject to any longer period required for a particular record or proceeding.
- Closed staff accounts — when a staff account is closed, we keep it closed for up to one month in case you change your mind, and then erase the account and profile records (profile, roles and permissions, sign-in session records, consent and communication preferences, and the links to the clinics you belonged to). Clinical records belong to the clinic and are not part of the account.
- Patient records processed for clinics — retained on the instructions of the clinic (the controller) under its documented retention schedule, applicable law and professional guidance. When the clinic's subscription ends, the clinic has 30 days to export its data, unless its order form sets a different period; the records are then deleted within 90 days and backup copies expire within a further 90 days, as clause 10 of the DPA sets out, subject to lawful retention.
- Platform security and clinical-access audit logs — the policy period for the specified audit-record classes is six years, subject to a documented necessity assessment, applicable controller instructions and legal holds. This is not a claim that automatic deletion across every log and backup has been verified.
- Voice recordings and transcripts — original consultation audio is deleted within 24 hours after the clinician accepts the transcript or note, and in any case no later than seven days after it was recorded, unless the clinic has given us a written instruction to keep it longer. Nightly deletion runs for recordings saved through the standard route. Older recordings, saved before 8 October 2026 or outside the standard route, remain in storage and are being brought under this rule; until then some may be kept longer than this paragraph says. Filed transcripts and clinical notes follow the clinic record schedule; deleting audio does not automatically delete those records. While a recording is waiting to upload, an encrypted copy is kept on the clinician's device and removed once the server confirms the save (see the Cookie Policy). Copies in encrypted backups expire with the backup cycle.
- Files uploaded to import another system's records — the holding copy of an import is deleted 7 days after the import is cancelled or fails; for a finished import, 30 days after its last unfiled document leaves Needs Filing, and in any case 90 days after the import. An import with no activity for 14 days is cancelled. A document that is still the only copy waiting to be filed is kept until someone at the clinic files it. Records filed to the chart follow the clinic's record schedule.
- The assistant's searchable memory — a copy taken from a patient's documents, notes, email, tasks, alerts or outreach, and a summary of a staff member's conversation with the assistant, is kept for 90 days from when it was made or last refreshed. The practice's own reference material is kept for 365 days from the last refresh, and staff members' saved assistant notes for 365 days. Each is deleted automatically after that. Copies made before 1 October 2026 were given an end date by the same rule, and none of them reaches its end date before 31 October 2026. A practice can ask for shorter periods.
- Clinical follow-up reminders — the reminders shown to staff are currently kept with no end date. We are setting one, and will state it here.
- Usage Data (section 3) — each event is kept for 180 days and then deleted automatically. Before that, it is counted into daily totals that hold no account or person, and those totals are kept for 24 months.
- People on our business contact list (section 3) — 24 months from our last contact with you, or until you ask us to remove you.
- MyBrigid accounts you delete — when you delete your MyBrigid account we keep it closed for up to one month in case you change your mind, and then erase the account and the personal record it held. While it is held closed it is not used for anything else. Records held by your clinic are not part of it (section 14).
- Early-access and demo contacts, product-update subscribers, and practices we have written to — the policy target is 24 months from our last contact with you, or until you unsubscribe from product updates. Cookie-consent records — the policy target is 12 months from the choice (see the Cookie Policy). Automatic purge and backup-expiry coverage for these categories are being verified; these targets are not a statement that every historical copy has already been deleted. Contact privacy@askbrigid.com to request removal or information about a specific record.
12. International Transfers
Ask Brigid's primary patient-record database and object storage are provisioned in the EU (Supabase, Ireland — AWS eu-west-1). Our database provider, Supabase Pte. Ltd., is incorporated in Singapore and its support staff can access the service; that access is covered by the EU Standard Contractual Clauses (Module Three) incorporated in its data processing agreement. Server functions called from our web apps and from other server functions run in 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 picks nearest the caller, which may be outside the EU, and holds data in memory only. Google Cloud's support staff may likewise have remote administrative access from outside the EU, under Standard Contractual Clauses (Module Three). The applicable Article 28 terms, Chapter V transfer mechanism, transfer assessment and provider configuration must be evidenced per route. Some legacy scope statements and release evidence are under review; inclusion in the register is not itself proof of supplier authorisation. Where each supplier is located, what it receives and the safeguard we rely on are set out in our Sub-Processor Register. In summary:
- AI drafting and administrative helpers use Google's Gemini models on Google Cloud Vertex AI, processed in Google's EU multi-region, inside the EU. The pre-consultation chart summary may fall back to Frankfurt, Germany (europe-west3), also inside the EU. Google Generative AI is used for the administrative routes and note and letter drafting described in section 6; it is not an approved clinical decision-support provider. Embeddings are produced in europe-west4 (the Netherlands).
- Anthropic (internal test route). For two of our own internal test practices, which hold only made-up patients, the assistant can call Anthropic's API in the United States. No clinic's data goes to Anthropic, and Anthropic is not a sub-processor for clinics.
- Voice transcription uses Google's Gemini transcription model on Google Cloud Vertex AI in the EU, with Google Cloud Speech-to-Text on an EU endpoint as the fallback. ElevenLabs and the US medical-dictation model are not transcription routes.
- Ask Brigid Live (voice) for staff uses Google's Gemini Live on Google Cloud Vertex AI in the EU, with administrative tools only; reading patient records by voice is switched off. The former Google AI Studio / US-audio route is disabled.
- Video visits are carried by Daily (Daily, Co., United States). The call server is pinned to Frankfurt, Germany. Account, room and usage metadata (such as join and leave times and network details) are processed in the United States, because Daily offers no EU data-residency option on our plan. The transfer relies on Daily's Data Processing Addendum: the EU-US Data Privacy Framework first, with Standard Contractual Clauses (Module Three) as the fallback. Nothing is recorded, transcribed or summarised, and recording of video visits stays switched off.
- Error and performance monitoring (Sentry; our own Sentry organisation, contracted directly, at its EU (Frankfurt) region) receives error reports, a 10% sample of page-load and request timings (with profiles of some of them), and the apps' own diagnostic log lines. In the Ask Brigid clinic web app only (not MyBrigid), for about one error in ten, it may also receive a short screen recording of the minute before the error. Every word and input on screen is masked before it leaves the browser. Media, documents, scans, signatures and uploads are blocked. Link addresses and file names are masked again before sending, and request bodies and headers are not captured. We never record whole sessions. Health data, direct identifiers and record references in addresses are scrubbed from all of these before they leave the application. Sentry's parent company is established in the United States, and the transfer is covered by Standard Contractual Clauses and the EU-US Data Privacy Framework.
- Email (Resend) is stored in the United States, under an Article 28 agreement and Standard Contractual Clauses. SMS (Twilio, EU and US routing) is used only for staff sign-in codes; SMS reminders and campaigns are switched off.
- Payments and identity checks (Stripe) are processed by Stripe's Irish entity and global card networks. On screens where you enter a card, Stripe's script sets cookies to prevent fraud (see the Cookie Policy). From 24 October 2026 clinical details are excluded from payment descriptions and product names; items created before that date are not rewritten.
- Push notifications go through Apple's push service to the iPhone apps, and in a web browser through the browser maker's own push service (Google, Mozilla, Apple or Microsoft, depending on your browser). They carry a device or browser address and a short notification label that names only the kind of update. For MyBrigid the label never carries clinical detail.
- Maps (Mapbox, United States) draw the map in MyBrigid's clinic finder and in a clinic's public listing settings. Mapbox receives your IP address and the map area being viewed (and, in the clinic's settings, the address or Eircode being placed on the map).
- Public reference lookups. When staff ask the assistant to look up a code, it may send a search term to public services: SNOMED and ICD terminology servers and the US NPI registry. We do not send patient records to these services, and we do not authorise patient identifiers in a search. They are public services without a contract with us. Medical-literature search (NCBI PubMed, Europe PMC) and drug-label lookups (openFDA, DailyMed) have been switched off since 2 October 2026.
- Address lookup, booking-form protection and calendar. Google Maps Platform (Places autocomplete) suggests addresses as staff type them in patient registration and practice setup: the text typed and the user's IP address go from the browser to Google, which may process them outside the EU. Google reCAPTCHA Enterprise is built in to protect the public booking-request form but is not switched on; if we switch it on we will update this policy first. If a clinician connects an iCloud calendar, Apple's calendar service (CalDAV) is read to show it in Ask Brigid.
- Hosting and website analytics. Our websites and apps are hosted and delivered by Cloudflare (Cloudflare, Inc., United States; its global network), under its Data Processing Addendum, relying on the EU-US Data Privacy Framework with Standard Contractual Clauses as the fallback. It handles the network details of each request: your IP address, the page address (which in the clinic app can contain an internal record reference, never a name or clinical content), browser details and timing, and request logging is on. It also carries what you enter in our website's forms to our database in Ireland. Clinical data goes between your browser and our database in Ireland, not through Cloudflare. Cloudflare sets no cookies for us and runs no analytics for us. Optional analytics on askbrigid.com use Google Tag Manager and Google Analytics (Google Ireland Limited, with processing possible in the United States) only if you opt in. The Ask Brigid and MyBrigid apps load no analytics or advertising script.
- Letters to practices are printed and posted by Cardly (section 3). The letters carry only the practice's name and business address; no individual's name is sent.
Transfer assessments and agreement/configuration evidence remain release gates where an international route applies. The current provider register is our Sub-Processor Register.
13. Browser Extension and Meeting Capture
The browser-extension meeting notetaker, meeting recording, AI meeting summaries and filing of meeting-derived clinical content are disabled for the first-clinic release. Installing software or clicking a record control would not, by itself, establish the controller's lawful basis or satisfy participant transparency requirements.
- Reopening conditions: approved purpose and lawful basis, participant notice/permission procedure, role and access mapping, provider agreement/residency, retention/deletion test, DPIA, incident path and production evidence.
- No consent shortcut: a participant's permission, where required, does not authorise a prohibited provider route or replace the clinic's GDPR analysis.
- Fail closed: no clinic meeting may be captured through this route until the release gate is approved and the clinic has supplied its required notice and staff procedure.
This section describes the launch boundary, not an offer that meeting capture is currently approved or available.
14. The MyBrigid app
Launch status: MyBrigid is available. It was released on 16 September 2026. What follows is the privacy boundary that applies to the app as it stands today. It opens only for an adult (18 or over) whose link to their clinic has been confirmed by the clinic. Personalised medical advice and symptom triage are outside the intended release scope, and the app has no AI chat (section 6). Where AI is applied to your record it is governed by the permission you give in the app (section 6), and cross-clinic access is governed by Share your records (section 7).
- Who the controller is: when your MyBrigid account is linked to a clinic, that clinic remains the data controller of your medical record and we process it on the clinic’s behalf. A standalone record — a personal health record kept in MyBrigid without a connected clinic (conditions, allergies, medications, vitals, documents, family links) — is not something a new user can start in this release, because the app opens only with a confirmed clinic link. Some accounts created before that rule still hold such a record. For those, DJG Media Limited, CRO No. 762838 is the data controller. We hold that record only so the account owner can see it and use it. Our basis is Article 6(1)(b) (providing the account the person asked for) and, for the health information the person entered into their own record themselves for their own use, Article 9(2)(a) (their explicit consent, which they can withdraw at any time by deleting entries or deleting the account). We use that record for nothing else, and do not share it. If you hold such a record and would rather we did not, delete it in the app or write to privacy@askbrigid.com.
- Data the app itself sends us: your device’s push-notification token and its type (iPhone or iPad), so alerts you enable can be delivered (versions before October 2026 sent the browser's description of the device, its model and software version, instead of the type), minimised crash and diagnostic reports, photos and documents you choose to upload, and payment records when you pay a clinic invoice. Payments are processed by Stripe — your card number never touches our servers.
- Notifications: alerts are delivered through Apple’s push service. The notification says what kind of update it is; clinical kinds read only "New update in your record". No clinical detail is put in the notification.
- What stays on your device: Your session is stored in the device keychain.
- Face ID or Touch ID unlock (optional): you can choose to unlock MyBrigid with Face ID or Touch ID on your iPhone (Me → Login & security). Your iPhone does the check itself: your face or fingerprint data never leaves it, and we never receive, see or store it. We store only, in your device's keychain, whether you turned the setting on for your account. It is off unless you turn it on, you can turn it off at any time, and your password always works instead.
- Apple Health (optional): on iPhone you can bring readings from Apple Health into your record (Readings → Import from Apple Health). MyBrigid asks iOS for read-only access to blood pressure, heart rate, weight, body temperature, oxygen saturation and blood glucose. iOS lets you choose which of these to allow, and you can change that at any time in Settings → Health → Data Access & Devices → MyBrigid. MyBrigid never writes to Apple Health. Nothing is read until you ask it to check, and only the readings you choose are saved. A saved reading becomes part of your health record in the same way as a reading you enter yourself; we also keep Apple Health's own identifier for it, so the same reading is never saved twice. If you turn on Check every 30 days, the app checks again when you open it, at most once every 30 days, and saves new readings of the types you chose from the last 90 days; you can turn this off on the same page. We do not use Apple Health data for advertising or marketing, we do not sell it, and we do not share it with anyone other than your clinic.
- Identity verification: before you can add a family member, request a repeat prescription or book a remote visit in the app, we ask you to confirm you are the account holder. Stripe carries out this check for us: you photograph an identity document (a passport, driving licence or national identity card) and take a live selfie, and Stripe compares your face with the photo on the document. This is biometric processing. Before anything is captured, Stripe asks for your explicit consent to this on its own consent screen, and we rely on that consent (GDPR Article 9(2)(a)). You can decline, or withdraw by stopping part-way, and nothing more is captured; you can keep using MyBrigid, but family links, repeat prescription requests and remote-visit booking in the app stay unavailable until you verify, and you can still contact your clinic directly. We receive the result and the details Stripe read from the document, and we use only your surname and date of birth, which we compare with your clinic record, or with your own profile if no clinic is linked. We keep the outcome, whether those details matched and a reference number for the check, not the document, the selfie or the details on it. Once Stripe has checked the document and we have compared those details, whether or not they matched, we ask Stripe to redact the session, which removes the document images, the selfie and the details read from the document. Stripe also keeps some verification data as an independent controller, under its own privacy policy; you can ask Stripe about that data at privacy@stripe.com.
- Location and maps: if you use “find nearby clinics” or sort pharmacies by distance, the app uses your device's location. Sorting pharmacies happens on your device. For nearby clinics, the position is sent with the search. The current version asks for an approximate position, not a GPS fix, and rounds it to about 1 km before sending it; the iPhone app version published before October 2026 asks for a precise position and sends it as your device reports it. Either way it is used only for that search, and we do not store your location. The map itself is drawn by Mapbox (United States), which receives your IP address and the area of the map you are looking at, as any map service does.
- Emergency contact: you can record an emergency contact. We hold the name, relationship and telephone number you enter, for your clinic to use if your care requires it. The person named is covered by section 3.
- Family access to a child’s record: where a family member asks to see a child’s record, the link is held until the child’s clinic confirms that the person asking has parental responsibility. Nothing is shared until then.
- Your rights, in the app: there are two ways to take your data with you. Download my data (Me → Download my data) gives you a summary of what the app shows: your details, your medication list, your letters and documents and your test results, as files and spreadsheets. It is not a complete copy: it leaves out next of kin and emergency contacts, insurance details, advance directives, follow-up tasks, your full appointment history, portal messages, consent and communication-preference records, and anything the clinic has not yet released to you. My full record (on the same screen) builds a complete copy of your record, including those additional items, as a download. You can make up to three full-record requests in 24 hours; write to us if you need more. For anything else, write to privacy@askbrigid.com. To delete your account, use Me → Login & security → Delete account. The deletion covers account information, personal-record information and uploads we control, family links and device registrations, subject to applicable retention exceptions and backup expiry. We keep the account closed for up to one month in case you change your mind, and then erase it (section 11). Deleting MyBrigid does not automatically delete records held by your clinic. The clinic assesses requests about its records under applicable data-protection law, retention requirements and professional duties. Where retention is necessary, the clinic should explain the reason and period. Contact privacy@askbrigid.com about data for which DJG Media is controller, and your clinic about its records.
- Advertising and tracking: we do not use patient health data for advertising and do not authorise cross-company advertising tracking in the launch release. The App Store privacy information describes the app version distributed there; material differences should be reported to privacy@askbrigid.com.
Related legal documents
Terms of Service · MyBrigid Terms of Service · Clinician Terms · Data Processing Agreement · Software qualification · Cookie Policy · Acceptable Use Policy · Accessibility Statement · Compliance Overview
This page renders the policy itself, not a summary of it. The version is fingerprinted, so the exact wording in force on any date can be established:
SHA-256: 4d8541f0482bde60961011d56d3c3a3cf822c1ec9f5a3722ff19d187358b2cef
Source: docs/legal/PRIVACY_POLICY_2026-10-25_v23.md
Download compliance documents