DIATRAKR
DIATRAKR Privacy notice Applies to diatrakr.uk and the record service
Last updated 15 October 2026

Your record is on a server you can point at.

This notice describes what happens to your data. It is short because the architecture is short: one server, one database file, no third parties in the request path.

What changed, and when

Until October 2026 DIATRAKR was an Android app that stored everything on the phone and had no accounts at all. It is now a web app with accounts, because sending a report to your unit and getting to your record from more than one device both need a place to keep it.

The privacy claim changed shape rather than disappearing. It used to be "your data never leaves your device". It is now "your data never leaves infrastructure this service controls, and no company sits between you and your clinic". If you preferred the first arrangement, the export button still gives you the whole record as a file you can keep yourself.

What is stored, and where

One file on one machine

Everything you type is stored in a single SQLite database on a private server in the United Kingdom. That database holds your account record (name, email address, hashed password), your treatment entries, your team contact list and your settings.

One thing stays in your own browser: a treatment you have started filling in but not saved yet. It is kept there - and only there, never sent anywhere - so that navigating away or reloading the page by accident cannot lose a session's numbers. It is discarded as soon as you save the treatment, sign out, or ask for a blank form, and it is not readable by anyone else using this service.

Stored

Treatments, targets, team contacts.

Hashed

Your password, with PBKDF2-HMAC-SHA256 and a random per-account salt. Never recoverable from the database.

Not stored

No advertising identifier, no device fingerprint, no location, no analytics events.

Never

Sold, brokered, shared with an insurer, or mined for anything.

What is not collected

  • Advertising networks or ad SDKsnone
  • Analytics, telemetry or crash reportingnone
  • Third-party scripts or pixelsnone
  • Content delivery networksnone
  • Web fonts from anyone elsenone, they are served from this machine
  • Cookies beyond the session cookie needed to stay signed inone

There is no cookie banner on this site because there is nothing to consent to. The one cookie that exists is the signed-in session, and it is set only after you sign in.

Reports, and who sees them

A report only exists when you build one, and it only goes anywhere when you take it away. What you download is a draft that opens in your own email app, so the message leaves from your own address through your own email provider. This server is not in the path at all and keeps no copy of what you send. The recipients are your unit, your nurse, or anyone else you add to your team list, and nobody can be added to that list but you.

Nothing about what you sent is stored here: the record is rebuilt from your entries every time you ask for it. Your own account's activity shows that you exported a record and when, which is there for you, not for anyone else. A share link is the one thing that is kept, so it can be listed and switched off; only its fingerprint is stored, never the link itself.

One email does come from this service. When you create an account, a confirmation link is sent to the address you gave, from noreply@diatrakr.uk, and it contains nothing but the link. Creating an account also sends a notice to this service's own admin address, so that a new sign-up is not missed; it carries the name and address you registered with and nothing else.

Getting it out, and getting it deleted

  • Export everything as one JSON fileSettings → Download everything
  • Import it back into this or any future copySettings → Import a copy
  • Delete one treatmentRemove it from the log
  • Delete the whole account and every entryEmail the address below

A deletion request is carried out by hand, on the same machine the database lives on, and confirmed back to you. There is no retention period to wait out and no backup that quietly keeps a copy after you have asked.

Security, honestly stated

Traffic is encrypted in transit. Passwords are hashed, never stored in a readable form, and a session cookie is required to reach any of your data. The database is not encrypted at rest, so anyone with administrative access to the machine could read it. That is one person, who also keeps a dialysis record of their own here.

No system is perfect. If you find a problem with this one, say so rather than assuming it is known.

Children, and other people's data

DIATRAKR is not aimed at children. If you are under 16, use it with the adult who looks after your treatment. If you log entries on behalf of someone else, you are responsible for having their permission to keep their health information here.

Changes to this notice

If this notice changes in a way that affects what is stored or who can read it, the date at the top changes and the change is described here. It will not be quietly rewritten.

Contact

Questions about privacy, or about your data: admin@diatrakr.uk.

Built and run by the patient whose record it holds

DIATRAKR is a self-tracking aid. It is not a medical device, it does not diagnose anything, and it is not a substitute for your renal team.