What is held
The account itself
- Your name and email address. The address is how you sign in. It is stored in lower case and has to be unique.
- Your password, hashed. Never the password itself. Accounts moved across from the previous Haresign site keep the hash they already had, and it is re-hashed with a stronger algorithm the first time you sign in here.
- A permanent account identifier. A random UUID, created once and never reissued. It is what other Haresign applications will use to recognise you, which is why it is not your email address — people change mailbox and employer.
- Whether your address has been confirmed, and whether that came from you following a link, from staff, or from the previous system.
- Which organisations you belong to, your role in each, who decided it and when.
Existing Haresign sign-ins
Accounts created from an existing sign-in
If your account was created from your existing Haresign sign-in, it was created with your name, email address, password hash and organisation memberships. Nothing else was copied: no clinical or practice data, no sessions, no password-reset links, no API keys, no subscriptions and no application data.
A record links your Haresign Identity account to the sign-in it was created from, so the two can be kept consistent. It holds identifiers and checksums — not a second copy of your name, address or password.
Keeping the account safe
The security record
Every sign-in, failed sign-in, password change and membership decision is recorded. This is the part most worth reading twice.
Each entry holds the time, what happened, your account identifier where one is known, the address the attempt was made against, the network address the request came from and the browser it reported.
Two consequences worth being explicit about:
- The record is kept even when no account matched. That is what makes an attack on accounts that do not exist visible at all.
- Closing an account does not erase the history. The account row is emptied of you, but earlier security events still name the address they were recorded against. The trail cannot be edited — that is deliberate, because anything that could rewrite it could also erase the record of an attack.
There is not yet an automatic retention limit on these events. They accumulate. A retention policy is required and is not written; until it is, this is the honest position rather than a claim we cannot support.
Credentials never reach the record. Anything that looks like a password, token or key is removed before an entry is stored, and network addresses and identifiers used for rate limiting are stored as keyed digests rather than in the clear.
Cookies
What this service sets
Two, both strictly necessary and neither used for tracking: one keeps you signed in, one protects forms against cross-site submission. They are set for this hostname only and are not shared with any other Haresign site.
There is no analytics, no advertising, no tag manager and no third-party script of any kind on any page here.
Leaving
Closing an account
Closing an account removes your name, email address, password, sessions and any outstanding links, and replaces the address with one that can never receive mail.
Two things are kept on purpose. The account identifier stays, so it can never be handed to somebody else. Your membership records stay, marked as ended: who had access to an organisation and when it ended is the organisation's record, not yours.
Closing an account and registering again with the same address gives you a new account with a new identifier. No Haresign application will treat the two as the same person.
There is no self-service closure yet. Ask staff and it is done for you.
Questions
Asking about your data
Contact Haresign to ask what is held about you, to correct it, or to have your account closed.