The short version
Key Biscayne Guide uses your email address only for the emails you request. There are two separate lists. Signing up for one list does not add you to the other.
Condition alerts email you when a condition you chose matches: a Florida Department of Health beach advisory change, a sargassum outlook change, a kite-wind window, weekend low-tide timing, or the Monday tide forecast. These send only when they match, except the Monday forecast, which is weekly.
The Key Biscayne Daily is a short morning email about the water, getting around, what's on, and around the island, with a brief sponsor line. It is sent each morning by default. After you confirm, you can switch to every other day. Every Daily email includes an unsubscribe link that takes effect immediately.
We do not sell your address, share it with advertisers, or place third-party open-tracking pixels in messages. The services do not ask for a password, name, phone number, home address, or payment information.
What we collect
When you request a condition alert or The Daily, we store the normalized email address, the page where the request began, and timestamps for request, confirmation, preference changes, and unsubscribe. For condition alerts we also store the fixed rules you selected. For The Daily we store your send frequency (every morning, or every other day). We keep a minimal delivery record: the type of message, the edition or condition occurrence it belongs to, Cloudflare’s message identifier when one is returned, delivery state, attempt count, and a bounded error category. We do not retain full outbound message bodies in the database.
Confirmation, management, session, and unsubscribe credentials are generated from cryptographically random values. Only a SHA-256 digest is stored. The raw value appears in the email link or secure browser cookie long enough to perform its single job. Confirmation and management links expire after 24 hours; a management session expires after 30 minutes. A global unsubscribe revokes active sessions immediately.
Why we keep consent and delivery history
Consent history proves which emails you requested and when you changed them. Delivery history prevents a repeated scheduled check or Queue retry from sending the same message twice. It also lets us honor an unsubscribe after a job has been queued but before it is delivered. Suppression records prevent further sends after a hard bounce or complaint. These records are operational safeguards, not an advertising profile.
Cloudflare processing
The site, database, scheduled checks, Queues, bot protection, and transactional email run on Cloudflare. Cloudflare therefore processes the technical data required to serve the page and deliver requested messages. Its handling of data is governed by the Cloudflare Privacy Policy and related service terms. The application does not store long-term raw IP addresses. Cloudflare’s edge security and normal service logs may process network information as part of operating and protecting the service.
Source data inside a message
Condition-alert messages include only public facts needed to explain the match: a Florida Department of Health advisory state, a NOAA/National Weather Service wind forecast, a NOAA CO-OPS tide prediction, or NOAA's regional sargassum inundation outlook. Those public agencies remain the authoritative sources. The email connects the source condition to your saved rule; it does not combine the public data with a location history or individual behavioral profile.
The Daily draws on the same public island sources — water, tides, wind, getting around, and what's on — and may include a brief sponsor line. It does not combine that material with a location history or individual behavioral profile.
Cookies and measurement
The public site does not need an account cookie. After a valid one-time management link is submitted, the browser receives a secure HttpOnly session cookie plus a CSRF-protection cookie. Both expire after about 30 minutes and are used only for alert management. Site performance and aggregate page activity may be measured through Cloudflare’s first-party analytics. Clicks on labeled partner links are counted only as a daily total per link and page; no IP address, cookie or other identifier is stored for that count. We do not use an email open pixel, and a recipient’s failure to load images is not treated as engagement.
Stopping emails and requesting changes
Every condition-alert email contains two controls: a one-time link to manage individual rules and a separate link to stop all alerts. The one-click unsubscribe endpoint accepts the email client’s standard POST and takes effect immediately. You can also request a fresh management link from the conditions alerts page. Generic responses prevent that form from revealing whether another person’s address is subscribed.
Every Daily email contains a one-click unsubscribe link that takes effect immediately, plus a mailing address as required by law. After you confirm, a link in the email also lets you switch from every morning to every other day, or back. Unsubscribing from The Daily does not change your condition alerts, and the reverse is also true.
To ask about correction or deletion of a record, contact the site owner through Alberto Sadde’s website. Some minimal consent, suppression, or delivery evidence may need to remain long enough to prove an unsubscribe, prevent repeat delivery, investigate abuse, or meet legal obligations. It will not be reused for promotion.
Changes to this notice
If either product begins collecting new categories of personal data, introduces payment, adds another delivery channel, or changes how addresses are used, this page will be updated before that behavior launches. A material change will not silently turn a condition-alert address into a Daily subscription, or the reverse.