Your curiosity
is not a lead form.
What this project stores, what it does not ask for, and what changes when you follow a link.
No wallet or identity request
The public learning hub does not request wallet connections, signatures, recovery phrases, private keys, government identification, payments or an email address. Practice tools use fictional amounts and fixed examples.
Your browser stores your progress
Bookmarks, completed checkpoints and practice preferences are stored locally under the stonkbuilder.learn.v1 key. These are not encrypted. They are visible to anyone with access to the same browser profile and can disappear when browser data is cleared. You can export or reset this data from Your reading list.
Search stays in the browser
The search index ships with the static site. Searching and filtering are performed locally; no search requests are sent to an external analytics or AI service. On a deployed website the hosting provider may still receive routine request logs, including visited URLs. Do not enter personal or secret information into search.
First-party visitor estimates
The learning site records page views with a small first-party script; no analytics vendor receives these events. The shared HTTPS gateway currently hides visitor network addresses from the learning site, so unique-visitor and country totals are not available and are not guessed. If client-address forwarding is enabled later, the server can use its local country database and a keyed one-way token; the token and country would be retained for up to 30 days, without storing raw addresses in the visitor summary. The script uses session storage to avoid repeating the same page event in one browser tab session and does not set an analytics cookie. Shared networks, mobile carrier address changes, proxies and VPNs can make visitor and country estimates inaccurate. Routine hosting logs may separately retain network addresses under the hosting provider's log policy.
External sites have their own rules
Source and product links open separate websites. This hub does not share its local learning progress with them, and does not control their security, availability, cookies or privacy practices. Referrer behavior is limited by the site's referrer policy.
The private editorial studio is different
The password-protected studio is hosted separately from the public learning pages. It uses HTTPS, an HttpOnly Secure SameSite session cookie, and an in-memory session. Editorial drafts, revisions, and site settings are stored on the site server and are not served as public files. Production releases require human-approved content and replace the current static edition atomically.
Before a real launch
The operator must add their legal identity, contact details, actual hosting and data-retention arrangements, and jurisdiction-appropriate notices. This project page describes the supplied software, not a completed legal compliance review.