Careloom ← Back to home

Data Processing Agreement

Effective 31 October 2026 · replaces the 14 October 2026 version

The short version: your agency is the controller of its care and staff records and Careloom is the processor. Careloom acts only on your instructions, keeps the records in the EU, tells you within 48 hours of a breach, gives 30 days' notice before changing a sub-processor, and keeps everything ready for you to take for 30 days after you leave — longer, once, if you ask — then deletes it. The rest of this page is the same promise in the words GDPR Article 28 requires. It is accepted with the terms of service at signup.

The parties, and where this fits

This agreement is between Careloom Limited (CRO no. 822185, 22 Crieve Mor Avenue, Crievesmith, Letterkenny, Co. Donegal, F92 PT7V — "Careloom", "we") and the home-care agency identified in the Careloom account ("the agency", "you"). The agency is the controller of the care records it keeps in Careloom; Careloom is the processor, acting only on the agency's instructions.

It forms part of, and is subject to, the terms of service. Where it conflicts with those terms on the subject of data protection, this agreement wins. The limits on liability in the terms apply to this agreement (section 11).

It is written in plain English. It is intended to meet, and where it is silent is to be read consistently with, the European Commission's standard contractual clauses between controllers and processors (Decision (EU) 2021/915).

1. Words with a fixed meaning

"GDPR" means Regulation (EU) 2016/679 and the Data Protection Act 2018. "Personal data", "processing", "controller", "processor", "data subject", "personal data breach" and "special categories of data" mean what the GDPR says they mean. A "sub-processor" is any processor Careloom engages. "Agency personal data" is the personal data Careloom processes on the agency's behalf under this agreement, described in Annex I.

2. Roles and scope

2.1 The agency determines the purposes and means of the processing. Careloom processes agency personal data only to provide the Careloom service and only on the agency's documented instructions.

2.2 The agency confirms it has a lawful basis (GDPR Art. 6) and a special-category condition (Art. 9 — for client care, typically Art. 9(2)(h), the provision of health or social care, under section 52 of the Data Protection Act 2018; for staff sickness and other absence records, typically Art. 9(2)(b), employment law, under section 46; in each case with the section 36 safeguards) for the data it puts into Careloom, and that its own privacy information tells clients and staff that a processor is used. Where the agency records Garda vetting, it does so under the National Vetting Bureau (Children and Vulnerable Persons) Acts 2012 to 2016 and, so far as a vetting record is data about criminal convictions or offences, Article 10 GDPR and section 55 of the Data Protection Act 2018.

2.3 The agency's practical duties: it decides who on its team may use Careloom and removes access when someone leaves; its people keep their logins to themselves; and it keeps client names and care details out of support emails and feedback messages, referring to records in the app instead, so that health data stays inside the protections built for it. Careloom deletes any client details that reach a support mailbox once the request is dealt with.

3. What Careloom undertakes (Art. 28(3))

Careloom will:

  • (a) Instructions. Process agency personal data only on the agency's documented instructions — this agreement, the agency's use and configuration of the service, and any further instruction the agency gives in writing, of which Careloom keeps a record — including on international transfers, unless required by law, in which case we tell you first unless the law forbids it.
  • (b) Confidentiality. Ensure that the persons authorised to process the data are under a duty of confidence. Those persons are Careloom's director and any contractor given access to the database or the console, who is given it only under a signed confidentiality undertaking.
  • (c) Security. Apply the technical and organisational measures in Annex II (Art. 32). Because agency personal data includes health data, those measures include logged access to every health record and tenant isolation enforced by the database itself.
  • (d) Sub-processors. Engage sub-processors only as section 5 allows.
  • (e) Data-subject rights. Taking account of the nature of the processing, assist the agency by appropriate technical and organisational measures to respond to data-subject requests (access, rectification, erasure, restriction, portability, objection). The service's own tools — per-client export, the access-log export and the erasure procedure — are the primary means of this assistance. If a data subject contacts Careloom directly about agency personal data, Careloom passes the request to the agency promptly and does not answer it itself, other than to say who the controller is.
  • (f) Assistance. Assist the agency in meeting its own duties under Arts. 32–36 (security, breach notification, impact assessments, prior consultation), taking account of the information available to us.
  • (g) Deletion or return. At the end of the service, return the agency personal data if the agency chooses to take it, and delete it and existing copies, on the timetable in section 7, unless law requires retention.
  • (h) Audit. Make available the information needed to demonstrate compliance with Art. 28 and allow for and contribute to audits (section 8).
  • Tell the agency at once if, in our opinion, an instruction infringes the GDPR.

