Data Processing Agreement

Last updated: 2026-07-02

InspectReady (Crocker Digital Ltd) — customer-facing DPA for the care-home-uploads-evidence-data flow

This Data Processing Agreement ("DPA") is entered into between:

(1) Crocker Digital Ltd, a company incorporated in England and Wales with company number 17008789, registered office at 71-75 Shelton Street, Covent Garden, London, WC2H 9JQ ("Processor", also "InspectReady", "we"); and

(2) the legal entity identified in the Customer's InspectReady account — typically a care-home provider or a small group operating one or more CQC-registered locations — acting as controller of the personal data it uploads or causes to be processed through the service ("Controller", "Customer", "you").

This DPA forms part of and is incorporated into the InspectReady Terms of Service at https://inspectready.co.uk/terms/ (the "Agreement"). In the event of conflict between this DPA and the Agreement in relation to the processing of Customer Personal Data, this DPA prevails.

This DPA is offered to any business Customer that processes personal data through the service. It takes effect automatically: this DPA is incorporated into the Agreement as a matter of contract when the Customer creates an account, and applies whenever the Customer uploads or causes to be processed personal data relating to people who are not users of the service (for example, residents, service users, and staff named in policies, audits, or evidence files). The Customer does not need to sign or tick a box separately for this DPA to apply — automatic incorporation into the Agreement is how we meet UK GDPR Article 28 for every business Customer. A printable copy is available at /legal/dpa/ and may be countersigned and returned to privacy@inspectready.co.uk if a Customer's internal procurement process requires it, but countersignature is not a condition of the DPA taking effect.

1. Interpretation

1.1 In this DPA, the following expressions have the meanings set out below. Terms not defined here have the meaning given in the Agreement, and capitalised terms not defined in either have the meaning given in UK Data Protection Law.

"Affiliate" — any entity controlling, controlled by, or under common control with a party.

"Applicable Data Protection Law" or "UK Data Protection Law" — the UK General Data Protection Regulation (as retained and amended by The Data Protection, Privacy and Electronic Communications (Amendments etc) (EU Exit) Regulations 2019), the Data Protection Act 2018, the Privacy and Electronic Communications (EC Directive) Regulations 2003, and any successor legislation, together with any guidance or code of practice issued by the Information Commissioner.

"Customer Personal Data" — personal data provided by or on behalf of the Customer to the Processor for processing under the Agreement. This includes data the Customer uploads or enters, data entered by individuals to whom the Customer has granted access, and metadata generated by the service in the course of processing that data.

"Data Subject", "Personal Data", "Personal Data Breach", "Processing", "Controller", "Processor", and "Special Category Data" — as defined in UK Data Protection Law.

"Restricted Transfer" — a transfer of Personal Data from the UK to a country which is not the subject of UK adequacy regulations.

"Schedule 1" — the processing description set out at the end of this DPA.

"Schedule 2" — the technical and organisational measures set out at the end of this DPA.

"Schedule 3" — the list of approved sub-processors referred to in clause 5.

"Standard Contractual Clauses" — the International Data Transfer Agreement issued by the Information Commissioner under section 119A of the Data Protection Act 2018 on 2 February 2022, or the International Data Transfer Addendum to the EU Standard Contractual Clauses issued on the same date, in each case as they may be updated from time to time.

1.2 In this DPA, references to "writing" include email.

2. Subject matter, nature, purpose, duration

2.1 The Processor processes Customer Personal Data only to provide the InspectReady service in accordance with the Agreement and this DPA, and only on the Customer's documented instructions.

2.2 The full description of processing — subject matter, duration, nature, purpose, categories of Data Subjects, and types of Personal Data — is set out in Schedule 1.

2.3 This DPA takes effect on the day the Customer first uses the service and continues until the later of (a) termination of the Agreement, and (b) the Processor completing the deletion, anonymisation, or return of Customer Personal Data in accordance with clause 9.

