Privacy Policy

Logbook content (only if you use the Logbook)

• • Places you pin, including their names and map coordinates
• • Dive entries: date and time, notes, and optional details such as dive type, depth, bottom time, buddy name, visibility, and water temperature
• • Trips you create and the places you assign to them
• • Photos you attach to a dive, and their captions
• • Share tokens if you choose to publish a trip or place

Why: to provide the Logbook feature you asked for. Lawful basis: performance of our contract with you (Article 6(1)(b)).

Account information

• • Email address and authentication data (held by Clerk)
• • A user identifier that links your account to your Logbook

Why: to create your account, sign you in, and keep your data separate from other users. Lawful basis: performance of our contract.

Billing information

• • Subscription status and billing history (held by Stripe)
• • Payment card details are collected and stored by Stripe, never by us

Why: to take payment and manage subscriptions. Lawful basis: performance of our contract, and legal obligation for tax and accounting records.

Technical and analytics data

• • Server and security logs, which include IP address and browser type
• • Cookieless, aggregated page analytics via Vercel Analytics (no cross-site tracking, no advertising profiles)
• • Your app settings and presets, which are kept in your browser's local storage and not sent to us

Why: to keep the service secure, diagnose faults, and understand which features are used. Lawful basis: our legitimate interests in running a reliable, secure service.

How Logbook photos are stored

Photos you attach to a dive are resized in your browser and then uploaded to private storage (Vercel Blob). They have no public web address by default: every request goes through our server, which checks that you are signed in and that the photo belongs to your account before sending it back. If you turn sharing on for a trip or a place, photos on that share can be loaded by anyone with the link. Deleting a photo, a dive, or your Logbook removes the stored file as well as the database record. Turning sharing off immediately stops the old link from working.

Map tiles and place search

Map images come from OpenStreetMap, so your browser contacts their servers directly and they will see your IP address and the area of the map you are viewing. When you search for a place name, the search text is sent through our server to OpenStreetMap's search service, so your IP address is not shared with them for searches.

Share links you turn on

Sharing is off until you create a link for a trip or a place. Anyone who has that link can see the name, notes, and photos you attached there. We do not list share pages in search results. The link is unguessable, but it is still a public URL: only share it with people you trust, and turn it off when you are done.

Location data you enter

We do not use your device's GPS. Dive locations are only the coordinates of pins that you place on the map yourself.

Where your data is held

Our database is hosted in the European Union. Some of our providers are based in, or support their services from, the United States. Where data is transferred outside the UK or EEA, it is protected by UK approved safeguards such as the International Data Transfer Addendum or Standard Contractual Clauses, or by an adequacy decision.

How long we keep things

• • Logbook content: until you delete it, or until you delete your account
• • Account data: for as long as your account is open
• • Billing records: up to 7 years, to meet UK tax and accounting rules
• • Server logs: a short rolling period for security and troubleshooting
• • Encrypted backups may retain deleted content for up to 30 days before they expire

Essential cookies

Used to keep you signed in and to secure payments. These are required for the service to work and cannot be turned off.

Local storage

Your settings and presets are stored in your browser. You can clear them at any time in your browser settings.

No tracking or advertising cookies

We do not use advertising cookies and do not track you across other websites. Our analytics are cookieless and aggregated.

How we protect your data

• • HTTPS encryption for all traffic
• • Authentication handled by Clerk
• • Every Logbook request, including each photo, is checked against the signed-in account, so users cannot read each other's private entries. Share links are the exception: they only work for the trip or place you chose to publish
• • Payments handled by Stripe; we never see card details

If something goes wrong

No service can promise perfect security. If a breach affects your rights we will notify the ICO within 72 hours where required, and tell affected users without undue delay.

Children

SnapShark is not intended for children under 16. If you believe a child has given us personal data, email us and we will delete it.

Questions or concerns?

Policy updates

We may update this policy as the service changes. If a change materially affects how we use your data, we will update the date at the top of this page and, where appropriate, tell you by email before it takes effect.