Cookie Preferences

Cookies are small text files stored on your device to remember preferences, keep sessions secure, and—if you allow—measure anonymous usage. They cannot run programs or deliver viruses by themselves. This page explains what we set, why, and how to control them.

Questions about cookies go to [email protected] with subject “Cookie inquiry.” Include your browser and approximate dates of activity so we can trace logs responsibly without over-collecting identifiers.

Essential cookies load without consent because the site cannot function otherwise. Analytics cookies load only after you accept via the banner. Declining optional cookies does not block navigation or enrollment forms beyond what technically requires a session token.

You may revisit preferences by clearing site data or contacting us to reset server-side flags tied to your account, if any. Browser vendors publish instructions for blocking third-party cookies; follow those guides for device-level control.

We use strictly necessary cookies for security and load balancing, functional cookies for UI state such as dismissed banners, and optional analytics cookies for aggregated traffic. We do not set advertising retargeting pixels on this property.

Embedded conferencing or document links may set their own cookies when you click through. Their policies govern those experiences. We minimize embeds and prefer outbound links where feasible.

Representative entries: session_id (necessary, session, first-party), csrf_token (necessary, session, first-party), analytics_optin (functional, 12 months, first-party), traffic_sample (optional analytics, 6 months, first-party). Exact names may rotate with deployments; purposes remain equivalent.

Chrome, Edge, Firefox, and Safari each expose settings to block or delete cookies. Blocking all cookies may break login flows. Use per-site exceptions if you need tight control while preserving access to enrollment portals.

Disabling essential cookies may prevent forms from submitting or may log you out frequently. Disabling optional analytics only affects our ability to see aggregate navigation patterns; it does not change pricing or eligibility.

When we add a materially new optional category, we refresh this page and may prompt you to reconfirm analytics consent. Essential changes for security may deploy without notice but will remain proportionate.

If your district manages browsers centrally, their policy may override local controls. Provide this page to IT teams so they can whitelist necessary endpoints for enrollment and live sessions.

We store minimal records showing consent timestamps to demonstrate accountability. Logs exclude marketing fluff and are accessible on request where law allows.