DiverCity Privacy Policy

Last updated 5 October 2026. Applies to version 1.1.0 and later.

Who to contact

DiverCity is published by DeepCode Studio, France. For any question about this policy or about your data, write to deepcodestudio242@gmail.com.

What the app stores on your device

Everything you enter is saved in the app's private storage on your phone.

Your dives: date, site, depth, duration, temperature, air, weight, suit, notes
The buddies you name on a dive
Photographs and club stamps you add
Your gear, its service history, receipts and manuals
Photographs of your certification cards, and your insurance details
Optional profile fields: name, date of birth, certification number, emergency contact, blood group. Any of them can be left empty
A GPS position, only if you press the locate button, saved on the dive you are logging
When you photograph a dive computer with the camera inside the app, where the phone is at that moment. It is used on the phone to suggest the known dive sites nearest to you, and is never sent anywhere

What leaves your phone, and when

Your logbook lives on your phone and needs no connection. Three things can leave it, and each one only when you do something.

1. Reading a page of a paper logbook, or the screen of a dive computer

When you photograph a page, or the screens of your dive computer, and press Read, the app sends:

the photograph of the page, or of the computer's screens (up to four), with the photograph of the dive brief if you added one, and
a reader ID: a random number the app draws once, shown on the reader screen and under Me, Readings, used to count your credits. It is not your phone's or Google's identifier and says nothing about who you are.

Nothing else goes with them: not your logbook, not your name, not your position, not where the picture was taken.

The photograph goes to DiverCity's server, run on Netlify, which passes it to Anthropic's Claude to be read and hands the result back to your phone.

Our server deletes the photograph when the reading starts, and the reading as soon as your phone receives it. Anything your phone never comes back for is deleted within one hour.
Anthropic processes the page on our behalf, deletes it within 30 days, and does not use it to train its models (Anthropic's retention policy).
What our server keeps: for each reader ID, how many credits it has used, so that each reading is counted once. And, for one day, how many pages were read from each network address and how many of them showed no dive, stored as a one-way digest that cannot be turned back into the address. If you buy credits on Google Play: the credits your reader ID has left, and a one-way digest of the purchase so it is counted once. Google handles the payment; we never see your card or your Google account. No photograph, no text read from a page.

A logbook page can carry other people's names and signatures, such as a dive master's stamp. They are read for you, shown only on your phone, and not kept anywhere else.

Netlify (United States) hosts the server and, like any host, sees your network address when your phone calls it. Anthropic is also based in the United States. Both act on our behalf and only to read the page you asked us to read.

2. Lakes and rivers on the map

When you explore a map close in and your phone is online, the app downloads map tiles from OpenFreeMap to draw the lakes and rivers there. OpenFreeMap sees which area of the map is being shown and your network address. Nothing from your logbook is sent. Offline, the map simply shows no lakes.

3. Sharing a dive

When you share a dive or a trip, the dive itself is written into the link, after the #. Browsers never send that part of an address to any server, ours included. The link goes only where you send it.

Backing up your logbook

So that a lost phone does not mean a lost logbook, the app writes a copy of your logbook and lets Android place it in your own Google account backup, the account already signed in on your phone. On a new device, the app finds that copy and puts your logbook back. The backup is handled by Android and governed by Google's privacy policy. You can switch it off at any time in your phone's Android settings.

Your dive photographs are not included: they are large, the Android backup has a size limit, and your phone's gallery already holds them. After a restore your dives are all there and their photographs are empty. Use Export if you want to keep everything.

There is no automatic backup in the browser version, including on iPhone. Use Export from time to time.

Permissions

Permission	What it does	When you are asked
Camera	Photograph a dive, a club stamp or a certification card	When you tap the camera
Internet	Read a logbook page you chose to read, and draw lakes on a map explored online	Granted by Android at install. The app uses it for nothing else
Location, precise or approximate	Place a new dive site on the map	Only when you press the locate button. Never in the background

Choosing a photograph you already took needs no permission: Android's own photo picker hands the app only the one you pick. Refusing the camera or location leaves the app working, with that one feature unavailable. You can withdraw them at any time in your phone's settings.

Advertising and analytics

This version contains no advertising, no analytics and no tracking. If a future version introduces any, this page will say so before that version is published.

Getting your data out, or deleting it

Take it with you. Export produces your entire logbook as UDDF, CSV and PDF, plus your photographs as a zip.
Change it. Every field in the app is editable.
Delete it. Uninstalling the app, or clearing its data in your phone's settings, removes everything on your phone permanently.
The reader's count. To have the credit count of your reader ID deleted from our server, write to us with the ID shown on the reader screen. Pages and readings need no request: they are already gone within the hour.

If you have a question or a complaint about how your data is handled, write to the address above. In France you may also contact the CNIL, www.cnil.fr.

Deleting your data from DiverCity

DiverCity, by DeepCode Studio, keeps your logbook on your phone only. To delete it, uninstall the app or clear its data in your phone's settings: nothing of your logbook is kept anywhere else by us.

The only thing our server keeps about you is the credit count of your reader ID, if you have used the logbook reader. To have it deleted:

In DiverCity, open the paper logbook reader (the + button, then Photo of a paper logbook) and copy the READER ID shown at the bottom of the screen.
Send it by e-mail to deepcodestudio242@gmail.com with the subject "DiverCity data deletion".
We delete that count within 30 days and confirm by reply.

What is deleted without any request: the photographs you send to be read and their readings, within one hour on our server and within 30 days at Anthropic; the count of pages read from each network address, the day after. Nothing is kept beyond these periods.

Children

DiverCity is intended for adults and is not directed at children.

Changes to this policy

Any change is published on this page with a new date.