Trust

Trust & Security

Last updated: 19 August 2026

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.

Where your data lives
United Kingdom
AWS London (eu-west-2)
Separation
Enforced by the database, not by app code
Care documents
Private storage, never a public link
Operated by
Myfinity Ltd
England & Wales
ico.
Registered with the Information Commissioner’s Office
UK data protection registration — 25 August 2026, application C2015753. New entries appear on the ICO public register once processed, so you can check us there yourself rather than take our word for it.

1. Where your data is held

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.

2. How companies are kept apart

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.

3. Care documents and photographs

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.

4. Who can see what

Access follows the job, and the limits are enforced on the server, never by hiding buttons.

  • Office staff — owner, manager, coordinator and a view-only role. Company settings, pay policy and staff accounts are restricted to owners and managers.
  • The view-only role cannot write anything. That is enforced on every table in the database, so it holds even if someone bypasses the screen entirely.
  • Carers see their own visits and only the service users they are assigned to. Their app is tied to a registered device with a private PIN, limited to three devices per carer.
  • Families see only what your office chooses to share, for their relative alone.
  • Regions can further narrow what a coordinator sees, where a company runs several areas.

5. Every change is recorded

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:

  • A visit a carer has checked into is a delivered call and cannot be cancelled or deleted — it stays part of the care record.
  • Cancelled visits are marked cancelled, never removed, so the reason survives.
  • Check-in and check-out are recorded with time and location, and work offline — a carer with no signal still gets an accurate record, uploaded when signal returns.
  • Records struck out in error are kept and marked, not erased.

6. How we build and patch

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.

7. Who else touches the data

We use a small number of established suppliers to run the service. These are our sub-processors under the Data Processing Agreement:

SupplierWhat they doWhere
Supabase (on AWS)Database, authentication and file storageLondon, UK
VercelRuns the web applicationEU / global edge
CloudflareDomain and network protectionGlobal edge
ResendSends system email (invitations, resets, notices)EU / US
StripeSubscription billing. Never sees care dataEU / US
AnthropicPowers Carelo AI, where you switch it onUS
Mapbox / OpenFreeMap / GeoapifyMaps and address lookup for visit routesEU / US
Apple & GoogleDistribute the carer and family apps, and push notificationsGlobal

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.

8. Your data stays yours

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.

  • Export whenever you like — rosters, timesheets, care records and matrices export to Excel and PDF from inside the product, without asking us.
  • Leaving — if you go elsewhere, you can take your data with you. We are not interested in holding a care provider hostage with their own records.
  • Subject access and erasure — we support you in answering requests from the people you care for.

Our full Privacy Policy and Terms of Service set the rest out formally.

9. What we are working towards

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:

In place UK data residency, database-enforced separation, private document storage, role-based access and audit trails. Described above, and we are happy to walk any of it through with your IT or governance lead.
In place UK GDPR Article 28 processor terms — our Data Processing Agreement is published, not hidden behind a sales call.
In place ICO registration — Carelo is registered with the UK Information Commissioner's Office (registered 25 August 2026, application C2015753). New entries appear on the public register once the ICO processes them, so you can verify this yourself.
In progress NHS Data Security and Protection Toolkit — we are completing the assessment. When it is published it is publicly searchable, so you will be able to verify it yourself rather than take our word for it.
In progress Cyber Essentials Plus — independently assessed technical controls.
In progress DCB0129 clinical risk management — the clinical safety standard for health and care software, with a named Clinical Safety Officer and a hazard log.

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.

10. Ask us anything

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.

Security and governance enquiries

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.