Data Processing Agreement
Last updated: 15 November 2026
This agreement sets out the terms required by Article 28(3) of the UK GDPR for personal data that you put into the MalinArc platform about the people your work involves: your clients, your contractors and your staff. It forms part of the Terms of Service.
1. Which of us is the controller
For the records you create, you are the controller and we are the processor. A party record, a quotation, a purchase order, an inspection, a service report, an intervention, a contractor dossier or a framework agreement exists because you decided to create it and decided what to put in it. We hold it on your instructions. The periods in this agreement are those instructions, written down.
The personal data is what those records hold about people: names, contact details and job titles; signatures and photographs; the positions recorded with field evidence; the qualifications, Right to Work checks and DBS checks recorded for contractors' staff, a DBS check being information about criminal records; and bank details. The people are your clients and their contacts, your contractors and their staff, your own staff, and anyone else your records name. We process it for as long as you use the platform, and then as sections 3 and 4 set out.
For your own account, we are the controller. Your sign-in, our billing records, our subscription invoices to you, and our own governance and audit logs are ours, held for our own purposes and our own legal obligations. Those are covered by the Privacy Policy, not by this agreement, and no instruction under this agreement changes them.
The distinction decides who owes what. Where we are your processor, a person exercising their rights goes to you and we assist. Where we are the controller, they come to us directly.
2. Our instructions, and the limits on them
We process the personal data covered by this agreement only on your documented instructions, which are: operating the platform for you as described in the Terms of Service, and the retention periods set out below. If the law requires us to process it in any other way, we tell you before we do, unless that law forbids it. If we think an instruction of yours breaks data protection law, we tell you at once.
Apart from three things, we do not process it for any purpose of our own. For those three we are the controller, each is set out in the Privacy Policy, and no instruction under this agreement changes them.
Fraud checks across the platform. When a contractor gives a business on MalinArc its documents, we compare its certificate numbers, the fingerprints of its files and its company name with those of other contractors on the platform, to find a certificate claimed twice, a file reused or a name recycled. Each finding is a signal for the person who decides to judge; it decides nothing by itself.
The shared registry. A company recorded by more than one business on MalinArc is held once, one record for each company number, with its public identity from Companies House, and each business's records point to it.
Usage figures. Once a month we record, for each workspace, how it used the platform in the month before: its plan, its number of members against its seats, how many inspections, service reports and invoices were made in it, and its storage against its limit. Those figures are counts, never the content of a record or anything about a person in it. We hold them for billing and account management, and they are deleted when the workspace is purged.
Everyone who handles it is under a duty of confidence. We keep the security measures required by Article 32, and we notify you without undue delay if we become aware of a personal data breach affecting your data, so that you can meet your own obligations. We help you with your data protection impact assessments and any prior consultation with the Information Commissioner, with what we know of the processing.
We use sub-processors. The current list, what each one does and where it is established, is section 6 of the Privacy Policy. We will tell you before adding or replacing one, so you have the opportunity to object. Each is bound by a written agreement that protects your data as this one does, and we remain responsible to you for what it does.
3. How long we keep it while you are a customer
While your account is open we keep the records you create for as long as you keep them. Deleting a record removes it from the live platform; its history is kept as described below, and its backup copies end as section 5 sets out.
Some records are kept beyond that. An issued invoice, credit note, quotation or purchase order, and the snapshot of each party frozen into it at the moment of issue, are kept for seven years from issue: VAT Act 1994 Schedule 11 paragraph 6 requires six years from the end of the accounting period in which the document was issued, which seven years from issue covers for an accounting period of up to a year. That obligation falls on you, as the business that issued or received the document, not on us as your processor. Evidence of asbestos work is kept for forty years, the period the Control of Asbestos Regulations 2012 set for the health records of the people who do that work, and evidence of structural, roofing, cladding and fire safety work for thirty years, the longest the Building Safety Act 2022 allows for a claim under the Defective Premises Act 1972. Keeping each record for its period is part of your instructions to us (section 2), and we carry it out for you.
The worker's position inside an evidence record does not share its period. The location taken when a worker arrives to start an inspection, a service report or an intervention, the one taken when they file an inspection or a report, and the one on each photograph are removed six years after they were taken, and the record itself stays for its own period. The reasons for keeping the record of the work do not reach the worker's position, and six years is the Limitation Act 1980's period for a claim about the work. A legal hold on the record, its job, its property or its pack pauses the removal, and the deletion of a closed workspace, until it is lifted or its review date passes.
A tender you publish, and the tender submissions made to it, are kept for seven years from when the tender was awarded or ended: the winning submission and its pay requests from the award, the others from the close. That is the six years the Limitation Act 1980 allows for a claim about the work, and a year's margin. A tender you never published was never seen by anyone else, and it is deleted with your account.
A framework agreement you run, with its lots, rates and suppliers and the call-offs, competitions and responses made under it, is kept for seven years from when it ended: when it expired, or you terminated or cancelled it. That is the same six years and a margin, because a claim about work called off under it can turn on its terms. While a purchase order placed under it is still kept, the framework is kept with it. A framework no supplier was ever appointed to was never shared with anyone, and it is deleted with your account.
The commercial terms you agree with a contractor or a client are kept version by version, each with its rates, thresholds and impact assessments, for seven years from when that version stopped applying: when a newer version replaced it, its dates ran out, the relationship was terminated, or one of you left. That is the same six years and a margin, because a claim about work priced under the terms can turn on them. A version never agreed is kept for twelve months after its relationship ends. A contractor's own base rates, which no client sees, are kept for as long as the contractor keeps them and are deleted with its account.
The history of a record, meaning who created, changed or sent it and when, is kept for as long as the record is. Where the record is one of those above, the history follows its period. Where the record goes with your account, its history is kept for six years from each entry, the Limitation Act's period for a claim about it, and then deleted.
An organisation in the shared registry, such as a contractor, a counterpart or a subcontractor, is deleted once no record names it, and never sooner than a day after it was added. The history of your organisation's legal identity keeps each version for seven years after it stopped applying, the same period as the documents issued under it.
An invitation you send a contractor is kept for twelve months after it ends: once it is accepted, declined, withdrawn or left to lapse. One a contractor accepted is kept for as long as the dossier it opened. One nobody accepted is deleted with your account.
A contractor's compliance dossier is kept for seven years from the end of the relationship: when you suspend it, its approval lapses, or it is archived. That is the same six years and a margin, because a claim about the work can turn on how the contractor was vetted. An application you reject is kept for twelve months from the rejection, and one never completed for twelve months from its last activity: no relationship began, and the claims a refusal can give rise to run for months, not years. Reopening an application stops its clock. The contractor's own company record, with its users, references, insurance and documents, is deleted once the last dossier it serves is gone.
A DBS check you record against a dossier, with the decision it informed, stays on record while you rely on it. An approval stays until its recheck date has passed, or until a later approval of the same person takes its place, and is then deleted six months later, as a rejection is six months after its decision: the most the DBS Code of Practice allows. A check you record and never decide is deleted six months after you recorded it. The record is yours alone: another organisation relying on the same contractor keeps its own.
4. What happens when you leave
Article 28(3)(g) gives you the choice of having your data returned or deleted at the end of the service. You make that choice here, in advance, and it is this:
- Cancel. The workspace owner may cancel at any time. We first show them, in the app, the date the period already paid for ends. When they ask, we email a single-use link; the app shows a reference and the email quotes it, so a reference you did not see in the app is not from us. The cancellation is made only when the owner opens that link and signs in on its page with their password and a code from their authenticator app, against the legal notices the page states. From that moment the workspace closes: nobody can sign in to it, and nothing in it can be created, changed, sent, issued or recorded. A limited, read-only offboarding area opens to the workspace owner alone at once, behind their password and second factor, and we email the owner. The subscription runs to the end of the period already paid for and then ends; nothing already paid is refunded. Until that date, or a sign-off, whichever is sooner, the workspace owner can resume the subscription from the offboarding area at no charge, which ends the offboarding. If no paid period remains — a renewal unpaid, or a trial — the subscription ends and the offboarding begins at once.
- Request your data. The owner requests it there. We build it overnight in two parts, the data (every record as a CSV file) and the collection (the photographs, PDFs and certificates your records name, with the invoices we issued you), and email the owner as each part is ready. If it is not requested, we build it anyway thirty days after the cancellation.
- Collect and verify. Each part downloads from a short-lived link that can be issued again, and every download is recorded. Every file carries its SHA-256 checksum, shown in the part's manifest. The owner confirms the files they hold are intact, or reports a problem, and we build that part again.
- Sign off. The owner signs off with their password and second factor, against the checksums of the two parts. Signing off confirms you have your data, ends the offboarding and any chance to reactivate the workspace, and starts the hundred and twenty days to its deletion. It cannot be undone.
- Collection deadline. Please collect and sign off within sixty days of normal use stopping. We remind the owner thirty, fourteen, seven and one day before that date.
- Deletion. We delete your workspace and everything in it, including both parts, one hundred and twenty days after you sign off, or one hundred and twenty days after normal use stopped if you do not — so never fewer than one hundred and twenty days after normal use stopped, and up to sixty days more if you sign off close to the deadline. Nothing is deleted before both parts are built and the owner has been told each is ready, and a legal hold withholds the deletion while it lasts.
- If you do not collect your data, we delete anyway. Silence is deletion. We do not hold your data indefinitely waiting for a reply, because holding it with no purpose would itself be unlawful.
If you want your data returned in some other form, tell us before the deletion date. To keep it on the platform, reactivate your workspace before you sign off and before that date. After that there is nothing left to return. We keep the record of your departure (what was built, sent, downloaded, confirmed and signed for) for six years after it ends, as evidence that your data was returned.
Records we are required by law to keep, as described in section 3, survive this and are then deleted at the end of their own period.
So does a tender you published. The contractors who answered it are party to it, and your leaving does not take it from them: it counts as the tender's close, and the tender is deleted seven years later, as section 3 describes.
A contractor's dossier works the same way. The contractor who submitted it is party to it, so it is suspended when you leave rather than deleted, and kept for seven years from then.
So does a framework agreement you run. The suppliers appointed to it are party to it, so your leaving ends the framework rather than deleting it, and it is kept for seven years from then. If you are a supplier on another organisation's framework, that organisation keeps the record that you were on it, with the call-offs and responses you made under it, for the same period.
The terms you agreed with another organisation survive your leaving for them, and end seven years after they stopped applying. An invitation you sent that a contractor accepted stays with the dossier it opened. Invitations still outstanding stop being usable thirty days after you cancel, and come back if you reactivate. If you were invited to another organisation's calendar event, it keeps the record that you were asked and how you answered.
Work you gave a contractor under a contract is the contractor's record as well as yours. When you leave, your contract and the visits it gave are deleted, but the contractor keeps the jobs it planned from those visits, and each keeps your business name as the visit gave it, and nothing else of yours.
5. When a deletion is actually complete
Deleting a record removes it from the live platform immediately. Copies of it can survive for a period in backups, which exist so that your data can be recovered if something fails. There are two sets: ours, an encrypted copy of the databases and of the uploaded files, taken daily to our storage in France and kept for 27 days; and our database provider's, the backups its recovery needs, held with the databases in London, and a daily copy it keeps in France for up to 35 days.
Backup copies are put beyond use: they are not read, not queried, not used to make any decision about anyone, and not returned to the live platform except in a recovery. They are encrypted at rest.
No backup copy is kept for more than thirty-five days. A deletion is therefore complete thirty-five days after it is made: by then every backup taken before it, ours within twenty-seven days and the provider's within thirty-five, has itself been deleted.
A recovery does not bring back what was deleted. If we ever restore the platform from a backup, every deletion made since that backup was taken, whether under a retention period, a purge or an erasure request, is made again before the platform is back in use.
Files you upload — photographs, certificates, rendered documents — are encrypted at rest by our storage provider, and each is recorded in a register under your workspace or, once it is issued, sealed or shared with someone and so kept after you leave, under ours. Deleting your workspace removes its records and queues every file that is yours alone for deletion, and a file kept after you leave is deleted at the end of its own period like any other record. We are building a key for each workspace, under which its files will be encrypted so that deleting the workspace destroys the key and makes every copy unreadable at once, backups included. Until that is in place, a deleted file's copies in backups are put beyond use as this section describes, and are gone when the last backup holding them is.
6. Helping you answer a person's request
A request from one of your clients, contractors or staff is yours to answer. Article 28(3)(e) requires us to help you, and we do so in two ways.
Through the platform. A person who works in your workspace can make a request about what it records about them from their profile, and it reaches your workspace's Data requests inbox, where your owner and admins see it with its due date. They are emailed when it arrives, a week before it is due if it is still open, and again if the date passes; the emails name the right and the dates, not the person. For each request the platform shows you what it holds about the person in your workspace, and gives you the tools to answer: their export, in a spreadsheet form or a machine-readable one; erasure of your contact records carrying their email, with what the retention register keeps listed by class and end date; and, for an objection to the recording of their position, withholding it from then on, including the position a photograph file carries in its own metadata, and removing it from the records you hold of them that are not yet sealed. Sealed records keep it, as the evidence they were, and a photograph file already received keeps what it carried, as it was checked when it arrived. While an objection waits, the person may ask that their position is not recorded until you answer (Article 18), and may withdraw it. You decide; the platform carries it out and records each step, by who took it, in the request's trail and your audit trail. You can also read, correct and export the records you hold, and erase a person's contact details from a party record, directly.
By asking us. Where the platform cannot reach something, write to us and we will action it, or tell you why we cannot, in time for you to answer within the one month the law gives you.
While your workspace is closing. A request still reaches your Data requests inbox and you still answer it, from the same read-only offboarding area, until you sign off or the collection deadline passes. If a request is answered after we have already built the data part of your export, we note beside that part what changed rather than building it again, so what you downloaded and what we now hold do not drift apart unnoticed.
One limit applies to both routes, and it is not ours to waive. Where a record is held to satisfy a legal obligation — an issued document and the party snapshot inside it, kept for the VAT record-keeping period section 3 sets — erasure does not reach it. Article 17(3)(b) disapplies the right in that case. What we can do is remove the contact details that sit outside that obligation, which is what the erase function does: the email address, the telephone number, the named contacts and the bank details go, and the business identity the invoice depends on stays.
7. Showing you we have done this
We make available the information you need to demonstrate compliance with Article 28, and we allow and contribute to audits you or an auditor you appoint carry out, on reasonable notice and no more than once a year unless a regulator or an incident requires otherwise.
8. Where your data is
Our servers, file storage and databases are in the United Kingdom, in OVHcloud's London region. Our databases are operated by Aiven from Finland, which holds their recovery backups in London and a daily copy in France; our own encrypted backups are in OVHcloud's Gravelines region in France. The EEA is covered by UK adequacy, so no additional transfer mechanism is required. Email goes through Infomaniak in Switzerland, also covered by UK adequacy. The bot check at sign-up and on the data request page is Cloudflare's, card payments are Stripe's and error reports go to Sentry's EU region; transfers to the United States among those are made under the safeguards section 7 of the Privacy Policy names. Section 6 of the Privacy Policy names each provider and what it does.
9. Contact
Questions about this agreement, or a request under section 6, go to privacy@malinarc.com.
MalinArc Group Ltd is registered in England and Wales, company number 17342933. ICO registration reference ZC223350.