Trust

What we can claim today.

Dated statuses instead of adjectives. If something is not reviewed, certified or built, this page says so — that is more useful to you than a badge.

Security and compliance posture

Last reviewed November 3, 2026.

Security reviewIn development

Three internal passes in 2026. February: the Rust core, Tauri configuration, dependencies and frontend (32 findings). August: every Alexandria repository, including the credential layer and plugin system — every finding fixed or accepted with written reasoning. A further August pass into code the first two skipped left a few items open, each written down.

Independent auditPlanned

Not yet commissioned. The credential vault, identity system and integrity layer are the areas we would want reviewed first.

FERPAIn development

Readiness work in progress. Not certified, and nobody has assessed us against it.

GDPRIn development

The architecture helps — personal data stays on the learner’s device — but a deployment still needs its own assessment. No DPA is published yet.

AccessibilityPlanned

No formal WCAG audit has been done. The interface needs design work generally, and this is part of it.

Service levelsPlanned

None offered. There is no managed service to attach them to yet.

Where the data is

Where learner data lives
On the learner’s device, in an encrypted SQLite database. Not on our servers, because there are no servers holding it.
What relays see
Relays help peers find each other and pass along encrypted bytes they cannot read. They carry no authority over what passes through them, anyone can run one, and a deployment can use its own.
What this website collects
An email address if you join the waiting list or send an inquiry, plus the role and platforms you pick. Analytics are cookieless and carry no personal identifiers.
Credential verification
Runs in your browser. A credential you check on this site is never uploaded — there is nowhere for it to go.

The full policy for this website is on the privacy page. The implementation is described on the technology page.

Reporting something

Security findings go to admin@alexandria.ifftu.dev. We would rather hear it from you than read about it later, and we will credit you unless you ask us not to.

Alpha · waiting list

Join the waiting list

We are letting people in one group at a time while the alpha settles. Tell us who you are and what you’d run it on, and we’ll email you when it’s your turn.

This joins the waiting list, not the alpha — we’ll email you when it’s your turn.