Confidentiality requires practical controls.

Restricted review

The application is designed for invite-only investigator accounts, authenticator verification and role-based database permissions. Private routes are not indexed or cached. There is no public case directory.

The reference and secret status code are required together for status lookup. Status responses do not include descriptions, contacts, wallets, evidence or investigator notes.

Evidence is disabled pending verification

Attachments enter private quarantine with a server-computed SHA-256 integrity hash. They remain unavailable until scanning passes. Investigator downloads require MFA and case access, verify the stored hash and record an audit event. No public attachment URLs or inline previews are issued.

Protect your information

Never share a private key, recovery phrase, password, OTP or wallet backup. Do not submit identity documents by default. Redact unrelated personal information from a separate copy while preserving originals.

Use a device and network you trust. Hosting providers, network operators and security systems may process limited technical metadata. Pseudonymous reporting is not a guarantee of anonymity.

No external AI processing or advertising tracking

The application does not send reports or evidence to external AI services. Reporting and status pages have no advertising pixels or behavioural analytics. Optional anti-abuse checks process technical information through the configured security provider.

Responsible vulnerability reporting

Use the security channel listed on the contact page. Provide a minimal reproducible description using fictional data. Do not download other people’s records or include real evidence in a vulnerability report.

A release requires independent security testing. The implementation has not been certified or independently audited by virtue of being available here.