3. Roles of the parties

3.1 In respect of Customer Personal Data uploaded or caused to be processed by the Customer, the Customer is the Controller and the Processor is the Processor. This captures, for example, residents' and service users' names appearing in care-planning evidence, medication (MAR) records, incident and safeguarding records, and staff names appearing in policies, audit findings, training records, and rotas uploaded as evidence.

3.2 In respect of the account data of the Customer's own users (names, email addresses, roles, passwords, audit-log entries, billing contact details, and the service-notification email preference), the Processor is an independent Controller. Processing of that data is described in the Processor's Privacy Policy at https://inspectready.co.uk/privacy/.

3.3 Nothing in this DPA creates a joint-controllership arrangement under Article 26 of the UK GDPR in respect of Customer Personal Data.

4. Processor obligations (UK GDPR Article 28(3))

The Processor shall:

4.1 Instructions. Process Customer Personal Data only on the documented instructions of the Customer, including with regard to Restricted Transfers. The Customer's instructions are those contained in (a) the Agreement, (b) this DPA, (c) the configuration options the Customer sets in-product, and (d) any further written instruction notified to support@inspectready.co.uk. If the Processor considers that an instruction would infringe Applicable Data Protection Law, it shall notify the Customer without undue delay.

4.2 Confidentiality. Ensure that persons authorised to process Customer Personal Data have committed themselves to confidentiality or are under an appropriate statutory duty of confidentiality.

4.3 Security (Article 32). Implement appropriate technical and organisational measures to ensure a level of security appropriate to the risk. The measures in force at the date of this DPA are set out in Schedule 2. The Processor may update Schedule 2 from time to time provided the level of protection is not materially diminished.

4.4 Sub-processors. Engage sub-processors only in accordance with clause 5.

4.5 Data-subject rights assistance (Articles 12–23). Taking into account the nature of the processing, assist the Customer by appropriate technical and organisational measures, insofar as possible, to respond to requests from Data Subjects exercising their rights. In particular:

