Anonymity is a responsibility.
Choosing a tip platform means deciding who to trust with information someone may have taken a risk to share. You deserve to understand how that information is handled. TypVault is in beta, and its security work continues as the software develops. Explore the architecture and its supporting evidence in our security documentation.
Every claim traces to a test
Every promise TypVault publishes about itself is written as a test that runs against the software on every change. If the behavior drifts, the test fails and the promise comes down. The full list, in plain language and with the count of tests behind each one, is at typvault.info.
The promise of anonymity
TypVault’s intake asks for no name, and the platform stores no IP address, device signature, or browser fingerprint.
What continuity looks like
TypVault is designed for separate program deployments, each with its own database and encryption keys. The current beta includes an export of a program’s operational records in standard formats. The design assumes any single organization can fail, including this one, and aims to keep each program’s footing independent of the others.
Report a vulnerability
If you find a weakness in the platform or this site, write to security@typvault.org. A person reads every report. Tell us what you found, how to reproduce it, and how to reach you if you want a reply.
We will acknowledge your report, keep you updated while we fix what you found, and credit you if you want credit. We ask for reasonable time to fix the issue before public disclosure. There is no bounty program.
A security.txt file at the standard location on this site carries the same address.