Cookie choices
This release-candidate website uses browser storage that is necessary to provide core functionality and remember choices such as cookie preferences and demo interface settings. Optional analytics and marketing technologies must not be activated until the visitor has chosen to enable them.
Necessary technologies
These support functions requested by the visitor, security, session or basket functionality, and remembering privacy or interface preferences. Where a technology is strictly necessary for the requested service, consent is not relied upon for setting it.
Known first-party browser storage in this demo
ohi-cookie-preferences-v1 stores the visitor's optional Analytics and Marketing choices and the date on which the preference was saved. It is used so the site can remember the visitor's privacy choice.
ohi-demo-employment-questionnaire stores questionnaire progress locally in the visitor's browser for demonstration purposes only. This demo must not be used with real health information. Production occupational-health data must use the secure authenticated clinical system rather than browser local storage.
Other strictly necessary session, security, basket or interface storage may be introduced as production functions are completed. The final inventory must be generated from the deployed system rather than inferred from design documentation.
Analytics
No production analytics provider is declared by this release-candidate policy. If analytics technologies are introduced, they will be treated as optional unless a specific exemption applies and will not be activated through this site's consent architecture before the required visitor choice has been recorded.
Marketing
No production advertising or remarketing provider is declared by this release-candidate policy. Advertising, remarketing and campaign-measurement technologies are treated as optional and should remain disabled until the visitor enables Marketing in Cookie settings.
Changing your choice
You can reopen Cookie settings from the footer at any time. Rejecting optional technologies should not prevent access to the core public website. A material change to optional tracking may require a fresh choice.
Before production launch
The production policy must be populated from a final cookie and tracking audit, including the actual technology/provider, purpose, first- or third-party status and duration for every cookie or similar technology in use. Third-party scripts must be technically connected to the consent state so they cannot run before the required choice has been made.
Production draft · requires final data-protection review and a deployment-specific cookie audit.