Document history

This page is updated by admin team. Please send feedback and reports if you see anything unclear/invalid.

No verifiable previous revision is available from the current data source: Notion’s API doesn’t expose a page’s edit history to this integration. Shown below is the current published version — the only version this page can genuinely display.

Technology and infrastructure

Published version Aug 29

Open-source developmentPrivacy engineeringSystems administrationBackup & recoveryData governanceDigital accessibility

Summary

Version 0.1 is a responsive public website built on maintainable infrastructure and limited external services. Its technical priorities are privacy, transparency, reliability, security, and free and open-source technology where suitable.

Application

The website implements the journeys defined in Version 0.1 scope. The Figma release file defines the interface and behaviour without prescribing a particular programming language or framework.

Infrastructure

The deployment targets Hetzner infrastructure with HTTPS, controlled access, backups, monitoring, error reporting, and documented recovery. Deployment should be reproducible and containerised where useful.

Technology choices

Free and open-source technology is preferred when it is suitable and maintainable. Proprietary services may be used for regulated or operational functions when their role is documented.

Integrations

Notion supplies approved documentation and treasury publication data. Stripe processes donations. Wise supplies banking data. Self-hosted Plausible provides website analytics. Credentials remain server-side and every integration receives only the permissions it requires.

Security

Secrets must not enter the public repository or browser. Administrative access requires strong authentication, controlled ownership, recorded changes, maintained dependencies, and a recovery process.

Analytics and consent

Plausible is used only to understand website use and performance. Analytics must not be used to infer sensitive characteristics, political views, or future participant profiles.

Analytics begins only after a clear choice. Declining or closing the request records refusal and does not restrict the website. The stored consent record should contain only what is needed to remember the choice and allow it to be changed or withdrawn.

Any change to the provider, hosting, data collected, or purpose must be reflected in the consent interface before the new processing begins. The governing principles are defined in Privacy.

Ownership and handover

The association should control the repository, infrastructure, domains, integrations, and production accounts. Handover documentation must cover deployment, configuration, backups, recovery, monitoring, and third-party dependencies.

Interface source

The reference interface is the version 0.1 release design.