Disclosure & Privacy

Data sources

Three layers feed every briefing:

• Regulatory primary records — Florida DBPR Division of Hotels & Restaurants (inspections, licenses, emergency orders, ownership changes) and the Florida Sunbiz corporate registry. DBPR republishes these extracts in batches; RiskyEats re-fetches them whenever the pipeline runs, and every page states the date its data runs through. Sunbiz corporate data refreshes quarterly.
• Open geo + places data — Foursquare OS Places (Apache 2.0), Overture Maps (CDLA 2.0), and the Google Places API for closure verification on a watch cohort.
• Community + media signals — closure and opening posts from public Facebook food groups (most prominently Foodies Who Review South Florida), captured through a browser-extension flagger and OCR pipeline; plus headlines from South Florida media outlets (Sun Sentinel, Miami Herald, South Florida Business Journal, Eater Miami, and others). Every community or media signal is cross-checked against the regulatory and places layers before it earns an attribution on a card.

Accuracy

Briefings are point-in-time public-record snapshots. The DBPR data we display is current as of the snapshot timestamp shown in the masthead and footer, which lags the live Florida licensing system by up to 24-48 hours. Verify current license status with Florida DBPR's public records portal before any operational decision.

Where we surface a closure, ownership change, or violation pattern, we attempt multi-source corroboration. If a single source flags a restaurant as closed but the regulatory record still says active, the conflict is shown on the card rather than resolved silently.

The narrative prose is generated by language models trained against the day's structured records — the numbers are deterministic and traceable; the prose is editorial framing, not analysis.

Privacy

The names, addresses, license numbers, inspection dates, violation counts, and ownership records on this site are public records. They are not private data about any individual.

We do not collect personally-identifying information from readers. The only data we receive about visitors is what their browser sends to our analytics provider (page URL, referrer, broad device class, country-level geolocation) — see Cookies & analytics.

We do not sell, share, or otherwise transfer reader data.

Cookies & analytics

We use Google Analytics 4 to measure aggregate page views. GA4 sets first-party cookies for session continuity. You can opt out via the Google Analytics opt-out browser add-on or block analytics via your browser's privacy settings.

The share buttons are plain links to each platform's own share page — they load no script, set no cookie, and share nothing unless you click one and complete the share on that platform.

Some pages do fetch files from other hosts, and those hosts see your IP address and browser when they do. Most pages load web fonts from Google Fonts. Report pages with charts load the Chart.js library, and the venue browser loads its database engine, both from the jsDelivr CDN. Map pages load the MapLibre mapping library from unpkg, and the county map fetches its county-boundary data from GitHub. None of these are analytics or tracking scripts, but they are third-party requests and you may wish to block them.

Hosting & infrastructure

The static site is published via Tiiny Host. The data pipeline + render code runs on private infrastructure under the operator's control; no reader requests touch that infrastructure.

Contact & corrections

Found a name, address, or fact that doesn't match the public record? Email corrections@riskyeats.com with the license number and the discrepancy. Accepted corrections take effect the next time the site rebuilds.

Press, partnership, or data-licensing inquiries: hello@riskyeats.com.