PRIVACY
Privacy notice
Interim notice for the SigBond controlled testing programme (Stage 1 beta)
Version 1.1 · Last updated 27 September 2026
Who we are
SigBond Ltd ("SigBond", "we") is the controller of the personal data described in this notice.
- Company number: 17435690 (registered in England and Wales)
- Registered office: Four Winds, Allington Lane, Eastleigh, SO50 7DD
- Contact: team@sigbond.com
What this notice covers
SigBond is running a controlled product-development and testing programme (a "beta"). It is not a commercial service. This notice describes only the personal data we actually process during the beta. It does not describe features that are planned but not yet built.
If we change what we do with personal data, we will update this notice, along with its version and date.
Who this notice applies to
- Testers — tradespeople who agree to take part in the beta.
- Clients — customers of a participating tradesperson who are asked to confirm a job. A tradesperson may enter your phone number so we can send you a request to confirm the details of a job you have agreed. See "Where we get your data" below.
What data we process
Depending on how you use the beta, we may process:
- Account details — name (or display name), email address, and a password (stored only in hashed form, never in plain text).
- Business details (testers only, optional) — business name, business address, company number.
- Phone number — when you enter a mobile number, we store a fixed-length code (a hash) of it and its last four digits. If a tradesperson sends you a request to confirm a job, we also keep the number itself, encrypted, while that request is waiting for your answer, so the confirmation text can be sent again. We delete it as soon as you confirm or decline, or when the request expires after 14 days.
- Security data — to protect our text-message service from abuse, we keep a scrambled (hashed) form of the internet address a verification code was requested from, and delete it after 24 hours.
- Verified record detail — the details of a job that two parties confirm: job title and description, price, dates, materials notes, job postcode, and the names of both parties. This is held in our own database. Only a cryptographic fingerprint (a SHA-256 hash) of this detail is published to the Nostr network — never the detail itself.
- A signing keypair — to sign verified records, we generate a cryptographic keypair for your account and hold the private key for you in encrypted form. This is a custodial arrangement for the beta.
- Reviews (if used) — a rating and any text you submit about a completed job.
- A reputation figure — a headline figure calculated from your verified records and reviews and shown on your profile. It is worked out fresh each time it is shown; it is not stored as a separate record.
- Usage and feedback data — basic analytics about how the beta is used (for example, which steps are completed), and any feedback or bug reports you send us.
We do not, in this beta, process payment card details, identity documents, or any credit, insurance or pre-screening data. We do not use those features, because they do not yet exist.
Where we get your data
- Directly from you, when you register, complete a job record, or send us feedback.
- From a participating tradesperson, if they enter your phone number to send you a request to confirm a job. Where this happens, you will receive a text message from SigBond explaining why you have been contacted and linking to this notice. If you do not want to take part, you can ignore the message or ask us to remove your number.
Why we are allowed to use your data
- Consent — testers take part voluntarily and can withdraw at any time.
- Legitimate interests — running, securing and improving the beta, and enabling two parties to create a shared, confirmed record of a job they have agreed. Where we rely on legitimate interests, you can object (see "Your rights").
Who we share it with
We use a small number of service providers to run the beta:
- Twilio — sends the text messages. Twilio receives the mobile number and message content at the moment of sending. Twilio is based in the United States. Twilio also tells us whether each text was delivered, and we store that status.
- Postmark — sends transactional emails. Postmark receives the email address and message content. Postmark is based in the United States.
- DigitalOcean — hosts our systems. Our data is held in a London data centre.
- The Nostr network — receives only cryptographic fingerprints (hashes) and public keys. It does not receive names, contact details or job detail.
Where a provider is outside the UK, the transfer is covered by appropriate safeguards (such as the UK extension to the EU–US Data Privacy Framework, or standard contractual clauses).
We do not sell personal data, and we do not use it for advertising.
How long we keep it
We keep beta data for as long as the beta runs and while your account is active. Because this is an early testing programme, deletion during the beta is handled by us on request rather than by an automatic process — contact us and we will remove your data where it is technically possible to do so. There are two exceptions, which are deleted automatically: the encrypted copy of a client's number, as soon as the confirmation request is answered or expires, and the scrambled internet address, after 24 hours. Fingerprints already published to the Nostr network contain no personal data.
Your rights
You have the right to ask us to give you a copy of your data, correct it, delete it, restrict or object to our use of it, or provide it in a portable form. During the beta, please exercise these rights by emailing team@sigbond.com and we will respond.
If you are unhappy with how we handle your data, you can complain to the Information Commissioner's Office (ico.org.uk).
Automated decisions
We do not make decisions about you by automated means that produce legal or similarly significant effects.
Children
The beta is for people aged 18 and over. It is not intended for children.
Changes
This is an interim notice for the beta. We will update it as the programme develops, changing the version number and date each time.