Data Processing Addendum

We are only a processor when you let us in.

Corlayr runs on your infrastructure and your database. In normal operation we hold none of your customers' data and have no route to it. This addendum covers the one case where that changes: a support engineer working on a live environment at your request.

Last reviewed 2 November 2026Self-hostedSupport access only

The particulars.

What Article 28(3) requires a processing agreement to state, stated.

ItemWhat it is here
RolesYou are the controller. We are the processor, and only for the data described below.For your own employees' details that we hold to run the engagement, we are a separate controller, and the privacy notice covers that.
Subject matterDiagnosing and resolving a fault, incident or question in a Corlayr deployment, at your request.
DurationThe length of the support engagement, and no longer than the agreement it sits under.
Nature and purposeReading, and where you direct it correcting, records in a live or restored environment in order to find and fix a defect.
Personal dataWhatever the affected records happen to contain. Typically identity details, account and transaction records, control outcomes and case notes.We do not choose this. It is whatever is in the rows that the fault touches.
Data subjectsYour customers and their beneficial owners, your counterparties, and your own staff whose actions are recorded in the audit trail.

The addendum.

1

When this applies

This addendum forms part of the written agreement between you and 4EC LABS LTD for the supply of Corlayr. It applies whenever we process personal data on your behalf, which in practice means when you grant a named engineer access to an environment holding live records, or when you send us an extract, a backup or a log that contains them.

It does not apply to the ordinary running of the software, because we are not party to that. The system runs in your infrastructure under your control, and we receive nothing from it unless you send it.

2

We act only on your instructions

We process the data only on your documented instructions, including about transfers, unless we are required to do otherwise by law, in which case we will tell you before processing unless that law forbids it. A support ticket you raise, and the access you grant to answer it, are instructions for this purpose.

If we think an instruction breaches data protection law, we will say so and will not proceed until it is resolved.

3

Confidentiality and who may touch it

Access is limited to the people who need it to do the work in front of them. Everyone with access is bound by written confidentiality obligations that survive the end of their engagement with us, and each access is to a named individual rather than to a shared account.

4

Security

We take the measures required by Article 32. In this context the ones that matter most are organisational: access is granted per incident rather than standing, it is time limited, it is revoked when the ticket closes, and it is logged by your system rather than by ours, so the record of what we did sits with you and we cannot alter it.

Where data has to leave your environment, it travels encrypted in transit, is held encrypted at rest on our side, and is confined to the smallest extract that answers the question. We will always prefer a redacted or synthetic reproduction to a copy of live records, and will ask for one first.

5

Sub-processors

We do not appoint a sub-processor to handle your data without your prior specific or general written authorisation. Where you give general authorisation, we will give you reasonable notice of any intended addition or replacement so that you can object, and if you object we will not make the change for your engagement.

Any sub-processor we do appoint is placed under the same obligations as these by written contract, and we remain fully liable to you for their performance.

6

Helping you meet your own obligations

We will assist you, so far as is reasonable and taking account of what we can see, in responding to requests from data subjects exercising their rights. In most cases you will not need us: the data is in your system and your own operators can answer.

We will likewise assist with your data protection impact assessments, prior consultations with the Information Commissioner, and your own security obligations, by providing the information about the software that only we hold.

7

Telling you about a breach

If we become aware of a personal data breach affecting data we process for you, we will notify you without undue delay and in any event within twenty-four hours of becoming aware, with what we know at that point rather than waiting for a complete picture. We will keep you updated as we learn more and will help you make any notification you owe to a regulator or to data subjects.

8

Returning it or deleting it

At the end of the support engagement, and at your choice, we delete or return everything we hold, and delete existing copies, unless the law requires us to keep something. We will confirm deletion in writing if you ask.

9

Audit

We will make available the information needed to show we have complied with this addendum, and will allow and contribute to audits and inspections conducted by you or an auditor you appoint, on reasonable notice and no more than once a year unless an incident gives you cause.

10

Transfers out of the United Kingdom

We will not transfer your data outside the United Kingdom without a lawful transfer mechanism in place, being an adequacy decision covering the destination, or the UK international data transfer agreement or addendum to the EU standard contractual clauses, together with any supplementary measures the transfer risk assessment calls for.

Because the system is deployed where you chose to deploy it, the normal position is that the data never leaves that jurisdiction at all.

11

Which document wins

If this addendum conflicts with the rest of the agreement, this addendum governs the processing of personal data and the rest of the agreement governs everything else. Terms used here that are defined in the UK GDPR carry those meanings.

Questions about this document, and requests for the signed version for your procurement file, go to legal@corlayr.com.

Bring this to your DPO.

The architecture is the argument here: a system you host yourself produces a much smaller processing relationship than a service run on your behalf. We are happy to walk a data protection officer through it.