A clear read on your privacy.

FanProof uses Vercel Web Analytics to understand visits in aggregate. Vercel describes this service as cookie-free and anonymized. It can provide broad information such as pages viewed, referring sites, approximate geography, browser, operating system, and device category.

We also record a small set of named site interactions: when a venue guide or card is selected, when venue search or filters are used, when more directory results are requested, when a carousel or section link is used, and when an outbound ticket link, source link, correction link, fan-signal link, or venue-suggestion link is selected. Search events contain only the query length and result count—not the words typed. Ticket and source events describe the destination and page context for the click. They do not tell FanProof whether a ticket was purchased or whether a linked form was submitted.

On production venue guides, FanProof also keeps a limited first-party event record for a venue page load, meaningful section visibility, and categorized planning-resource clicks. A random identifier for the current browser tab and a separate random pageview identifier help prevent duplicate counts; neither is an account, cookie, fingerprint, or cross-site identifier. These records use the venue, stable section or destination category, server receipt time, editorial content version, and sanitized campaign or referring domain when available. They do not include names, email addresses, precise location, raw IP addresses, full user-agent strings, full referring URLs, link text, or arbitrary notes.

For a ticket-resource click, FanProof creates a new random handoff identifier used only for that single click and records the coarse acquisition channel, ticket-link placement, affiliate or official source, and commission-window category. The identifier is not derived from the browser-tab or pageview identifiers, is never reused, and does not contain personal information. FanProof does not currently add this one-use identifier to the ticket link or send it to the ticket seller.

When you arrive through a tagged campaign link, FanProof reads only standard campaign labels such as source, medium, campaign, and content. Sanitized labels can be kept in session storage for the current browser tab so the visit is still attributed after you move from the landing page to a venue guide. These labels describe the link—not the person who selected it.

When you arrive from another site, FanProof may also keep only a coarse source class—organic search, organic social, referral, or direct/unknown—for the current browser tab. FanProof does not store the full referring URL or a search query in this label.

When you select an Impact-tracked Ticketmaster affiliate link, FanProof may add three coarse reporting labels to that link: the venue guide, the ticket-link placement and layout, and the broad acquisition channel. Impact can associate those labels with clicks, actions, and affiliate earnings. The labels do not contain a visitor ID, full referring URL, search query, email address, or other personal information.

FanProof may randomly assign the browser to one of two ticket-link layouts and save only that layout label in local storage. This keeps the experience consistent while we compare aggregate link impressions and clicks. The label is not an account, does not identify you, and is not used for advertising across other sites.

For internal measurement checks, FanProof can set a local browser QA marker that keeps owner verification out of public campaign outcomes. The marker contains no account or visitor identifier, changes only how that browser's analytics are recorded, and can be cleared before ordinary browsing resumes.

Vercel Speed Insights may measure loading and responsiveness through standard web-performance signals. We use this information to find slow or frustrating parts of the experience.