Disclosure & Privacy
RiskyEats is independent restaurant-inspection journalism, built from public records under the Florida Sunshine Law. We are not affiliated with the Florida Department of Business and Professional Regulation (DBPR) or any government agency.
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 records refresh twice daily; 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.
Newsletter signup
If you subscribe to our weekly digest via the form on the homepage, your email address is stored at MailerLite (our email provider) and used solely to send the digest. You can unsubscribe via the link in any digest email; we delete unsubscribed addresses on the next pipeline tick.
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. Corrections are typically pushed in the next pipeline tick (twice daily).
Press, partnership, or data-licensing inquiries: hello@riskyeats.com.