Privacy Template

Privacy Notice

Template privacy notice for a research and data-visualisation web application. Tailor this notice to actual deployment practices and infrastructure before production use.

Research DashboardPrivacy Notice

Document details

Template placeholders should be replaced with organisation-specific details before publication.

Last updated: [Effective Date]
Controller / operator
[Organisation Name]
Privacy contact
[Data Protection Contact]
Contact email
[Contact Email]
Retention policy owner
[Organisation Name]

Overview

This Privacy Notice explains how [Organisation Name] may process information when users access the Air Quality, Weather Forecasting & Research Dashboard. It is a template and must be adapted to reflect actual hosting, logging, analytics, and support arrangements.

Categories of information that may be processed

  • IP address and connection metadata, where this is processed by hosting, CDN, security, or server logs.
  • Browser and device information, such as browser version, operating system, screen size, or language settings.
  • Approximate location inferred from network requests or user-selected country or region.
  • User-selected location, recent searches, and dashboard preferences if you choose to store preference cookies or local browser state.
  • Consent preferences, including whether you accepted, rejected, or customised optional cookies.
  • Application performance information or error logs used to diagnose failures and improve reliability.
  • Analytics information only if analytics is enabled and consent has been granted where required.

Why information may be collected

  • To render dashboard content and respond to requests for air-quality, weather, geography, and research data.
  • To remember optional preferences when you request that the application do so.
  • To secure the service, detect abuse, diagnose incidents, and maintain operational reliability.
  • To understand application performance and usage patterns only where analytics is lawfully enabled.

How information is used

Information may be used to deliver requested pages and APIs, remember consent or settings, protect the service, troubleshoot failures, and improve the quality of the research dashboard. The current application should not be described as collecting marketing profiles or advertising identifiers unless those technologies are actually added.

Retention

Retention periods depend on the category of information, operational need, deployment configuration, and legal obligations. Consent choices may be retained until changed; preference storage may persist until cleared by the user or the browser; operational logs may be retained for a limited security and troubleshooting period defined by [Organisation Name].

Third-party services

Third-party environmental-data providers, hosting providers, observability vendors, and geographic-data providers may receive request metadata where necessary to deliver or secure the service. Examples may include air-quality APIs, meteorological APIs, government monitoring networks, satellite products, open-data portals, and geographic-data providers.

User privacy rights

  • Depending on applicable law, users may have rights of access, correction, deletion, objection, restriction, portability, complaint, or withdrawal of consent.
  • Users can revisit cookie settings at any time from the footer link labelled Cookie Settings.
  • Jurisdiction-specific rights, timelines, and verification requirements should be added by [Organisation Name].

Cookie preferences

Strictly necessary storage is used to remember consent choices and operate essential application functions. Optional preference and analytics storage remains disabled until you grant consent where legally required.

International and provider disclosures

Because the platform aggregates international environmental and geographic information, request flows, provider availability, and data-processing locations may vary by provider and deployment region. Additional country-specific disclosures may be required.

Contact

Privacy questions, rights requests, and complaints should be directed to [Data Protection Contact] at [Contact Email]. Where required, add regional supervisory-authority details and formal complaint channels.

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.