Know what you’re sharing.

On your device

Favorites, display settings and reporting drafts may be saved in browser storage. You can clear them using your browser’s site data controls. Usage counters do not keep a visitor identifier in browser storage.

Accounts and contributions

You can browse parks and games without an account. Google sign-in is optional for browsing and required to save shared reports or sync favorites. For account creation, we verify Google’s signed identity token and keep a hashed Google account identifier, a username (initially random), your favorite teams and default team, an optional profile picture or selected icon, and a hashed session identifier. Your Google name, email and picture are not imported into the account database. Pictures you choose to upload are cropped and resized on your device, then stored with your account settings. Profiles and contribution statistics are currently visible only to the signed-in owner. Username edits do not change account ownership. Milestone badges describe participation and current review status, not certified landing accuracy. A secure HttpOnly cookie keeps you signed in for up to 30 days. Signing out revokes that device’s session. Other providers and manual signup are not connected to the hosted beta. The separate local community pilot is a different account service.

Accepted landing reports and approved issue descriptions may be public. Don’t include private information in a report. Issue receipts and account credentials are private. Live observations go to the shared CatchLanding database for review. When Google accounts are enabled, new observations belong to your account and remain accessible after signing in on another device. Earlier guest observations remain associated with their original device and are not automatically merged into accounts. Signed-in issue reports are saved to the shared database with account ownership, report text, optional park/page context, device/browser family, app version and review history. The public board omits account identifiers and screen context. New issues are private pending review; you can see your own reports across devices. A small per-tab draft in session storage preserves the form through sign-in and is cleared after a confirmed save. Common credential/email spills are redacted, but leave private information out of reports. Submission limits use salted daily network hashes, not stored raw IP addresses. If the shared issue API is unavailable in a static archive, the form prepares an email draft; you must send that yourself.

Usage and sponsor counts

The hosted CatchLanding beta records small daily totals of page views, known interface clicks, park choices, active seconds and sponsor events. These counters omit free-text inputs, full URLs, precise locations, account identity and raw IP addresses. They do not store individual events or visitor/session identifiers. A random per-page transport ID is discarded; a short-lived salted batch receipt prevents duplicate counting. A salted daily network hash limits abuse and is separate from the totals. Reports cover the last 30 days, with bounded cleanup of older totals and an owner cleanup tool. These are sampled interaction counts, not unique people, ticket purchases or complete conversion funnels. Server operational logs are separate.

These first-party counters respect Do Not Track and Global Privacy Control. Counters are disabled in offline/static archives; the hosted beta uses the shared first-party counter service. We do not load third-party advertising or session replay scripts.

Turn off anonymous usage counts

External links

Ticket sellers, MLB resources, sign-in providers and Polymarket operate their own services and privacy policies. A referral URL may identify this project to a partner. A purchase happens on the seller’s website.

Download and removal requests

Manage your account data → lets signed-in fans download their own profile, shared observations, corrections, issue reports and removal requests. Large histories download in clearly labeled parts. Identity hashes, sign-in tokens, network hashes, other fans’ records and private moderation notes are excluded.

A removal request is saved for owner review; it does not instantly delete your account or published contributions. You can cancel a pending request. Requests already under review need owner assistance. Account exports use a creation/edit cutoff, while current statuses and profile preferences are read at the stated time. Browser drafts and earlier guest reports are excluded.

Contact

Privacy contact details are being configured for the public launch.

Live ball observations

The live page checks the MLB game feed while visible. Draft spots and notes are kept in this browser (up to 30 drafts). Shared reporting uses the signed-in account when Google sign-in is enabled, with a secure HttpOnly session cookie for up to 30 days. Before account activation, reports use a random device session. It stores the observed event, map edition, first and final locations, optional section/row labels, source, notes, optional public video evidence links and video timestamps, and correction history. Video links are used for review and are not automatically fetched from arbitrary fan URLs. Guest reports stay under review and do not automatically change the heat map or earn rewards. The owner can privately export and review reports, including their correction history. Reports are not deleted when the cookie expires. Signed-in fans can request removal in account settings; for older guest reports, contact the owner with the game, ball and approximate submission time. A salted daily network hash limits submissions; raw IP addresses are not stored in the report database. Cloudflare and MLB may process connection metadata under their own policies. Avoid entering private details in notes. Google receives basic sign-in information under its own privacy policy. CatchLanding does not request Gmail, Drive or other Google service access. Use account settings or contact the owner for account or contribution removal requests.