The short version
Key Biscayne Guide uses your email address only to confirm, deliver, and manage the specific condition alerts you request. We do not sell the address, share it with advertisers, add it to an editorial newsletter, or place third-party open-tracking pixels in messages. The service does not ask for a password, name, phone number, home address, or payment information.
What we collect
When you request an alert, we store the normalized email address, the fixed rules you selected, the page where the request began, and timestamps for request, confirmation, preference changes, and unsubscribe. We also keep a minimal delivery record: the type of message, the 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 rules you requested and when you changed them. Delivery history prevents a repeated scheduled check or Queue retry from sending the same occurrence 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 alert 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 an alert
Condition messages include only public facts needed to explain the match: a Florida Department of Health advisory state, a NOAA/National Weather Service wind forecast, or a NOAA CO-OPS tide prediction. 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.
Cookies and measurement
The public site does not need an alert 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. We do not use an email open pixel, and a recipient’s failure to load images is not treated as engagement.
Stopping alerts and requesting changes
Every condition 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.
To ask about correction or deletion of an alert 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 the alert 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 general marketing list.