Private records. Clear limits.
This page describes the software behavior. It does not replace the responsible institution’s own privacy and retention policy. Confirm that institution before submitting real information.
What the application stores
The category, optional general area and date, description, optional contact email, and any follow-up reference are stored with an internal ID, status and timestamps. Private review notes are retained with the reviewer account and time. Descriptions, contact details, reference fields and notes are encrypted in the database using the application key. This is not end-to-end encryption: the application can decrypt records for authorized reviewers. Infrastructure administrators who control the key and database can also access the data.
Where records do not appear
Private reports are separate from public pages, search, sitemaps and the general contact inbox. This feature exposes no report API, AI/MCP integration, email notification, public status lookup or file upload. Submission pages tell search engines not to index them; this instruction alone is not an access-control guarantee. No account is required to submit. This does not promise network anonymity: hosting, proxy or security logs may retain connection metadata. Avoid unnecessary identifying details.
Retention and operator responsibility
The feature does not automatically delete records, export them or forward them elsewhere. Turning intake off stops new submissions while retaining existing records for authorized review. The operator must establish its retention, access and response policies before real use; no retention duration is promised here.