Privacy policy

Last updated: 10 November 2026

This is a translation. The Dutch text is the one that is legally binding: read it in Dutch.

Nextdive is an online dive logbook for divers, buddies and clubs. This policy explains which data we keep, why, who can see it and what your rights are. In short: we only keep what your logbook needs, we sell nothing, we show no ads and we use no tracking.

1. Who is responsible?

The data controller is Spectes, Dina Appeldoornlaan 52, 1421 TD Uithoorn (Chamber of Commerce (KvK) no. 42205042), reachable at info@nextdive.app. You can get in touch there with any question about your data. What a club keeps about its members and students we process on behalf of that club; then the club is responsible (see section 3).

2. What data do we keep?

• Account: name, username and a hash of your password (never the password itself), and which version of the terms of use you agreed to and when. If you sign in with Microsoft, Google or Apple, we keep the account ID and email address they pass on to us (with Apple, the address you chose to share, which can be a hidden relay address) and, for Google, the link to your profile photo.
• E-mail: the e-mail address you add (in your profile or when you create an account), once you confirm it via the link we send, and which kinds of e-mail you want. We don't keep the content of the e-mails we send, and don't track whether you open them or click links in them.
• Profile: profile photo (if you upload one or use your Google photo), certifications, the number of dives logged before Nextdive, your visibility setting and display settings.
• Dives: date and time, duration, depth, temperature, gas, tank and pressures, dive site, place and country, dive computer, notes, training details, gear and the buddies you tag. Buddies without a Nextdive account are kept only as the name you type. With Nextdive Pro also the photos you add to a dive (at most five), kept as JPEG without the location and camera data in the file, and visible only to you and the buddies tagged on that dive.
• Dive planner: the plans you save, and that and when you accepted the planner's terms (which version), so we can show that you did.
• Buddies and clubs: your buddy connections, memberships and roles at clubs, sign-ups for group dives, buddy teams, rental gear and whether you are a paying member.
• Courses: when you take a course with a club, your sign-up (name, e-mail address, phone, date of birth if the course has a minimum age, and remarks), whether you're confirmed or on the waiting list, whether you paid, and per lesson your attendance, the skills done and the instructors' notes. If you book a course on the club's own website or in its web shop, the club passes these details on to Nextdive and you get a welcome e-mail with the club's invitation to join it on Nextdive; you don't need an account for the course. For club staff: the lessons and group dives they teach and the times they said they can or can't.
• Clubs that pay Nextdive: the club's billing details, which subscription it took, who agreed to it, when and to which version of the club terms, its invoices, and for each payment its status and, when it failed, the bank's reason. For a club that pays per active member, who was a member on which days, so an invoice can be checked. The club's bank account details go to Mollie, not to Nextdive: we only keep the reference of the direct debit.
• Pro bought in the app: which subscription you took in Google Play or the App Store, until when it runs, whether it renews, and the store's reference for it, so Pro works on every device you sign in on. You pay the store; we never see your payment details.
• Certification cards and documents: the date and number on your certification cards, and if you keep them in Nextdive (Nextdive Pro), the type, dates and number of documents such as first aid or your dive insurance. For a dive medical statement we only keep its dates, never what it says. Clubs see nothing of your documents unless you share one: then their staff see only whether it's valid on the day of a group dive or lesson, never its dates or number. Your dive card's QR code opens a page anyone with the code can see: your name and photo, your certifications without their numbers, and until when the documents you share are valid. It isn't indexed by search engines, and a new code makes the old one stop working.
• Imported files: a file you import (FIT, UDDF, Subsurface, PDF, CSV or zip) is only read. We keep the dive data from it, not the file itself.
• Technical data: a session cookie to keep you signed in, and server logs (including IP address, time and requested page) for security and troubleshooting. When you sign in to the Nextdive app, we keep a hash of its sign-in tokens and the device name, until you sign out or they expire (at most 90 days unused). If you allow notifications in the app, we keep your phone's push token until you sign out or remove the app.
• Security: if you switch on two-step verification, its secret (encrypted) and hashes of your recovery codes; for a passkey only its public key and name; and a security log of sign-ins, failed sign-ins and changes to your sign-in details, which you see under Settings › Security.

We do not ask for health data (such as heart rate), your own payment details or location history.

3. Why, and on what legal basis?

