Cookie Policy
Template cookie and browser-storage policy for the research dashboard. Update this page to match your real deployment, vendors, and consent requirements.
Document details
Template placeholders should be replaced with organisation-specific details before publication.
- Consent version
- 1.0
- Cookie settings link
- Available in the footer
- Marketing technologies
- Disabled / Not used
- Jurisdiction review
- [Jurisdiction]
What this policy covers
This policy explains how the dashboard uses cookies, local storage, and similar browser technologies. The current implementation distinguishes necessary, preferences, analytics, and marketing consent and does not combine them into a single mandatory agreement.
Strictly necessary
These technologies are always active where technically required and cannot be turned off through the preference dialog.
- Security, fraud prevention, and core application integrity.
- Session or state handling needed for the application to operate.
- Remembering cookie-consent choices and essential application state.
Preferences
Preference storage remains disabled until you opt in.
- Theme or display preferences where offered.
- Map preferences, selected pollutant, selected weather variable, country, unit system, or language preferences.
- User-selected location or recent in-app searches if [Organisation Name] chooses to store them locally.
Analytics
Analytics must remain disabled until consent is granted where legally required. Optional analytics or tracking code should not load before that consent is available.
- Page views, feature usage, and dashboard interactions.
- Performance measurements, error reporting, and aggregated product-improvement metrics.
Marketing
Marketing cookies are disabled and not used by the current application. If marketing technologies are introduced later, they should remain off until separately consented to where required.
Consent behaviour
- Before consent: necessary enabled, preferences disabled, analytics disabled, marketing disabled.
- After Accept all: necessary enabled, preferences enabled, analytics enabled, marketing enabled only if actually used.
- After Reject optional: necessary enabled, preferences disabled, analytics disabled, marketing disabled.
How to manage consent
On first visit, the dashboard presents a consent banner with equally accessible Accept all, Reject optional, and Manage preferences actions. Users can reopen Cookie Settings at any time from the footer to review or change their choices.
Do not load optional services before consent
Optional analytics or marketing services should not execute before the relevant consent is granted. Hiding a tracking interface while still loading tracking code is not sufficient.
Retention and expiry
Retention periods depend on the storage item and purpose. Necessary consent records may remain until updated, while optional preferences may remain until you withdraw consent, clear browser storage, or the application removes them.
Contact
Questions about this Cookie Policy should be sent to [Contact Email]. Add any jurisdiction-specific contact or complaint details required by law.
Legal review
This content is a professional template, not legal advice.
Review governing-law, controller, retention, provider, and contact language with qualified counsel before relying on this material in production.
Where local law requires consent records, processor disclosures, or region-specific rights, add those provisions directly to the relevant pages.