01 / Privacy-services product concept
Connection
Evaluate private network and DNS services.
VPN and DNS services address different exposures. Provider trust, retained metadata and the device’s other network paths still matter.
Privacy-services product concept
A proposed subscription and dashboard for managing practical privacy services, with a clear explanation of each service’s role and limits.
Design and research · public preview
How it works
Select a part to see its role, the decisions behind it, and what still needs evidence.
01 / Privacy-services product concept
Evaluate private network and DNS services.
VPN and DNS services address different exposures. Provider trust, retained metadata and the device’s other network paths still matter.
02 / Privacy-services product concept
Separate public contact details from personal ones.
Email aliases and masked phone numbers have different recovery, forwarding and identity requirements. They do not create a universal anonymity guarantee.
03 / Privacy-services product concept
Evaluate forwarding and broker-removal services.
Mail forwarding and data-broker removal have operational and identity requirements. The design must state what a provider holds and what can actually be removed.
04 / Privacy-services product concept
Keep accounts, renewal and scope understandable.
The product aims to minimize collected customer data. Partner terms, legal responsibilities and the self-hosted versus reseller boundary still need resolution.
Design principles
Explain what a service protects and which exposures remain.
A privacy dashboard should have a deliberate data boundary.
Resale, affiliate and self-operated models have different responsibilities.
Project status
Product concept. Provider agreements, resale rights, pricing and operating responsibilities remain open. No service signup or checkout is offered here.
Source and project notesThe source repository requires authorized access. This public page contains a curated explanation and original schematic illustrations.