Privacy Policy

Account information (only if you sign in). Creating an account is optional and requires only an email address — there are no passwords. If you sign in, we store your email address, and the event plans, artists, teams, music genres, and accessibility planning priorities you save are synced to our database so they follow you across devices. Sign-in works through a single-use link — or, for installed home-screen apps, a single-use 6-digit code — that we email you (delivered via Resend); both expire after 15 minutes. Signed-in sessions are kept server-side and expire after 90 days of inactivity. We use your email address only to send the sign-in links and codes you request and — if you turn them on from the My Plan page — event-day reminder emails about your own saved plans. Reminders are off by default and every reminder includes a one-click unsubscribe link. We do not send marketing email. You can delete your account at any time from the My Plan page, which removes your email address, synced plans, follows, and preferences from our servers.

Location data (only with your permission). If you grant your browser permission, we read your device’s approximate coordinates and send them to our server to find events near you. Your coordinates are also stored in your browser’s localStorage so the Service remembers your preference across visits. We do not associate your location with your identity, and we do not store your coordinates in any database. If you instead type a city or ZIP code to set your location, that text is sent to our server and converted to coordinates using the third-party geocoding services Zippopotam.us and Nominatim (OpenStreetMap) so we can find events near it.

Event-day live checks. To show event-time weather, our server sends the venue’s coordinates and event date to the United States National Weather Service; it does not send your location or account information. If you choose a live traffic or transit link, your browser opens Google Maps with the venue and, when available, the starting area saved in this browser. PathToSeat does not receive the resulting route or navigation activity.

Local browser storage. The Service uses localStorage to remember your geolocation preference, recent searches and recently viewed events, saved event plans (including any custom events you add — event name, performers, venue, date, and time — and any parking address or restaurant you choose), artists and teams you follow for event alerts, your selected music genres and accessibility planning priorities, event-alert acknowledgements, and interface preferences such as theme, text size, sorting, collapsed sections, and dismissed prompts. To support offline and resilient use, the Service may also temporarily cache public event listings in your browser; those cache entries are keyed to the location preference used for the request. If you are not signed in, saved plan data remains on your device; if you sign in, your saved plans — including any custom events, parking address, and dining choice they contain — plus followed artists, teams, music genres, and accessibility planning priorities are also synced to our database as described above. Using the optional suggestion features involves the separate transmission described below.

Server logs.Our hosting provider (Vercel) automatically records standard request information, including IP address, user agent, referrer, and timestamps. Vercel uses this data to operate and secure the platform. Vercel’s standard security logs are typically retained for about 14 to 30 days before deletion.

Analytics and performance telemetry. We use Vercel Web Analytics to collect aggregate, privacy- friendly usage metrics, including page views, referrers, and a limited set of interaction events such as which events and guide sections are opened, calendar filters and formats used, correction forms started or submitted, whether pasted text or an ICS file successfully prefilled the add-event form, guide-feedback votes (accurate or outdated, per section), whether a plan was shared via the share sheet or the clipboard, and searches that returned no results. Those interaction events use fixed categories only. We do not include raw search terms, user-entered locations, exact coordinates, ZIP/postal codes, cities, email addresses, pasted or imported event text, correction text, saved event-plan contents, event or venue identifiers, or persistent user identifiers. Vercel Speed Insights collects anonymous page-performance metrics such as load and navigation timing. These tools do not use cookies or track you across other sites. Vercel may process limited request and device metadata, including coarse location derived from a request, under its privacy-focused analytics model.

Calendar tools. Downloaded calendar files contain only the public event details displayed by the Service. If you choose Google Calendar, your browser opens Google with those details prefilled. Google may process request, device, and account information under its own privacy policy. PathToSeat does not access your calendar or calendar account.

Plan sharing.Choosing “Share plan” builds a text summary of your saved plan (event name, date, venue, and the seat, parking, dining, checklist, and merch details it contains) plus a link to the event page, and hands it to your device’s share sheet — or, where sharing is unavailable, copies it to your clipboard. The summary goes only to the app or person you choose to share it with; it is not sent to or stored on PathToSeat’s servers.

Address, venue, and restaurant suggestions, maps, and directions. The Service offers optional type-ahead suggestions in three places: the custom parking-address field, the venue field of the add-your-own-event form, and the restaurant search in the dining guide. After you enter at least three characters, your browser sends that partial text, along with the public event-venue coordinates (or your approximate location) used to bias results, to PathToSeat’s server. We relay them to Google Places to return suggestions. Selecting a suggestion sends its Google place identifier so we can obtain the formatted name and address (and, for venues, coordinates). We do not intentionally log this text or save it in an application database. The parking address, venue, or restaurant you choose is saved in your browser’s local storage as part of your event plan; if you are signed in, it syncs to our database with the rest of that plan. Nearby-place map previews may also load from Google Maps, and choosing “Open directions” sends the saved address to Google Maps. Google processes these requests under the Google Privacy Policy.

Correction reports.If you submit a “Report a correction” form, we receive the category and description you enter, the event or venue you are reporting, and — only if you choose to provide it — an email address for follow-up. Reports are emailed to our support inbox (delivered via Resend), may be forwarded to an internal notification channel, and are recorded in our server logs; they are not stored in an application database. We use a provided email address only to follow up on your report.

Guide feedback votes. Guide sections may ask whether their information was accurate. If you answer, we receive only fixed values: the section, your accurate-or-outdated verdict, the page’s site-relative path (never the query string), and the event or venue identifier and name. Votes contain no free text and no email address. They are recorded in our server logs as an aggregate freshness signal, and “outdated” votes may be forwarded to an internal notification channel so we can review the section; they are not stored in an application database.

We do not collect: names, phone numbers, payment information, or passwords. We collect an email address only if you choose to create an account or include one in a correction report. Pasted confirmation-email or calendar text used to prefill the add-event form is parsed in your browser and is not sent to PathToSeat; only the fields you review and save become part of a local or synced plan. Other than optional accounts, synced plans, correction reports, guide feedback votes, and the transient suggestion and geocoding lookups described above, we do not maintain a database of user-submitted content.