Cookie Policy.
Access cookies, browser storage and the choices available to you.
Last updated: 29 October 2026.
Cookies and similar storage
This policy explains the cookies and browser storage used by coase.pro. Cookies are small values sent with relevant requests; local storage and session storage keep information in your browser. They are used here for access, security and functionality you request, rather than advertising profiles. For the controller’s identity, providers and your data-protection rights, see the Privacy Policy.
What the site uses
Protected-download access
__Host-coase_access is a first-party technical cookie issued after a successful download-access form submission. It holds a random token, not your name or email, and allows further downloads in the same browser for 30 days. The token is associated with the server-side access record. It is restricted to secure connections and is not accessible to page JavaScript. Blocking or deleting it means that access may need to be requested again.
Session storage: navigation and requested work
coase-enquiry: selected catalogue services and notes used to prepare your enquiry.coase-model-enquiry: your selected model specification and any edits for the contact-page draft.coase-configurator-v1:…: BHAUS configuration answers, selection and review state.coase:selected-work:…andcoase:selected-work:last-page: example filters, search text, view and return-navigation state.
These values are stored on your device for the tab session, subject to your browser’s restoration behaviour. They support the navigation or configuration you use and are not advertising identifiers.
Persistent local storage
coase-appearance: your chosen dashboard appearance.coase.boole.deal.v1: the BOOLE deal/model saved in your browser so that your work can be restored.
These entries have no built-in fixed expiry: they remain until cleared by the tool, your browser or you. They are stored locally and are not automatically uploaded to COASE. On a shared computer, clear saved site data after use if you do not want another user of that browser profile to see your saved work.
Cloudflare security
Cloudflare protects and delivers the site. Depending on the security checks applied to a request, Cloudflare may issue technical security cookies, such as cf_clearance after a challenge or __cf_bm where its bot-management service is used. These are conditional infrastructure cookies, not a statement that every visitor receives them. Their presence and expiry depend on the active security service: Cloudflare documents a 30-minute inactivity expiry for __cf_bm; challenge-clearance duration depends on the configuration. Consult Cloudflare’s cookie documentation for the applicable details.
Why there is no advertising-consent banner
The site does not include advertising or profiling trackers in its current implementation. The access and functional storage described above supports the services you request. A consent banner is not required solely for technical storage; the Italian Data Protection Authority’s cookie guidance explains this distinction. If non-essential tracking is introduced, this policy and the consent mechanism must be updated before that tracking is activated.
How to manage or remove stored data
Use your browser’s privacy/site-data settings to inspect, block or delete cookies and storage for coase.pro. Deleting the access cookie ends remembered download access. Clearing local storage also removes saved model work and preferences, so export anything you need first. Closing a tab normally ends its session storage, although restoring a browser session may restore it. Blocking storage can prevent saved configurations, navigation state or access from working as expected.
Deleting browser data does not erase registration, download or email records already held by COASE. To request their deletion, contact [email protected]. The Privacy Policy explains server-side retention and your rights.