Ask Brigid is practice software built for speed. Brigid Clinical Intelligence takes on the admin, and patients pay by card through a link.
Some of it is, and some isn't. Of the practice systems sold to Irish consultants, a few publish that patient records sit in Ireland, some host elsewhere in the EU, and at least one hosts in the UK. GDPR itself doesn't require Irish storage. What matters is that you know where your records are, what else touches them, and what legal route covers anything that leaves the EEA.
This article explains public information and the law in general terms. It is not legal advice.
What GDPR actually requires
GDPR treats the European Economic Area as one space. Patient data stored in Dublin, Frankfurt or Amsterdam is all inside it, and moving data between them needs no special transfer mechanism.
Leaving the EEA is different. Chapter V of the GDPR allows a transfer to a non-EEA country only on one of a few bases. The two you'll see most in vendor paperwork are:
- An adequacy decision. The European Commission has found the country's protection essentially equivalent. Its list of adequacy decisions includes the UK, and the US for companies in the EU-US Data Privacy Framework.
- Standard contractual clauses. Contract terms approved by the Commission, signed between your vendor and its supplier.
The UK matters most for Irish practices. The Commission renewed the UK's adequacy decision on 19 December 2025, and it now runs until 27 December 2031. So UK hosting is a lawful route today, but it is outside the EU, and it depends on that decision staying in place.
Some hospital contracts, insurers or your own policies may ask for more than the law does, for example EU-only or Ireland-only storage. If yours does, that's the requirement to test vendors against.
Where each system says it keeps your records
This is what each vendor's own public pages said when we read them on 10 November 2026. We haven't audited anyone's infrastructure, including our own. Vendors change hosting, so check the current page before you rely on it.
| System | What the vendor publishes about storage | Source |
|---|---|---|
| Ask Brigid | Database, sign-in and file storage in Ireland (AWS eu-west-1). AI processing in Google Cloud EU regions. Named routes outside the EU, such as email and support access. | Data processing agreement, clause 12 |
| Enquiry Medical | Home page FAQ: "patient and practice data stored within Ireland" and "no patient data is processed outside the EU". Its patient record page says "EU-based infrastructure". | enquirymedical.ie |
| Karesta | "A Dublin datacenter with West Europe failover", under the Irish Data Protection Commission. Aimed mainly at allied-health and GP clinics. | karesta.com |
| SigniQ | "Built and hosted in Ireland", on "Irish-controlled infrastructure". Listed by the Health Innovation Hub Ireland and aimed at physiotherapy and allied health. | hih.ie |
| Socrates | Data "stored by you, locally, on a server at your practice", unless you choose its cloud hosted option. Off-site backup keeps an encrypted copy elsewhere. The FAQ doesn't name a cloud region. | Socrates security FAQ |
| iMedDoc | "Hosted on Amazon Web Services (AWS) in the UK." | iMedDoc FAQ |
| CloudMedico | Application and database servers with DigitalOcean in Frankfurt, Germany. Some sub-processors are outside the EEA, mainly in the US. | CloudMedico privacy policy |
Two things stand out. First, "Ireland" and "EU" are not the same claim, and one vendor uses both on different pages, so ask which applies to the patient record. Second, a server in your own rooms is local, but then backups, security updates and physical security are partly your job.
If you're on iMedDoc and want to understand the export side, our guide to extracting your records from iMedDoc's AWS UK hosting covers it.
Storage is only half the answer
The database is where records rest. Plenty of other services can touch the same data:
- Email and text messages. Appointment reminders and letters usually go through a third-party sending service, which may be in the US.
- AI features. Scribes, letter drafting and summaries often send audio or text to a cloud AI provider. Check the region for those calls separately.
- Backups. A backup copy can sit in a different region or with a different supplier from the live database.
- Support access. A supplier's engineers may be able to reach the system from outside the EU, under contract terms.
- Card payments, maps and video calls. Each is its own supplier with its own location.
None of this is automatically wrong. It's normal, and GDPR has rules for it. But a single line such as "your data stays in Ireland" can't cover all of it, so the sub-processor list is the document to read.
Five questions to ask any vendor
Send these in writing and keep the reply:
- Which country, and which data centre region, holds the live patient database? Where are the backups?
- Please send your current sub-processor list, with each supplier's location and what data it receives.
- Which of those routes take patient data outside the EEA, and what Chapter V basis covers each one?
- Where do AI features process audio and text, and is any of it kept or used for training?
- How much notice will you give before you add a sub-processor or move hosting, and can I object or leave if you do?
Our data processing agreement checklist goes further on the contract side, and our piece on checking where a dictation app stores data covers dictation tools.
Where Ask Brigid stands
Here's what our own published terms say, including the parts that aren't in Ireland.
- In Ireland: the database, sign-in and file storage run in AWS Dublin (eu-west-1), through our database provider, Supabase. Server functions called from the web apps are pinned to Ireland.
- Elsewhere in the EU: AI drafting and admin helpers use Google's Gemini models on Vertex AI in Google's EU multi-region. Search copies are processed in the Netherlands, and the chart summary may fall back to Frankfurt.
- Outside the EU, and named in the agreement: transactional email (Resend, United States), remote support access by Supabase (a Singapore company) and by Google Cloud support staff under standard contractual clauses, sign-in texts for staff who choose them (Twilio), and server functions called from the iPhone app, scheduled jobs or supplier webhooks, which can run outside the EU and hold data only in memory while they handle a request.
The full list, with each supplier's status, is on our sub-processor register, and clause 12 of the data processing agreement sets out the transfers. We give at least 30 days' written notice before adding or replacing a sub-processor that will process your data. We don't claim any security certification.
Frequently asked questions
Does GDPR require patient data to be stored in Ireland?
No. GDPR doesn't require storage in Ireland or in any one member state. Data can move freely within the EEA. Sending it outside the EEA needs a legal basis under Chapter V, such as an adequacy decision or standard contractual clauses. Some contracts or hospital policies may ask for more, so check yours.
Which practice software keeps patient data in Ireland?
From what vendors published on 10 Nov 2026: Ask Brigid keeps its database, sign-in and file storage in AWS Dublin (eu-west-1). Enquiry Medical's FAQ says data is stored within Ireland. Karesta says a Dublin data centre with West Europe failover. Socrates data sits on a server in your own practice unless you use its cloud option. iMedDoc says AWS in the UK. CloudMedico says Frankfurt.
Where is iMedDoc data hosted?
iMedDoc's FAQ says practice data is hosted on Amazon Web Services in the UK. The UK has an EU adequacy decision that runs to 27 December 2031, so this is a lawful transfer route, but the data is outside the EU.
Is UK hosting allowed for Irish patient data?
Yes, as things stand. The European Commission renewed the UK's GDPR adequacy decision on 19 December 2025, and it runs until 27 December 2031. If it lapsed, transfers would need other safeguards.
Does "stored in Ireland" mean nothing leaves Ireland?
Not always. Storage is one part. Email, text messages, AI processing, backups and vendor support access can each run somewhere else. The vendor's sub-processor list is where that shows up.
Where does Ask Brigid store patient data?
Ask Brigid's database, authentication and file storage run in Ireland, in AWS eu-west-1. AI processing runs in Google Cloud regions inside the EU. Some routes run outside the EU, such as transactional email (Resend, United States) and remote support by the database provider, and the data processing agreement lists each of them.
Your next step
This week, send the five questions above to your current vendor and keep the reply on file. If you're comparing systems, our guide to practice software in Ireland sets the main options side by side. To see Ask Brigid itself, explore the sample practice: it's the real app on invented data, with no sign-up.
Ask Brigid is looking for a small number of founding consultant practices. Request early access and we will reply with current availability and the next step.
Ask Brigid takes the admin so the clinic day stays clinical.
For private consultants
Leave when your last patient does.
Practice software built for speed. Brigid Clinical Intelligence takes on the admin, and your team approves every step.
See Ask Brigid for consultants How to choose practice software