Dive Command · Privacy Policy
What Dive Command does with your data
Dive Command is a native iOS companion to depthplanner.com, built by DiveRobotix LLC. This page explains — plainly, and completely — what the app collects, where it goes, and what stays on your phone.
| Effective | September 5, 2026 |
|---|---|
| App | Dive Command |
| Bundle ID | com.depthplanner.app |
| Accounts required | None |
| Ads / trackers | None |
| Dive log storage | On your device only |
01 Overview
Dive Command wraps the depthplanner.com dive planner in a native app and adds on-device instruments a website can’t provide: a barometer for altitude correction, GPS tagging, camera access, haptic alerts, local notifications, a Home Screen widget, and an Apple Health write-out for logged dives.
The design principle behind all of it is the same one behind a dive computer: your dive plans and log entries are yours, stored locally, and nothing leaves your device unless a specific feature you use requires it — the AI dive assistant, a public tide lookup, or a Health write you approved.
Dive Command has no user accounts, no login, no advertising SDKs, and no analytics or crash-tracking libraries. There is nothing to sign up for and nothing being profiled.
02 What we collect
Each row below is a category of data the app can touch, the action that triggers it, and where it ends up.
| Data | Collected when | Stored | Shared with |
|---|---|---|---|
| Dive plans & log entries depth, times, buddy, site, notes |
You plan or log a dive | On-device, inside the app | Nobody |
| GPS coordinates | You tag an entry/exit point | Saved with that log entry, on-device | Nobody |
| Photos | You attach one to a log entry | Saved with that log entry, on-device | Nobody |
| Barometric altitude | You tap “Auto-Detect Altitude” | Read once to fill in a field; not logged | Nobody |
| Dive workout, depth & water temp | You save a log entry with Health enabled | Apple Health, on your device (and iCloud if you sync Health) | Apple Health only — write-only, never read back |
| AI dive-assistant chat messages | You send a message to the in-app AI assistant | Not stored by Dive Command after the reply is shown | depthplanner.com (DiveRobotix LLC) |
| Approximate coordinates for tide lookups | You check tide or current predictions | Not stored | NOAA CO-OPS public API |
We do not collect your name, email, device identifiers for advertising, or any data you haven’t directly created by using a specific feature.
03 Third parties
Two outside services are reachable from within the app, both triggered only by your action:
- depthplanner.com AI proxy — powers the optional AI dive-planning assistant. The text you type is sent to DiveRobotix LLC’s server to generate a reply; if you don’t open the assistant, nothing is sent.
- NOAA CO-OPS (tidesandcurrents.noaa.gov) — a free, public U.S. government API used to look up tide station data and predictions. No personal data is required or attached beyond the location needed to find the nearest station.
Neither service is an advertising or analytics network, and neither receives your dive log, photos, or Health data.
04 How it’s used
Everything the app collects exists to run the feature you triggered it for:
- Depth, time, and altitude figures feed the Bühlmann ZHL-16C dive-table calculations you’re viewing.
- GPS and photos are attached to the log entry you’re editing, for your own record.
- Chat messages are sent only to generate the assistant’s reply.
- Health writes let your dives show up alongside other workouts in Apple’s Health app.
None of it is used for advertising, sold to data brokers, or combined into a profile — there’s no account for a profile to attach to.
05 iOS permissions
iOS shows a native prompt the first time each of these is used; the app functions with any of them denied, minus the corresponding feature.
| Permission | Why Dive Command asks |
|---|---|
| Motion & Fitness | Reads the barometer once to auto-detect your altitude for dive-table corrections. |
| Location When In Use | Tags dive entry/exit points and finds the nearest tide station. |
| Camera | Attaches a photo you take to a dive log entry. |
| Photo Library | Attaches an existing photo to a dive log entry. |
| Health — Share (read) | Required by Apple’s App Store review for any HealthKit write access; Dive Command never reads your Health data back. |
| Health — Update (write) | Saves a logged dive as an Underwater Diving workout with depth and water-temperature samples. |
| Notifications | Alerts you when your no-fly window clears or a surface interval completes. |
06 Your choices
- Permissions can be reviewed or revoked any time in Settings → Privacy & Security, or per-app under Settings → Dive Command.
- Dive log data, photos, and GPS tags live on your device. Delete a log entry to delete its data; deleting the app removes everything the app itself stored.
- Health data is managed inside the Health app itself (Browse → Activity → Workouts), since it’s written into Apple’s store, not ours.
- AI assistant conversations aren’t retained by us after a reply is generated — simply don’t use that feature to avoid sending any text.
07 Security
Because dive plans, logs, photos, and GPS tags are stored locally rather than on a server we run, there’s no central database of your dive history for us to secure or for a breach to expose. Network requests to depthplanner.com and NOAA use HTTPS in transit.
08 Children
Dive Command is a technical dive-planning tool and is not directed at children. We do not knowingly collect information from anyone under 13.
09 Changes to this policy
If Dive Command’s data practices change — for example, adding a new native capability — this page will be updated and the effective date above will change accordingly. We won’t change what’s described here to permit broader use of data already collected.
10 Contact
Questions about this policy or a data request can be sent through depthplanner.com/contact-us.