Clinic order form
Last updated: 28 September 2026
Published template — completion and adoption required. Publication makes this form available for review; it does not sign it for any clinic, activate a feature, change an existing instruction or confirm that an operational commitment has been tested. Complete the clinic-specific particulars and conditions before execution or use.
Version: 2026-09-28_v8 Published: 28 September 2026
What this template changes. Aligns the intended feature and family-access scope with David's current instructions and corrects the list of unresolved particulars. It carries forward the commercial selections recorded in v7, including monthly billing from confirmed go-live, the 90-day parallel-run refund, the 36-month plan-price lock, the selected liability-cap figure and support hours. Those earlier records are not a customer's execution or Duncan's approval of this revision.
Still to complete before execution: Customer identity and authority; plan, users, usage and VAT treatment; approved features/providers; working-data window; liability aggregation and exclusions; clinical/operational retention justification; technical recovery/export/deletion evidence; and the applicable controller and supplier signatures/acceptance receipts. No blank or proposed option becomes agreed merely by appearing in this template.
1. Parties and service
Field | Agreed particulars |
|---|---|
Supplier | DJG Media Limited (trading as askbrigid.com and myBrigid), CRO No. 762838, Coliemore House, Coliemore Road, Dalkey, Dublin, Ireland |
Customer legal name and legal form | To complete; identify the controller, not only the practice's trading name |
Customer registration number, if applicable | To complete; not required for a sole trader |
Customer address | To complete |
Authorised customer signatory and role | To complete |
Customer privacy and incident contacts | To complete, including an urgent contact route |
Supplier contact | support@askbrigid.com; privacy@askbrigid.com; legal@askbrigid.com |
Start date | To complete after release conditions are satisfied; the Customer's access begins on this date |
Go-live date | The date the Customer confirms in writing that it will use the Service for its practice ("you say go"). Where a migration is performed, that confirmation follows the Customer's check of the moved records under clause 8.3. Where no migration is performed, the go-live date is the start date unless the Customer names a later date |
Migration | To complete: none, or commissioned from [source system] under the migration instruction attached to this order. Fee: none unless stated here |
Territory | Republic of Ireland |
Products | Brigid clinic app and clinic-linked MyBrigid, within the enabled scope below; MyBrigid access is free to patients and separate from clinic healthcare charges |
Included features | Attach the approved feature schedule; do not infer inclusion from a plan name |
Excluded purposes | Diagnosis, clinical triage, medical risk scoring/alerts, treatment recommendations, prescribing decisions and autonomous clinical decisions. Other unavailable routes are identified in the approved release schedule; this template does not enable them |
Patient eligibility and representative access | Own accounts: age 18+. Intended family scope: clinic-verified guardian access for under-16s and separately verified authorised adult representatives. Guardian links end at 16; ages 16–17 are handled directly with the clinic. Attach the tested authority and confidentiality procedure |
Recording/transcription and AI | Intended scope: patient recording/transcription, drafting notes from supplied material, factual summaries and administrative patient conversations; approved supplier-purpose review and access/AI-consent enforcement are required. General notes require a no-patient-information declaration |
Clinic mailbox assistance | Intended scope includes approved shared/clinic and individual staff inboxes and attachments. Attach the actual provider/purpose schedule and transparency/lawful-basis assessment; no automatic patient-consent check is represented for every unlinked email |
2. Subscription and payment
Field | Agreed particulars |
|---|---|
Plan | Essential / Professional / separately negotiated existing entitlement arrangement |
Included users and usage | To complete |
Agreed price, currency and VAT treatment | To complete; verify against the checkout/invoice before execution |
Founding discount / free period | None unless stated; specify amount and exact end date |
Billing interval | Monthly in advance, from the go-live date. No fee is payable for any period before the go-live date (clause 8.3). Activation condition: verify that checkout bills from the confirmed go-live date before signing the order |
Initial term | One month from the go-live date |
Renewal | Successive one-month terms |
Customer notice to prevent renewal | 30 days before the end of the current term |
Payment method / due date | To complete |
Payment grace, suspension and restoration | To complete; specify notice, cure period and how access is restored |
Prices on the date of this order (price lock, clause 8.4) | To complete from the published price list on the date the Customer accepts this order — on 23 September 2026 Essential €129 and Professional €299 per month billed monthly, or €103 and €239 per month billed annually, excluding VAT. Verify against the checkout before execution |
An annual arrangement requires an express completed variation stating the annual charge, term, renewal and cancellation rules; a displayed monthly equivalent is not a monthly subscription. Full AI is not offered as a new self-service sale. No optional feature may bypass the release's clinical or privacy restrictions through a higher subscription tier.
3. Termination and continuity
Convenience termination: Customer gives 30 days' written notice effective at the end of the current monthly term, except during the parallel period, when clause 8.2 applies instead (immediate effect; refund as clause 8.2 sets out); Supplier gives 90 days' written notice. Termination for material breach: written notice and 30 days to cure, subject to any lawful need for earlier protective restriction. The DPA's supplier-objection termination remedy applies.
Commercial suspension does not create a new right to retain patient information or prevent fulfilment of data-protection obligations. Agree the authorised export/access route during any suspension or dispute before execution. The parties coordinate an orderly exit; patient care and statutory records requests are not resolved merely by disabling a subscription.
4. Return/deletion on exit
The Controller chooses return or deletion under the DPA. David selected the following periods for this template on 19 September 2026. They require clinic agreement and technical verification before becoming commitments:
Stage | Proposed deadline and trigger |
|---|---|
Export window | 30 days from the end of service. Export during the term, at any time and without fee, is clause 8.1 |
Active-system deletion | Within 90 days after the export window closes |
Backup expiry | Within 90 days after active-system deletion |
The completed schedule must cover database backups and copied storage objects, approved supplier copies and any justified retention exception. Backup copies are restricted from ordinary use; restoration must preserve deletion/restriction decisions. Record the method, evidence and responsible owner. A rolling database backup alone does not establish expiry of object-backup copies. The supplier confirms completion or explains a lawful retention exception with category, basis and duration.
No production patient processing begins under this order until these periods/processes and the record-category schedule below are agreed in writing and can be met.
5. Support, availability and incidents
Ordinary support hours: Monday–Friday 09:00–17:00 Europe/Dublin, excluding Irish public holidays, through the in-product report control or support@askbrigid.com. First-response targets are urgent 15 working minutes, high one working hour, normal four working hours and low 24 working hours. These are contractual first-response targets, not resolution guarantees, adopted on David's confirmation. The clock starts when a request is received during support hours; a request received outside those hours starts at the next opening. Only time within support hours counts: the clock pauses at closing and resumes at the next opening. All times follow Europe/Dublin, including daylight-saving changes. For clarity, 24 working hours means three full eight-hour support days, not 24 elapsed hours. Security-incident handling below is separate and is not paused by this support schedule.
No numerical uptime commitment or service credit applies unless expressly completed in an attached schedule. State planned-maintenance arrangements and measured recovery targets separately.
Security incidents are separate from ordinary support. The DPA's without-undue-delay/24-hour controller-notification commitment applies when the Supplier becomes aware of a covered breach, including outside support hours. Incident lead: David Galvin. Proposed deputy: Mark, subject to confirmation of contact and availability. Attach the tested urgent contact route; do not promise “next business day” as the only incident response.
6. Liability and insurance
The selected inter-party liability cap is the greater of €50,000 and the fees paid in the twelve months before the first event giving rise to the claim, applied to the stated twelve-month aggregation period. David confirmed adoption of this cap on 19 September. The precise aggregation-period operation, exclusions, any separate data-protection limit and treatment of customer-data loss remain to be completed before execution; adoption of the figure does not resolve those unspecified particulars.
Nothing excludes liability that cannot lawfully be excluded or limits a data subject's mandatory rights under Article 82 GDPR. Statutory conditions govern liability between responsible controllers/processors and to data subjects; a contract between these parties does not determine a patient's rights. The DPA's Article 28 duties remain intact. Specify the interaction between those duties and any permitted inter-party monetary limit expressly.
Current insurance position: David reported on 19 September 2026 that the Supplier has no cyber insurance and no technology professional-indemnity insurance currently in place. No insurer, policy, insured limit or coverage certificate is represented. David selected proceeding with launch with this absence of cover disclosed for Mark's review. This records the Supplier's launch preference, not completed legal review of this revision or a Customer's acceptance. The Customer must receive this disclosure in the order before deciding whether to enter the agreement. If cover is subsequently obtained, record the actual insurer, policy reference, limits/excess, exclusions, territory, dates and written confirmation that the intended activity is covered. A quote, application or unsigned template is not evidence that cover is in force.
7. Contract documents and precedence
Enter exact versions of the platform terms, DPA and each schedule. For personal-data processing duties, the DPA prevails over conflicting commercial wording. This order supplies the clinic-specific particulars the DPA expressly leaves to it; it does not reduce mandatory obligations. For other commercial particulars, this order takes precedence over the platform terms to the extent expressly agreed. The parties must resolve remaining conflicts before execution, with legal review and privacy advice as appropriate.
Incorporated document | Version / file / evidence reference |
|---|---|
Brigid Terms of Service | To complete |
Data Processing Agreement | To complete; current accepted versions are not replaced by a published template without the applicable execution/change process |
Schedule A — processing/retention | Complete below |
Schedule B — authorised suppliers | Complete below |
Service/support variations | None unless attached and identified |
The four guarantees | Clause 8 of this order |
8. The four guarantees
These are the four guarantees published on askbrigid.com on the date of this order, made binding here in the words of this clause 8; the website's wording summarises them and is not incorporated. The liability cap in clause 6 does not reduce a refund due under clause 8.2 or fees waived under clause 8.3. They are commercial terms: for personal-data duties the DPA still prevails (clause 7), and nothing here reduces a mandatory obligation. For commercial particulars they prevail over any conflicting wording in the platform terms.
8.1 Your data leaves free. At any time during the term, and during the export window in clause 4 after it ends, the Customer may ask for a full export of the data the Supplier processes on its behalf, in a structured, commonly used and machine-readable format (DPA clause 10), with stored documents and recordings in their original file formats. The Supplier delivers it within five Business Days of the request. No fee is charged for any export requested within that window, including on exit. This is in addition to the self-service export in the Service. "Business Day" means Monday to Friday, excluding Irish public holidays. Activation condition: a Supplier-run full export of a live clinic, delivered inside five Business Days, must be proven before an order is signed on this clause.
8.2 Run it alongside your current system for 90 days. For 90 days from the go-live date (the parallel period) the Supplier does not require the Customer to switch off, cancel or stop using any existing system, and nothing in the Service does so. The Customer may end this agreement at any time during the parallel period by written notice, with immediate effect — the 30-day notice in clause 3 does not apply. The Supplier then:
- refunds in full every subscription fee paid under this order, and the unused balance of any top-up tokens the Customer bought at the price it paid for them, within 30 days of the notice;
- provides the export in clause 8.1 free of charge; and
- applies clause 4 to return or deletion.
Fees already incurred on patient card payments taken through the Service during the parallel period are not refunded, because they relate to money the practice has already received.
8.3 We move your data, and you don't pay unless you go live. Where the Supplier performs a migration under this order (from HealthOne, Socrates, iMedDoc, a spreadsheet or paper records, under the migration instruction attached to this order, clause 1), the Supplier maps the records out, rehearses the move against representative records, and sets the Service up with the Customer's staff. The Customer checks the moved records before go-live. If anything is missing or wrong when the Customer checks it, the Supplier fixes it before go-live. If the Supplier cannot fix it to the Customer's reasonable satisfaction, the Customer may decline to go live by written notice: this agreement then ends, no fee is payable (billing starts only at go-live, clause 2), and imported copies are deleted under Schedule A.
8.4 The price on your first order is your price for three years. For 36 months from the go-live date, the Customer may subscribe to any plan that was offered for self-service on the date the Customer accepted this order, at the price recorded for it in clause 2 — including on a change of plan — and no price increase applies on any renewal in that period. After 36 months the then-published price applies from the first renewal that begins at least 30 days after the Supplier gives the Customer written notice of it. An annual arrangement is priced under its own variation (clause 2).
Schedule A — processing and retention
The DPA states the ordinary processing operations and data categories. Record the clinic's specific purposes/restrictions and category schedule here. A separate migration instruction is required only if a migration is commissioned; do not demand an extra migration document from a clinic starting with no import.
Record category | Purpose and controller | Period / start trigger / basis | Deletion and backup method |
|---|---|---|---|
Clinical record, including final clinician notes | Delivery of care by the Customer as controller | The patient's lifetime plus eight years after confirmed death, subject to applicable exceptions and documented preservation holds. This proposed clinic policy requires the Controller to document necessity and applicable specialty or statutory duties; it is not a universal statutory minimum | Controller-instructed erasure of the active record, followed by backup expiry within the period in clause 4 |
Raw consultation audio, if enabled | Working aid, not the record. The checked transcript and the clinician's note are the clinical record | Deleted 24 hours after the clinician accepts the transcript or note, and in any case 7 days after recording. The Customer may instruct a different period, which overrides these defaults. See audio retention schedule. Activation condition: verify the current production deletion mode and a successful rehearsal; the earlier draft recorded report-only mode and is not fresh runtime evidence | Scheduled deletion of the audio object; backup expiry within the period in clause 4 |
Raw/edited transcripts | Same purpose as the clinical record once filed to it; working data until filed | Filed to the clinical record: as the clinical record row. Unfiled after the working-data window: deleted as working data | Active deletion on filing decision or window expiry; backup expiry as above |
Patient messages, submissions and uploads | Care communication and record completion by the Customer | Filed to the clinical record: as the clinical record row. Not filed: working data, deleted on the working-data window | Active deletion; backup expiry as above |
Imported source files and temporary processing | Migration and format conversion only, where a migration is commissioned | Working data. Deleted once the import is reconciled and accepted, and in any case on the working-data window | Active deletion of source files and intermediates; backup expiry as above |
Patient links, sharing and representative authority | Controlling who may see a record | Authority records follow the clinical record. Share links and their tokens are working data and expire on their own stated expiry, independently of the record they point at | Link/token expiry and revocation; authority records deleted with the record |
Clinical-access/security and choice evidence | Accountability, security investigation and proof of the patient's choices | Access and security logs: as stated in the security documentation. Legal and optional-choice receipts: six years after the relevant relationship ends, subject to a documented necessity assessment, applicable holds and a verified deletion process | Controlled service-only deletion runner with scoped holds; content-free run log retained |
Supplier-held copies and backups | Underlying purpose/role | Active supplier copies are deleted under the agreed instruction and supplier terms. Restricted backups expire within the agreed backup period. Any separate lawful retention is identified by category, role, basis and period | Supplier deletion on instruction; backup expiry by rotation, not by selective edit |
The Customer's acceptance of this order is the documented instruction. Article 28(3)(a) requires the processor to act only on the controller's documented instructions. The Customer does not need to supply a separate instruction document: accepting this order at signup adopts the periods in this Schedule A as the Customer's documented retention instruction to DJG Media, and the executed copy is the record of it. Where the Customer wants different periods, it states them in this Schedule before acceptance and those override the defaults. Leaving a row unchanged is an instruction to apply it.
Working-data window. Working data that is not filed to the clinical record is deleted from active systems 30 days after it is created (period proposed, not yet selected), and in any case under clause 4 when service ends; backups then expire within the clause 4 backup period.
Two classes, one rule each. Anything filed to the clinical record follows the clinical record's period. Everything else is working data and goes on the shorter working-data window. Filing is a workflow classification, not the legal test for retention. The Controller must assess the purpose, necessity and applicable duties for each category, including correspondence or audio that itself forms part of a care record. This split is DJG Media's proposed standard, selected by David on 19 September 2026. It is a draft until the Customer confirms it and the active-plus-backup deletion sequence is proven end to end; see the release condition at the end of clause 4 and the release review below.
Record legal holds/retention exceptions and the review/release process. Do not classify every professional recommendation as a statutory minimum. The clinic's privacy notice must identify its processing and Brigid's role.
Schedule B — supplier authorisation
Complete only for the routes actually used. The public register includes historical and excluded providers and is not itself this clinic's authorised set. Assess controller versus processor roles per service. In particular, payment processing for the Supplier's own billing and clinic invoice processing need not have identical roles.
Provider/service | Purpose, data and role | Countries/remote access | Contract/transfer evidence | Retention/configuration evidence | Authorised? |
|---|---|---|---|---|---|
Supabase database/auth/storage/backup | To complete | To complete | To complete | To complete | Pending |
Google service(s), if included — list each | To complete | To complete | To complete | To complete | Pending |
Vercel hosting/logs | To complete | To complete | To complete | To complete | Pending |
Sentry monitoring, if included | To complete | To complete | To complete | Scrubbing/access evidence | Pending |
Resend transactional email, if included | To complete | To complete | To complete | To complete | Pending |
Stripe service(s), if included | To complete | To complete | To complete | To complete | Pending |
Apple APNs, if included | Device tokens/minimal notifications; role to confirm | To complete | To complete | To complete | Pending |
SMS or other communication service, if included | Identify the actual route, not a generic provider list | To complete | To complete | To complete | Pending |
The DPA's advance supplier-change notice and objection process applies. Adding a row here does not fill a missing contract or transfer safeguard.
Execution
Customer | Supplier | |
|---|---|---|
Legal entity | Pending | DJG Media Limited |
Authorised signatory / role | Pending | Pending |
Signature or attributable electronic acceptance | Not signed | Not signed |
Date and exact document version | Pending | Pending |
Before execution: complete the customer particulars, record the authorised signatory, settle every proposed option, attach the applicable schedules and verify the stated operational commitments. Supplier publication approval is not a clinic signature or evidence of solicitor review. The company has authorised publication; external solicitor review of this revision remains pending. Earlier review snapshots retain their own versions and fingerprints.
Additional review notes
The lifetime-plus-eight-years clinical-record proposal is not asserted to be one statutory rule for every specialty. Each clinic must confirm a justified category schedule. Review the very short support targets against actual staffing and the availability of an urgent incident contact. Verify the full export and go-live billing guarantees before execution; a template promise is not operational proof.
Download the exact document (Markdown)
SHA-256: 4987d41d863bf7748e9b7557f03c23f16d757a7fb9a70d7407596f8b36491da0
Source: docs/legal/ORDER_FORM_2026-09-28_v8.md