- Legal
- Cookie Policy
Cookie Policy.
Cookies, browser storage and the choices available to you.
Last updated: 17 November 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 security and for 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
No access or login cookie
COASE does not set a cookie of its own. Requesting an example report does not open a session: the request is recorded on our server as described in the Privacy Policy, and the report, if approved, is sent to you by email.
Session storage: navigation and requested work
coase-enquiryandcoase-model-enquiry: the service, model or configuration you were looking at when you opened the contact page, used to prepare your enquiry draft.coase-configurator-v1:…: BHAUS configuration answers, selection and review 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-mandate29-v1: services, scope choices and mandate context entered in the engagement configurator, so that you can resume. They are not sent anywhere unless you submit an enquiry.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 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. Clearing local storage removes saved model work and configurator choices, 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 or navigation state from working as expected.
Deleting browser data does not erase report requests or email records already held by COASE. To request their deletion, contact [email protected]. The Privacy Policy explains server-side retention and your rights.