Session cookie
The configured session cookie keeps requests associated with your browser session, including form state and signed-in access. Its name and lifetime are deployment settings; the default lifetime is 120 minutes. Session storage and browser-close behavior depend on the operator’s configuration.
CSRF and remembered sign-in
Laravel may set XSRF-TOKEN for request-forgery protection. If you choose remembered sign-in, an authentication recaller cookie can preserve that choice. These serve authentication and security rather than advertising.
Preferences and notifications
The signed-in push feature uses the acadflow_push_account local-storage key to reconcile a device with the current account. A browser push subscription is created only after you enable it and grant permission; the server stores the endpoint and delivery keys. Disable it from Notification Preferences or your browser settings.
Offline caches and local data
When PWA/offline features are enabled, a service worker can cache application assets and supported responses, and IndexedDB can hold supported pending offline actions. This public marketing layout does not register a service worker. On shared devices, sign out and use browser site-data controls where appropriate.
Managing storage
Browser controls let you block or clear cookies, local storage, cached data and notification permissions. Clearing necessary storage may sign you out, reset preferences or remove unsynchronized offline actions. Keep any important unsent work before clearing site data.
Analytics and consent
This public website adds no optional tracking tools and does not display a misleading “accept all” banner for essential storage alone. The wider application can record server-side usage and discovery events as described in the Privacy Policy. Any future optional tracking needs its own assessment and appropriate controls.
A question about what this means for you?
The platform team can clarify the arrangements for this installation and your institution.
Get in touch ↗