Privacy Policy — Abys Dive Planner
Version of October 27, 2026. Applies to the Abys Dive Planner mobile app (Android and iOS) and to its web version, which only reads the configuration file (section 7): no account and no purchase on the web. The French version is the reference text.
In short
- Abys works without an account. Your dive plans, settings and gas library stay on your device, with or without an account.
- No analytics, no advertising, no trackers, no install identifier.
- At launch, the app reads a configuration file, without any identifier (section 7).
- Everything else leaves only if you decide so: a bug report, the end-of-beta survey, and an optional account opened with Apple or Google — your sign-in identity and your subscription status, never your plans (section 8).
- A subscription is paid to Apple or Google. They inform our server of every transaction, without your identity (section 9).
- When you share a plan (QR code, PDF), you choose the recipient; nothing goes through an Abys server.
1. Who is responsible
The data controller is David Jury, developer of Abys Dive Planner. Contact for any question or request about your data: contact@abysdive.app.
2. What stays on your device
The app stores locally, in the device's storage, what it needs to work:
- your dive plans, their variants and their backup copies;
- your planning settings (gradient factors, gas consumption, ascent and descent rates, altitude, alert thresholds, gas prices…), your settings profiles, your gas and cylinder library;
- your preferences (units, language, display) and the app's state (intro seen, last "what's new" version, acceptance of the CCR and gas-blending warnings);
- the state of your Abys Pro access (trial, subscription, Founder status), so that it works offline, and the last value read from the configuration file (section 7);
- if you sign in: your account session and a "this device has signed in" marker (section 8).
Your plans, settings and preferences are never sent to the developer or to anyone else, whether you have an account or not. The developer has no access to them. To erase them, clear the app's data in your device settings, or uninstall the app.
3. Device permissions
All are optional: the app works without them; the related feature is simply unavailable.
| Permission | What it is for | What leaves the device |
|---|---|---|
| Camera | Reading the QR code of a shared plan | Nothing: the image is decoded on the device, neither kept nor sent |
| Photos | Picking an image that contains a QR code | Nothing: same on-device processing |
| Location | Estimating the altitude of the dive site when the device's barometer is unavailable | Nothing: only the altitude is used; coordinates are neither kept nor sent |
4. When you share a plan
- QR code: the plan is encoded into the image on the device. Scanning also decodes on the device. No server is involved.
- PDF: the document is created on the device, then handed to your system's share sheet; you choose the app and the recipient. What happens next is up to the app you chose.
5. Bug reports and suggestions
When: only if you tap "Report a bug / suggest a feature" in the settings, or "Report this problem" on the error screen.
How: the app opens a Google Forms form in an in-app browser. Before opening it, the app shows you the technical details that would help reproduce the problem, and asks whether you want to attach them:
- the app version and build number;
- the operating system (Android or iOS) and its version;
- the app language;
- from the error screen only: the technical description of the error (at most 600 characters), which contains no plan and no setting.
If you choose to attach them, they pre-fill the form and reach Google as soon as it opens, even if you do not submit it. If you choose not to, the form opens empty and nothing is sent until you submit. Either way, anything you type into the form (including an e-mail address if you give one) is added.
Why: to understand and fix defects in the app, and to receive your suggestions (the developer's legitimate interest in providing a reliable tool, at your request).
How long: responses are kept while the issue is handled, and for at most 24 months.
6. End-of-beta survey
If you choose to answer it (it is never required to use the app), a Google Forms form collects:
- the e-mail address you provide;
- your answers (how you dive, what you liked, what is missing, how you use the app, your view on pricing);
- whether you agree for your answers to be quoted without your name.
Why:
- to grant you the Founder status promised in exchange (lifetime access to the Pro version), and to find you when it is time to activate it — this is the performance of that commitment;
- to improve the app from your answers (legitimate interest).
Your address is used for that only: it is never sold, never shared for advertising, and never used to send you advertising.
How long: the address is kept as long as your Founder status exists; the survey answers for at most 24 months after the end of the beta.
7. The configuration file
When: when the app starts, then now and then when you come back to it (at most once an hour after a successful read).
What: the app reads a small file, hosted by Google (Firebase Hosting), that tells it which features are open — accounts, for example. The request carries no identifier: no account, no cookie, no device identifier. As with any web page, the host sees the IP address of your connection and the kind of system making it. The file receives nothing else, and Abys keeps nothing from these reads. The web version of the app reads the same file, in the same way.
Why: to open a feature to everyone without waiting for a new version of the app, and to be able to close it again if something goes wrong (legitimate interest).
8. Your account (optional)
When: only if you choose to sign in ("Sign in" in Settings > Account, or from a feature that needs it, such as "I'm a Founder"). An account is never needed to use the free version. It is used to get Abys Pro back on your other devices and to activate the Founder status.
As long as you have never signed in, the account component is not even loaded: the app sends nothing to our servers.
How: you sign in with Apple or with Google. The sign-in itself happens on their side, under their policies. Your Abys account is then created by Firebase Authentication, a Google service acting for us as a processor. On Android, signing in with Apple goes through an Apple page opened in the browser; the answer from that page passes through our server, which hands it to the app without keeping any of it.
What we record:
- your sign-in identity: an internal identifier, the provider (Apple or Google), your account's identifier at that provider, the e-mail address it passes on to us, and the dates the account was created and last signed in. With Apple, we ask for the e-mail address only — Apple's relay address if you choose to hide yours; your name is not requested. With Google, Google also passes on your Google account's name and profile picture. Abys neither reads nor uses them, and erases them from your account's profile as soon as it is created; Firebase Authentication nevertheless keeps a copy attached to your account, which Google updates at each sign-in and which is deleted with the account;
- if you sign in with Apple, a refresh token issued by Apple. It is used for one thing only: asking Apple to revoke Abys's connection to your Apple ID when you delete your account;
- the state of your Abys Pro access: subscription (store, expiry date, auto-renewal on or off) or Founder status;
- your Founder status claim, if you make one: the e-mail address you enter (the one from the end-of-beta survey), its state (pending, granted, not found) and its dates. We match it, by hand, against the list of survey answers (section 6);
- the purchases attached to your account (section 9);
- the times of your latest requests to the server, to limit abuse.
What we never record: your plans, your settings, your library, your location.
While you are signed in, the app reloads your session at launch and renews it with Firebase Authentication.
Why: to provide the service you ask for (getting Abys Pro back on your devices), to keep the Founder commitment, and to allow the revocation of the Apple connection, which Apple requires.
How long: until you delete your account. Signing out does not delete the account.
Deleting your account:
- in the app: Settings > Account > "Delete my account". Deletion is immediate; it needs an internet connection;
- without the app: the page https://abysdive.app/suppression-compte explains how, or write to contact@abysdive.app; we delete the account and confirm it within one month at most.
What is then erased: your sign-in identity, the state of your Pro access, your Founder claim, the Apple token and the usage limits. We ask Apple to revoke the connection; if Apple does not answer, the token is erased anyway, and you can remove the authorisation yourself in your Apple ID settings ("Sign in with Apple"). Your purchases are detached from your account: they are no longer attached to any account, and can attach to a new one.
What stays: your plans, on your device; your subscription, which Apple or Google keeps billing until you cancel it in your store; your end-of-beta survey answers, if any (section 6); our servers' technical logs (section 10).
9. Subscription and purchases
Payment is made to Apple (App Store) or Google (Google Play), under their terms. We never see your payment details.
Without an account, the app checks your purchase with the store, on the device, and sends nothing to our servers. The stores, however, inform our server of every transaction of the app (purchase, renewal, refund, expiry): transaction identifiers, the product, dates, and at Apple the store's country and the price — never your name or your address. A purchase made without an account is recorded without an account; it will attach to the first account you sign in with.
With an account, at the time of purchase the app gives the store an identifier derived from your account, which reveals neither your name nor your address. It then sends our server the store's proof of purchase, which we verify with Apple or Google before attaching the purchase to your account.
What we record for each purchase: the store, the product, whether it is a real or a test purchase, the expiry date, auto-renewal on or off, its state (active, expired, refunded or revoked, pending), the date it was last checked, and the account it is attached to, if any. We also keep the log of the stores' notifications, as they arrive.
Why: to give you the Pro access you paid for, on your devices (performance of the contract); to take renewals and refunds into account even when you do not open the app (legitimate interest).
How long: each purchase, while the subscription runs, then 24 months after its last expiry; the notification log, 24 months.
10. Who receives this data
- The developer, alone.
- Google, as a processor: Google Forms and Google Sheets for the forms and their responses (sections 5 and 6); Firebase for the configuration file, accounts, the state of Pro access and purchases (sections 7 to 9). The account registry's data and our server functions are hosted in the European Union (Belgium). Firebase Authentication is a global Google service, and Google may process data outside the European Union; such transfers rely on the mechanisms provided by the GDPR (EU–US Data Privacy Framework and standard contractual clauses).
- Our servers' technical logs (an account's internal identifier, a request's IP address, never an e-mail address or any content) are used for security and diagnosis; they are erased automatically after 30 days.
- Apple and Google process, under their own policies, the data related to downloading the app, to signing in with their account and to payments in their stores. Abys has no access to it beyond what this policy describes and the aggregated statistics they provide.
No data is sold, rented or shared for advertising.
11. Your rights
Under the GDPR, you may request access to your data, its rectification, its erasure, the restriction of its processing, object to it, and obtain its portability. Write to contact@abysdive.app; you will get an answer within one month. Your account can also be deleted directly in the app (section 8).
These rights cover the data described in sections 5 to 9. The data in section 2 is held only by you, on your device.
You may also lodge a complaint with the French data protection authority, the CNIL (www.cnil.fr), or with the authority of your country of residence.
12. Children
Accounts and the bug-report and end-of-beta forms are not intended for people under 15. If you believe a minor has sent us data, write to us and it will be deleted.
13. Changes
This policy may change with the app. Each version is dated; any significant change is announced in the app before it applies.