Version 2026-06-09

Privacy policy

This privacy policy explains how RouteBeer handles personal information collected through the RouteBeer website, beta waitlist, and private beta app.

Who we are

RouteBeer is operated by Ben Keenan. Contact: [email protected].

What we collect

When you join the waitlist, we collect your name, email address, platform preference, beta interest, consent status, source URL, referral or campaign tags where available, form version, privacy policy version, submission timestamp, and basic technical metadata such as user agent.

If you use the private beta app, we may collect account details, profile details, friend and invite data, route and venue choices, crawl participation, check-ins, comments, photos, drink logs, scores, notification preferences, privacy settings, safety reports, and app support messages.

RouteBeer uses location for route discovery, check-ins, live crawl sharing, and recaps. Live location is intended to be temporary and controlled in-product. Some durable records, such as check-ins, completed route history, distance summaries, or recap trails, may be kept as part of your crawl history.

Why we use it

We use this information to manage the RouteBeer beta waitlist, decide which testers to invite, send beta access emails, send product updates you consented to receive, prevent spam, and keep consent records.

In the beta app, we use data to provide accounts, routes, crawls, live participation, maps, games, notifications, recaps, safety/reporting features, support, product analytics, crash diagnostics, and abuse prevention.

Lawful basis

For beta and product update emails, we rely on your consent. For app features you choose to use, we process data to provide the beta service. For security, safety reports, diagnostics, abuse prevention, and record keeping, we may rely on legitimate interests where appropriate. Some optional analytics or session replay features may rely on consent or in-app privacy controls.

Email marketing

We only send RouteBeer beta/product emails where you have ticked the consent box. You can unsubscribe or withdraw consent at any time by contacting us at [email protected]. All marketing emails include an unsubscribe link.

Analytics, diagnostics, and PostHog

RouteBeer may use Firebase Analytics, Firebase Crashlytics, and PostHog to understand beta usage, feature flags, app errors, and product quality. These tools may process events, device or session identifiers, app version, screen names, feature usage, crash details, and diagnostic context.

PostHog is being added for product analytics, feature flags, beta diagnostics, and session replay where enabled. Session replay can record interactions in the app or website, so RouteBeer will use masking and sampling controls and will avoid intentionally recording private comments, photos, precise live location views, passwords, or payment details.

You can manage optional analytics and diagnostics in the beta app where settings are available. If analytics or session replay is added to the public website, the cookie notice will be updated and any required consent mechanism will be shown before non-essential tracking is enabled.

Where data is stored

Waitlist submissions are stored using Cloudflare Pages Functions and Cloudflare KV. The beta app uses Firebase services for authentication, database, storage, functions, notifications, analytics, diagnostics, and app protection. RouteBeer also uses Google services for maps, places, route estimates, sign-in, and AI-assisted route generation. PostHog is being added for analytics, feature flags, diagnostics, and session replay where enabled. Future email providers or beta distribution tools may process your email address and invite status.

How long we keep it

We keep waitlist records while RouteBeer is in beta and review inactive records after 12 months. If you withdraw interest, we aim to remove you from active waitlist segments within 30 days, unless we need to keep minimal suppression data to avoid contacting you again.

Beta app account data is kept while your account is active. Completed crawl history may be kept for up to 24 months for recaps, support, safety reports, and product history unless you delete it sooner or ask us to delete your account. Live location should be cleared when sharing stops, you leave a crawl, or the crawl ends, with stale live-location cleanup targeted within 24 hours of crawl end. Beta tester records are kept during beta and for up to 12 months after beta ends unless you become an active user.

Your rights

Depending on your location, you may have rights to access, correct, delete, restrict, object to, or request a copy of your personal data. To exercise these rights, email [email protected].

Deletion requests

If you ask us to delete your account or waitlist record, we will verify your request and aim to complete it within 30 days where possible. Shared crawl history may need to be anonymised rather than fully removed where deletion would affect other participants' records, or where limited retention is needed for safety, legal, or dispute reasons.

Complaints

If you are in the UK and are unhappy with how we handle your personal data, you can contact the Information Commissioner's Office. Please contact us first so we can try to resolve the issue.

Children

RouteBeer is intended for adults. We do not knowingly collect information from children or market RouteBeer to under-18s.

Changes

We may update this policy as RouteBeer develops. The version date at the top shows when this policy was last updated.