Skip to main content

Cookie Policy

Last Updated: November 8, 2026

This Cookie Policy explains how Dive Connect, LLC ("DiveConnect," "we," "us") uses cookies and similar technologies on the Diveconnect.io website and our mobile apps. It should be read together with our Privacy Policy.

1. What Are Cookies?

Cookies are small text files placed on your device when you visit a website. We also use related technologies such as browser local storage, software development kits (SDKs) in our mobile apps, and pixels or tags. We refer to all of these as "cookies" in this policy. Cookies can be "session" cookies (deleted when you close your browser) or "persistent" cookies (which remain until they expire or you delete them), and they can be set by us ("first-party") or by a third party we use ("third-party").

2. How We Use Cookies

We use cookies to keep you signed in, to keep the Platform secure, to remember your preferences, and — with your consent — to understand usage and measure marketing. We group cookies into three categories:

A. Strictly necessary (always on)

These are required to operate the Platform and cannot be switched off. They include:

Cookie / technologyPurposeType
Supabase auth sessionKeeps you signed in and authenticates requestsFirst-party, session/persistent
dc_cookie_consent_v1Remembers your cookie choices so we don't ask againFirst-party (local storage), persistent
NEXT_LOCALERemembers your language preferenceFirst-party, persistent (1 year)
DC_CURRENCY, DC_UNITSRemember your display currency and units (metric or imperial)First-party, persistent (1 year)
Security / fraud-prevention (incl. Stripe)Protects against fraud and abuse during checkout and sign-inFirst- & third-party
Error & performance monitoring (Sentry)Detects crashes and errors so we can keep the Service secure and reliable. This runs on a legitimate-interest basis and is not used for advertising or cross-site tracking.First- & third-party

B. Analytics (consent required)

These help us understand how the Platform is used — which pages and listings are viewed and how features perform — so we can improve them. They are only set after you consent, and include:

  • PostHog — product analytics (including clicks, repeated or unresponsive clicks, and JavaScript errors) and session replay, to see how features are used and where people get stuck. Form inputs are always masked in replays, and page text is masked on account pages such as messages, bookings, profile, and checkout.
  • Sentry Session Replay — a masked recording of page interactions (all text, form inputs, and media hidden) for a sample of visits and for visits where an error occurs, so we can see what led to a problem.
  • Vercel Web Analytics & Speed Insights — privacy-friendly traffic and page-performance measurement.

Anonymous page count. Until you make a choice, we count page views without cookies: the page address without its query string and the domain of the site that sent you. Nothing is stored on your device, no identifier is kept between visits, and no replay runs. It stops if you reject or if your browser sends Do Not Track or Global Privacy Control.

C. Marketing & third-party embeds (consent required)

These are used to personalize content and to measure the effectiveness of marketing campaigns. They are only set after you consent. This category also covers third-party embeds that set their provider's own cookies — in particular Google Maps, which displays interactive maps and location search. To further minimize data sharing, our maps load only after you explicitly click to load them.

3. Your Choices & How to Control Cookies

Consent banner. When you first visit, our cookie banner lets you "Accept all," "Reject" non-essential cookies, or open "Settings" to choose Analytics and Marketing individually. Non-essential cookies are disabled until you consent, and your choice is saved so we don't ask again. You can reopen the banner at any time from the "Cookie preferences" link in the footer to change your preferences.

Browser & device controls. Most browsers let you block or delete cookies through their settings. Blocking strictly necessary cookies may cause parts of the Platform to stop working.

Do Not Track. Because there is no common industry standard for "Do Not Track" signals, we do not currently respond to them; our consent banner is the primary way to control non-essential cookies.

4. Third-Party Cookies

Some cookies are set by the third-party providers we use to operate the Platform — for example Stripe (payments and fraud prevention) and Sentry (error monitoring), which run as essential; and, only after you consent, PostHog and Vercel (analytics) and Google Maps (interactive maps). Those providers process data under their own privacy terms. The vendors we rely on are listed in our Privacy Policy.

5. Mobile Apps

The DiveConnect mobile apps do not use browser cookies. They store your sign-in session and settings on your device, send crash diagnostics to Sentry, and contain no advertising SDK; they do not track you across other companies' apps or websites and do not use your device's advertising identifier.

The apps include optional PostHog usage analytics that is off until you opt in, either with "Allow analytics" on the first-run privacy screen or in Settings → Privacy → Usage analytics. You can turn it off again there at any time. When on, it records screen names, app open and background, a few product events (search length but never the text, listing viewed, booking started or completed), and crash and error events, linked to your account user ID. It does not record your screen, use the advertising identifier, or derive location from your IP address, and the IP address is discarded. See our Privacy Policy for details.

6. Changes to This Policy

We may update this Cookie Policy from time to time. We will post the updated version here and revise the "Last Updated" date above.

7. Contact

Questions about this policy? Contact us at privacy@diveconnect.io.