Privacy Policy
Last updated: November 4, 2026
Your dive log and photos stay on your device or in your iCloud. Below receives usage events, crash reports, and information sent by connected features. The full list is at below.app/open.
Information We Access
Location Data
We access your location to automatically detect dive sites when you import dives.
Purpose: Site detection and dive location tagging.
Health Data
We read dive data from Apple Watch including depth and water temperature.
Purpose: Import Apple Watch dive recordings into your dive log.
Bluetooth
We use Bluetooth to connect to dive computers for wireless dive downloads.
Purpose: Import dives from Shearwater, Suunto, Garmin, Oceanic, and other dive computers.
Photo Library
We access your photo library to display photos taken during your dives.
Purpose: Show dive photos in your dive log.
How Your Data Is Stored
On Your Device
Your dive log is stored on your iPhone. Photos stay in your photo library. If you enable iCloud sync, your dives also live in your own iCloud account.
Your iCloud (Optional)
If you enable iCloud sync, your dives sync through your personal iCloud account. We never see this data—it goes directly between your devices.
Our Servers
Below's API receives usage events, a random per-install ID on every request, and information sent by connected features. Share anonymously is off by default. The full list is at below.app/open. Your full dive log is not uploaded.
Anonymous Community Contributions
Share anonymously is off by default. When you turn it on, Below sends observations from dives at catalogue sites to help other divers plan.
For each dive at a catalogue site, Below sends visibility, water temperature, current, surge, sea state, the dive date and time, the site ID, and a random token for that dive. The server keeps the month and year. It also receives your average star rating for each site. Your full dive log, depth profile, photos, notes, and buddy information are not sent by this setting.
Contributions carry no name, account, or email. A device hash and a random token let you update or withdraw them. The hash lets Below group reports from the same device.
Editing a dive sends updated values while sharing is on. Deleting a dive withdraws its contribution, even if you have since turned sharing off. Turning sharing off stops new contributions; it does not remove earlier ones. Contact us to request deletion of records held by Below.
Data Retention
Your dive log stays on your device or in your iCloud. Below and its service providers also keep some information listed at below.app/open. On-device retention:
- Dive logs: Kept until you delete them
- Location breadcrumbs: Automatically deleted after 30 days
- Site cache: Refreshed periodically, no personal data stored
Your Rights
Under GDPR, CCPA, and other privacy regulations, you have the following rights:
Right to Access
Your dive log is visible in the app. Contact us to request access to records held by Below or its service providers.
Right to Delete
Delete dives in the app. Deleting the app removes local data; copies in your iCloud and records already sent to Below or its service providers may remain. Contact us to request deletion of those records.
Right to Portability
Export your dives to UDDF, CSV, or our open JSON format anytime.
Right to Control
Manage permissions in iOS Settings. Revoke any permission at any time.
Contact Us
For privacy questions or concerns, contact us at support@below.app
Changes to This Policy
We may update this policy as the app evolves. Significant changes will be communicated through app updates.
Analytics
This website uses Plausible Analytics, a privacy-first, cookieless analytics service. Plausible does not use cookies, does not collect personal data, and does not track you across websites or devices. No consent banner is required under GDPR, ePrivacy Directive, CCPA, or PECR.
The data collected includes page views, referrers, device type, browser, operating system, and country (derived from your IP address — the IP itself is never stored). We also record anonymous events such as App Store button clicks to understand how visitors interact with the site. All data is aggregated and non-identifiable. Plausible's data policy for full details.
The Below iOS app sends usage events to Below's API. Each event carries a one-way hash of an identifier Apple assigns to Below on your device. Every API request also carries a random ID the app creates on first launch. Some events include a dive site ID; they do not include your name, account, email, or full dive log. The full list is at below.app/open.
Subscription Analytics
Subscription events include trial activation, paywall views, purchases, and renewals. They carry the device hash used for other usage events and a token that ties purchases to those events. Apple also sends Below transaction metadata through App Store server notifications.
Device Usage Profiles
We use a one-way hash of Apple's identifier for Below to group app events from the same device. These records include storefront country, app version, session counts, and feature usage. The hash lets us recognise repeated events from that device; it is not a name or email.
App Store Server Notifications
Apple sends us server-to-server notifications about subscription lifecycle events (renewals, cancellations, billing issues). These notifications contain transaction metadata but no personal user information. We use this data for renewal tracking, churn analysis, and service improvement. No personal data from these notifications is stored or shared.