Privacy Policy

Last updated: October 20, 2026

Welcome to Find Local ("Find Local," "we," "us," or "our"). This Privacy Policy explains what information is (and isn't) collected when you use the website findlocal.community (the "Service"). The short version: browsing needs no account, we run no third-party analytics or advertising trackers, and the only data about your preferences lives in your own browser.

1. Information we collect

Nothing you have to give us. Browsing the Service needs no registration or login, and it has no profiles or social features. Only developers who want an API key create an account.

• Preferences stored in your browser. Your chosen city (a cookie named fl_city) and any events you save are stored on your device using cookies and browser storage. They are used to render the pages you request and are not sent to us for any other purpose or linked to an identity.
• How you found us (first-party only). On your first visit we set a cookie named fl_src holding the page you landed on, the website that referred you (its domain only) and any campaign tags in the link (utm_*); clicking a sign-up button sets fl_cta with which button it was. They stay in your browser and are read only if you create a developer account, when they are saved with that account so we can see which pages and channels bring developers. They expire after 90 days and 1 day, are never shared, and you can clear them at any time.
• Approximate location, for nearby events. The events widget may look up the town your connection comes from (Cloudflare's IP-based estimate, about 1 km) to suggest events near you; it is not stored or logged by us. "Use my location" asks your browser for your position only when you press it, and sends it rounded to about 100 m as part of the search.
• Log and usage data. Our hosting provider (Cloudflare) automatically records standard technical information for security and reliability when you access the Service, such as IP address, browser type and pages requested. This data is processed in aggregate and is not linked to an identified person.
• Developer accounts and API usage. If you create a developer account we hold your email, name, sign-in methods, plan and the optional answer to "What are you building?". For each API or MCP call made with your key we record the endpoint or tool, the metro and filters requested, the response status, and technical request details (country, network, user agent and, for calls from a Cloudflare Worker, the calling site), to meter your plan, support you and improve the API. This usage log is kept for up to 90 days.
• Widget usage. When an events widget loads, when a visitor filters it, opens an event or adds one to their calendar, and when a visitor reaches a page carrying the widget from a search engine (we note which engine, e.g. Google, and whether they arrived on an event link), we record which website it is embedded on (its domain only), the widget's settings (view, area, category, the site owner's partner tag), which filter fields were used (not what was typed), the country and the browser's user agent. No cookie is set, and no IP address, location or identifier for the visitor is recorded. We use it to see which sites use the widget and which features matter; it is kept for up to 90 days.
• Communications. If you email us, we receive whatever you choose to send.

2. How we use information

• To provide, operate and maintain the Service (for example, showing events for your chosen city).
• To keep the Service secure and reliable.
• To understand aggregate usage (for example, page views by country) and improve the Service.
• To email developer-account holders. Account emails (sign-in links, plan and billing changes) are part of the service. A short series of onboarding tips and a heads-up when a key nears its monthly quota are on by default; product updates are sent only if you opt in. Every optional email has an unsubscribe link, and both can be switched off on your account page.

3. Affiliate links and third-party commissions

The Service may contain affiliate links to third-party websites, venues or ticketing services. Find Local may receive a commission if you make a purchase through these links, regardless of whether the purchase is made immediately after clicking or later. This does not affect your privacy or the price you pay.

4. Automated access and data scraping

Using automated means to collect data from the Service beyond what our robots.txt allows is prohibited without our written permission. Developers who want structured access should use the JSON API, MCP server or widgets.

5. Analytics and tracking technologies

Find Local does not use third-party analytics or session-recording tools such as Google Analytics or Microsoft Clarity, and does not set advertising or cross-site tracking cookies. Our hosting provider may collect privacy-preserving, aggregate traffic metrics that do not use cookies or identify individual visitors. The only attribution we do is the first-party fl_src / fl_cta cookies described in section 1, which never leave findlocal.community unless you sign up. If we introduce other analytics tooling in the future, we will update this policy first.

Embedded maps load tiles from OpenStreetMap only when a map is on screen; OpenStreetMap's own privacy policy applies to those requests.

6. How we share information

We do not sell personal data. We share information only:

• With service providers that run the Service on our behalf (web hosting and database infrastructure from Cloudflare), who may access it only to perform those tasks.
• As aggregated, anonymized data that does not identify anyone.
• For legal reasons, if required by law or a valid request from a public authority.

7. Your rights and data control

Because preferences are stored on your device, you control them directly: clear your browser's cookies and site data for findlocal.community to remove them. If you have contacted us by email and want that correspondence deleted, ask us. If you hold a developer account you can delete it yourself, at any time, from your dashboard: that erases your email, sign-in methods, sessions, API keys and their usage history, and cancels any subscription. Stripe retains past invoices for as long as tax law requires.

8. Children's privacy

The Service is not directed to children under 13 and we do not knowingly collect personal information from them. Users must meet the legal age required in their jurisdiction to attend events involving alcohol or other age-restricted activities.

9. California and European users

Residents of California (CCPA) and data subjects in the European Economic Area (GDPR) have rights to access, correct, delete and port personal data, and to object to or restrict certain processing. Browsing creates no account data; if you hold a developer account, this covers your account email, API keys' metadata, usage counts and billing records (payments are processed by Stripe), as well as email correspondence; contact us at the address below and we will comply with all applicable laws and verifiable requests. Find Local does not sell personal information.

10. Changes to this policy

We may update this Privacy Policy from time to time. We will post the new policy on this page and update the "Last updated" date.

11. Contact us

Questions about this policy: elliot@findlocal.community.