Privacy Policy

What we collect

Browsing Fallow never needs an account — there is no public sign-in, and we don’t collect an email address, a name, or any other identifying profile information from visitors.

• Submissions: anything you submit — an event, a venue, a correction, or a photo/flyer — along with any notes you add. Submissions aren’t tied to an account; we don’t know who sent one beyond basic technical data used for abuse prevention (below).
• Calendar feeds: a private feed link (and the city/date filters you chose for it) so your calendar app can stay in sync. Feed links are single-use tokens, not tied to any personal information.
• Chat messages: what you send to Oliver (the chat assistant), processed to generate a reply and to detect abuse.
• Location, only if you tap “Use my location”/“Search near me”: your browser asks permission and sends your coordinates for that one search, so Oliver can find events near you instead of only by a typed city. We never request or collect this silently, don’t store it beyond answering that message, and it’s not tied to any profile.
• Basic technical data: request metadata used only to rate-limit abuse (e.g. too many submissions in a short window). We don’t run ad trackers or analytics scripts on this site.

Cookies

We set a small number of functional cookies: one to keep a chat conversation connected to your browser session, and (for our internal team only) an admin sign-in session cookie — public visitors never get one of those. None of these are used for advertising or cross-site tracking.

Photos and flyers

If you upload a photo or flyer, it’s sent to a third-party AI vision service to read event details off of it (name, date, venue, and similar). That reading is a first draft, not a fact — it always goes to a human curator for review before anything is added to the archive. The image itself is stored so the curator can check it against what was extracted.

Who else sees this data

We don’t sell or rent your data. It's shared only with the services that run Fallow:

• Supabase, for our database and file storage.
• Cloudflare, which hosts the site.
• AI providers (DeepSeek, NVIDIA, OpenRouter, and the underlying models they route to) for chat replies and reading uploaded photos/flyers.
• Tavily and Firecrawl, to read a pasted event link and help fill in missing event details.

Your choices

• Revoke a calendar feed any time from the calendar page.

Changes

If how we handle data changes in a meaningful way, we’ll update this page and change the date at the top.