Privacy by design is visible in decisions that reduce data and system power, not only in a well-written privacy notice.
Topic
Which data is essential
The first test is necessity. Every data item should have a concrete purpose, retention period, and access rule. “It might be useful” is not a sufficient purpose.
Topic
Encryption and access are not the same thing
Encryption protects data in transit or at rest, but it does not automatically explain who controls the keys. Check whether the provider can read content, recover keys, or correlate metadata.
Topic
Where control resides
Self-hosting and zero knowledge answer different needs. The first moves infrastructure control; the second limits what the service can know. Both require clear operational responsibilities.
Topic
Deletion and exit
A data-respectful product should explain export, deletion, backups, and propagation times. Privacy also includes a practical way to stop using the service.
Checklist
What to verify
- Documented minimisation
- Clear key ownership
- Defined retention periods
- Practical export and deletion