Trust / Security & responsible access

Trust needs boundaries that work.

Role-based access, careful handling and accountable review are part of the planned platform architecture.

Pre-launch edition · 3 min read · Updated October 2026
The idea, in focus

The public information website and the future member platform have different responsibilities. This site does not ask for private case evidence, identity documents or payment details.

On this page
01

Current website behaviour

Public content, downloads and a local search index explain the project. An email composer opens your email application. There is no active member dashboard or verification form on this site.

02

Planned access model

The planned model connects access to a live role, geographic scope, service wing, sensitivity and purpose. An ended appointment should remove its associated authority.

03

Sensitive information

Private case evidence is intended for trained handlers with a service need. Professional and institutional referrals should use a defined, limited information packet.

04

Security before service release

The proposed platform requires security review, appropriate authentication, protected records, incident handling and tested recovery before relevant services open.

05

Report a concern

Use the contact address with the subject Website security concern. Describe the affected page and issue without sending credentials, accessing other people’s information or disrupting a service.

A practical example / Planned experience

A role change ends its access

01

The starting point

An officer leaves a community role.

02

How the parts connect

The planned process ends the mandate, reassigns open work and removes the permissions connected to that role.

03

What useful progress means

A continuing personal membership does not preserve former officer authority.

Explore the connected pathway

Find your way.

Search the community, services, wings and practical questions.

Esc to closeExplore all pages →