Privacy Policy

Last updated: 16 November 2026

This Privacy Policy explains how MalinArc ("we", "us", "our") collects, uses, shares, and protects your personal data when you use our platform, mobile applications, and related services (collectively, the "Service").

1. Who we are

MalinArc is operated by MalinArc Group Ltd, a company registered in England and Wales.

Registered address: 22a Freegrove Road, London N7 9JN, United Kingdom

Company number: 17342933

ICO registration reference: ZC223350

For the purposes of the UK General Data Protection Regulation (UK GDPR) and the EU GDPR, MalinArc Group Ltd is the data controller for personal data processed through the Service, except where we process data on behalf of our customers as a data processor (see the Data Processing Agreement).

2. What data we collect

We collect the following categories of personal data:

  • Account data — name, email address, password (hashed), account preferences, role within your workspace
  • Business identity — company name, registration number, VAT number, trade certifications, business sector
  • Contact details — postal address, phone number, business email addresses
  • Banking and payment data — payment card details (processed by Stripe; we do not store full card numbers), billing address, invoicing details
  • Position data — where a device records one, a worker's position when they start and file work and with each photograph, timestamped and kept beside the evidence record
  • Identity documents — a passport or driving licence, with a proof of address, that a person with no account uploads to show who they are when they make a data request about a business's records (section 9). We do not ask for identity documents to verify a workspace: a workspace is verified by a confirmed company email, by its company number at Companies House where it has one, and by a code we post to its address (its registered office for a company, or for a business with no company number that is registered for VAT, the address HMRC holds for its VAT number)
  • Media and photos — photographs and videos captured during inspections, including EXIF metadata
  • Audit logs — system-generated records of actions taken within the platform, including timestamps, IP addresses, and user agent strings
  • Device and technical data — browser or device type, operating system version, app version, and connection details

If you capture evidence in the field

When you take photographs as evidence of work for a workspace, or your position is recorded when you start or file that work, the workspace is the controller of that data and MalinArc Group Ltd processes it for the workspace as its processor (see the Data Processing Agreement).

Before your first photograph or position is recorded in a workspace, the web app shows you a notice from that workspace. It names the workspace as controller and us as its processor, and says what is recorded and why, on what basis, who receives it, how long each part is kept, what your rights are and how to object. The periods it gives are read from our retention register at the moment the notice is shown. We do not accept a photograph or a position from you until you have acknowledged the notice, and if the notice changes, nothing more is accepted until you have acknowledged the new one. Each acknowledgement is kept for the workspace, with the notice exactly as you saw it. The web app, and each mobile app we release, shows the notice before your first capture.

The notice stays available from your profile in the web app, under Privacy. From there, or from the notice itself, you can object under Article 21 to your position and your photographs being recorded. Your objection is recorded against the workspace, which decides it as the controller, with the date an answer is due. While it waits you can ask that your position is not recorded (Article 18), and you can withdraw it. Once it is upheld, your position is no longer recorded, and it is removed from the records the workspace holds of you that are not yet sealed. A record already sealed (sent to a client or invoiced) keeps it, as the evidence it was, and a photograph keeps any position its own file carries, as it was checked when it arrived.

3. How we use your data

We process your personal data for the following purposes:

  • Service delivery — providing the platform: inspections and reports, jobs and scheduling, commercial documents, contractor onboarding, tenders and the rest of the Service
  • Billing and subscriptions — processing payments, managing subscriptions, issuing invoices, handling refunds; and, once a month, recording each workspace's use of the platform in the month before (its plan, members against seats, how many inspections, service reports and invoices were made in it, and its storage against its limit), counts only, kept until the workspace is purged and shown to its owner and admins in the app
  • Contractor onboarding — verifying contractor credentials, trade certifications, and business identity through automated checks; and, once a contractor is approved, asking Companies House again each month about the company (its status, overdue filings, insolvency history and officers) and checking the Procurement Act 2023 debarment list, telling the company that approved it of any change
  • Identity verification — verifying a business's identity when its workspace is set up and whenever it changes: its company number at Companies House, a code posted to its address, and, where it records a VAT number, HMRC's confirmation of it
  • Fraud detection — checking that a file arrives as it was sent, checking contractor submissions for duplicate certificate numbers, reused document files, impossible dates, suspicious insurance details and recycled company names, each a signal a person reviews, and, where a service report records positions, checking them against the job's address and against each other
  • Compliance and legal obligations — maintaining audit trails, complying with tax and financial reporting requirements, responding to lawful requests from authorities
  • Platform improvement — analysing anonymised usage patterns to improve platform reliability and features
  • Communications — sending the emails the Service needs (account confirmations, sign-in codes, invoice receipts, security alerts). We send no newsletter or marketing email

