Cookie Notice

This Notice covers cookies, local storage and similar technologies used by Diving.Management, Diving.Software and Diving.Voyage. Cookies are small identifiers stored or read by a browser. Similar technologies may store session state or measure interactions.

The Platform may use necessary technologies to authenticate users, maintain secure sessions, prevent cross-site request forgery, preserve essential checkout state, remember consent choices, balance traffic and prevent fraud or abuse. Google reCAPTCHA may process device, network and interaction signals on protected public forms. Stripe may set necessary payment, authentication and fraud-prevention technologies on its hosted or embedded payment surfaces.

These technologies are required to provide the service or security and are not switched off by an optional-cookie control. Users can block them in browser settings, but login, booking or payment may fail.

No optional analytics, advertising, retargeting or cross-site profiling technology may be activated until it is listed in the live cookie table and, where required, the user has made an affirmative choice. Rejecting optional technologies must be as easy as accepting them. Consent must be granular by purpose, recorded and withdrawable without affecting necessary service.

Before publication, an automated or manual deployment audit must populate a live table with: cookie/technology name, provider, domain, purpose, category, first/third party, duration and access to third countries. The table must reflect the production deployment, not development assumptions.

At minimum, the audit must cover the Platform session cookie, CSRF token/storage, consent preference, Stripe payment technologies and Google reCAPTCHA. A provider's broad policy link does not replace the specific table.

Users can open “Cookie settings” from every public page, change optional choices and withdraw consent. Withdrawal prevents future optional use and does not invalidate prior lawful processing. Browser controls may delete or block technologies; provider controls may also apply.

We update this Notice and live table when technologies or purposes change. A new optional purpose requires a new choice where law requires it; it is not silently enabled from an older consent.