Cookie & Browser Storage Policy
Last updated October 8, 2026
Operator: Homeroom Assistant · Missouri, USA
The public website, fictional demo, and signed-in classroom service have different storage needs. This page explains common browser mechanisms and what clearing them can and cannot do.
Browser mechanisms and purposes
Browser storage is not limited to cookies. The signed-in service may use the mechanisms below for the described functions when a feature or browser supports them. Exact contents vary with the feature and device.
| Mechanism | How it may be used |
|---|---|
| HTTP cookies | A website or service may set small values that a browser sends with matching requests. Cookie use depends on the site and provider configuration; this policy does not assign a particular cookie purpose or lifetime. |
| localStorage | The signed-in app keeps selected display preferences between visits. Its authentication client also persists sessions in browser storage; the app source does not specify that storage backend. |
| sessionStorage | The signed-in app keeps a Teacher’s Desk navigation preference for the current browser tab. |
| Authentication session storage | The signed-in authentication client persists sessions and refreshes tokens. The configured SDK storage adapter determines where that session data is stored. |
| IndexedDB and offline queues | The app stores Teacher’s Desk documents, assets, and recovery copies in IndexedDB. Supported offline workflows also keep structured records or queued changes on the device; trusted-browser keys are stored there for device-security functions. |
| Teacher’s Desk cache and recovery | IndexedDB can preserve documents, media assets, annotations, and recovery copies so workspace changes remain available after an interruption. |
| Cache Storage and PWA files | When the offline-capable PWA build is enabled, its service worker caches the application shell files needed to load the app. |
| Optional external media | Displaying an externally hosted image, video, or document may contact its host automatically to load the media, including when a teacher places it on a shared screen. External links can also send a request to their provider. |
| Session memory and HTTP cache | Temporary page memory supports the running page. A browser’s ordinary HTTP cache may keep requested files for reuse. |
| Downloaded files and printed copies | Saved outside the website’s browser storage and managed by the person or organization holding the device or copy. |
Public website and fictional demo
The public website serves informational pages. Its interactive demonstration uses fictional classroom data and temporary page memory; it is not connected to a real classroom in those flows. A change in the demo is not a signed-in record. Do not enter real student or private classroom information in it.
Signed-in classroom service
The signed-in app can store information in the browser to support authentication, offline classroom work, queued updates, Teacher’s Desk recovery, and trusted-browser functions. Some copies may remain on a device until the device reconnects or its local storage is cleared. An offline device cannot receive a remote erase instruction while disconnected.
The Privacy Policy explains our retention schedule. Browser copies and server records have separate deletion paths.
Clearing browser data
Your browser may let you clear cookies, site data, cached files, or offline application data for an origin. Clearing may remove unsynced work, queued changes, recovery data, or trusted-browser keys and may require signing in or setting up the device again. Check that work has synchronized before clearing storage when possible.
Clearing or signing out does not itself delete server records, server backups, support records, or files downloaded or printed outside the browser. It may not clear the separate app origin if you cleared only the public website origin. A server deletion does not instantly erase a disconnected browser copy.
External media and files
When you choose to open externally hosted media or a third-party link, the provider may receive a request and apply its own practices. Homeroom Assistant does not control an independent provider’s storage or notice. Downloaded, printed, or exported copies are handled by whoever holds them.
Storage requirements and consent obligations depend on the service, feature, and applicable law. This page does not make a blanket cookie-free or consent-compliance claim. For questions, contact privacy@homeroomassistant.com.