ZHL16

Privacy Policy

Last updated 25 October 2026 · Applies to zhl16.com and the ZHL16 decompression planner.

You can use the planner without an account and without giving us anything that identifies you. An account is optional, and it exists to store your dive logs and certifications and to sync them between devices. This page says exactly what is collected, why, who else sees it, how long it is kept, and how to get it removed.

1. Who is responsible

The data controller is the operator of ZHL16, reachable at support@zhl16.com. That address handles privacy requests as well as ordinary support.

2. The short version

3. What we collect

Account and sign-in

You sign in with Google, GitHub or Microsoft. From the provider we receive an account identifier, your email address, your display name and (for GitHub and Google) an avatar URL. We do not receive or store your password. What each provider shares is governed by its own privacy policy.

StoredExample
Account id, email and whether the provider verified ityou@example.com
Display name, public handle, avatar@deep-diver
Linked providers and the account id they gave usgoogle, github, microsoft
Profile details you choose to addbio, home location, visibility

Dive logs and certifications

This is the content of the service, and it is detailed by nature:

GPS coordinates and certification numbers are the most sensitive fields here. Both are optional, and a dive marked private is visible only to you and your mutual buddies.

Social graph

Who you follow, who follows you, and the mutual connections that make a “buddy”. Buddy connections are created by following, or by exchanging a short-lived QR code in person.

Payments

Subscriptions and the lifetime purchase are processed by Stripe. We receive a customer id, a subscription id, the plan, its status and the current billing period. We never see or store your card number. Stripe's own privacy policy covers the payment details you give it, and we keep invoice records as tax law requires.

Technical data

DataWhy
Session record: creation time, expiry, browser user-agent, IP at sign-inKeep you signed in, and let you and us spot a session that is not yours
Last activity: timestamp, IP address and country of the most recent authenticated requestSecurity (detecting abuse) and internal product analytics — how many accounts are still in use
Request metadata handled by our host, including IP addressDelivering the site, and protecting it from attacks
Google Analytics identifiers — only if you accept analyticsUnderstanding which pages are used

Last-activity IP and country are recorded at most once every five minutes per session. They are never returned by the API and are not shown on any profile.

What we do not collect

No advertising identifiers, no cross-site tracking, no profiling for marketing, no special-category data (health, biometric) is requested. Note that a dive log can imply things about your health and fitness; that is your content, and you decide who sees it.

4. What other people can see

This is the part worth reading twice.

SettingWho can see it
Profile is public (default)Anyone with the link: name, handle, avatar, bio, home location, member since, aggregate statistics, public certifications, public dives, and how many buddies you have
A dive is public (default)Anyone with the link to your profile: date, site, depth, duration, temperature, and its depth chart
A dive is privateYou, and your mutual buddies while your profile is private
Profile is privateOnly you and your mutual buddies see dives and certifications; everyone else sees your name, avatar and statistics
LeaderboardPublic accounts only, aggregated from public dives and certifications
Diver searchSigned-in users only

Deleting an account does not delete copies that other people or search engines already made, or content another diver posted about you (for example, tagging you on their dive).

5. Cookies and local storage

Two cookies, both first-party and both required for the service to work. Neither is used for tracking.

NamePurposeLifetime
dp_sidYour signed-in session. Opaque random id; no profile data inside it. HttpOnly, Secure, SameSite=Lax.30 days
dp_oauth_stateBinds a sign-in attempt to the browser that started it, so a link captured by someone else cannot sign you into their account.10 minutes

Preferences live in your browser's local storage, not in cookies:

KeyWhat it holds
decoPlanner.theme, dp.locale, deco_unit_prefsYour theme, language and unit preferences
decoPlanner.state, decoPlanner.chartOpts, decoPlanner.expandedDive, decoPlanner.expandedResult, decoPlanner.advancedOpenThe plan you are editing and your planner layout
zhl.consentYour cookie choice, so we do not ask again

Analytics is optional and off by default. If you accept, Google Analytics sets its own cookies (_ga, _ga_*). You can change your mind at any time with Cookie settings in the site footer, which turns analytics off and removes its cookies.

Clearing site data in your browser removes all of the above and signs you out.

6. Why we use it, and our legal bases

Where the GDPR applies, we rely on:

We do not make decisions about you by automated means, and we do not profile you for marketing.

7. Who we share it with

We do not sell your personal data. It is shared only with the processors that run the service:

ProcessorWhat it handles
CloudflareHosting for the site and API, the database, and file storage. Request metadata (including IP address) passes through its network.
StripePayment processing and subscription billing
Google, GitHub, MicrosoftOnly when you choose to sign in with them; they authenticate you and return your identity to us
Google AnalyticsOnly if you accept analytics
OpenStreetMap NominatimReverse geocoding: when a dive has coordinates and no place name, the rounded coordinates (about 1 km) are sent to look up a place like “Ras Mohammed, Egypt”. No account id, email or name is sent, and the answer is cached so repeated dives at one site do not ask again.

We may also disclose data where the law requires it, or to establish or defend a legal claim. If the service is ever transferred to another operator, your data may transfer with it, subject to this policy.

8. International transfers

Our processors operate globally, so your data may be stored or processed outside your country, including in the United States. Where personal data leaves the EEA or the UK, transfers rely on the European Commission's Standard Contractual Clauses or an equivalent safeguard offered by the processor. You can ask us for details of the safeguard that applies to a given processor.

9. How long we keep it

Your account and its content are kept while your account exists. Specific periods:

DataRetention
Account, dive logs, certifications, buddy connectionsUntil you delete them, or delete your account
Uploaded UDDF filesUntil you delete the dive or your account. Files are stored by content fingerprint, so if another account uploaded an identical file, that shared copy stays until they delete it too.
Sessions30 days, or until sign-out or account deletion
Sign-in attempts that were abandoned10 minutes
Place-name cache for coordinatesUp to 1 year; holds no user identifier
Idempotency records for retried writes24 hours
Payment and invoice recordsAs long as tax and accounting law requires, held by Stripe and by us
BackupsA deleted record may persist in encrypted backups for up to 30 days before it is overwritten

Deleting your account (profile settings → Delete account) cancels any live subscription, removes your avatar and uploaded files from storage, and deletes your user record. Everything that hangs off it — session, saved certifications, dive logs, buddy connections and tags — is deleted with it.

10. Your rights

Where the GDPR or similar law applies, you can:

Write to support@zhl16.com. We answer within 30 days, and we may need to verify that the account is yours before acting on a request.

11. Security

Everything travels over TLS, and HTTP/3 where your network supports it. Sessions use opaque random identifiers in HttpOnly, Secure cookies, so signing out revokes access immediately. Sign-in states are single-use and bound to the browser that started them. Access to data is scoped per account on the server, not trusted from the browser. Credentials for third-party services are stored as encrypted secrets.

No system is perfect. If you find a vulnerability, please tell support@zhl16.com before disclosing it publicly, and give us a reasonable chance to fix it.

12. Children

The service is not directed at children. You must be at least 16 to create an account. If we learn that an account belongs to someone younger, we will delete it.

13. Changes

If this policy changes in a way that matters, we will announce it in the app, and for signed-in readers by email where we have one, before the change takes effect. The date at the top is the date of the current version.

14. Contact

Privacy questions and requests: support@zhl16.com.

You can also complain to your national data protection authority. In the EU, that is the authority in the country where you live or work.