What is active on the front end
This static build applies visible and invisible controls intended to reduce attack surface and reduce accidental oversharing.
- Strict content security policy in the page.
- No third-party trackers or widget scripts.
- Bounded fields and client-side normalization.
- No HTML rendering from visitor input.
- Anti-bot checks including hidden traps, timing checks, and interaction thresholds.
What is deliberately not on this site
This site is intentionally narrow.
- No CMS.
- No database.
- No plugin ecosystem.
- No web chat widget.
- No live message storage through the page itself.
Why the onward channels are limited
Signal and Proton Mail are the only onward routes in this version. That keeps the interface narrower and avoids mixing the front door with softer public messaging paths.
- Signal is positioned as the primary private route.
- Proton Mail is positioned as the structured written route.
- The page is designed to keep the full note local until you choose otherwise.
What this page does not claim
This page does not claim perfect security, total legal sufficiency, or full operational proof by wording alone.
- Front-end controls matter, but they are not the whole stack.
- Security truth depends on the live environment as deployed.
- This page is written to stay honest about that boundary.
Operational base: England, United Kingdom. This page is written to support transparency, consent, minimization, and user understanding in plain English. It is not legal advice and it does not replace a full legal review of the live operating environment.