Privacy policy

Last updated: 29 August 2026 · applies to seahazards.com

What this site collects

seahazards has no accounts, no sign-up, no comment forms and no newsletter. You can read everything on it without telling us who you are, and we do not build profiles of visitors.

Like almost every website, our servers keep standard request logs — the IP address, the page requested, the time, and the browser's user-agent string. We use them to operate the site, to debug problems and to block abuse, and we delete them on rotation. They are not used for advertising and are not sold or shared.

If you are issued a key for the paid API, we additionally store that key, the contact details it was issued to, and per-key usage counts — the minimum needed to operate and bill the API.

Advertising cookies

This site shows ads served by Google AdSense. Third-party vendors, including Google, use cookies to serve ads based on your prior visits to this website and to other websites. Google's use of advertising cookies enables it and its partners to serve ads to you based on your visits to this site and/or other sites on the internet.

Where the law requires it (for example in the EEA, the UK and Switzerland), a consent message is shown before any personalised advertising cookies are set, and you can decline them.

We run no analytics of our own — no Google Analytics, no tracking pixels. The only cookies on this site come from the advertising described above.

Requests your browser makes to others

The base map is loaded directly by your browser from OpenFreeMap (tiles.openfreemap.org), so that service sees the tile requests — including your IP address — as any web server sees its visitors. All other data on the map (the warnings themselves, weather and wave context) is served from our own servers. Links to external chart catalogues and official sources are ordinary links; nothing is sent to them until you click.

Changes and contact

If this policy changes, the date at the top changes with it. Questions, or a request about data that concerns you: see API access for how to reach us, or About for who runs the site and where its data comes from.