Policies

Privacy

Draft policy based on platform requirements. The Platform Owner must review and replace it with final copy before launch.

Contact details are private. They are encrypted at rest and absent from application logs and public APIs.

A supplied phone number is normalized where possible, encrypted for private recovery, and indexed with a keyed hash for one purpose only: duplicate reduction. Phone possession is not verified in the first release.

A visitor may supply another person's phone number. Duplicate reduction is therefore an abuse control, not identity proof.

Display-name, phone, and email values are stripped automatically from any draft saved for the browser session. These fields are never written to local storage, session storage, IndexedDB, URL parameters, or history state.

Contact data is kept separate across the local, staging, and production environments and is managed through migrations and backups that are part of the release process.