4. Careloom's own data

Separately from this agreement, Careloom is the controller of the data the privacy policy describes: website enquiries and newsletter sign-ups, the logins of people who sign in (the email address and sign-in security settings), and billing contacts. That data is governed by the privacy policy, not by this agreement. A person's staff record inside the agency's workspace is agency personal data, governed by this agreement.

5. Sub-processors (Art. 28(2) and (4))

5.1 The agency gives general authorisation for Careloom to engage the sub-processors listed in Annex III, each of which is bound by data-protection terms no less protective than this agreement. A copy of a sub-processor's data-protection terms is available on request, commercial terms redacted.

5.2 Careloom gives the agency 30 days' notice of any intended change (adding or replacing a sub-processor) by email to the agency's registered administrator address, sent from hello@careloom.ie, before the change takes effect, so the agency may object on reasonable data-protection grounds. If an objection cannot be resolved before the change takes effect, the agency may end its subscription without penalty, and its free export and the return-or-delete right in section 7 apply.

5.3 Careloom remains liable to the agency for a sub-processor's performance of its data-protection obligations as for its own acts, within the limits in section 11.

6. If there is a personal data breach (Art. 33)

Careloom notifies the agency without undue delay, and in any event within 48 hours, after becoming aware of a personal data breach affecting agency personal data, with the information the agency needs to meet its own duty to the Data Protection Commission: the nature of the breach, the categories and approximate numbers of people and records affected, the likely consequences, and the measures taken — in phases where the facts are not yet known. Careloom keeps a written breach-response procedure and follows it. Careloom does not notify the Commission or data subjects on the agency's behalf unless separately agreed; that duty sits with the agency as controller.

7. Return and deletion (Art. 28(3)(g))

7.1 For as long as the service runs, and for 30 days after it ends, the agency can take a full copy of agency personal data, free. The full export gives the records as spreadsheets, and Careloom switches it on within one working day of the agency asking. If the agency needs longer to move to another service, it may ask in writing before those 30 days end, and Careloom extends them once, free, for as long as the agency reasonably needs (the EU Data Act's switching rules). A few security secrets — key-safe codes and access links — are never written to an export file; they stay readable in Careloom until deletion, and the export's own list says which. Documents and photos open from the records they belong to, and on request Careloom provides them together. This is how Careloom returns the data.

7.2 At the end of that period (section 7.1, with any extension), or sooner if the agency asks in writing, Careloom deletes agency personal data from the live database and file storage, and deletes existing copies, except data Careloom must keep by law. Careloom confirms deletion in writing on request.

7.3 Backups are not edited one record at a time; they age out on the provider's rolling schedule (seven days on Careloom's current plan), and every backup holding the data has expired within 30 days of deletion. Until then, backups are restored only for disaster recovery and are protected by the Annex II measures.

8. Audit (Art. 28(3)(h))

8.1 Careloom makes available this agreement, its sub-processor list, its security-measures statement and its record of processing activities to demonstrate compliance, and answers the agency's written audit questions.

8.2 Where something is still left unanswered, the agency — or an independent auditor it appoints who is not a competitor of Careloom — may audit Careloom in person once in any twelve months, and also after a personal data breach affecting the agency or when a regulator requires it. The agency gives 30 days' written notice, except after a breach or at a regulator's request. The audit is at the agency's cost, in Irish business hours, under a written confidentiality undertaking, and without disrupting the service or compromising other agencies' security.

8.3 The data centres behind the service do not admit visitors. For them, the audit is a review of the providers' own independent audit reports (such as SOC 2 or ISO 27001).

9. Where the data is, and transfers outside the EEA

9.1 Agency personal data, including every care record, is hosted in the EU (Ireland). Careloom will not transfer agency personal data outside the EEA except to a sub-processor listed in Annex III and only with an appropriate transfer mechanism.

