Security

The most important security property of this prototype is structural: there is very little to attack. This page describes that architecture and is explicit about the difference between an architecture and a certification.

Security by architecture

• Local-first: the pilot has no accounts and no application server holding learner data, so there is no central store to breach.
• Data minimisation: only what is needed stays in your browser; the research export is pseudonymous and user-initiated.
• A small, audited dependency surface with no unnecessary runtime dependencies, which keeps the attack surface small.
• Content integrity: research content is content-fingerprinted and frozen, and automated validation/audit gates run on every change.
• No telemetry: the application does not phone home.

What we do NOT claim

An architecture is not an audit. We make no claim to any of the following, because no repository evidence supports them:

• No ISO 27001, SOC 2, or comparable certification; no formal external security audit or penetration test; no bug-bounty programme; no encryption or compliance guarantees.

Responsible disclosure

To be completed before public release If you find a security issue we want to hear about it privately, before any public disclosure. A monitored disclosure contact must be set here before public deployment; until then, report issues through the project repository. We will not fabricate a security inbox that nobody reads.