[ DATA — Practical data notice ]
Know what gets saved
This page describes the features implemented in this application. It is not a blanket claim about infrastructure providers or the privacy policies of external sites.
Reading list and lesson progress
An anonymous, HTTP-only browser cookie identifies your reading profile. The database stores a hash of that identifier, saved article or lesson keys and timestamps. No account or cross-device synchronization is provided. Use the reading-list page to clear all saved items and lesson progress. Clearing cookies alone can make the old anonymous profile inaccessible without deleting its stored rows.
Tool recommendations
A randomly generated browser identifier is stored in local storage. The database stores that identifier, the selected tool and the vote time. Counts represent submitted browser recommendations, not verified people or product ratings. The server prevents duplicate votes for the same browser identifier and tool.
Newsletter interest
Submitting the form stores the email address, optional name, source label and registration time in this application's database. Automated email dispatch and confirmation are not configured. This form does not send an email or subscribe you to a third-party mailing platform.
Lab calculators and worksheets
Calculator inputs are sent to this server for deterministic arithmetic and are not written to the application database. Do not submit secrets or raw customer content. Worksheet edits remain in the browser tab until you copy or download them. No external model inference is performed by the Lab.
External links and infrastructure
Official source links open other websites whose policies and cookies are their own. The hosting platform may maintain infrastructure and access logs outside the application database. This page does not assert that those logs are disabled.
Scope and retention
This build does not provide a full account-management, consent-management or production retention program. Before a public production launch, the operator should define contact details, deletion procedures and retention periods appropriate to its jurisdiction and hosting configuration.