← KaiKuu

Privacy Policy

Version 2026-10-23 · effective 23 October 2026

This explains what we do with your information, in plain English. We have tried to make it readable rather than thorough-sounding. If anything here is unclear, ask us — an explanation you cannot follow is not really a disclosure.

Who we are

KaiKuu is run by Trusted Source Medical Ltd (company number 16075246), which is the data controller for everything described here. That means the responsibility for your information sits with us, not with your employer.

Our Information Governance Lead is Richard Muswell, and there is a named partner you can reach about patient confidentiality specifically. You can contact either by email at contact@trustedsourcemedical.com, or use the Contact form inside the app.

We do not have a Data Protection Officer. That is a deliberate, documented decision rather than an oversight: the law requires one where an organisation processes this kind of data at large scale, and we do not — this is a small platform used by a single department's clinicians. If that changes, we will appoint one, and it would be someone independent of the people who build the software.

Your account is yours, not your employer's

You sign up as an individual. Your agreement is with us directly, and your logbook belongs to you.

If you join an organisation on KaiKuu — your department, for instance — that organisation does not get your data, cannot see your logbook unless you share something with it, and has no say in what you record. If you leave that organisation, or leave the employer entirely, your account and everything in it stay with you.

What about my patients?

This is the question worth answering first.

KaiKuu is built on the principle that patient-identifying information should never arrive here in the first place. Before an image is uploaded, your browser checks it for visible identifiers and warns you, and you confirm two things explicitly: that the image and your notes are anonymised, and that you have the patient's consent to keep the anonymised image for teaching and training. An entry cannot be saved without those confirmations — it is enforced by the database, not by a checkbox we trust.

Because the images are anonymised, they are not information about an identifiable person, and the data protection law described in the rest of this notice is mostly about *your* information rather than your patients'. We still treat every image as though it were clinical patient data — UK storage, strict access control, nothing public — because that is the right way to hold it, not because we are obliged to.

If something identifiable does slip through, tell us and we will remove it promptly. That is a failure to fix, not an argument to have.

What we collect

Why we use it, and on what legal basis

We use your information to provide the thing you signed up for: a logbook, progress against a curriculum, mentoring and sign-off, and teaching communities. Our legal basis is that we need it to deliver the service you have asked us for — in the law's terms, performance of a contract.

We also check scans for patient information before they are shared. The check runs on your own device, and if it is unsure about an image, that image is held back until one of our moderators has looked at it. This is how we try to stop a patient detail reaching other people, and it is part of providing the service.

For a short time after a moderator has decided, one named member of our team may look at a held-back image to work out why the check got it wrong — it currently raises the alarm far more often than it should, and the only way to improve it is to study the cases it got wrong. For this one narrow purpose our legal basis is our legitimate interests: a check that cries wolf is a check people learn to ignore, and that would put patients at risk. We look at how the check behaved, not at who is in the image. You can tell us to leave your images out of this, and we will — see Your rights below.

We do not use your information to advertise to you, we do not sell it, and we do not profile you.

If we ever want to use your scans to train AI models, that is a separate, specific choice you opt into. It is off unless you turn it on, and nothing flows to it today.

Who else sees it

Other members see only what you choose to share, and they see you as a display name and member code — never your email address. If you share a scan with a community, members of that community can see it; you can unshare it and it stops being visible.

A mentor who reviews your scan sees that scan. That is the point of asking them.

Behind the scenes we use three companies to run the service, and none of them uses your data for their own purposes:

Where your data lives

In the United Kingdom and Europe, and nowhere else. We chose each supplier on that basis, and we would treat moving your data outside the UK or Europe as a decision requiring its own assessment, not an operational detail.

How long we keep it

Your logbook stays for as long as your account does. If you close your account, your scans, images and clips are deleted with it — we do not keep a copy in case you change your mind.

Before deletion we will offer you a full copy of your portfolio to download and keep. Take it: once the deletion runs, the record is gone.

If you neither use nor close your account for five years, we will email you, warn you again a month later, and then delete it. We would rather remind you than hold a clinical portfolio indefinitely for someone who has moved on.

We keep backups, and they are kept on a rolling window rather than forever. So when something is deleted it goes from the live service immediately, and works its way out of our backups within 35 days at the outside. The database itself is backed up daily and those copies are kept for a week; the images are kept a little longer, because they are the part that could never be recreated.

An image held back by the check is kept for seven days after a moderator has decided about it, so that it can be studied to improve the check, and then it is no longer reachable. Seven days from the decision, not from when you uploaded it.

Records of safety decisions — a report, a moderation action, an administrative action — are kept longer, so that we can account for decisions we have made. They contain no patient information.

Your rights

You can ask for a copy of your information, ask us to correct it, ask us to delete it, object to how we use it, or ask us to restrict it. Contact us through the app and we will help. There is no charge and we will respond within a month.

One of those rights is worth spelling out. Where we rely on our legitimate interests — which, on this platform, means only the studying of held-back images described above — you can object, and you do not have to give a reason. Tell us and we will leave your images out of it. Nothing else about your account changes, and the check itself still runs: it protects patients, so it is not something you or we can switch off.

One thing we will not delete, and you should know this before it matters: if you have signed off another clinician's scan, that sign-off stays on their record — including your name, regulator and registration number — even if you later close your account. A sign-off is a professional attestation you gave to someone else, and their portfolio depends on it; removing your name would quietly damage a record belonging to a person who had no say in your decision to leave. Everything else about you is deleted. We will tell you exactly what was kept, and you can complain to us or to the regulator if you disagree.

You can also complain to the Information Commissioner's Office at ico.org.uk. We would rather you came to us first, but it is your right either way.

Automated decisions

Nothing about you is decided automatically. We use automated checks to help spot patient-identifying information in images before upload, but those only ever advise — you make the call, and your confirmation is what counts.

Security

Images and clips are held in private storage and reached only through short-lived links. Access is enforced by the database itself, row by row, so a mistake in application code does not open your logbook to someone else. Administrative access requires two-factor authentication and is logged.

We do not claim to be unbreakable. We claim to have designed for the day something goes wrong, and to tell you promptly if your information is affected.

Cookies

We use cookies only to keep you signed in and to remember a few of your own preferences. There is no advertising, no analytics tracking you across other websites, and nothing to consent to beyond using the service.

Changes to this notice

If we change something that matters, we will tell you in the app rather than quietly updating this page and hoping you re-read it. Each version is dated, and this one is shown at the top.

Questions about anything here? Use the Contact form in the app, or write to our Data Protection Officer.

Terms of Use →