Is It a Promise or a Guarantee?
A privacy promise is a statement about what a company will do with your data. A technical guarantee is a limit on what the company can do. "We will never read your messages" is a promise. A system built so the company has no way to read them is a guarantee.
The common question is, "Does this company say it respects my privacy?" The more useful one is, "What would stop it from changing its mind?" The difference matters whenever a tool asks you to trust it with something personal: your messages, your photos, your health records, your DNA.
Promises depend on the company staying the same
A privacy policy is only as durable as the company behind it. Policies get rewritten, companies are bought and sold, and courts can order data handed over. None of that requires anyone to act in bad faith.
The genetic testing company 23andMe is a clear case. After it went bankrupt in 2025, a court approved the sale of its assets, including the genetic data of more than 15 million customers. The buyer, a nonprofit led by one of the company's co-founders, pledged to improve the privacy policies, so customers were now relying on a promise from a new owner.
Ask: if this company were sold tomorrow, what would happen to what I gave it?
Guarantees are built into the system
A guarantee works differently. End-to-end encryption scrambles a message on the sender's device and unscrambles it only on the recipient's, so the service in the middle never holds a readable copy. A court order cannot make a company produce what it does not have.
Signal, an encrypted messaging app, publishes the subpoenas it receives. When a U.S. grand jury demanded account information for 37 phone numbers, the most Signal could provide was when each account was created and when it last connected. Message content and contact lists are not on its servers.
Think of the difference between a postcard and a sealed letter. The mail carrier may promise not to read the postcard. The sealed letter doesn't depend on that promise.
Ask: if someone demanded my data from this company, what could it actually hand over?
Guarantees have edges too
A guarantee covers something specific, not everything. Encryption usually protects what you say, but the service may still know who you talk to and when (metadata, the information about a message rather than its content). A guarantee also depends on how the whole system is built. An unencrypted backup of your messages, for example, sits outside the protection the app advertises.
Ask: what exactly is protected, and what isn't?
Start close to home
Pick the app that holds your most personal information.
- Does it say it won't look, or that it can't?
- What happens to your data if the company is sold or shuts down?
- What does it still keep, such as contacts or timestamps, even if the content is protected?
Limits and open questions
Guarantees are not always available or practical. Many useful services need to read data to work, such as search, spam filtering, or shared documents. In those cases, a strong promise backed by law and outside audits may be the best option. A guarantee is also only as good as how it was built, and most people cannot check that themselves.
Open questions:
- When a service has to read your data, what would make its promise trustworthy?
- Who should verify that a technical guarantee works as described?
Newsletter connections
- Looks Good on Paper: the protection written down is not always the one people live with.
Related ideas
- Privacy by Design: why staying safe shouldn't depend on each person finding the right settings.
Appears in
- Privacy: the fourth stop, on what a privacy promise can and cannot protect.
Sources and further reading
- NPR: Judge OKs sale of 23andMe, and its trove of DNA data, to a nonprofit led by its founder (June 30, 2025)
- Signal: Grand jury subpoena for Signal user data, District of Columbia
- Ann Cavoukian, Privacy by Design: The 7 Foundational Principles (Information and Privacy Commissioner of Ontario, 2009).
What changed
- 2026-11-19: First published.
Spot something that needs correcting or updating, or have an example from your own community? Email me at hello@wiobyrne.com.