4. Lawful bases for processing

We rely on the following lawful bases under Article 6 of the GDPR:

  • Performance of a contract (Art. 6(1)(b)) — processing necessary to provide the Service under our Terms of Service, including account management, inspection processing, and billing
  • Legitimate interests (Art. 6(1)(f)) — platform security and the prevention of abuse (rate limits, sign-in protection and the bot check at sign-up), improving the Service from counts and logs, enforcing our acceptable use policy, and two activities assessed in a written legitimate interests assessment against the interests of the people concerned. Positions and photographs recorded by field workers: the interest is proof of where and when work was done, on which disputes, audits and insurance turn; no less intrusive proof exists; and the balance holds only with the safeguards now in place: the worker sees the workspace's notice before anything is recorded and nothing is recorded until they acknowledge it; they can object from the notice or their profile, and an upheld objection stops the recording; a position is removed six years after it was recorded while the record keeps its own period; and positions are not used for productivity, attendance or working-hours purposes, which would be a new purpose needing its own assessment. Automated checks on contractor submissions:within what a contractor submitting credentials to be verified would expect, provided that every signal is advisory, read by the person at the client who decides, and never decides anything by itself, and that contractors are told the checks run, as this notice tells them
  • Consent (Art. 6(1)(a)) — where we ask for it to process optional data you choose to provide. You may withdraw consent at any time
  • Legal obligation (Art. 6(1)(c)) — where processing is required by applicable law, such as tax record retention, anti-money laundering requirements, or responding to lawful authority requests

If you are a contractor answering a company's questionnaire. The company that invited you is the controller of what you give in its pre-qualification questionnaire, and MalinArc processes it on that company's behalf. The company receives it to decide whether to engage you: because it is needed to enter into and perform a contract with you (Art. 6(1)(b)), and for its legitimate interest in checking the contractors it uses (Art. 6(1)(f)), on which the checks against public registers (Companies House, HMRC and the scheme registers) also rest. None of it rests on your consent; the questionnaire asks a consent only where it is the basis, and you may refuse or withdraw it without affecting your qualification. Automated checks run on what you submit: duplicate certificate numbers, reused document files, impossible dates, suspicious insurance details and recycled company names raise signals for the company's reviewer. A person decides; no signal decides anything by itself. You may object to those checks under Article 21 (section 9).

5. Special category and sensitive data

Where a workspace owner requires DBS verification for safeguarding purposes, MalinArc acts as a processor on behalf of that workspace owner, who is the controller and must be a DBS registered body or apply through an umbrella body.

We do not store an image, scan or copy of a DBS certificate. Attempts to upload one are refused. The workspace owner records only the outcome of the check it verified: the name of the person checked, the date and level of the check, the certificate reference number, whether the person is registered with the DBS Update Service, and the decision taken. An approved check stays on record while the workspace owner still relies on it — until its recheck date has passed, or a later approval of the same person takes its place — and then, as for a rejection from its decision, the DBS Code of Practice allows it six months more before deletion, to allow for dispute resolution, and we keep it no longer. A check recorded without a decision is removed six months after it was recorded. Criminal conviction details are never stored.

Before DBS requirements can be enabled, the workspace owner must accept the Appropriate Policy Document and declare how it is entitled to receive certificate information.

Identity documents uploaded with a data request are kept encrypted, opened for nothing but the check of who asks, and deleted when the request ends (section 9).

6. Data sharing and subprocessors

We share personal data with third-party service providers ("subprocessors") who process data on our behalf. All subprocessors are bound by data processing agreements that require them to protect your data to the same standard we apply.

Our subprocessors are:

  • OVHcloud — our servers, file storage and backups. Servers and files in London, United Kingdom; backups in Gravelines, France
  • Aiven Oy — our databases and cache, run from Finland with the data held in OVHcloud's London region, and a daily backup copy of the databases in France
  • Infomaniak Network SA — the email we send you (Switzerland)
  • Stripe — card payments, which MalinArc Group Ltd takes through Stripe; card details go to Stripe and never to our servers. Stripe also uses payment data on its own account, as an independent controller: to choose the banks and payment providers it uses, to prevent fraud and financial loss, for its own billing, to meet its legal duties including anti-money-laundering and know-your-customer checks, and to develop its products, under its own privacy notice
  • Sentry — error reports from the Service, held in its EU region, with personal data removed before they are sent

Public registers we ask about a business are not subprocessors: Companies House, HMRC, the Environment Agency and the postcode service receive the number or postcode being checked and answer for themselves as independent controllers. Virus scanning runs on our own servers and sends nothing anywhere.

