Understand what
stays private.
This describes the technical design. Organization-specific legal and retention details must be completed before public launch.
This website
No advertising, analytics SDKs, tracking pixels, marketing cookies or contact forms are included. Hosting providers may process ordinary request metadata such as IP addresses and access logs. A private hosted preview may require host-managed sign-in.
The local file checker
Files and calculated hashes stay in your browser. The checker does not upload them. You can use the PowerShell instructions instead.
The messaging service
The central server sees accounts, public keys and routing information. Message and document contents are encrypted on client devices. Queued ciphertext follows configured server retention rules; no blanket claim of zero metadata is made.
Exports and backups
Transcripts and exported documents are unencrypted files you choose to create. Protect their storage and transfer. Key backups are encrypted and require their separate password; they do not contain local history.
Before public operation
The operator must publish its legal name, address, privacy contact, applicable lawful bases, retention periods, processors and rights-request procedure. Those details have not been supplied and are not invented here. Use the administrator’s established contact channel during private evaluation.