Documentation site, not a hosted data service.
The site provides documentation, education, local browser demonstrations, downloads, and links to project resources. It does not offer visitor accounts, a contact form, advertising, or a database for Recovery Decks, keys, plaintext, or protected customer data.
Voided libraries may be integrated into third-party applications. Those applications choose their own architecture, data collection, key custody, servers, and legal terms. This notice does not cover them.
Demo inputs stay in the browser.
Text, generated keys, Recovery Deck examples, derived values, and protected artifacts used in the website labs are processed locally by browser JavaScript and the bundled Rust/WASM runtime. The site does not intentionally transmit those values to a Voided backend. Demo state is ephemeral and is cleared by refresh, navigation, or closing the page, subject to ordinary browser memory behavior.
The page exposes raw values so learners can inspect the complete round trip.
Do not paste real keys, deck order, credentials, customer data, or other secrets into any demo.
Infrastructure still receives a web request.
When a browser requests a page, hosting and delivery infrastructure may process an IP address, user agent, requested path, referring page, timestamps, network and security signals, response status, and transferred byte counts. Those facts are used to deliver the site, cache static files, prevent abuse, diagnose failures, and maintain security.
The site does not embed a first-party analytics SDK, advertising pixel, behavioral profiling script, or marketing tracker. Essential infrastructure may use short-lived security mechanisms when necessary to defend the site.
No sale, advertising, or cross-context targeting.
Voided does not sell visitor personal information, share it for cross-context behavioral advertising, or use it for targeted marketing. Request metadata may be processed by infrastructure providers strictly to host, cache, route, secure, and operate the site, or disclosed when legally required.
Keep operational data narrow.
Voided does not create a visitor profile or application account record. Infrastructure logs and security events, when generated, should be retained only for the period needed for delivery, abuse prevention, incident response, and legal obligations. Access is limited to people and providers that need it to operate or secure the site.
No internet service can promise absolute security. The site minimizes risk by remaining static, avoiding secret submission, and keeping demonstrations local.
Ask privately.
Depending on where you live and which law applies, you may have rights to know, access, correct, delete, restrict, or object to processing of personal information. Because this site has no account or submission form, it may not be possible to connect ordinary request metadata to a named person without enough information to locate the request.
Submit a private advisory labeled Privacy request with the approximate date, time, requested path, and enough non-secret detail to locate the relevant event. Do not include credentials, raw keys, Recovery Deck order, plaintext, or customer data. Identity verification may be required before disclosing or deleting data.
Education without profiles.
The fundamentals material may be useful to learners of many ages, but the site is not directed at collecting information from children and does not knowingly request a child’s name, contact details, account, or secret material. A parent or guardian who believes personal information was collected may use the private request route above.
External links have their own terms.
Links to GitHub and other external resources leave voidednetwork.com. Those services control their own collection, cookies, accounts, privacy notices, and legal terms. A link identifies a relevant resource; it does not extend this website notice to that service.
MIT licensed. No security warranty.
The Voided source code is provided under the MIT License. The license text in the repository controls, including its warranty and liability disclaimer. Documentation and examples explain intended use; they do not certify the complete security, compliance, or legal sufficiency of an integrating application.
Read the license ↗Report security issues privately.
Use a private GitHub Security Advisory for suspected vulnerabilities. Include the affected version, platform, minimal reproduction, and impact. Do not attach real plaintext, raw keys, Recovery Deck order, a derived Recovery Key, stable roots, customer data, or secret environment values.
Open private advisory ↗Material changes update this page.
The effective date at the top changes when this notice materially changes. The current notice remains linked from site navigation. Questions about a public integration belong on Support; privacy and vulnerability matters use the private route.