We keep this document short: it describes the kinds of storage you might encounter while skimming our static files versus loading framed experiences from partners.
First-party essentials
Our HTML bundle may rely on browser cache alone. We do not run a bespoke login, so there is no first-party credential cookie from us.
Preference hints
If your browser remembers form fields or accessibility zoom levels, that happens locally on your device and is not transmitted as part of a loyalty profile we maintain.
Third-party frames
Embedded publishers may drop their own identifiers to keep audio engines stable or resume a paused tutorial. Review their policies if you need enterprise-grade blocking rules.
Managing storage
Use your browser’s site-settings panel to clear data per hostname, or launch a private window when you want a blank slate before trying a demo route.