The service provides in-Settings actions to request a data export and to request account deletion (the Processor actions these within one month, in line with the UK GDPR), per-home evidence deletion in-product, and in-product correction of profile fields.
For Data Subject requests that cannot be fulfilled through the self-serve tooling (e.g. requests made by residents, service users, or staff of the Customer, rather than by the Customer's own account holders), the Customer is responsible for responding to the Data Subject. The Processor will supply reasonably-necessary data or information on request to enable that response.

4.6 Article 32–36 assistance. Assist the Customer, taking into account the nature of the processing and the information available to the Processor, in ensuring compliance with the Customer's obligations under Articles 32 to 36 of the UK GDPR (security, breach notification, data protection impact assessments, prior consultation).

4.7 Return, deletion, or anonymisation (clause 9). At the end of the provision of services, return, delete, or anonymise Customer Personal Data in accordance with clause 9.

4.8 Audit information (clause 10). Make available to the Customer all information necessary to demonstrate compliance with this clause 4, and allow for and contribute to audits in accordance with clause 10.

4.9 Records. Maintain records of all categories of processing activities carried out on behalf of the Customer as required by Article 30(2) of the UK GDPR.

5. Sub-processors

5.1 The Customer grants the Processor a general authorisation to engage the sub-processors listed in Schedule 3 (and those currently listed at https://inspectready.co.uk/legal/subprocessors/, which forms part of Schedule 3 by reference), for the purposes set out against each entry.

5.2 The Processor shall:

(a) impose on each sub-processor, by written contract, data-protection obligations substantially equivalent to those imposed on the Processor under this DPA;

(b) remain liable to the Customer for the performance of each sub-processor's obligations;

(c) give at least 30 days' prior notice of the addition or replacement of a sub-processor, by email to the Customer's registered billing contact and by updating the public subprocessor list.

5.3 If the Customer has a reasonable, data-protection-based objection to a new sub-processor, it shall notify the Processor within 14 days of the notice. The parties shall work in good faith to resolve the objection. If no resolution is agreed within a further 30 days, the Customer may terminate the Agreement without penalty and the Processor shall refund any pre-paid but unused portion of the subscription.

6. International transfers

6.1 The Processor shall not transfer Customer Personal Data to a country outside the UK unless one of the following applies:

(a) the country is the subject of UK adequacy regulations; (b) the transfer is governed by the Standard Contractual Clauses; (c) another transfer mechanism permitted by Applicable Data Protection Law is in place.

6.2 Where the Processor relies on the Standard Contractual Clauses for a Restricted Transfer to a sub-processor, the Processor is authorised by the Customer to enter into those clauses on the Customer's behalf as exporter. The Customer acknowledges that the current Restricted Transfers supporting the service are set out in Schedule 3. Application data (the home's policies, audits, and evidence files) is hosted in the UK (Supabase, London, eu-west-2); the Restricted Transfers relate to supporting services (billing, email, monitoring), not to the primary evidence store.

6.3 The Processor has completed a Transfer Risk Assessment for each Restricted Transfer it relies upon. A summary of those TRAs is available to the Customer on reasonable request.

7. Personal data breach

7.1 The Processor shall notify the Customer in writing without undue delay, and in any event within 48 hours, after becoming aware of a Personal Data Breach affecting Customer Personal Data.

7.2 The notification shall include, to the extent known at the time:

(a) the nature of the Personal Data Breach, including the categories and approximate number of Data Subjects and Personal Data records concerned; (b) the likely consequences of the Personal Data Breach; (c) the measures taken or proposed to be taken to address the Personal Data Breach and to mitigate its possible adverse effects; (d) the name and contact details of the Processor's point of contact for further information.

7.3 The Processor shall cooperate with the Customer in investigating, mitigating, and remediating the Personal Data Breach, including providing reasonable assistance with any notification to the Information Commissioner (Article 33) and to affected Data Subjects (Article 34). The breach contact is security@inspectready.co.uk.

7.4 For the avoidance of doubt, notification of a Personal Data Breach is not an admission of fault or liability by the Processor.

8. Data subject requests

8.1 If the Processor receives a request directly from a Data Subject to exercise any right under UK Data Protection Law in respect of Customer Personal Data, the Processor shall, without undue delay, forward the request to the Customer and shall not respond to the Data Subject directly except (a) to confirm receipt and forward, or (b) as instructed by the Customer or required by law.

8.2 Where the request is made by a Data Subject whose personal data is processed by the Processor as Controller under clause 3.2 (e.g. the Customer's own account holder exercising rights in relation to their account record), the Processor shall handle the request directly as Controller.

9. Return, deletion, and anonymisation

9.1 On termination or expiry of the Agreement, the Processor shall, at the Customer's choice expressed in writing within 30 days of termination, delete or return to the Customer all Customer Personal Data, and delete existing copies, except to the extent that the Processor is required or entitled to retain a copy by applicable law or under clause 9.4.

9.2 If the Customer does not make a choice within the 30-day window, the Processor shall default to deletion in accordance with the Data Retention and Deletion policy at https://inspectready.co.uk/legal/retention-and-deletion/ — the home's policies, audits, and evidence files (and the underlying stored objects) are removed following the life-of-subscription-plus-30-day-grace window described there.

9.3 Deletion is deemed complete when the personal data is no longer accessible in the Processor's production environment and ordinary backup rotation has expired that copy, which shall be no later than 35 days from the date of the deletion instruction (or the default date under 9.2).

9.4 Immutable audit and compliance records (erasure by anonymisation). InspectReady maintains an append-only account audit log recording security- and compliance-relevant events (sign-in, evidence generation, share-link creation, deletion). That log is immutable by design — the ledger tables enforce PostgreSQL FORCE row-level security with UPDATE and DELETE grants revoked from every role, including the service role — so that it can serve as a contemporaneous compliance record consistent with Regulation 17(2)(c) of the Health and Social Care Act 2008 (Regulated Activities) Regulations 2014. When a user account is deleted or an erasure request is fulfilled, the Processor removes or anonymises the personal data associated with that individual — profile fields, evidence-file contents, and file-level metadata — and revokes access; the immutable audit-log events are retained as a record, with personal identifiers minimised or dissociated from the natural person so far as the immutable ledger permits. The Processor does not represent that every database row referencing a user is physically destroyed where retention of the immutable audit or compliance record is required or appropriate. This is erasure by removal and anonymisation, consistent with audit-log retention — not a warranty of whole-row hard-deletion. This treatment reflects Article 17(3)(b) and (e) of the UK GDPR (retention for compliance with a legal obligation and for the establishment or defence of legal claims).

9.5 The Processor may retain de-identified, aggregated, or anonymised data for product-analytics purposes where such data no longer constitutes Personal Data.

10. Audit

10.1 The Processor shall make available to the Customer, on reasonable request and not more than once per 12-month period, the following information in order to demonstrate compliance with this DPA:

(a) the Processor's current Technical and Organisational Measures (Schedule 2); (b) the Processor's Records of Processing Activities to the extent relevant to the Customer; (c) the most recent independent audit reports or security certifications held by the Processor's sub-processors (for example, SOC 2 reports and ISO 27001 certifications held by Supabase, Stripe, and Netlify); (d) a summary of any material Personal Data Breach affecting Customer Personal Data in the preceding 12 months.

10.2 If the information provided under 10.1 does not reasonably address the Customer's concern, the Customer may, on 30 days' written notice and at the Customer's cost, conduct an audit of the Processor's processing operations relevant to this DPA. The Customer shall appoint an independent auditor who is not a competitor of the Processor, and the auditor shall enter into reasonable confidentiality undertakings.

10.3 The parties shall agree the audit scope, timing, and methodology in good faith. Audits shall be conducted during business hours and shall not unreasonably interfere with the Processor's operations.

11. Liability

11.1 The liability of each party arising from or in connection with this DPA is governed by the limitation of liability provisions of the Agreement. The limitation-of-liability cap in the Agreement is a single cap that applies to the Agreement and this DPA together, and the Processor's total aggregate liability shall not exceed that cap.

11.2 Nothing in this DPA excludes or limits either party's liability for (a) death or personal injury caused by negligence, (b) fraud or fraudulent misrepresentation, or (c) any other liability that cannot be limited or excluded under applicable law.

11.3 As between the parties, the Customer shall remain responsible for ensuring that it has a lawful basis for the processing it instructs the Processor to carry out, including collecting any consents or providing any notices required of the Customer as Controller. The Customer shall indemnify the Processor against any claim, loss, or regulatory action arising from the Customer's failure to do so, except to the extent caused or materially contributed to by the Processor.

12. General

12.1 Order of precedence. This DPA prevails over any conflicting term of the Agreement in respect of processing of Customer Personal Data.

12.2 Variations. The Processor may amend this DPA on at least 30 days' notice to reflect changes in Applicable Data Protection Law or to the service. If the amendment materially reduces the Customer's protections, the Customer may terminate the Agreement for convenience on notice given within the 30-day window, and the Processor shall refund any pre-paid but unused subscription fees.

12.3 Governing law and jurisdiction. This DPA is governed by the laws of England and Wales. The parties submit to the exclusive jurisdiction of the courts of England and Wales.

12.4 Severability. If any provision of this DPA is held to be invalid or unenforceable, the remaining provisions continue in full force and effect.

12.5 Acceptable use. The Customer's use of the service, and the categories of data it may upload, are further governed by the Acceptable Use Policy at https://inspectready.co.uk/legal/acceptable-use/, which limits the upload of special-category data to what is strictly necessary as compliance evidence.

12.6 Notices. Notices to the Processor shall be sent to privacy@inspectready.co.uk and (for notices of a legal nature) copied to the Processor's registered office. Notices to the Customer shall be sent to the registered billing contact on the Customer's account.

12.7 Entire agreement. This DPA, together with the Agreement, constitutes the entire agreement between the parties in respect of processing of Customer Personal Data.

Schedule 1 — Processing description (UK GDPR Art 28(3))

Element	Detail
Subject matter	Provision of the InspectReady CQC-readiness, policy-management, audit, and evidence-pack service to the Customer.
Duration	From the date this DPA takes effect until the return, deletion, or anonymisation of Customer Personal Data under clause 9.
Nature of processing	Storing, organising, retrieving, adapting, structuring, analysing (via deterministic rule engine mapping evidence to the CQC quality statements), transmitting, and erasing personal data; generating PDF/ZIP evidence packs; issuing time-limited read-only auditor share links.
Purpose	(a) maintaining SAF-mapped policies, audit schedules, and findings; (b) storing compliance evidence files; (c) computing an evidence-coverage indicator and gap view; (d) generating evidence packs the Customer presents to CQC or shares with an auditor.
Categories of Data Subjects	(a) residents and service users of the Customer's care home(s) whose data appears in care-planning, medication, incident, or safeguarding evidence; (b) staff of the Customer named in policies, audits, training records, or rotas; (c) third parties (e.g. relatives, professionals) named incidentally in uploaded evidence or correspondence.
Types of Personal Data	Names, contact details, dates, role/employment information, care and health-related information appearing in evidence (care plans, MAR records, incident and safeguarding records), and any personal data contained in files the Customer uploads as evidence.
Special Category Data	Health data and other special-category data may appear in care-home evidence. Customers are instructed in the Acceptable Use Policy not to upload special-category data beyond what is strictly necessary as compliance evidence. The Customer, as Controller, is responsible for its lawful basis under Article 9 of the UK GDPR (typically the health/social-care condition).
Children's data	Not expected in the ordinary case (adult social care). Where a service user is under 18, the Customer remains Controller and is responsible for the lawful basis.
Frequency of processing	Continuous for the duration of the subscription.

Schedule 2 — Technical and organisational measures

The Processor implements, at minimum, the following measures as at the date of this DPA:

Encryption in transit. HTTPS enforced on all public endpoints. HSTS with preload. TLS 1.2 minimum.
Encryption at rest. Postgres volumes and storage objects encrypted at rest (AES-256) by the Supabase-managed infrastructure in the UK (London, eu-west-2) region.
Access control (per-home isolation). Row-level security policies on every table that stores Customer Personal Data, scoped to home_id within org_id so a home's evidence never crosses to another home or organisation. Evidence files live in a private storage bucket; downloads use short-lived server-minted signed URLs issued only after the access check.
Authentication. Supabase Auth with email + password and a bot challenge (Cloudflare Turnstile) on signup, login, and password reset. Password reset requires a signed link. Session cookies are first-party.
Personnel. The Processor's personnel with production access are bound by written confidentiality obligations. Access is on the principle of least privilege.
Sub-processor management. Sub-processors are selected and engaged in accordance with clause 5. Each infrastructure sub-processor holds its own SOC 2 Type II report or equivalent (Supabase, Stripe, Netlify, Sentry).
Backups. Supabase automated daily backups with point-in-time recovery on paid tiers. Backup media is encrypted.
Immutable audit log. An in-product account audit log captures security- and compliance-relevant events (sign-in, evidence generation, share-link creation, deletion). The audit_log table is append-only — it enforces FORCE row-level security with UPDATE and DELETE grants revoked from every role (including the service role), so history cannot be rewritten. Only identifiers and action metadata are stored in the log; file contents are never written to it. On account deletion or erasure the associated personal data is removed or anonymised while the immutable events are retained as a compliance record (clause 9.4).
Vulnerability management. Dependencies are tracked; high-severity CVE patches applied promptly. Error monitoring via Sentry with request-body and PII stripping.
Incident response. The Processor operates a written incident-response process and notifies affected Customers under clause 7. A post-incident review is conducted for every major incident.
Deletion and anonymisation. Evidence and home data follow the published Data Retention and Deletion policy — a life-of-subscription-plus-30-day-grace window, then a scheduled sweep removes evidence files and home records; personal identifiers in the immutable audit log are anonymised rather than the ledger destroyed (clause 9.4).
Physical security. Delegated to the hosting sub-processors (Supabase, Netlify). The Processor does not operate its own data-centre.

Schedule 3 — Approved sub-processors

The current sub-processor list is maintained at https://inspectready.co.uk/legal/subprocessors/ — single source of truth. The Processor's commitment to 30-day change notice is set out in clause 5.2(c).

As at the date of this DPA the sub-processors are:

Sub-processor	Legal entity	Purpose	Region	Transfer mechanism
Supabase	Supabase Inc. (US) / Supabase Ltd (UK)	Application database, authentication, and private evidence-file storage	UK (London) — `eu-west-2`	Processed in the UK region for this account; no Restricted Transfer triggered in ordinary operation. SCCs held in the Supabase DPA as a fallback.
Stripe	Stripe Payments Europe, Limited (Dublin — EU contracting entity)	Payments and subscription billing	EU (Ireland) primary; US for group support operations	Adequacy (EU/UK) for the EU contracting entity; UK Addendum to EU SCCs in the Stripe DPA as a fallback for US-importer transfers.
Resend	Plus Five Five, Inc. (operating as Resend) (US)	Transactional email delivery	EU + US	UK IDTA / UK Addendum.
Netlify	Netlify, Inc. (US)	Hosting and edge functions	US with EU/global edge	UK IDTA / UK Addendum.
Upstash	Upstash, Inc. (US)	Rate-limiting cache (Redis) — short-TTL request counters for abuse prevention; no account or evidence data	EU (Ireland) — `eu-west-1`	UK IDTA / UK Addendum in the Upstash DPA.
Cloudflare	Cloudflare, Inc. (US)	Turnstile bot challenge on signup, login, and password reset. Challenge token + IP address (Cloudflare-side only).	Global edge	UK IDTA / UK Addendum in the Cloudflare customer DPA.
GoatCounter	Martin Tournoij (NL, sole trader)	Cookieless analytics — does not ordinarily process Customer Personal Data (aggregated only)	EU	Not a Restricted Transfer.
Sentry	Functional Software, Inc. (US)	Error monitoring. Request bodies and PII stripped before reporting.	EU (de.sentry.io)	EU region selected; SCCs as fallback.
UptimeRobot	Uptime Robot Service Provider Ltd	Uptime monitoring — HTTP pings to public health endpoints; no personal data	Global	No Customer Personal Data processed.
Microsoft 365	Microsoft Ireland Operations Limited	Support / data-subject-request mailbox (`support@`, `privacy@`, `security@`)	EU (Ireland)	No Restricted Transfer in ordinary operation.

Acceptance by the Customer. This DPA is incorporated into the Agreement automatically and applies to every business Customer without a separate acceptance step. The Customer is deemed to have accepted this DPA by (a) creating an InspectReady account (the Agreement at https://inspectready.co.uk/terms/ incorporates this DPA by reference), or (b) continuing to use the InspectReady service after the date shown below. A countersigned printable copy may be returned to privacy@inspectready.co.uk where a Customer's procurement process requires it; this does not change the date or scope of the DPA taking effect.

Acceptance by the Processor. Signed for and on behalf of Crocker Digital Ltd.

Date: 2 July 2026

Signed: ______________________ Brian Crocker, Director