Privacy

Mardi Gras FYI is published and operated by Andrew Dunn. For help or privacy questions, email mardigras@dunn.us or visit the support page.

You can use Mardi Gras FYI without creating an account. The application processes the parade selections, filters and search terms needed to answer your request. It does not create a personal profile or save search history in its database. It does not take reservations or payments.

Maps and lodging comparisons

Nearby-place searches send locations along a public parade route and the requested type of place to Google Maps Platform. Comparing a place selected from those results sends its Google place ID to Google to retrieve its current details. Loading a Google map sends browser and network information to Google.

The optional lodging form sends the labels and coordinates you enter to Mardi Gras FYI after you agree to the comparison. These entries are used to calculate route distance and display your comparison. They are not saved in the parade database, source archive or an application cache. The form clears its fields after a successful comparison. Results remain in the current view until you choose another result or close the view.

Supplied lodging entries are excluded from the model’s conversation context. In an embedded app, the chat host still processes the app interaction. Google receives the coordinates needed to display supplied locations on its map. Do not enter your current GPS location in the lodging form.

Opening walking directions sends the selected route destination to Google Maps. Choose your starting point in Google Maps; Mardi Gras FYI does not request your precise starting location in chat.

Storage and retention

Google place responses are used for the current request and are not saved in our database, source archive or an application cache. We keep aggregate daily provider-request counts to limit usage. Those counts contain no user identifiers or search content and have no scheduled expiration. The database and source archive also retain public parade information and its source records.

Cloudflare hosts the service and processes network requests. The public website includes Cloudflare’s performance beacon. Cloudflare’s Web Analytics documentation describes seven-day retention for unsampled beacon data and six months of sampled analytics history. Other network and security information is handled under Cloudflare’s Privacy Policy.

Chat and copies you keep

Chat hosts process tool results under their own policies. Using Add parade to chat shares the selected parade and public place results. It excludes entries from the lodging form. Your host’s privacy policy and history settings govern retained chat data; use its controls to remove chats. Calendar downloads and copied links remain wherever you save them, and you can remove those copies yourself.

Google describes its handling and retention of map and directions information in Google’s Privacy Policy and retention explanation. Use Google’s controls for information associated with your Google account. These provider-held records are subject to their own retention and removal controls.

Updated October 5, 2026.