• To provide your logbook, statistics, buddy and club features: performance of the contract (Art. 6(1)(b) GDPR).
• E-mails about your account (confirming your address, resetting your password) and notifications about your own buddies, dives and clubs: performance of the contract. You switch each kind of notification off in your profile or with the link in every such e-mail.
• Nextdive news: your consent (Art. 6(1)(a)). It is off until you switch it on.
• What a club keeps about its members, students and participants (members and roles, group dives and trips, buddy teams, rental, courses and lessons, and what the club's website sends): we process it on behalf of that club. The club decides what it keeps and is responsible for it (the controller); Nextdive is its processor, under the data processing agreement. You can also ask your club about it; requests that reach us we forward.
• Clubs' invoices and payments: performance of the contract with the club and a legal obligation (Art. 6(1)(c)) to keep them.
• Connections with Garmin or Suunto: your consent (Art. 6(1)(a)), which you withdraw at any time by disconnecting.
• Security, preventing abuse and fixing errors (server logs), and names of buddies without an account: legitimate interest (Art. 6(1)(f)). If someone wants their name removed from your logbook, we do so.

4. Who can see your data?

• You see and manage all your data.
• Buddies you tag on a dive see that dive and can copy it to their own logbook. Your profile with statistics and recent dives is visible according to your own setting: everyone, only buddies (default) or nobody.
• Clubs you are a member of see your name, role, sign-ups, buddy team and rental gear, and your certification according to your visibility setting. For a course you take, its staff see your sign-up, attendance and their notes; you see your lessons, not the notes.
• AI summary: an instructor of a course you take can have AI write a summary of your progress for the club's staff. It uses your lessons, attendance, skills and the staff's notes and remarks at that club, and your logged dives only if your profile is visible to that instructor (everyone, or only buddies and you are buddies). Your name isn't sent. The club's staff see the summary; it is kept with your sign-up for the course.
• The administrator can view and manage accounts, only for support and administration.

We never sell or rent out your data and never share it with ad networks or data brokers.

5. Service providers

• Microsoft Azure (hosting, database, photos and logs), in the EU (Sweden). A data processing agreement with Microsoft applies.
• Azure Communication Services (Microsoft) sends our e-mails, with data kept in Europe. It receives your e-mail address, name and the e-mail itself, only to deliver it.
• Microsoft, Google and Apple, only if you sign in with them. Nextdive only receives your account ID, name, email address and (Google) profile photo.
• AI models in Microsoft Azure, only when you use an AI feature such as scanning a paper logbook: the photo you send is processed by an OpenAI model operated by Microsoft (Azure OpenAI) to read the dives, and isn't stored by Nextdive. What is sent may be processed outside the EU; that happens under the EU-US Data Privacy Framework and the European Commission's standard contractual clauses. Nothing is sent unless you start it.
• The same AI models, for the summary of a student that a club's instructor asks for (section 4): what the club recorded about the student and, if visible to that instructor, their dives, without their name, with the same safeguards. Microsoft doesn't use it to train models.
• Google Firebase Cloud Messaging and Apple Push Notification service, only if you allow notifications in the app: they receive your phone's push token and the title and text of each notification, only to deliver it, with the same safeguards for processing outside the EU.
• Mollie (Amsterdam), only for clubs that pay Nextdive: it collects the invoices by direct debit or a payment the owner starts, and receives the club's name, billing e-mail address, the amounts and the bank or payment details the club enters there. Mollie is a licensed payment institution and also processes this under its own responsibility.
• Google Play and the Apple App Store, only if you buy Nextdive Pro in the app: the store sells it to you and handles payment, VAT and refunds under its own responsibility. We receive from it only the state of your subscription and a random code that ties it to your account.
• Have I Been Pwned (Pwned Passwords): when you choose a password, we check whether it appeared in a known data breach by sending only the first 5 characters of a hash of it, never the password itself.
• Open-Meteo: when you type a place for a dive, your browser looks up suggestions at open-meteo.com. Only the typed text goes there, no account data.

6. Connections with Garmin and Suunto

You can choose to connect your Garmin Connect or Suunto account, so new dives land in your logbook automatically. For this:

• The connection is only made when you explicitly give consent on the Garmin or Suunto sign-in page. We never see your password there.
• We only fetch dive activities and keep the same dive data as for a manual import (see section 2). Other activities and health data are not stored.
• We only read. We never send data to Garmin or Suunto.
• Your Garmin or Suunto data, and your account ID there, are used only within Nextdive. We never pass them on to other services, ad networks or data brokers.
• If you disconnect (in Nextdive or at Garmin/Suunto), we stop fetching immediately and delete the access tokens. You choose whether dives imported so far stay in your logbook or are deleted.

Apple Health (iPhone app): when you choose to import from Apple Health and allow it, the app reads only your diving workouts with their depth, water temperature and starting position, on your phone. Only the dives you tick, or with “Add new dives by themselves” switched on the new ones, are sent to Nextdive and kept as a manual import (see section 2). The app never writes to Apple Health, reads no other health data, and never uses Health data for advertising or passes it on. You withdraw access at any time in the iPhone's Settings › Health › Data Access & Devices.

7. How long do we keep data?

As long as your account exists, with these exceptions for courses and clubs:

• Students without an account are removed from a course a year after its last lesson.
• What a club's website sends to Nextdive (orders, form entries) is kept in the club's log for at most 30 days.
• The names behind a club's count of active members go 90 days after that month's invoice was paid; only the days are left.
• What a club keeps stays as long as the club exists. When the owner deletes the club, the club's personal data goes within 30 days.
• Invoices and their payments are kept for seven years, as Dutch tax law requires, also when the club is deleted.

If you delete your account (Settings → Delete account; see how), your account, dives, gear, photo and connections are deleted immediately. Database backups are overwritten within 7 days, server logs after 30 days.

8. Security

All connections use HTTPS. Passwords are hashed with Argon2id and checked against known data breaches, and you can add two-step verification or a passkey. The database is only reachable by the app, and the app uses no database passwords but a managed identity. Access tokens for Garmin and Suunto and secrets for two-step verification are stored encrypted. If a data breach puts you at risk, we report it to the Dutch Data Protection Authority and to you.

9. Cookies

Nextdive only uses functional cookies: a session cookie (at most 30 days) to keep you signed in and, when you sign in with Microsoft or Google, a sign-in cookie from Azure. No analytics or tracking cookies, and so no cookie banner.

10. Your rights

You have the right to access, rectify, erase, restrict, object to and port your data. Much of this you can do yourself: export all your dives as CSV (Settings → Account), change your details and delete your account. For anything else, contact us as in section 1; we reply within a month. If you disagree with how we handle your data, you can lodge a complaint with the Dutch Data Protection Authority or the supervisory authority in your own EU country.

11. Changes

When this policy changes, we update the date at the top. We announce important changes in the app before they take effect. The Dutch text is binding; translations are for convenience.