Skip to main content

Trust & Safety

Principles page

Trust, privacy and consent are product requirements, not decoration.

Squaddies is a pre-seed concept and visual MVP, so this page sets the public principles for future privacy-by-design, safeguarding, data ownership and Green Zone / Blue Zone separation.

Static preview

Trust model concept

Static principles

Privacy

Data minimisation and purpose clarity

Consent

User choice before future routing

Separation

Green Zone public trust kept apart from Blue Zone concepts

Non-negotiable boundary

No hidden command surveillance.

Emergency boundary: Squaddies is not an emergency service. If someone is in immediate danger, call emergency services or seek urgent local help immediately.

Privacy and consent

Future features must be privacy-led and consent-first.

The current public site does not collect support requests, run AI, process applications or expose dashboards. These principles define how future work should be judged.

Principle

Privacy-by-design

Future product design should minimise data collection, explain purpose clearly and avoid collecting sensitive information without a defined need and user understanding.

Principle

Consent-first approach

Future routing, introductions or evidence-building journeys should be based on clear user choice, transparent context and revocable permission where appropriate.

Principle

Data ownership

Future users should understand what they provide, why it is requested, who can see it and what choices they have before any deeper workflow is built.

Green Zone / Blue Zone separation

Public trust must not become hidden surveillance.

Green Zone is the planned public trust, support and route-finding layer. Blue Zone / Aegis is the future enterprise readiness concept. Personal Green Zone support interactions must not be presented as hidden command surveillance or quietly repurposed for command insight.

Green Zone

Public trust layer

Future public-facing route-finding and community concepts should be safe, consent-led and separate from enterprise readiness ideas.

Blue Zone / Aegis

Synthetic readiness concept

Future command/readiness demos must use synthetic, aggregated, anonymised or permissioned data only. No live operational datasets are used in this stage.

Boundary

No hidden command surveillance

Personal support interactions should not be turned into unconsented command monitoring, welfare scoring or personnel analytics.

Safeguarding boundaries

Clear limits protect users and the project.

Squaddies does not provide medical, clinical, legal, official welfare, crisis counselling or command decision advice. Any future support-related feature must present boundaries before use.

Boundary

Not an emergency service

Immediate danger should be handled by emergency services or urgent local help.

Boundary

Not medical or clinical advice

Future content should not diagnose, treat or replace qualified professional support.

Boundary

Not legal or welfare advice

Squaddies cannot replace official legal, welfare, chain-of-command or benefits guidance.

Boundary

Not command decisioning

Future tools must not make command decisions or present automated decisions as authoritative.

Endorsements

No endorsement claimed or implied

Squaddies does not claim Ministry of Defence, NATO, NHS, government, armed forces or public sector endorsement.

Vanguard

No official selection or certification

Vanguard is a future technical aptitude concept, not an official selection, qualification, certification or assured career route.

Echo

No live AI claim

Echo is a future route-finding assistant concept only. It is not live AI, clinical triage or crisis support.

Aegis

Synthetic data rules

Aegis is a future command/readiness SaaS concept. Early demos must use synthetic data only and must not imply access to real personnel, medical, welfare, command or operational datasets.

Claim-safety principles

Plain language before polished language.

The safest Squaddies copy should state the current stage, avoid fake traction, avoid implied approvals, identify future modules as planned and keep all sensitive support, AI and readiness concepts clearly bounded.

Pre-seed concept Visual MVP Future-facing only Subject to validation and funding

Trust is the foundation for every future module.

Explore the platform direction with clear boundaries around privacy, safeguarding, consent and claims.