What is recorded
The analytics system records page views, broad device category, external referrer hostname when the browser supplies one, approximate reading depth and interactions with site features such as search, comparison tools, learning activities and outbound source links. A random session token links events within one browser tab so navigation paths can be understood.
What is not recorded
The analytics dataset does not store raw IP addresses, visitor names, email addresses, advertising identifiers or a persistent visitor ID. The public tracker does not set an analytics cookie, use fingerprinting or record session replay.
The session token is random, stored only in sessionStorage and is not reused as a cross-session identity. It is intended to distinguish a short navigation journey from unrelated events.
Search and activity data
Internal search terms can be recorded so missing information can be identified. Learning activities can record aggregate completion and scores. The biocomputer builder can record the selected architecture categories. These events are used to improve the site and are not tied to a persistent visitor identity.
Retention
First-party analytics event files are retained for up to 180 days. Search Console and hosting infrastructure are separate services and may process data under their own terms.
Browser privacy signals
The first-party tracker does not run when the browser exposes Global Privacy Control or a supported Do Not Track signal. The site administrator can also exclude a browser locally from the analytics dashboard, which is useful when checking deployments.
The About page explains the site’s editorial scope and authorship.