1. Your browser sends the number over HTTPS
The live service requires an encrypted HTTPS connection. The application must briefly handle the number in memory to check it, normalise its international format and request delivery of your verification code. This is different from storing a plain-number register.
2. The register stores a keyed fingerprint
Numbers in different local and international formats are converted to the same canonical international form. The application derives a matching value using a secret key. The active global registry stores that keyed fingerprint, the preference and verification/version timestamps rather than a full phone-number field.
A plain, unkeyed hash is not enough protection for predictable phone numbers. The matching key is kept in the server’s private configuration, separately from the database. A database copy by itself does not contain that key.
3. Full phone fields are encrypted where the workflow needs them
While a verification request is pending, its destination is stored encrypted. The verification code is stored as a separate keyed value. Full contact mappings retained by a participating business are also encrypted using a key separate from the matching key.
This does not mean every database field is encrypted. Business names, external references, masked numbers and other service metadata may remain readable. People should not put phone numbers or secrets into free-text notes or external IDs.
4. TouchSMS delivers the code you requested
The SMS provider must receive the destination and message to deliver your code. The current provider is TouchSMS. Processing that requested verification is not a sale of the register or permission to market to registered people. TouchSMS keeps its own service records under its privacy policy.
5. A business checks its own contacts
When an authorised business washes its list, the application compares those contacts with the active registry and the business’s own suppressions. Results identify the business’s own rows or external IDs. The master register, matching key and another company’s contact records are not exported.
Authorised operator contact-list exports can include separately retained full phone mappings. Business suppression exports use the business’s own references and masked numbers; neither exports the master register. Each business remains responsible for applying opt-outs in its sending platform.
6. You can leave or request a correction
Verify your number to leave the register. The operator can also review an authorised removal request. Removal deletes the active global entry and its verification requests, and old codes cannot restore it. A fresh verified registration is allowed later.
Earlier company suppressions remain so that a removal does not silently give businesses permission to send marketing again. Historical backups and a provider’s records are handled separately under their retention and recovery procedures.
What these protections do and do not promise
Key separation, encryption and restricted access reduce exposure. They do not make the records absolutely anonymous, guarantee that a server can never be compromised or protect data if an attacker obtains both the database and the relevant keys. No service can promise that every participating business will always comply or that all unwanted texts will stop.
Pending verification secrets are cleared after use, cancellation or expiry. Expired verification metadata is removed by scheduled cleanup, and wash-result files are available for twenty-four hours. Read the full privacy and scope notice for retention and contact details.
No ongoing work for you
There is no daily login, recurring confirmation or promotional newsletter to manage. Your preference stays active until you or an authorised operator remove it. You remain free to use a direct unsubscribe link, report a suspicious message or contact a sender separately.
Questions about your information? Contact the privacy operator.