How this static website handles visitor information and external links
Privacy notice
How the website handles information
This website is a static professional and research resource. It uses a consent-first approach and is designed to minimise collection of visitor information.
Consent-controlled analytics
The production website uses Google Analytics 4 only after a visitor selects Accept analytics. Analytics storage is denied by default, advertising-related consent remains denied, and no Google tag is requested before acceptance. Consented events are rechecked before transmission and are sent only after the tag has loaded successfully. Analytics remains disabled after rejection, outside the production domain, in local previews, or when Google services fail.
What analytics may measure
When accepted, Analytics may process ordinary page visits, broad referral sources, browser and device categories, approximate location and tightly governed interactions with public research resources. Observatory events use controlled page, metric, zone, filter, support and operational-error categories. Active-Fire Monitor events are limited to application opening, mode or rolling-window changes, a broad historical date-state category, download type, help topic and controlled error category. Searches, exact district names or codes, raw scientific values, full query strings, URL fragments, exception messages, file paths and other arbitrary text are not intentionally transmitted.
Advertising remains disabled
Advertising storage, advertising personalisation, remarketing and Google Signals are disabled in the website configuration. Google Analytics is used only to understand aggregated use of public pages and research resources.
Your privacy choices
The browser stores only the consent decision, the applicable policy version and the decision time. The record is retained for up to 12 months and is requested again after a material policy-version change. Visitors can reject Analytics or change a previous decision at any time through the Privacy choices control in the footer. Withdrawal denies Analytics storage, stops future governed events and makes a best-effort attempt to delete accessible Google Analytics cookies.
Contact links
Email, telephone and WhatsApp links open external applications or services selected by the visitor. Information shared through those services is governed by the relevant provider and by the communication the visitor chooses to initiate. The website does not provide a contact form.
Local mapping, processing and downloads
The Active-Fire Monitor uses locally hosted MapLibre assets and a boundary-only map, so no remote basemap provider is contacted. Filtering, table preparation and map-source preparation occur in the visitor's browser. Filtered CSV and GeoJSON downloads are generated locally in the browser from the current filtered records and are not uploaded to a saved-search service.
Accounts, saved searches and hosting logs
The website has no visitor account system, saved-search database or server-side store for monitor filters. Normal web-server logs may still record requests for security, reliability and service administration. The website does not claim zero logging because server logging is controlled by the hosting environment.
Local scientific processing and external services
Observatory and monitor scientific display calculations are processed locally in the visitor's browser. Optional usage analytics operate only after consent and are not required for any scientific function. Analytics failure does not affect either application. Publishers, ORCID, Google Scholar, ResearchGate, LinkedIn, GitHub, Figshare, Google Analytics and institutional websites apply their own terms.
Compatibility Observatory: the retained, unlinked self-contained Observatory remains analytics-free and processes its embedded analytical data locally.