Privacy Policy

Effective August 17, 2026 · Last updated August 17, 2026

MyDiveLogs is an iOS app and website for keeping a scuba diving logbook. It is built and run by Patrick Brown, an individual developer. This policy explains exactly what the app stores, why, where it lives, and how to get it back or get rid of it.

Short version: your logbook is yours. There is no analytics, no advertising, no tracking, and no third-party company receiving your data. The only reason anything leaves your phone is so it can appear on mydivelogs.com and survive a lost device.

1. What we collect

What you enter yourself

• Account — your email address and password. The password is stored only as a salted hash; nobody, including us, can read it back.
• Your name — first and last, as they appear on your certification card.
• Certifications — agency, level, card number and issue date for each certification you hold, plus your chosen card artwork and profile icon.
• Emergency details — the name and phone number of the person you want called. See the note below, because this is somebody else's information.
• Dive records — date, time, site, location, depth, duration, gas and mix, cylinder pressures and size, water temperature, exposure suit, weight, buddy name, your notes, and anything else you type into a dive.
• Trip checklist — which items you have ticked.
• Preferences — units, appearance and similar settings.

What comes in from a dive computer

If you import a dive from a Garmin .fit file or a CSV export, we store whatever that file contains, which can include:

• GPS coordinates of the entry point, and altitude.
• Heart rate — average, maximum, minimum, and a reading at each point in the dive.
• Oxygen and nitrogen exposure — CNS percentage, OTU, and modelled tissue loading.
• The full depth profile — a depth, temperature and cylinder pressure reading every few seconds for the length of the dive.

Heart rate and dive profiles are health-related information, and we treat them as such. The app does not read from or write to Apple Health, and does not request access to it. This data reaches us only inside a file you choose to import.

What the app collects on its own

• Server logs — when your app or browser talks to mydivelogs.com, the web server records the request, the IP address it came from and the browser or app version, as essentially every web server does. These are used for security and debugging and are not combined with your logbook.
• Sessions and sign-in tokens — so you stay signed in.

What we do not collect

• No analytics or usage tracking of any kind.
• No advertising, and no advertising identifiers.
• No tracking of you across other apps or websites. The app contains no third-party SDKs that could do so.
• No access to your camera, microphone, contacts, or your device's location. The app never asks, because it never needs to.
• No access to your photo library. When you choose a photo for your certification card, iOS shows you the picker and hands over only the single image you picked — the app cannot see anything else.

2. About your emergency contact

The emergency contact you enter is another person's name and phone number. Please make sure they are happy for you to record it. Dive Mode displays those details on your own lock screen so that whoever picks up your phone can act — that display is generated on your device from data already there, and turning Dive Mode on does not send anything anywhere. The details are stored on your device and, if you are signed in, in your account on mydivelogs.com, and they are shown to nobody else.

3. Why we hold it

Every item above exists for one reason: to be your logbook, on your phone and on the web, and to still be there if you lose the phone. Specifically:

• To show your dives, statistics and certification card.
• To sync between the iOS app and mydivelogs.com so the same logbook appears in both.
• To calculate the figures the app displays — air consumption, surface interval and similar — from your own dives.
• To let you sign in, and to keep your account secure.
• To reply if you contact support.

Under the GDPR, the legal basis is performance of a contract with you: you asked for a dive logbook and this is the data that makes one. Where you have chosen to provide something optional, such as an emergency contact, the basis is your consent, which you can withdraw at any time by deleting it in the app.

4. Who we share it with

Nobody. Your data is not sold, rented, traded or shared with any third party for any purpose. There are no analytics providers, no advertisers, and no data brokers involved at any point.

Two unavoidable exceptions, stated plainly:

• Hosting. mydivelogs.com runs on servers operated by Hostinger, who necessarily store the data on their hardware in order to host it. They act on our instructions and do not use it for their own purposes.
• Law. If we were compelled by a valid legal process, we would have to comply.

If MyDiveLogs were ever sold or transferred, your data would move with it, and you would be told before that happened.

5. Where it is kept, and for how long

Your logbook is stored on your device and, when you are signed in, on the mydivelogs.com servers hosted by Hostinger. It is kept for as long as your account exists.

There is no automatic expiry, because a dive log is a record you keep for decades. It goes when you decide it goes.

6. Deleting your account

You can delete your account from inside the iOS app, or from the Profile page on mydivelogs.com. It is a real deletion, not a disabled flag, and it happens immediately. It removes:

• Your account and password.
• Your profile, name, certifications and emergency details.
• Every dive, including imported depth profiles, heart rate and computer data.
• Your trip checklist.
• Every sign-in token and session, on every device you were signed in on.
• Any outstanding password reset link.

Nothing is retained afterwards. Deleting the app from your phone without deleting your account leaves the account intact — use the in-app option if you want it gone.

7. Your rights

Wherever you live, you can do all of the following, and most of them without asking us:

• See your data — it is all visible in the app and on the website.
• Export it — App Settings has an export that writes your entire logbook to a CSV file, including the imported depth profiles and computer data. It is a complete copy, not a summary, and it can be read by a spreadsheet or imported back in.
• Correct it — edit anything, any time.
• Delete it — see the section above.
• Object or complain — write to us at the address below. If you are in the EEA or UK you also have the right to complain to your local data protection authority.

If you are in California: we do not sell or share personal information as those terms are defined by the CCPA, and we never have. You will not be treated differently for exercising any right above.

8. Security

• All traffic between the app, the website and the server uses HTTPS.
• Passwords are stored as salted hashes and checked against known-breached password lists when you set them.
• Two-factor authentication is available and can be turned on from the iOS app.
• Sign-in tokens are stored in the iOS Keychain, and are revoked when you change your password or delete your account.

No system is perfectly secure, and it would be dishonest to claim otherwise. If we ever discovered a breach affecting your data, we would tell you.

9. Children

MyDiveLogs is not directed at children under 13 and we do not knowingly collect their information. If you believe a child has created an account, contact us and we will remove it.

10. Changes

If this policy changes in a way that affects what we collect or what we do with it, the date at the top will change and the app will say so. Continuing to use MyDiveLogs after that means you accept the updated policy.

11. Contact

Questions about any of this, or about your own data, go to support@mydivelogs.com. Patrick Brown is the data controller for the purposes of the GDPR.