Privacy

Diver Atlas (diveratlas.com) is a read-only dive-site encyclopedia operated by CoreSpaces LLC. We are not a certification agency and we do not sell trips. This page describes how we handle information on the site, in your passport, and through the public API and MCP server.

Your data

You own your diver data.

• Your certification number stays private. The public face of your passport is agency and level, plus centre-verified status when a listed shop attests your card.
• Centre credential checks and verify pages show name, agency, level, and verification status only — never your certification number.
• Read, browse, and research trips without logging in. Contribution (condition reports, ratings, plate edits) requires a free account and centre-verified status; Verified Diver is cert-gated, not a paywall.

What we collect

If you join or log in, we store the account fields needed to run your passport (for example email and display name). We use that email for authentication and service messages tied to your account — not for unsolicited marketing lists, and we do not sell or rent email addresses to third parties.

When you contribute, we store the report, rating, or edit you submit, linked to your account for integrity and attribution on the site. Public condition feeds and the API omit diver names, emails, and user IDs from report payloads.

What we publish

Encyclopedia plates, guides, and centre pages show only fields meant for public trip research. The read-only API and MCP return the same public atlas data: no write surface, no booking, no centre recommendations, and no private centre contact details (such as phone or email) beyond what already appears on public centre pages.

Plate verification is verified or editorial-unverified. Condition reports carry a verification tier and never include certification numbers.

Aggregate use of contributions

We may use contribution data in aggregate — for example reef-health trends, condition summaries, or anonymised statistics shown on plates and The Wall — without exposing your private account fields or certification number.

Cookies and logs

We use session cookies and similar mechanisms so you can stay signed in. Server logs may include IP address, user agent, and request path for security, abuse prevention, and rate limiting on the API (120 requests per minute per IP).

Changes

We may update this policy as the atlas grows. Material changes will be reflected on this page with an updated date.

See also Terms of use and About.