Catalogue · your records
Reference data
The catalogue this desk plans from comes down from a shared database. Everything you log stays in this browser. Those are separate directions and neither one requires signing in to anything.
Catalogue
What this desk is running
236
Waters
25
Species
23
Agency links
Running on the catalogue compiled into this build. No database is configured, so nothing is fetched and nothing is sent — the desk is complete as it stands.
Your records
On this device, and nowhere else
Nothing logged on this device yet. Trips, debriefs, sessions, journal notes and presets are written to this browser's storage and are never uploaded. Clearing site data or switching browsers loses them — so the export below is how a record moves to a new phone, and the import beside it is how it arrives.
Room on this device
What your record is taking up
A browser gives one site a fixed amount of room, and when it runs out a write does not fail loudly — it throws, and until recently this desk caught that and said nothing, so a day logged on a full phone looked saved and was not. This is the accounting, so a full device is something you find out here rather than on the water.
What never leaves this device
The short list
- Everything you log. Trips, debriefs, on-water sessions, journal notes and presets are read and written locally; there is no upload path in this build.
- Exact coordinates. There is no latitude or longitude column anywhere in the schema, and decimal coordinate pairs are stripped out of notes before they are stored — that is the notation a phone copies, and it is what the check actually covers.
- Anything from the instruments you have not confirmed. Confirmation still happens per trip, on this device.
- Device preferences (11 keys), including your theme, language and selected water.
The one direction traffic moves is down: the desk reads the shared waters, species and agency tables. It has no write access to them and no account to write as.