Draft legal document
Cookie notice
A draft, implementation-aligned explanation of cookies and similar technologies on the Portal Page website.
Document status
Version: Working draft, 10 August 2026
This document was generated as a responsible starting structure for Portal Page. It requires review by qualified Australian legal and privacy professionals, alignment with the actual product architecture and customer agreements, and approval by the company before publication.
Current website behaviour
The default website generated in this repository does not intentionally set analytics, advertising, personalisation or preference cookies. It contains no Google Analytics, Meta Pixel, session replay or behavioural advertising scripts.
The mobile navigation uses temporary page state and does not store a cookie or browser-storage identifier. The static website therefore does not display a consent banner by default.
Hosting and connected services
A production host or security layer may set strictly necessary cookies or process equivalent technical identifiers. The owner must test the deployed website and update this notice with the actual names, purposes, providers and durations.
The contact page creates a draft using the visitor’s email application rather than an external form endpoint. That email application and provider apply their own privacy, cookie and service terms. A link to another site does not set that site’s cookies until a visitor follows it.
Future analytics
If Portal Page later chooses analytics, it should begin with a defined measurement need and evaluate a privacy-respecting, proportionate approach. Any non-essential cookies or similar tracking must not be activated before legal review, notice updates and an appropriate consent mechanism where required.
Adding a script through a tag manager can change the accuracy of this page. Changes should follow a controlled review rather than ad hoc insertion.
Checking and contact
Before every production release, scan the deployed site, inspect response headers and review third-party requests. Insert a verified privacy contact before launch so visitors can ask about the result.