787daily

Privacy policy

Effective October 2026

Using 787daily is also covered by our terms of use.

What we collect

You can read the site without an account. We only receive personal information you choose to send us: an email address when you subscribe to a newsletter, set a spot alert or ask for a hike plan by email, your details when you use the contact form or the "Get matched" form, and a push address when you turn on alerts. We do not sell personal information or use advertising networks.

Newsletters

The daily email is sent only after you confirm your address. An address that is never confirmed is deleted after 48 hours. Every email has an unsubscribe link; when you unsubscribe, your record is deleted. Our emails are sent through Cloudflare Email Sending. To have your record removed at any time, write to hello@787daily.com.

Spot alerts by email

If you set an alert on a surf break or wind spot, we keep your address, the spot and the condition you picked, and nothing else. We use them only to email you, at most once a day, when the forecast meets the condition. The alert starts only after you confirm your address. Every alert email has a link to stop it, and the Manage link drops one alert or all of them; when nothing is left, your record is deleted. Unsubscribing from the daily email stops your alerts too.

Hike plans by email

If you ask for a hike plan by email, we use your address to send that one email. It is not added to any newsletter.

Alerts on your device

If you turn on storm, water or other alerts, your browser gives us a push address for your device, the alerts you chose and, for alerts by town, the town you picked. We use them only to send those alerts. Turning alerts off in the page or in your browser settings removes them.

Contact form

Messages from the contact form come to us by email so we can reply. We keep them as long as we need to answer and follow up. An event listing is also kept for 30 days on our editors' page, so it can be added to the events calendar.

Questions you type into Ask and requests you type into the hike planner are sent to an outside AI provider to be answered: Anthropic's Claude, reached through Cloudflare, with Cloudflare's own model as a fallback. They are not sent with your name or email, and we keep no log of them. Ask keeps each answer for up to six hours, filed under a scrambled form of the question alone, so the same question gets a quick answer. Searches on our search page run in your browser. The words you search for are not sent to us, and they are taken out of the page address before Google Analytics sees it. We also count how each Ask answer came out (answered, partly answered or not answered) and which part of our site it drew on, and whether a search found anything. The count never includes your question or the words you searched for, and nothing about you.

When you tap “Helpful” or “Not right” under an Ask answer or our live read of the island, we count the tap: which button, and which answer or read it was about. Nothing about you goes with it, and no cookie is set.

Flood-zone lookup

If you type an address on our flood-zone page, it comes to us and goes on to the U.S. Census Bureau, which finds it on the map. To look up the zone, we send that spot, rounded to about 11 meters, to FEMA and the Puerto Rico Planning Board. "Use my location" asks your browser first, and only the rounded spot leaves your device. We never log or keep the address. The answer for a spot is kept in Cloudflare's cache for up to a week, with nothing about who asked.

Limits against abuse

To stop abuse, we count requests per visitor using a one-way scrambled key, not your IP address, and drop the counts within a day: most last about a minute, and the daily counts on the hike planner and the email forms last 24 hours. Your IP address is never saved, with what you wrote or on its own. Before Ask, the hike planner, the contact form, the email sign-ups or the "Get matched" form accept a request, Cloudflare's Turnstile checks that it comes from a person and not a bot, under Cloudflare's own privacy policy.

How long we keep things

We keep no log of the questions you type into Ask or the hike planner. A "Was this useful?" tap is an anonymous count, with no cookie. An event listing is kept for 30 days, and a request to be matched with a professional for at most 12 months. Counts against abuse are dropped within a day. So the site can be restored if something breaks, we keep backup copies of what is stored for it, such as newsletter and alert sign-ups, for 30 days, with Cloudflare only and nowhere else; anything you have deleted is gone from them within those 30 days.

What your browser keeps

A few things are saved in your own browser so the site remembers them:

  • light or dark mode, your units, the town you picked as yours
  • which alerts you have already seen, and whether you dismissed the "add to home screen" prompt or the dust advisory
  • the towns you chose for storm alerts
  • your hurricane-prep checklist ticks
  • the layers you chose on the island map, and whether you keep its news panel open
  • whether you read the water utility's notices in English or Spanish
  • when you last visited, so the headlines new since then can be marked
  • that you signed up for the daily email, so the sign-up prompts stay away
  • a switch that leaves your browser out of our visitor counts, if you turn it on

For the length of a visit only, the browser also holds a contact-form draft (name, email and message, so an error does not lose it), the email you typed into a sign-up, and your hike-planner conversation.

All of it stays on your device and is never sent to us, except what you send yourself: a form, or a town you pick for an alert. Clearing your browser's site data removes it.

Analytics

We use Google Analytics 4 to understand which pages are read and which features are used, and to improve the site. Besides page views, it is told when you use certain features: for example a newsletter sign-up or unsubscribe, a link out to an original story, the Support button, a share or sort button, a question sent to Ask, or a "Get matched" request. It is told that you used the feature, never what you typed. It may set cookies and collect device and usage information under Google's policies. We also use Cloudflare Web Analytics, which sets no cookies and reports only totals. Separately, we count page requests by kind of page, with whether each one worked and how fast it loaded; that count holds no IP address, no page address and nothing else about who asked. When you leave a page, it also sends us one small report: how long the page was on screen, whether it was scrolled, and the kind of site you arrived from (a search engine, social media, another site or none). We keep it with the kind of browser and network it came from (never your address, your network's name, your browser's full name or the page you came from) only to tell readers from automated traffic and to see how people find us. The page-not-found page runs neither Google Analytics nor Cloudflare Web Analytics.

Every article summary links to an external, third-party outlet (e.g. El Nuevo Día, Primera Hora). Those sites have their own privacy policies and tracking practices. We have no control over them and encourage you to review their policies before visiting.

Hosting

This site is served by Cloudflare, which may process standard server logs and security signals such as IP address, the page requested and the time. Some pages show maps and photos that your browser loads straight from Windy, OpenFreeMap and Wikimedia; hike maps load their terrain from Amazon Web Services, during a storm our hurricane page shows the forecast cone from the National Hurricane Center, and the sailing maps' Chart button loads a nautical chart from NOAA's Office of Coast Survey. Each works under its own privacy policy.

Changes

If this policy changes, we will update the effective date above.