Depth Book: Scuba Dive Log — Privacy Policy
Last updated: 2026-10-05
This privacy policy applies to the mobile app "Depth Book: Scuba Dive Log" for Android:
- Google Play: package com.simonj.divelog, developer "Global Utility App Maker"
The app is developed and operated by Kyu-Hee Jang (Google Play developer name: Global Utility App Maker).
Contact: wkdrb2100@gmail.com
OVERVIEW
Depth Book does not require an account, and we do not sell personal information. It is a manual dive logbook: you type in your dives, dive sites, buddies, gear and certification card photos, and can export or back up your logbook. Your logbook is kept in the app's storage on your device. The app also uses Google services and advertising mediation partners for analytics, crash reporting, remote configuration, and advertising.
PHOTOS, CAMERA AND LOCATION
Photos are optional. "Add photo" (on a dive) and "Add card photo" (for a certification card) open the system photo picker, and only the image you choose is given to the app; the app does not browse the rest of your library. "Take photo" asks for camera permission the first time you tap it. The app saves a copy of the chosen or captured image in its own folder; the copy may include metadata stored in the image file, such as when or where it was taken. Images larger than 8 MB are not added. If you decline camera access, no photo is taken and you can still add photos from the picker or keep logging without them.
Location is optional. On the Sites tab, "I'm here" asks for location permission (while the app is in use only) and reads your current position once to fill the latitude and longitude fields of the site you are editing. The coordinates are stored only if you then save the site. The app does not request background location. If you decline, the fields stay empty and you can type coordinates yourself.
INFORMATION STORED ON YOUR DEVICE
For each dive the app keeps the dive number, date and local time, site, country, buddy, gear, gas, weights, depths, duration, tank pressures and size, water temperature, breathing setup, unit system, notes, attached photos (the app's copy, file name, size and a content checksum) and a drawn sign-off annotation if you add one. The app also keeps the dive sites (name, country, optional coordinates), buddies (name), gear (name, service due date), certification card photos (name and photo), templates you save, your display units and first dive number, and a list of the IDs of records you have deleted (kept so that a restored backup does not bring them back). There is no fixed limit on the number of records.
The app may also store basic operating information such as cached advertising settings and a cached More Apps list. Ad consent choices are stored on your device by Google's consent SDK.
The developer does not run a server that receives your logbook. The app reads developer-controlled advertising settings and a More Apps list from Google Cloud Firestore, but it does not upload your dives, sites, notes or photos. When you open the developer's other apps list, app icons are loaded from the web addresses in that list.
ANALYTICS, CRASH REPORTING, AND ADS
Google Firebase Analytics may process limited app-usage and technical information that the SDK collects automatically, such as app opens and sessions, app version, device type, and app-instance identifiers. The only event the app itself sends is an ad revenue event when an ad earns revenue, with the ad format, value, currency and precision. The app does not put dive details, names, notes, sites, coordinates or photos in analytics events.
Google Firebase Crashlytics may process crash reports and related technical information needed to diagnose app problems.
The app shows ads through Google AdMob: a banner at the bottom of the Log and Stats tabs once you have logged at least one dive, a native ad in the Close dialog, and full-screen ads: an app-open ad that may appear when you return to the app and an interstitial ad that may appear after you save a dive. The app does not start a full-screen ad while the dive editor is open. AdMob may also request ads from the Liftoff (Vungle) and InMobi mediation networks. Google, Liftoff and InMobi may process advertising identifiers and device, app, consent, network, and ad-performance information to provide and measure ads, and may use an IP address to estimate an approximate location. The app's own code does not give the coordinates you save to analytics or ad services; if you have allowed location permission, ad SDKs included in the app may be able to access device location under their own policies.
PERMISSIONS AND ADVERTISING CHOICES
The feature permissions the app may request are the camera and location while in use, each only when you tap the related button as described above. It does not request microphone, contacts, Bluetooth, health data, notifications, or background location, and it does not need storage permission to pick photos. The app also declares the vibration permission, which Android grants at install without a prompt, to give short vibration feedback for some taps and completed actions.
When the app starts, Google's consent message (UMP) is checked before any ad is requested. Where consent is required (for example in the EEA and UK), personalized advertising stays off unless your choice allows it. If the consent check fails, the app does not request ads until it is started again. The logbook works whatever you choose. Where Google requires it, the menu shows "Privacy choices", which reopens the consent message so you can change your advertising choice.
STORAGE AND YOUR CONTROL
You can delete a dive in the dive editor, a site, buddy, gear item or certification card on the Sites tab, and a template with "Delete template". Deleting removes the record from your logbook and, once the change is saved, its data file; when you edit a record, its earlier data file is removed the same way. Photos that are no longer used by any saved record, including photos you added in an editor and then removed or discarded, are deleted from the app's photo folder, usually right away and otherwise the next time the app starts. A photo still used by another record is kept, and if the app has found a damaged record it keeps all photos. If a file cannot be removed at that moment, the app tries again the next time it starts and can read your logbook normally. The list of deleted record IDs is kept. You can also clear the app's storage in Android settings or delete the app. Local data may be included in a Google or device backup depending on your backup settings; uninstalling normally removes the active copy but may not remove an older backup.
Export creates a CSV file (all dive fields, including notes, photo file details and the sign-off drawing data), a UDDF file (a limited summary without buddy, gear, notes or photos), or a PDF: "Whole logbook PDF" makes one file with a section for every dive, and "This dive PDF" in the dive editor makes a file for the dive as currently shown in the editor, including changes you have not saved. PDFs include site, buddy, gear, notes, photo file names and the sign-off drawing, but not the photos themselves. "Verified backup" creates a manifest and part files containing your whole logbook, settings, the deleted-record ID list and your photos. "Export raw record", shown for a record the app cannot read, writes that record's stored text to a file. These files are written to the app's private storage. If an export or backup fails or you cancel it, the app deletes the partial file. If the app is closed or stops while it is still writing a backup, that backup folder can stay incomplete. Each time the app starts and can read your logbook without finding a damaged record, it keeps the five newest export files and the three newest backup folders (an incomplete backup folder counts as one of these) and deletes older ones and unfinished export files; files you create in between stay until such a start, or until you clear the app's storage or delete the app. Sharing or printing only happens when you tap Share file, Share all backup files (which sends the manifest and every backup part together through the Android share sheet) or Print PDF; copies you send or save elsewhere stay there and are not affected by this cleanup. Files you pick for "Restore backup" are copied into the app's cache and are normally deleted once the app has read them.
Because we do not receive your logbook, we cannot delete it for you; the controls above remove it from the app. For questions about data processed by Google, Liftoff or InMobi, or to ask us for help with a privacy request, contact us at the address below.
Data processed by third parties is retained according to their service settings and policies. We use these services under their applicable terms, and we ensure that third-party service providers with whom we share user data provide the same or equal protection of that data as stated in this policy.
- Google Privacy Policy: https://policies.google.com/privacy
- Firebase privacy information: https://firebase.google.com/support/privacy
- Google advertising technologies: https://policies.google.com/technologies/ads
- Liftoff Privacy Policy: https://liftoff.io/privacy-policy/
- InMobi Privacy Policy: https://www.inmobi.com/privacy-policy
SECURITY
Your logbook, photos, exports and backups are kept in the app's private storage on your device, which the operating system protects from other apps; they are not separately encrypted by the app, and backup files are protected by an integrity checksum, not encryption. Protect your device with a screen lock, and take care where you share backups, which contain your photos and notes. Apart from the limited analytics events described above, the app does not upload your saved data. Communication between the app and Google services and the ad mediation partners uses encrypted connections (HTTPS/TLS). No method of storage or transmission is completely secure, but we limit what the app collects to what is described in this policy.
IMPORTANT NOTICE
Depth Book is a manual logbook. It does not connect to a dive computer and does not plan dives or calculate decompression or no-decompression limits. Gas consumption figures (SAC and RMV) are rough estimates based on the values you enter and must not be used for dive planning. The drawn sign-off annotation is a drawing only; the app does not verify identity, signatures or certifications. Always dive within your training and follow your dive computer, tables and dive professional.
CHILDREN
The app is not directed to children under 13, and we do not knowingly collect personal information from children.
CHANGES
We may update this policy if the app or its services change. The date above shows the latest revision.
CONTACT
Kyu-Hee Jang (Google Play developer: Global Utility App Maker)
Email: wkdrb2100@gmail.com