One recipient is not a subprocessor and is named separately for that reason. We use Cloudflare Turnstile to tell human visitors from automated ones when you sign up or make a data request without an account. To do that, Cloudflare receives your IP address, TLS fingerprint and browser user-agent string. Cloudflare acts on our instructions for the bot check itself, but it also uses those signals to improve its own bot-detection service, and for that purpose it is an independent controller rather than our processor. That use is governed by Cloudflare's own privacy terms, not by our agreement with them. Cloudflare states these signals are not used for advertising or to track you across other websites.

We do not sell your personal data. We do not share your data with third parties for their own marketing purposes.

7. International transfers

Your data is stored and processed in the United Kingdom: our servers, file storage and databases are in OVHcloud's London region. Where data leaves the United Kingdom, we rely on the following safeguards:

  • European Economic Area — our encrypted backups are kept in France, Aiven operates our databases from Finland and keeps a daily backup copy of them in France, and Sentry holds error reports in its EU region. The UK recognises the EEA as providing an adequate level of protection, so no additional safeguard is required.
  • Switzerland — our email is sent through Infomaniak Network SA. The UK recognises Switzerland as providing an adequate level of protection, so no additional safeguard is required.
  • United States — transfers to Cloudflare are made under the EU Standard Contractual Clauses as amended by the UK International Data Transfer Addendum, which form part of our agreement with them. Transfers to Stripe, which processes card payments for MalinArc Group Ltd, are made to Stripe, LLC in the United States. They rely on Stripe, LLC's certification under the UK Extension to the EU-US Data Privacy Framework. Should that certification lapse or be invalidated, they rely on the EU Standard Contractual Clauses (Commission Decision (EU) 2021/914) as amended by the UK International Data Transfer Addendum. Any access by Sentry's US operator to its EU region is made under the safeguards the UK GDPR recognises: the UK extension to the EU-US Data Privacy Framework where the provider is certified under it, otherwise the Standard Contractual Clauses with the UK Addendum.
  • Other transfers — where required, we use Standard Contractual Clauses (SCCs) approved by the European Commission, supplemented by transfer impact assessments

8. Data retention

We retain personal data only for as long as necessary to fulfil the purposes for which it was collected, or as required by law.

This section covers data for which MalinArc is the controller — your account, your sign-in, our billing records and our own governance logs. The documents you and your counterparties create on the platform, such as inspections, reports, quotations, orders and invoices, are held by us as a processor on your instructions. Their retention is governed by the data processing agreement, not by this notice, because the periods belong to your obligations rather than ours.

  • Workspace data — retained while the subscription is open. A workspace closes when its cancellation is confirmed. The workspace owner then collects its data in the offboarding area, signing in with their password and second factor, within sixty days, and signs off. The workspace is deleted 120 days after the sign-off, or 120 days after the cancellation without one, and never before its data has been built and the owner told it is ready
  • Your account — retained while you belong to a workspace. When the last workspace you belong to is deleted, your sessions end, and a day later your name, email address, password, two-factor and recovery details are erased. The account itself is kept without them, because documents and audit entries still name it
  • Sign-in and session data — retained for the life of the session and a limited period afterwards for security investigation
  • Our billing records — our invoices, credit notes and corrective invoices to you, the payments and refunds against them, and the VAT they record, are kept for 7 years from the date of issue, to meet our legal obligation to keep accounting and tax records for 6 years from the end of the accounting period they relate to (Value Added Tax Act 1994 and the Finance Act 1998). We are not registered for any scheme carrying a longer period
  • Your requests to us about your data — kept for 6 years after we close them, to show how each was handled, which is also how long a claim about that can be brought. Their history is kept with them
  • Governance and audit events — retained for 6 years. These carry no link to a workspace, so they survive its deletion; that is deliberate, and it is what allows us to show that a deletion was lawful and happened on time
  • Identity documents — retained only while verification requires them, then securely deleted. The certificate image from a criminal records check is never stored at all
  • Our former mailing list — we no longer run a mailing list. An address that joined it before 15 November 2026 is kept, with the record of its consent, only until its consent record's six years have passed, and is never emailed. An address entered but never confirmed is deleted, with its request, after 30 days. If you ask us to erase your address, we delete it and keep only a one-way hash of it, to show the request was honoured, for six years
  • Backups — copies of the platform's data, kept so that it 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. 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. So a copy of anything deleted survives in a backup for 35 days at most. Backups are encrypted and used for nothing but recovery. If the platform is ever restored from one, every deletion made since under a retention period or an erasure request is made again before the platform is back in use

Where a legal claim is live, or where the law requires us to keep something longer, we keep it for that reason and no other, and we record why.

9. Your rights

