Privacy · October 1, 2026 · Version 0.1.26
Read freely. Share deliberately.
No advertising trackers, wallet connection or automatic public posting. Learning and a first contribution do not require an account.
When you visit
The site serves static pages and small local scripts. Hosting providers and IPFS gateways may process IP addresses and request logs under their policies. We do not add advertising analytics. External source links take you to independent websites.
Your learning and contribution drafts
Lesson completion is stored in this browser’s local storage. A contribution plan stays in this tab unless you choose to keep it on the device. It contains your chosen path, time and optional note. It is not sent to us. Download it for a copy, use the reset controls to remove it, or clear site data in your browser. Local data is not encrypted against other users of the same browser and is not synchronized between devices.
Optional sign-in
Accounts are being configured and are inactive in this review release. The integration uses Supabase Auth, which can also be self-hosted. Once enabled, an identity provider shares the profile and email you authorize with the account service. The service holds an authentication record; session tokens and the PKCE verifier stay in this tab’s session storage. Provider and hosting operators remain dependencies. We do not request wallet access or repository write permissions through community sign-in.
Sign-in does not enroll you in email marketing or automatically make your profile public. A monitored private privacy contact and tested provider setup are required before registration opens. See account help and deletion instructions.
When you contribute publicly
The proposal link opens a draft on GitHub. You review and submit it yourself. GitHub requires an account to post; issues, comments and pull requests are public. Keep contact details, beneficiary records, identity documents, credentials and wallet secrets out of public posts. GitHub controls its own account and retention policies.
Decentralized copies
Public website copies can be redistributed. Removing a page from one host cannot erase independent mirrors. We do not publish participant records to IPFS or a blockchain. Donation addresses already displayed on the support page are public receiving requests, not personal account profiles.
Corrections and private concerns
Use a public GitHub issue for non-sensitive content corrections. A confidential community reporting address has not yet been published; do not place private information in a public issue. Account registration stays gated until a private contact is configured.
Find a first contribution →