9.2 The database (Supabase) and the email service (Resend) hold the data in the EU (Ireland), and the error-monitoring service (Sentry) in the EU (Germany), but all three are US companies; any access to the data from outside the EEA, for example by their own support staff, is covered by the standard contractual clauses in their data processing agreements. The services that may process limited, non-care data outside the EEA are the web host (Netlify), the payment provider (Stripe), Careloom's own mailboxes (Microsoft 365) and the phone push-notification relays (Google, Apple, Mozilla); each such transfer is covered by the provider's EU standard contractual clauses or its EU–US Data Privacy Framework certification.

10. How long this lasts

This agreement runs for as long as Careloom processes agency personal data — through the period after the service ends in section 7.1 and until backups have aged out (section 7). The clauses that by their nature should survive the end of the service — confidentiality, deletion, liability — survive it.

11. Liability

Each party's liability under this agreement — including a claim by one party against the other, under Art. 82(5) GDPR, for its share of compensation paid — is subject to the limits and exclusions in the terms of service (clause 10), which apply to claims under this agreement as they apply to any other claim under the terms. Nothing in this clause limits either party's liability to a data subject under Art. 82 GDPR.

12. If either side does not keep to this

12.1 If Careloom is in material breach of this agreement and has not put it right within 30 days of being told in writing, the agency may suspend the processing concerned or end its subscription, and section 7 applies.

12.2 If the agency insists on an instruction that Careloom has said infringes the GDPR, Careloom may end the subscription on written notice, and section 7 applies.

13. Changes to this agreement

When the service changes, this agreement may change with it. Careloom emails the agency's administrators at least 30 days before a material change takes effect, posts the new version here with a new effective date, and records which version each agency has accepted. An agency that does not agree may cancel before the change takes effect, with no penalty and a free export. This version is 2026-10-31. Questions to privacy@careloom.ie.