Under the GDPR and UK GDPR, you have the following rights regarding your personal data:

  • Right of access — request a copy of the personal data we hold about you
  • Right to rectification — request correction of inaccurate or incomplete data
  • Right to erasure — request deletion of your personal data, subject to legal retention obligations
  • Right to data portability — receive your data in a structured, commonly used, machine-readable format
  • Right to restriction — request that we limit processing of your data in certain circumstances
  • Right to object — object to processing based on legitimate interests or for direct marketing
  • Right to withdraw consent — where processing is based on consent, withdraw at any time without affecting the lawfulness of prior processing
  • Rights related to automated decision-making — request human intervention where decisions are made solely by automated means

To exercise any of these rights, contact us at privacy@malinarc.com. We will respond within 30 days.

If you have an account, you can make these requests yourself from the Privacy tab of your profile in the app. A request about your account is answered straight away: a copy of your account data, or the same in a machine-readable form, to download; or your account erased, with a list of what we must keep, why, and the date each part ends. Your account cannot be erased while it holds a workspace's subscription, and we tell you so and what ends it. What a workspace you work in records about you — your photographs, your positions, its contact records — is that workspace's to answer as its controller: a request about it goes to the workspace, which answers it with the platform's tools, and you see its answer in the same place.

If you have no account, but a business that uses MalinArc may keep records about you — as its client, a site contact, a reference or a member of a contractor's staff — you can ask at our data request page. We check the email address you give by sending a link to it. You then upload an identity document (a passport or a driving licence) and a proof of address dated within the last three months, giving the name each shows, the identity document's number and expiry, and the date on the proof of address. We keep both files encrypted, open them for nothing but the check of who asks, and delete them when your request ends. We never keep the identity document's number: only a code made from it with a secret key, so that the same document given on another request, under another name, can be recognised. We do not use the documents for facial recognition or read their text by machine.

If you began a sign-up with us and did not finish it, we may keep two records of it under your address: the address itself, kept only to tell you if a payment you made is refunded, and a copy of each email we sent you about it. We answer for those ourselves, on the same page, as soon as you follow the link, without the documents above, because they hold only your address and what we sent to it: a copy to download if you asked for your data, and otherwise what we keep, why, and until when.

Our staff check that the request is genuine and goes to the right businesses, then pass it, with your documents, to each business whose records carry the details you gave. Each business decides for itself whether your documents show who you are, and answers you itself, as the controller of its records; nothing is handed over, erased or restricted until it has accepted them. Beside your documents we show it what our own records say about them: how your request matched its records, whether the dates and names you gave agree, and whether the same document was given on another request. Where its records hold another email address for you, that address is asked to confirm the request too. We do not tell you which businesses hold your data before they answer, and we tell a business nothing about you beyond what you gave us.

A business, or we for a request about your account, may need more time where requests are complex or numerous: up to two further months. If so, you are told within the first month, with the reason.

10. Cookies

MalinArc sets three cookies, all of them needed to run the Service you asked for: bo_rt, which keeps you signed in (held by the browser alone, sent only to our sign-in routes, 30 days); bo_session_active, which tells our website that you are signed in to the app (one day); and bo_current_plan, which tells our billing pages your plan (one day). None carries a tracking identifier.

Two providers run on particular pages. Stripe, which takes card payments on the sign-up and billing pages, sets its own cookies there (__stripe_mid, one year, and __stripe_sid, thirty minutes) to prevent payment fraud; they are part of taking the payment you asked for. Cloudflare Turnstile, the bot check on the sign-up, account set-up and data request pages, tells humans from automated visitors without cookies. If we measure visits to our website we use Plausible, which sets no cookies and identifies nobody. We use no tracking, advertising or analytics cookies, so no cookie consent banner is required under the Privacy and Electronic Communications Regulations 2003 (regulation 6) and the ePrivacy Directive (Article 5(3)): consent is not needed for a cookie strictly necessary for a service you have asked for.

11. Contact

For privacy-related enquiries:

  • Privacy enquiries: privacy@malinarc.com
  • Postal address: MalinArc Group Ltd, 22a Freegrove Road, London N7 9JN
  • ICO registration reference: ZC223350

12. Complaints

If you are not satisfied with how we handle your personal data, you have the right to lodge a complaint with a supervisory authority:

  • United Kingdom: Information Commissioner's Office (ICO) — ico.org.uk

We encourage you to contact us first so that we can try to resolve your concern directly.

13. Changes to this policy

We may update this Privacy Policy from time to time, for example when we change how the Service works, the providers we use, or how long we keep data, or when the law changes. The version published on this page, with the date shown at the top, is the one in force, and it replaces every earlier version.

Where a change materially affects how we use your personal data, we email the owner of each workspace before it takes effect where we can, and otherwise as soon as it does. An earlier version is available on request from the address in section 11.