Skip to content
ClaimCore

Data protection

Sub-processors

Your firm is the controller of the claims data in ClaimCore. We are your processor, and everyone below is a sub-processor of yours. This is the complete list — there is no “and others” category.

WhoWhat they doWhat reaches themWhere
NeonManaged PostgreSQL. Every claim record, user account and audit entry.All structured claim data: claimant identity, contact details, date of birth, national insurance number, injury detail, vehicle, liability, finance and correspondence metadata.EU
Cloudflare R2Object storage. Every uploaded and generated document.Identity documents, bank statements, medical reports, engineer reports, signed agreements, invoices and payment packs.EU
VercelApplication hosting and the CDN in front of it.Data in transit only. Request logs may contain URLs, which include claim identifiers but not claim contents.UK/EU
Microsoft 365 / Graphonly if you buy the add-on that uses itThe Communications add-on: reading a firm's own mailbox and sending on its behalf.Correspondence between the firm, its clients, solicitors and insurers, and the attachments on it.UK/EU
getAddress.ioonly if you buy the add-on that uses itPostcode lookup on the public intake form and in the claim file.A postcode. No name, no claim reference, nothing that identifies a person.UK
DVLA vehicle enquiryonly if you buy the add-on that uses itRegistration lookup.A vehicle registration mark. Not linked to a claimant in the request.UK

What we will tell you, and when

  • We will give you notice before adding a sub-processor that will handle claims data, so you have time to object.
  • The three optional entries are only engaged if your firm buys the add-on that uses them. A firm on Core alone is served by the first three.
  • We hold no certifications — no ISO 27001, no Cyber Essentials, no SOC 2 — and there has been no third-party penetration test. That is stated on the security page too, and it will stay stated until it stops being true.