How divefy uses cookies and similar technologies
Last updated: May 25, 2026
Cookie Policy
This Cookie Policy describes the cookies and similar technologies (including browser local storage) used when you access divefy websites and applications. It should be read together with our Privacy Policy.
Personal data processed through these technologies is explained in our Privacy Policy.
What are cookies and local storage?
Cookies are small text files stored on your device when you visit a site. Local storage (such as localStorage) lets the browser save data on your device without sending it on every request. We use both to operate divefy, remember your choices, and—only after you accept our cookie banner in production—measure aggregated usage.
Categories
We group technologies as follows:
Essential: required for sign-in, security, session continuity, language or theme preferences, and core navigation. These run based on contract performance and legitimate interest; they are not used for advertising profiles.
Analytics (optional): used only after you click Accept on our cookie banner in production, to understand how the platform is used in aggregate (e.g. Google Analytics). You can refuse analytics and still use divefy; essential cookies remain.
First-party cookies (divefy)
__divefy_token_session (session token): stores your Firebase ID token so authenticated API requests work. Duration: aligned with token expiry (often about one hour, refreshed while you stay signed in). Essential.
__divefy_user_session: stores basic session metadata (e.g. display name, email) for the signed-in experience. Duration: session or until logout. Essential.
__divefy_user_profile: stores profile data needed in the UI (e.g. username, contexts). Duration: session or until logout / profile refresh. Essential.
__divefy_user_preference: stores preferences such as language and theme. Duration: typically up to one year. Essential.
__divefy_cookie_consent: records that you accepted analytics cookies on the banner. Duration: up to one year. Essential for honoring your choice.
__divefy_customer_membership (manager/web when applicable): stores the selected operator customer context for the Manager. Duration: session or until context changes. Essential for that app.
First-party cookie names use the __divefy_ prefix. They are typically set on the divefy domain or on a shared parent domain across subdomains (for example, .divefy.me) so your session works as you move between our apps.
Browser local storage (first party)
mantine-color-scheme (localStorage): remembers light/dark/system theme before React hydrates. Duration: until you clear site data or change theme.
current-lang (cookie): remembers interface language when you are not signed in or before preference cookie applies. Duration: session or per browser settings.
Other short-lived keys may be used by the UI framework; they do not track you across unrelated sites.
Third-party cookies and identifiers
When you use divefy, trusted providers may set their own cookies or similar identifiers on your device. We do not control all of these technologies; each provider has its own policy:
Google / Firebase Authentication: sign-in with Google or related flows may set cookies (e.g. on google.com) for authentication and fraud prevention. Required for social login where enabled.
Google Analytics (production, after consent): if you accept our cookie banner, gtag may set cookies such as _ga and _gid to measure traffic in aggregate. You can withdraw consent by clearing the consent cookie and site data, or using browser opt-out tools.
Firebase / Google (messaging & config): push notifications and Firebase SDKs may use storage or identifiers on supported devices. See Google’s privacy documentation.
Sentry: error and performance monitoring may attach session or device identifiers to diagnostic events (minimized data; production).
Cloudflare or similar CDN/WAF: edge security and delivery may use cookies such as __cf_bm for bot protection.
Map and geocoding providers: when maps or address search are shown, the provider may process location queries and set its own cookies if you interact with embedded map widgets.
Cookie banner and analytics consent
On production sites, Google Analytics and related measurement scripts load only after you accept the cookie banner. Essential cookies for login and preferences may be set before acceptance because they are necessary to provide the service. In development environments, analytics may be disabled regardless of the banner.
How to manage cookies
You can block or delete cookies in your browser settings. Clearing divefy cookies will sign you out and reset preferences. To opt out of analytics after accepting, clear site data for divefy or remove the consent cookie and reload the page. For Google Analytics, you may also use Google’s browser add-on or account ad settings where available.
Contact
For questions about this Cookie Policy, contact us through the support channels listed in the app or the contact form on this website.
