Privacy notice
Last updated 8 November 2026
This notice explains what personal data Thorium handles, what it is used for, and what you can do about it. It covers people who hold a Thorium account, people who are sent a document to sign, and people who visit this website.
Who is responsible for your data
Thorium is operated by Hdev Group (“we”). Who is responsible for your data depends on how you came to us:
- If you have a Thorium account, we are the controller of your account details and of how you use the service.
- If someone sent you a document through Thorium, the organisation that sent it is the controller of the document and of the record of you signing it. We process that data on their behalf and on their instructions. Questions about why they have your details, or requests to see or delete them, should go to them first. We will help them answer.
What we collect
Account holders
- Your name, email address and the workspaces you belong to.
- Your password is handled by our authentication provider (Google Firebase). We never see or store it. If you sign in with Google, we receive your name and email from Google.
- What you put into a workspace: documents, templates, contacts, comments and settings.
- Your IP address and browser details when you act on a document, as part of its audit trail.
People signing a document
When you open and sign a document, the audit trail records what you did so that the signature can be relied on later. Depending on how the sender set the document up, this can include:
- Your name and email address, as given by the sender.
- Your mobile number, if the sender requires a one-time code by SMS.
- That we emailed you a one-time code to open the document, if the sender requires one. The code itself is stored only as a salted hash and expires after ten minutes.
- The time of each action, your IP address, and your browser and device type.
- Your signature, initials and anything you type into the document’s fields.
- Your location, only if your browser asks and you allow it. Declining does not stop you signing.
- A passkey, if you choose to create one. We store only its public key.
- Photographs of pages you signed on paper, and the signatures cut from them.
- If you witness a deed: your name, home address and the statement you confirm about being present.
- That you accepted any handling conditions, how many times you opened the document, and any failed access-code attempts.
- Any time you were refused access, for example because the sender withdrew your access or limited the document to certain networks, with the IP address you tried from.
Checks on the signing session
To help stop a forwarded or stolen signing link being used by someone else, we assess each signing session. The assessment uses:
- From your browser: the writing system of your keyboard layout (for example Latin or Cyrillic, worked out from the letters printed on its keys, never from anything you type), your browser’s preferred languages, its time zone, and whether it reports being controlled by automation software. Some browsers don’t provide these, and that is fine.
- Information already in the document’s record: the IP address and device type you use, failed code attempts, refused access and whether the document was recently passed to you by someone else.
We never record keystrokes, passwords, codes or what you write. Your keyboard, language or location is never treated as suspicious by itself and cannot on its own cause an extra check. The browser details are not stored as they are: we keep only a one-way fingerprint of them, to notice if the same link is later opened from a differently set-up browser. The assessment is kept separately from the document’s audit trail, is visible only to the sending organisation’s administrators, and is never presented as evidence of who you are or where you were.
If the sending organisation has switched this on, an unusual session can mean you are asked for a one-time code sent to your email before you sign. In rare cases signing is paused until a person at the sending organisation reviews it. No decision with legal or similarly significant effect is made about you by automated means alone. If you are asked for an extra check or paused, you can contact the sender, who can review the session and let you continue.
Website visitors
Our servers log requests (IP address, page, time and browser) to keep the service running and secure. We don’t use analytics or advertising trackers. See the cookies page for the few cookies we set.
Why we use it
| Purpose | Lawful basis |
|---|---|
| Running your account and providing the service | Contract |
| Recording signing events so a signature can be evidenced later | Legitimate interests of the sender and the signers |
| Preventing fraud and abuse, and keeping the service secure | Legitimate interests |
| Assessing signing sessions so a stolen or forwarded link can’t be used | Legitimate interests of the sender, the signers and us in preventing fraud |
| Sending emails and SMS codes about a document | Contract, or on the sender’s instructions |
| Keeping records we are required to keep | Legal obligation |
We don’t sell personal data, use it for advertising, or use documents to train machine-learning models.
Who we share it with
We use these service providers to run Thorium. Each only gets what it needs.
| Provider | What for |
|---|---|
| Google Firebase | Sign-in and the application database |
| Amazon Web Services | Storing document files, sending email, and sending one-time codes by SMS where the sender asks for them |
| A time-stamping authority | Timestamping the sealed document. It receives a hash of the file, not the file. |
| A signature provider, if a workspace connects one | Applying an advanced or qualified signature. It receives a hash of the file. |
Other people on a document see what they need to: signers see each other’s names and signatures, and everyone gets the certificate of completion. A workspace can also send document events to its own systems using webhooks, or to its CRM or security logging tools (such as Splunk or Datadog). Events sent to security logging tools include the IP address and device type of the person who acted; other destinations don’t receive them. Where a workspace does this, it is the workspace’s choice and its responsibility. We will disclose data to authorities if the law requires it.
Transfers outside the UK
Some of our providers process data outside the UK. Where they do, we rely on UK adequacy regulations or the UK International Data Transfer Agreement or Addendum to protect it.
How long we keep it
- Account details are kept while your account is open, and deleted when you delete it.
- Documents and their audit trails are kept for as long as the workspace keeps them. The audit trail is evidence, so entries can’t be edited or deleted individually without breaking the chain.
- A workspace can set a retention period after which IP addresses and device details are removed from its audit trail. Removed entries are marked as redacted.
- Deleting a workspace deletes its documents, files and audit trails from our live systems straight away.
- Signing-session assessments are deleted automatically after the period the workspace sets, between 7 days and a year (30 days unless it chooses otherwise).
- One-time codes expire after ten minutes and are deleted once used or replaced.
- To show that audit trails haven’t been tampered with, we keep signed checkpoints of them. These hold document identifiers and hashes, not names or details, and are kept as long as the workspace is.
- Server logs are kept for a short period for security and then deleted.
Your rights
Under UK data protection law you can ask us to:
- give you a copy of your personal data;
- correct data that is wrong;
- delete your data, or restrict how we use it;
- stop using your data where we rely on legitimate interests;
- send your data to you or someone else in a portable format.
Some of these rights are limited where the data is evidence of a signature that others rely on. If you signed a document someone sent you, contact the sender first. Otherwise email privacy@hdev.uk. We’ll reply within a month.
If you’re unhappy with how we’ve handled your data, you can complain to the Information Commissioner’s Office at ico.org.uk.
Security
Documents are stored privately and served only through short-lived signed links. Access codes and one-time codes are stored as salted hashes. Audit trails are hash-chained and periodically signed with a key held outside the database, so they can’t be quietly rewritten. Traffic is encrypted in transit. If you think you have found a security problem, email security@hdev.uk.
Children
Thorium is not meant for anyone under 18, and we don’t knowingly collect their data.
Changes
If we change this notice in a way that matters, we’ll tell account holders by email before it takes effect. The date at the top shows when it last changed.
Contact
Hdev Group · privacy@hdev.uk