Ask Brigid Terms of Service
Last updated: 25 October 2026
Version: 2026-10-25_v9 (supersedes 2026-10-02_v8; re-acceptance required) Effective: 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: the laws of Ireland; exclusive jurisdiction of the Irish courts
1. Services
DJG Media Limited, CRO No. 762838 ("we") provides Ask Brigid, a practice administration and patient-record platform (the "Service"), through its clinic web and iOS apps and the connected MyBrigid patient app. The Customer is the practice that subscribes. Where an order form is executed, it identifies the Customer, plan, enabled features and processing instructions; where there is none, the subscription the Customer chose and the settings it uses do.
The Service includes patient-record management, staff-controlled scheduling, clinic communications, document handling and billing. Optional AI assistance (the Ask Brigid assistant, including voice through Ask Brigid Live) and transcription are subject to clause 5. A plan name or a permission setting does not authorise a feature that is unavailable or has not completed its required review.
The intended purpose of the Service is the administration of a healthcare practice: records, scheduling, communications, document handling, billing, transcription, and the preparation of drafts for a clinician to review and sign. It is not intended for the diagnosis, prevention, monitoring, prediction, prognosis, treatment or alleviation of disease, for clinical triage, or for clinical decision support, and the Customer must not use or configure it for any of those purposes.
2. Use Rights & Restrictions
We grant you a non-exclusive, non-transferable licence to access and use the Service for your internal business operations. You agree not to:
- Resell, sublicence, or lease the Service to third parties.
- Reverse-engineer or attempt to discover the source code of the Service.
- Modify or create derivative works based on the Service.
You must comply with the Acceptable Use Policy at askbrigid.com/acceptable-use, which forms part of these terms. We may suspend or terminate access as that policy describes.
3. Service Levels
Any binding availability target, support window, maintenance notice, service credit and exclusion is stated in a signed order form or service-level schedule, where there is one. Without one, no numerical uptime level or service credit applies.
4. Data Ownership & IP
Customer Data: You own all right, title, and interest in and to all data submitted by you or your users to the Service.
Company and Ask Brigid IP: We own the platform, software, Ask Brigid orchestration and configuration, brand assets, and documentation. Third-party models and services remain the property of their providers. No rights are granted except for the limited licence to use the Service.
5. AI Features — Patient Permissions, Clinician Duties, EU AI Act
The intended AI functions are transcription, preparation of draft notes and letters from supplied material, factual summaries of existing records, assistance with clinic email, and spoken instructions for administrative tasks through Ask Brigid Live. The AI features are not intended to make diagnoses, grade medical risk, perform clinical triage, recommend treatment, prescribe or make autonomous clinical decisions. The actual intended purpose, outputs and use of each feature must be assessed; describing it as administrative does not determine its medical-device status or override supplier terms.
The AI functions included are those that section 6 of the Privacy Policy lists as switched on, to the extent the Customer uses them; an executed order form or release schedule may narrow them. Before switching a function on for a Customer's patients, we verify the applicable provider agreement, processing route, privacy assessment and regulatory position, and we keep each function under review afterwards. We may restrict or switch off a function, on notice where practicable, if that review requires it. No patient choice or Customer instruction overrides an unlawful or contractually prohibited use.
- Patient notes and dictation: staff must identify the patient and verify their record access and the patient's applicable AI permission before sending patient content to AI or cloud transcription. Automated checks must support this requirement; the current implementation status is disclosed in section 6 of the Privacy Policy. The same rule applies when the clinician dictates their own note about the patient. A consultation recording also requires the clinic's recording procedure, notice and applicable permission.
- General notes: staff may record an administrative note after confirming that it contains no patient information. General note is not a way to bypass a patient's refusal or a missing record link. Staff use the patient-note flow if patient information is involved.
- Chat and summaries: patient-linked inputs, retrieved records and reusable conversation material require the applicable access and permission checks. Historical conversation material whose patient scope cannot be verified must be excluded from new AI input while remaining available for authorised staff viewing. The rollout of the automated exclusion is disclosed in section 6 of the Privacy Policy. The service must not represent an unverified patient scope as consented.
- Voice (Ask Brigid Live): staff can give spoken instructions for administrative tasks such as the diary, tasks and invoices. Reading a patient's record by voice is not available. Before the microphone opens, the user is told that they are speaking to an AI system.
- Patient conversations: no AI conversation with patients is offered. Messages from patients are handled by clinic staff.
- Clinic email and attachments: authorised staff can connect approved clinic/shared or individual staff mailboxes and use the enabled email assistance. The Customer must have authority for the mailbox and the processing, document the purpose and lawful basis, and comply with transparency and applicable confidentiality duties. The sub-processor register lists the email and AI providers used. Mailbox sorting puts emails in an order for staff to open them; it is not a statement about a patient. Email processing is not represented as automatically checking a patient-specific consent for every unlinked message or attachment.
- Review: staff check AI output against its source, correct errors and omissions, and approve a draft before signing, sending, filing or relying on it. An AI draft is not an autonomous clinical decision.
Roles under the EU AI Act. For the purposes of Regulation (EU) 2024/1689 we are the provider of the Service's AI functions and the Customer is the deployer (Article 3(3) and 3(4)). The functions are not intended for any use listed in Annex III, and the Service is not intended for a medical purpose (clause 1), so we treat them as not high-risk. The Customer must support the AI literacy of the staff who use them (Article 4) and use each function only for its stated administrative purpose. The Customer must not repurpose a function for diagnosis, triage, prognosis or treatment decisions; doing so would breach these terms and could make the Customer the provider of a different AI system under Article 25(1)(c). AI output is marked as AI-generated, and the Customer must not remove that marking.
Clinicians remain responsible for professional judgments and the records they approve. They must use only functions permitted for their role and purpose, and must not circumvent access, patient-choice or recording controls. Our medical-device position is set out on the Software qualification page. The note and letter drafting functions are being assessed under Article 2(1) of Regulation (EU) 2017/745 and MDCG 2019-11; these terms do not assert that an assessment or regulatory approval has been completed.
6. Audit and logging
The Service maintains audit records for covered security, access and consequential-action events. Our security documentation, available to the Customer on request, identifies the events captured, the applicable integrity and access controls, and material limitations. This is not a representation that every database event is captured or that every log has identical immutability or external anchoring. Retention follows the controller's documented instructions, the Data Processing Agreement, necessity review, and applicable legal or professional requirements.
On request, audit-log extracts are made available to the data controller (your clinic). They are made available to the Data Protection Commission and to other regulators only where the law requires it or the clinic instructs us.
Patient access-log extracts (Article 15). The Service can produce a patient's own access log: the date and time of each access, the name and role of the person who made it, what was accessed, the stated reason, whether emergency break-glass access was used, and the categories of data involved. It is produced from within the practice by a member of staff who holds permission to view that patient and a care relationship with them. It never includes a staff member's IP address, device or user agent, which describe the staff member rather than the patient. Producing an extract is itself recorded in the log, so it appears in the next one. Patients exercise their Article 15 rights through their clinic, which is the controller of their records: this clause is our commitment that the Service gives the clinic the means to answer such a request, not an undertaking by us to answer it to the patient directly.
7. Limitation of Liability
(a) Nothing in these terms excludes or limits liability for fraud or fraudulent misrepresentation, for death or personal injury caused by negligence, or any liability that cannot lawfully be excluded or limited, or limits a data subject's rights under Article 82 GDPR.
(b) Subject to (a), our total liability to the Customer for all claims arising in any twelve-month period under or in connection with the Service is limited to the greater of €50,000 and the subscription fees the Customer paid in the twelve months before the first event giving rise to the claim.
(c) Subject to (a), we are not liable for loss of profit, revenue, business or goodwill, or for indirect or consequential loss.
(d) The Service is provided with reasonable skill and care. AI output is a draft that the Customer's clinician must check (clause 5); we do not warrant that it is accurate or complete.
(e) An executed order form may set different limits. Where it does, it applies instead of (b) and (c).
8. Governing Law
These terms and any dispute arising from them are governed by the laws of Ireland, and the Irish courts have exclusive jurisdiction. Between businesses, and to the extent the law allows, terms that statute would otherwise imply are excluded.
The Service is provided by DJG Media Limited, CRO No. 762838, registered office at Coliemore House, Coliemore Road, Dalkey, Dublin, Ireland. The Ask Brigid family comprises Ask Brigid for staff and clinics and MyBrigid for patients; voice dictation is built into Ask Brigid. The Ask Brigid assistant is the AI assistant embedded in those services. These are product names, not separate legal entities.
9. Term, suspension and termination
Where an order form is executed, its termination rights and notice or cure periods apply. Where there is none, the Customer may cancel its subscription as the Refund and Cancellation Policy describes, and the payment, grace-period and refund rules in that policy apply; we may end the subscription on 90 days' written notice and, if we do, refund the subscription fees paid for any period after the end date. Following termination, we make customer data available for export and then return or delete it as clause 10 of the Data Processing Agreement sets out, in line with the controller's documented choice and applicable law. Tax and accounting records that DJG Media Limited holds for its own legal obligations are retained for the applicable period (generally six years under Irish Revenue guidance).
Suspension or termination for breach of the Acceptable Use Policy is as that policy describes (see clause 2 above and section 6 of that policy).
10. Payments from patients
If the Customer takes card payments from patients through the Service (deposits, invoices, or payments in MyBrigid), the payments are made to the Customer's own account with our payment provider, Stripe, under Stripe's terms for that account. The Customer is the seller. On each payment we charge a platform fee, a percentage of the payment set by the Customer's plan and shown on our pricing page on the day the Customer subscribes. The price guarantee in the Refund and Cancellation Policy applies to that percentage in the same way as to the subscription price. The fee is deducted from the payment by Stripe and is not returned if the Customer refunds the patient. Stripe's own processing fees are separate. The Refund and Cancellation Policy says how refunds to patients are handled.
11. MyBrigid and patient sharing
A patient can link a MyBrigid account to their record at the Customer's practice. Two controllers are then involved, each for its own processing: the Customer is the controller of its clinical record, and we are the controller of the patient's MyBrigid account (the account itself, the information the patient records in it and the choices they make there), as our Privacy Policy describes. When the patient chooses to share their record with another clinic, the record is made available to that clinic only at the patient's choice; each clinic is then the controller of what it holds. Neither party decides the other's purposes or means. Each party answers requests from patients about the processing it controls, and each tells the other without undue delay if it receives a request, or becomes aware of a personal data breach, that concerns the other's processing. Our processing of the Customer's clinical record on the Customer's behalf is governed by the Data Processing Agreement.
12. Professional-use obligations (Schedule 1)
The professional-use obligations published at askbrigid.com/clinician-terms — registration, indemnity, clinical authorship, audit-log accuracy, patient privacy and notification of regulatory change — form a schedule to these terms and are set out in Schedule 1. Schedule 1 forms part of these terms and binds every clinician who uses the Service for clinical work. The published page is provided for information; if it and Schedule 1 differ, Schedule 1 applies.
13. Documents and order of precedence
The agreement between us and the Customer is made up of: (1) an executed order form, if any; (2) the Data Processing Agreement, which prevails on the processing of personal data; (3) these terms, including Schedule 1; and (4) the Refund and Cancellation Policy and the Acceptable Use Policy. If they conflict, the earlier-listed document prevails, except that the Data Processing Agreement prevails over the order form on the processing of personal data. The Customer accepts the Data Processing Agreement through the acceptance step in the Service before production patient data is processed. The person who accepts these terms for a practice confirms that they have authority to bind it.
14. Usage allowance, top-ups and fees
The Customer's allowance of AI use, any top-ups and any charge for use above the allowance are those shown at checkout or in the order form. Fees are charged as the Refund and Cancellation Policy describes.
15. Notices
Notices to us go to legal@askbrigid.com, or to support@askbrigid.com for cancellation under the Refund and Cancellation Policy. Notices to the Customer go to the account owner's email address and to the address in the order form, if there is one. An email notice is received on the next business day after it is sent, unless the sender receives a bounce message.
Schedule 1 — Professional-use obligations
This Schedule applies to every licensed clinician (medical doctor, dentist, nurse, physiotherapist, pharmacist or allied health professional) who uses the Service for clinical work (the "Clinician"), on any clinician-facing surface. If the Clinician does not accept these obligations, the Clinician must not use the Service for clinical purposes.
-
Registration. The Clinician will keep their registration with the relevant professional body current: the Medical Council, the Dental Council, NMBI, CORU, the Pharmaceutical Society of Ireland, or the statutory regulator for the profession.
-
Professional indemnity. The Clinician will maintain professional indemnity insurance covering their clinical scope of practice for the whole period of their use of the Service.
-
Notification of regulatory change. The Clinician will notify DJG Media Limited within 30 days if their registration or their indemnity insurance changes status, including suspension, restriction, expiry or lapse.
-
Clinical authorship and verification. As part of their professional record-keeping duty and under these terms, the Clinician must author, read, verify and correct the clinical record before it is signed, sent, filed or acted on. The Clinician must not bypass the approved feature, access or patient-permission controls, and must not use an administrative feature for diagnosis, triage, prescribing, treatment recommendations or medical advice.
-
Audit-log accuracy. The Clinician will not falsify, delete or attempt to circumvent the audit log of their clinical actions. This is a contractual security and accountability requirement and supports the Clinician's professional record-keeping duties.
-
Patient privacy. The Clinician will access only the patient records strictly necessary for the care they are providing, applying the least-privilege principle and the data-minimisation principle in Article 5 of the GDPR.
Related legal documents
Clinician obligations (Schedule 1) · MyBrigid Terms of Service · Privacy Policy · Data Processing Agreement · Refund and Cancellation Policy · Software qualification statement · Acceptable Use Policy · Cookie Policy · Compliance Overview
This page renders the terms themselves, not a summary of them. The version you accept is fingerprinted, so the exact wording agreed can always be established:
SHA-256: 0944c381a38f7226c31ad470bacb11f93f48bbbb9ce2600b0209ccbdbbb4dd8c
Source: docs/legal/CLINICIAN_TOS_2026-10-25_v9.md
Ask Brigid Terms of Service — provenance
This note is not part of the contract. It is rendered on askbrigid.com/terms beneath the
SHA-256 footer, and it is deliberately kept out of the fingerprinted bytes: a hash over a
contract should cover the contract, not a commentary on it. The canonical contract file is
docs/legal/CLINICIAN_TOS_2026-10-25_v9.md, and the SHA-256 shown on the page is the SHA-256
of that file, whole and unmodified — the same value stored on the terms_versions row that
every acceptance binds to. Anyone can recompute it.
Why the fingerprint exists
A version label alone does not identify what was agreed. From version 2026-08-31_v5 onwards, each version of these terms has a canonical file and a SHA-256 fingerprint, and an acceptance is bound to that fingerprint. Version 2026-07-21_v4 has no fingerprint, and no fingerprint has been asserted for v4: its published wording was revised while it was in force, so no single text can be attached to it, and none is claimed. Later versions replace it, and an account that accepted only v4 is asked to accept the current version.
Version history
2026-08-31_v5 — the first version with a canonical file and a fingerprint. Its wording was
EXTRACTED from the page that was already publishing it — not retyped — and the extraction was
diffed back against that page's own text before the file was created: 771 words each side,
identical. No clause was added, removed or reworded in v5. Two accounts accepted it, and those
acceptances remain bound to the v5 fingerprint
(abb3406a692e18314223f2ce63b909314fa68e4d9eb44b317f5f519d9b80025c), not to anything published
later.
2026-09-10_v6 — changes the wording, so it is a new terms_versions row with its own
fingerprint and every account is asked to accept it afresh. What changed:
- this provenance note was moved OUT of the contract text, so the hash covers the contract alone;
- the Acceptable Use Policy was incorporated into clause 2;
- the "administrative candidate" wording in clause 5 was replaced with the four administrative routes actually enabled between 25 and 31 August 2026 on Google Vertex AI (EU);
- a single entity and governing-law form was adopted, matching the DPA;
- clause 6, "Audit and logging", is new. It states the append-only guarantee and the
hash chain, and it puts the patient access-log extract back into the contract. That sentence
had been removed on 7 September 2026 because the extract did not exist and the terms should
not promise what the product could not do. It exists now —
patient_access_log_extract, a tenant-scoped, permission-gated, care-relationship-gated function that returns no staff IP or user agent and records its own use — so the commitment is made again, in the accepted document rather than only on an informational page; - clause 9 (term, suspension and termination) carries the house post-termination data sentence;
- clause 10 and Schedule 1 bring the professional-use obligations, previously published only on the unfingerprinted /clinician-terms page, into the accepted document.
2026-10-01_v7 — a new terms_versions row: note and letter drafting, transcription and the
other AI routes described as they run, and the Ask Brigid / MyBrigid names. Published 1 October
2026 at 22:15 UTC; nobody accepted it before v8 replaced it.
2026-10-02_v8 — a new terms_versions row, re-acceptance required: no AI conversation with
patients is offered; a practice without an order form cancels under the Refund and Cancellation
Policy; the platform fee on patient card payments; who is controller of what when a patient uses
MyBrigid; the "trading as" wording dropped pending advice. Record:
docs/compliance/LEGAL_SET_CHANGE_LOG_2026-10-02.md.
2026-10-25_v9 — a new terms_versions row, re-acceptance required: a liability cap and
exclusions for practices without an order form; the intended purpose of the Service and the
parties' roles under the EU AI Act; Ask Brigid Live described; the provider-review statement in
clause 5 corrected; documents and order of precedence, usage allowance and notices clauses added;
the "previously titled" sentence removed.
Download compliance documents