Annex I — Details of the processing

  • Subject matter: provision of the Careloom care-coordination service.
  • Duration: the term of the agency's subscription, the 30 days after it ends (longer if extended under section 7.1), and until backups have aged out (section 7).
  • Nature and purpose: hosting and processing care records so the agency can schedule visits, check that visits happened in the way it chooses, record care and medication, manage staff and compliance, keep the agency's own policies and documents, operate a read-only family page (which shows a visiting carer's first name, or "the care team" where the agency chooses), invoice funders, and prepare timesheets and payroll exports.
  • Types of personal data — clients (care recipients): name, date of birth, address, phone number, care needs and special-category health data (care plans, medications and administration records, visit notes and observations, incidents including safeguarding and restrictive-practice records), a photo where the agency records the client's consent, documents the agency uploads to the client's record or to an incident, funding or HSE reference and billing details, family-page contact links.
  • Types of personal data — staff: name, contact details (including a home address), an emergency contact (a third party's name and phone number), role, staff ID, Garda vetting (that it was done, its dates, the disclosure's reference number, who checked it, where the agency keeps the original and any note the agency adds — never the disclosure itself), training records and expiries, copies of training certificates the agency attaches (never a vetting disclosure), the staff file (for each item the agency checks — references, employment history, qualifications, a fitness declaration, proof of identity, right to work and, for drivers, the driving licence and business-use insurance — the date it was seen, who checked it, where the agency keeps the original, a short line of detail (such as a referee's name and role, or gaps in employment explained) and any expiry date; never the documents themselves, and only that a fitness declaration was seen, never its content), a leaving record (the last working day, the reason and, for a dismissal, whether a safeguarding referral was needed — the reason and the referral answer read by the agency's owner and care managers alone), supervision records, working-time and clock records, leave and absence records (including sickness, and leave such as medical care or domestic violence leave), mileage, and — where the agency switches it on — a location recorded when a carer taps to record it (one point per tap, never continuous tracking) and the mileage worked out from those points.
  • Types of personal data — the agency's own documents: the policies, statement of purpose, insurance, complaints procedure and continuity plan the agency uploads (expected to hold no personal data beyond the people they name).
  • Types of personal data — account and usage: login identifiers, audit records (who changed what) and access records (who viewed which client).
  • Categories of data subjects: past and present care clients, and their family, next of kin or representatives (including the people given a family-page link); the agency's past and present staff (carers, coordinators, managers, administrators), and the referees and emergency contacts the agency records for them; the people the agency's own documents name.
  • Special categories: yes — client health data and safeguarding information, and staff sickness and absence records, each processed under the agency's Art. 9 condition; and Garda-vetting records, including a disclosure's reference number, so far as they are data about criminal convictions or offences, under Art. 10 (both in section 2.2).

Annex II — Technical and organisational measures (Art. 32)

These are the measures Careloom applies to agency personal data. The detail behind each is on the security page; this list is the contract.

  • Tenant isolation enforced by the database. Every table carries the agency it belongs to, and Row-Level Security policies restrict every read and write to the signed-in person's own agency. One agency can never see another's records, by the database's rule rather than application code.
  • Encryption in transit. All traffic between the app, the API and the database runs over TLS.
  • Encryption at rest. The database, file storage and backups are encrypted at rest (AES-256) on the provider's managed infrastructure.
  • Logged access to health records. Every read of a client's health record through the service is recorded with who read it and when; the agency can export that log.
  • An append-only audit trail. Changes to care records are recorded with who made them and when, and the record of a change cannot be edited or removed.
  • Personal logins and least privilege. Logins are individual, never shared; what a person can see and do follows the role the agency gave them; two-step verification is offered to every console user, and for a person who has set it up the database itself refuses every client and staff record to a sign-in that has not passed the second step.
  • No privileged key in the browser. The app holds only a public key; the privileged service key never leaves the server.
  • Device protection. A person may set a device PIN, which keeps the stored session encrypted on the device; sessions expire. Door key-safe codes cannot be read directly: each one is shown only on request, and every showing is logged.
  • Daily encrypted backups, restored only for disaster recovery, ageing out on a rolling window, seven days today (section 7).
  • Sub-processors starved of care data. The web host serves code, not records; the monitoring service receives error reports with personal data scrubbed; the email services never receive client-identifying mail from the platform.
  • A written breach procedure with a named lead, followed rather than improvised (section 6).
  • Written procedures for subject access, erasure and retention, kept with this agreement.

Annex III — Sub-processors

The processors Careloom engages to run the service, as at 14 October 2026. Changes follow section 5.

ProviderWhat it does for CareloomData it may processWhere
SupabaseThe database, authentication, file storage and server functions — the one place care records liveAll platform data, including client health dataEU (Ireland); a US company, so any access from outside the EEA is covered as section 9.2 says
NetlifyServes the app's code to the browserRequest metadata (such as an IP address) at the edge; no care dataGlobal edge network; standard contractual clauses or Data Privacy Framework certification
ResendSends the platform's own email: sign-in links, password resets, security notices to staffThe recipient's email address and the message; no care dataEU (Ireland); a US company, so any access from outside the EEA is covered as section 9.2 says
Microsoft 365Careloom's own mailboxes for support and correspondenceWhatever a correspondent sends; the agency keeps client details out (section 2.3)Microsoft's data-residency terms for EU customers; transfers under its standard contractual clauses
StripeSubscription billing and card processing; Careloom never stores card numbersBilling contact and payment data; no care dataStripe Payments Europe Ltd (Dublin), with processing in the US under Stripe's data processing agreement and standard contractual clauses
SentryError monitoring, switched on only when configuredError reports with personal data scrubbed before sending; no care dataEU (Germany); a US company (Functional Software, Inc.), so any access from outside the EEA is covered as section 9.2 says
Google, Apple, Mozilla (push relays)Deliver a short notification to a staff phone that has opted inThe phone's push address and an end-to-end encrypted message the relay cannot read; never client dataGlobal; the encryption is the safeguard

The services behind the careloom.ie website itself (MailerLite, Calendly, Plausible) process website data of which Careloom is the controller; they are listed in the privacy policy, not here.

Careloom
Built in Donegal, Ireland · © 2026 Careloom Limited. All rights reserved.
Registered in Ireland, CRO no. 822185 · Registered office: 22 Crieve Mor Avenue, Crievesmith, Letterkenny, Co. Donegal, F92 PT7V
Careloom ← Back to home

Data Processing Agreement

Effective 31 October 2026 · replaces the 14 October 2026 version

The short version: your agency is the controller of its care and staff records and Careloom is the processor. Careloom acts only on your instructions, keeps the records in the EU, tells you within 48 hours of a breach, gives 30 days' notice before changing a sub-processor, and keeps everything ready for you to take for 30 days after you leave — longer, once, if you ask — then deletes it. The rest of this page is the same promise in the words GDPR Article 28 requires. It is accepted with the terms of service at signup.

The parties, and where this fits

This agreement is between Careloom Limited (CRO no. 822185, 22 Crieve Mor Avenue, Crievesmith, Letterkenny, Co. Donegal, F92 PT7V — "Careloom", "we") and the home-care agency identified in the Careloom account ("the agency", "you"). The agency is the controller of the care records it keeps in Careloom; Careloom is the processor, acting only on the agency's instructions.

It forms part of, and is subject to, the terms of service. Where it conflicts with those terms on the subject of data protection, this agreement wins. The limits on liability in the terms apply to this agreement (section 11).

It is written in plain English. It is intended to meet, and where it is silent is to be read consistently with, the European Commission's standard contractual clauses between controllers and processors (Decision (EU) 2021/915).

1. Words with a fixed meaning

"GDPR" means Regulation (EU) 2016/679 and the Data Protection Act 2018. "Personal data", "processing", "controller", "processor", "data subject", "personal data breach" and "special categories of data" mean what the GDPR says they mean. A "sub-processor" is any processor Careloom engages. "Agency personal data" is the personal data Careloom processes on the agency's behalf under this agreement, described in Annex I.

2. Roles and scope

2.1 The agency determines the purposes and means of the processing. Careloom processes agency personal data only to provide the Careloom service and only on the agency's documented instructions.

2.2 The agency confirms it has a lawful basis (GDPR Art. 6) and a special-category condition (Art. 9 — for client care, typically Art. 9(2)(h), the provision of health or social care, under section 52 of the Data Protection Act 2018; for staff sickness and other absence records, typically Art. 9(2)(b), employment law, under section 46; in each case with the section 36 safeguards) for the data it puts into Careloom, and that its own privacy information tells clients and staff that a processor is used. Where the agency records Garda vetting, it does so under the National Vetting Bureau (Children and Vulnerable Persons) Acts 2012 to 2016 and, so far as a vetting record is data about criminal convictions or offences, Article 10 GDPR and section 55 of the Data Protection Act 2018.

2.3 The agency's practical duties: it decides who on its team may use Careloom and removes access when someone leaves; its people keep their logins to themselves; and it keeps client names and care details out of support emails and feedback messages, referring to records in the app instead, so that health data stays inside the protections built for it. Careloom deletes any client details that reach a support mailbox once the request is dealt with.

3. What Careloom undertakes (Art. 28(3))

Careloom will:

  • (a) Instructions. Process agency personal data only on the agency's documented instructions — this agreement, the agency's use and configuration of the service, and any further instruction the agency gives in writing, of which Careloom keeps a record — including on international transfers, unless required by law, in which case we tell you first unless the law forbids it.
  • (b) Confidentiality. Ensure that the persons authorised to process the data are under a duty of confidence. Those persons are Careloom's director and any contractor given access to the database or the console, who is given it only under a signed confidentiality undertaking.
  • (c) Security. Apply the technical and organisational measures in Annex II (Art. 32). Because agency personal data includes health data, those measures include logged access to every health record and tenant isolation enforced by the database itself.
  • (d) Sub-processors. Engage sub-processors only as section 5 allows.
  • (e) Data-subject rights. Taking account of the nature of the processing, assist the agency by appropriate technical and organisational measures to respond to data-subject requests (access, rectification, erasure, restriction, portability, objection). The service's own tools — per-client export, the access-log export and the erasure procedure — are the primary means of this assistance. If a data subject contacts Careloom directly about agency personal data, Careloom passes the request to the agency promptly and does not answer it itself, other than to say who the controller is.
  • (f) Assistance. Assist the agency in meeting its own duties under Arts. 32–36 (security, breach notification, impact assessments, prior consultation), taking account of the information available to us.
  • (g) Deletion or return. At the end of the service, return the agency personal data if the agency chooses to take it, and delete it and existing copies, on the timetable in section 7, unless law requires retention.
  • (h) Audit. Make available the information needed to demonstrate compliance with Art. 28 and allow for and contribute to audits (section 8).
  • Tell the agency at once if, in our opinion, an instruction infringes the GDPR.

4. Careloom's own data

Separately from this agreement, Careloom is the controller of the data the privacy policy describes: website enquiries and newsletter sign-ups, the logins of people who sign in (the email address and sign-in security settings), and billing contacts. That data is governed by the privacy policy, not by this agreement. A person's staff record inside the agency's workspace is agency personal data, governed by this agreement.

5. Sub-processors (Art. 28(2) and (4))

5.1 The agency gives general authorisation for Careloom to engage the sub-processors listed in Annex III, each of which is bound by data-protection terms no less protective than this agreement. A copy of a sub-processor's data-protection terms is available on request, commercial terms redacted.

5.2 Careloom gives the agency 30 days' notice of any intended change (adding or replacing a sub-processor) by email to the agency's registered administrator address, sent from hello@careloom.ie, before the change takes effect, so the agency may object on reasonable data-protection grounds. If an objection cannot be resolved before the change takes effect, the agency may end its subscription without penalty, and its free export and the return-or-delete right in section 7 apply.

5.3 Careloom remains liable to the agency for a sub-processor's performance of its data-protection obligations as for its own acts, within the limits in section 11.

6. If there is a personal data breach (Art. 33)

Careloom notifies the agency without undue delay, and in any event within 48 hours, after becoming aware of a personal data breach affecting agency personal data, with the information the agency needs to meet its own duty to the Data Protection Commission: the nature of the breach, the categories and approximate numbers of people and records affected, the likely consequences, and the measures taken — in phases where the facts are not yet known. Careloom keeps a written breach-response procedure and follows it. Careloom does not notify the Commission or data subjects on the agency's behalf unless separately agreed; that duty sits with the agency as controller.

7. Return and deletion (Art. 28(3)(g))

7.1 For as long as the service runs, and for 30 days after it ends, the agency can take a full copy of agency personal data, free. The full export gives the records as spreadsheets, and Careloom switches it on within one working day of the agency asking. If the agency needs longer to move to another service, it may ask in writing before those 30 days end, and Careloom extends them once, free, for as long as the agency reasonably needs (the EU Data Act's switching rules). A few security secrets — key-safe codes and access links — are never written to an export file; they stay readable in Careloom until deletion, and the export's own list says which. Documents and photos open from the records they belong to, and on request Careloom provides them together. This is how Careloom returns the data.

7.2 At the end of that period (section 7.1, with any extension), or sooner if the agency asks in writing, Careloom deletes agency personal data from the live database and file storage, and deletes existing copies, except data Careloom must keep by law. Careloom confirms deletion in writing on request.

7.3 Backups are not edited one record at a time; they age out on the provider's rolling schedule (seven days on Careloom's current plan), and every backup holding the data has expired within 30 days of deletion. Until then, backups are restored only for disaster recovery and are protected by the Annex II measures.

8. Audit (Art. 28(3)(h))

8.1 Careloom makes available this agreement, its sub-processor list, its security-measures statement and its record of processing activities to demonstrate compliance, and answers the agency's written audit questions.

8.2 Where something is still left unanswered, the agency — or an independent auditor it appoints who is not a competitor of Careloom — may audit Careloom in person once in any twelve months, and also after a personal data breach affecting the agency or when a regulator requires it. The agency gives 30 days' written notice, except after a breach or at a regulator's request. The audit is at the agency's cost, in Irish business hours, under a written confidentiality undertaking, and without disrupting the service or compromising other agencies' security.

8.3 The data centres behind the service do not admit visitors. For them, the audit is a review of the providers' own independent audit reports (such as SOC 2 or ISO 27001).

9. Where the data is, and transfers outside the EEA

9.1 Agency personal data, including every care record, is hosted in the EU (Ireland). Careloom will not transfer agency personal data outside the EEA except to a sub-processor listed in Annex III and only with an appropriate transfer mechanism.

9.2 The database (Supabase) and the email service (Resend) hold the data in the EU (Ireland), and the error-monitoring service (Sentry) in the EU (Germany), but all three are US companies; any access to the data from outside the EEA, for example by their own support staff, is covered by the standard contractual clauses in their data processing agreements. The services that may process limited, non-care data outside the EEA are the web host (Netlify), the payment provider (Stripe), Careloom's own mailboxes (Microsoft 365) and the phone push-notification relays (Google, Apple, Mozilla); each such transfer is covered by the provider's EU standard contractual clauses or its EU–US Data Privacy Framework certification.

10. How long this lasts

This agreement runs for as long as Careloom processes agency personal data — through the period after the service ends in section 7.1 and until backups have aged out (section 7). The clauses that by their nature should survive the end of the service — confidentiality, deletion, liability — survive it.

11. Liability

Each party's liability under this agreement — including a claim by one party against the other, under Art. 82(5) GDPR, for its share of compensation paid — is subject to the limits and exclusions in the terms of service (clause 10), which apply to claims under this agreement as they apply to any other claim under the terms. Nothing in this clause limits either party's liability to a data subject under Art. 82 GDPR.

12. If either side does not keep to this

12.1 If Careloom is in material breach of this agreement and has not put it right within 30 days of being told in writing, the agency may suspend the processing concerned or end its subscription, and section 7 applies.

12.2 If the agency insists on an instruction that Careloom has said infringes the GDPR, Careloom may end the subscription on written notice, and section 7 applies.

13. Changes to this agreement

When the service changes, this agreement may change with it. Careloom emails the agency's administrators at least 30 days before a material change takes effect, posts the new version here with a new effective date, and records which version each agency has accepted. An agency that does not agree may cancel before the change takes effect, with no penalty and a free export. This version is 2026-10-31. Questions to privacy@careloom.ie.

Annex I — Details of the processing

  • Subject matter: provision of the Careloom care-coordination service.
  • Duration: the term of the agency's subscription, the 30 days after it ends (longer if extended under section 7.1), and until backups have aged out (section 7).
  • Nature and purpose: hosting and processing care records so the agency can schedule visits, check that visits happened in the way it chooses, record care and medication, manage staff and compliance, keep the agency's own policies and documents, operate a read-only family page (which shows a visiting carer's first name, or "the care team" where the agency chooses), invoice funders, and prepare timesheets and payroll exports.
  • Types of personal data — clients (care recipients): name, date of birth, address, phone number, care needs and special-category health data (care plans, medications and administration records, visit notes and observations, incidents including safeguarding and restrictive-practice records), a photo where the agency records the client's consent, documents the agency uploads to the client's record or to an incident, funding or HSE reference and billing details, family-page contact links.
  • Types of personal data — staff: name, contact details (including a home address), an emergency contact (a third party's name and phone number), role, staff ID, Garda vetting (that it was done, its dates, the disclosure's reference number, who checked it, where the agency keeps the original and any note the agency adds — never the disclosure itself), training records and expiries, copies of training certificates the agency attaches (never a vetting disclosure), the staff file (for each item the agency checks — references, employment history, qualifications, a fitness declaration, proof of identity, right to work and, for drivers, the driving licence and business-use insurance — the date it was seen, who checked it, where the agency keeps the original, a short line of detail (such as a referee's name and role, or gaps in employment explained) and any expiry date; never the documents themselves, and only that a fitness declaration was seen, never its content), a leaving record (the last working day, the reason and, for a dismissal, whether a safeguarding referral was needed — the reason and the referral answer read by the agency's owner and care managers alone), supervision records, working-time and clock records, leave and absence records (including sickness, and leave such as medical care or domestic violence leave), mileage, and — where the agency switches it on — a location recorded when a carer taps to record it (one point per tap, never continuous tracking) and the mileage worked out from those points.
  • Types of personal data — the agency's own documents: the policies, statement of purpose, insurance, complaints procedure and continuity plan the agency uploads (expected to hold no personal data beyond the people they name).
  • Types of personal data — account and usage: login identifiers, audit records (who changed what) and access records (who viewed which client).
  • Categories of data subjects: past and present care clients, and their family, next of kin or representatives (including the people given a family-page link); the agency's past and present staff (carers, coordinators, managers, administrators), and the referees and emergency contacts the agency records for them; the people the agency's own documents name.
  • Special categories: yes — client health data and safeguarding information, and staff sickness and absence records, each processed under the agency's Art. 9 condition; and Garda-vetting records, including a disclosure's reference number, so far as they are data about criminal convictions or offences, under Art. 10 (both in section 2.2).

Annex II — Technical and organisational measures (Art. 32)

These are the measures Careloom applies to agency personal data. The detail behind each is on the security page; this list is the contract.

  • Tenant isolation enforced by the database. Every table carries the agency it belongs to, and Row-Level Security policies restrict every read and write to the signed-in person's own agency. One agency can never see another's records, by the database's rule rather than application code.
  • Encryption in transit. All traffic between the app, the API and the database runs over TLS.
  • Encryption at rest. The database, file storage and backups are encrypted at rest (AES-256) on the provider's managed infrastructure.
  • Logged access to health records. Every read of a client's health record through the service is recorded with who read it and when; the agency can export that log.
  • An append-only audit trail. Changes to care records are recorded with who made them and when, and the record of a change cannot be edited or removed.
  • Personal logins and least privilege. Logins are individual, never shared; what a person can see and do follows the role the agency gave them; two-step verification is offered to every console user, and for a person who has set it up the database itself refuses every client and staff record to a sign-in that has not passed the second step.
  • No privileged key in the browser. The app holds only a public key; the privileged service key never leaves the server.
  • Device protection. A person may set a device PIN, which keeps the stored session encrypted on the device; sessions expire. Door key-safe codes cannot be read directly: each one is shown only on request, and every showing is logged.
  • Daily encrypted backups, restored only for disaster recovery, ageing out on a rolling window, seven days today (section 7).
  • Sub-processors starved of care data. The web host serves code, not records; the monitoring service receives error reports with personal data scrubbed; the email services never receive client-identifying mail from the platform.
  • A written breach procedure with a named lead, followed rather than improvised (section 6).
  • Written procedures for subject access, erasure and retention, kept with this agreement.

Annex III — Sub-processors

The processors Careloom engages to run the service, as at 14 October 2026. Changes follow section 5.

ProviderWhat it does for CareloomData it may processWhere
SupabaseThe database, authentication, file storage and server functions — the one place care records liveAll platform data, including client health dataEU (Ireland); a US company, so any access from outside the EEA is covered as section 9.2 says
NetlifyServes the app's code to the browserRequest metadata (such as an IP address) at the edge; no care dataGlobal edge network; standard contractual clauses or Data Privacy Framework certification
ResendSends the platform's own email: sign-in links, password resets, security notices to staffThe recipient's email address and the message; no care dataEU (Ireland); a US company, so any access from outside the EEA is covered as section 9.2 says
Microsoft 365Careloom's own mailboxes for support and correspondenceWhatever a correspondent sends; the agency keeps client details out (section 2.3)Microsoft's data-residency terms for EU customers; transfers under its standard contractual clauses
StripeSubscription billing and card processing; Careloom never stores card numbersBilling contact and payment data; no care dataStripe Payments Europe Ltd (Dublin), with processing in the US under Stripe's data processing agreement and standard contractual clauses
SentryError monitoring, switched on only when configuredError reports with personal data scrubbed before sending; no care dataEU (Germany); a US company (Functional Software, Inc.), so any access from outside the EEA is covered as section 9.2 says
Google, Apple, Mozilla (push relays)Deliver a short notification to a staff phone that has opted inThe phone's push address and an end-to-end encrypted message the relay cannot read; never client dataGlobal; the encryption is the safeguard

The services behind the careloom.ie website itself (MailerLite, Calendly, Plausible) process website data of which Careloom is the controller; they are listed in the privacy policy, not here.

Careloom
Built in Donegal, Ireland · © 2026 Careloom Limited. All rights reserved.
Registered in Ireland, CRO no. 822185 · Registered office: 22 Crieve Mor Avenue, Crievesmith, Letterkenny, Co. Donegal, F92 PT7V