You are handing us your service users' care records. This page says plainly where those records live, how your company's data is kept apart from every other company's, who can see what, and what we are still working towards. It is written for the person doing your due diligence, not for a marketing brochure — so it names what we have not done yet as clearly as what we have.
Every care record, note, document and photograph sits in a PostgreSQL database hosted in AWS London (eu-west-2). It does not leave the United Kingdom in the ordinary course of running the service.
Data is encrypted in transit — the site and both apps are HTTPS only, and the strict-transport policy covers every company's subdomain — and at rest on the underlying storage.
This is the question that matters most in multi-tenant care software, so here is the honest detail rather than a reassurance.
Every table in the database carries the owning company, and separation is enforced by PostgreSQL Row-Level Security — rules that live in the database itself and are applied to every query. It is not a filter our application code remembers to add. If a query forgot its company filter tomorrow, the database would still return nothing belonging to anyone else.
Each company also gets its own address — yourcompany.carelo.co.uk — but that is for routing and branding. The identity that decides what data you can reach comes from your signed-in session, never from the web address.
Care plans, assessments, body-map photographs, supervision records and any file you upload are held in private storage. There is no public link to them, and no link that keeps working if it is forwarded or leaks.
When a member of your office staff opens a document, we check they are signed in and that the document belongs to their company, and only then issue a link that expires within sixty seconds. Files uploaded by carers or families are checked against their actual contents, not just their file name, so a document cannot smuggle in something else.
Access follows the job, and the limits are enforced on the server, never by hiding buttons.
Care records are evidence, so Carelo is built to keep them honest rather than tidy. Changes are written to an audit trail with who made them and when, and the system deliberately refuses to rewrite history:
Every change runs through automated type checking, linting and an automated test suite before it ships, and dependencies are scanned for known vulnerabilities. When something is found, it is fixed and the fix is recorded — including what the problem was, who it could have affected and how the fix was verified.
We would rather tell you that plainly than claim nothing ever goes wrong. Software that never reports a defect is usually software nobody is checking.
We use a small number of established suppliers to run the service. These are our sub-processors under the Data Processing Agreement:
| Supplier | What they do | Where |
|---|---|---|
| Supabase (on AWS) | Database, authentication and file storage | London, UK |
| Vercel | Runs the web application | EU / global edge |
| Cloudflare | Domain and network protection | Global edge |
| Resend | Sends system email (invitations, resets, notices) | EU / US |
| Stripe | Subscription billing. Never sees care data | EU / US |
| Anthropic | Powers Carelo AI, where you switch it on | US |
| Mapbox / OpenFreeMap / Geoapify | Maps and address lookup for visit routes | EU / US |
| Apple & Google | Distribute the carer and family apps, and push notifications | Global |
Carelo AI is off unless you turn it on, and it is built to read rather than change your records. Billing never receives care data.
You are the data controller for your service users' records. We are your processor, on the Article 28 terms set out in our Data Processing Agreement, and we process those records only to run the service for you.
Our full Privacy Policy and Terms of Service set the rest out formally.
We would rather you hear this from us than discover it in a procurement questionnaire. Carelo is a young product built by a small team, and there are recognised assurances we are working through rather than claiming:
If one of these is a condition of buying, tell us where you are in your process and we will be straight with you about our timing rather than promising a date to win the meeting.
If you are completing a supplier assurance questionnaire, send it over — we would rather answer your form properly than hand you a brochure. If you believe you have found a security problem in Carelo, please tell us before telling anyone else, and we will work with you on it.
Email support@carelo.co.uk with “Security” in the subject line and it will reach the right person. Carelo is operated by Myfinity Ltd, registered in England and Wales.