Mardi Gras FYI

Privacy

Mardi Gras FYI is published and operated by Andrew Dunn. For help or privacy questions, email mardigras@dunn.us or see the About 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.

Google Maps on the website

On a parade page, loading the route map sends browser and network information to Google. The Hotels, Restaurants and Bars buttons ask our server to search Google Places near that parade’s route. Our server sends Google locations along the route and the type of place you chose, then shows Google’s results on the page.

AI apps and the MCP server

The Mardi Gras app in AI assistants and our MCP server at https://mardigras.fyi/mcp don’t use Google Places. They have no nearby-place search or lodging comparison and send no Google place data to AI models. Their answers come from the parade calendar, route maps and local advice.

The app’s map is a Google map that loads inside a frame served by Mardi Gras FYI, which sends browser and network information to Google. It displays the map only and makes no Places requests. In an embedded app, the chat host still processes the app interaction.

Opening walking directions sends the selected point on the parade route to Google Maps as the destination. Google Maps asks you for a starting point; Mardi Gras FYI doesn’t send a starting point and doesn’t ask for your location in chat.

Storage and retention

Google place results from the website’s nearby search 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.

The public website uses Umami, an analytics tool that Mardi Gras FYI runs on its own server at umami.dunn.us, to count page views. For each view it records the page, the site that linked you there, and your browser, operating system, device type, language and country. Umami doesn’t use cookies. It uses your IP address to work out your country but doesn’t store it, and it counts visitors with an anonymous code made from the website, your browser details and a value that changes every month. This analytics data is kept until we delete it. The AI app, the map frame and the API don’t load Umami. See Umami’s documentation.

If you email mardigras@dunn.us, we keep your message, your email address and anything you include in that mailbox so we can reply. Fastmail hosts the mailbox and processes and stores its messages. See Fastmail’s Privacy Policy.

Chat and copies you keep

Chat hosts process tool results under their own policies. Using Add parade to chat shares only the selected parade’s details. 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 .