This website
The site does not set analytics cookies. On the Decker detail page only, a development-only first-party operational adapter can record two narrowly defined events: successful story-detail rendering and selection of a verified Apple or Google store button. A per-event retry record may remain in this browser for no more than seven days. It contains cryptographically random short-lived event, journey, session and transition IDs plus exact website build and configuration revisions. It excludes names, phone numbers, account IDs, free text, invitation selectors and secrets, page URLs, queries and referrers. Website events are not linked to a later native purchaser and do not claim web-to-purchase attribution. Missing or invalid development configuration disables this adapter without changing the page.
The hosting service also processes ordinary request information needed to deliver and protect the site. An invitation secret stays in the browser fragment and is absent from HTTP URLs, but the nonsecret selector is part of the required /join/… request path and may appear in provider invocation or access logs. This repository does not claim zero logs or an approved provider-log retention period. Before connected public release, Cloudflare account administrators must restrict log access and apply the CEO/legal-approved retention setting.
Launch notifications
Request launch updates opens a draft in your email app addressed only to help@metrolore.com, with the city or story you selected. You choose whether to send it. The website does not collect an email address through a form, send the message, store a signup or confirm delivery. If you do not have an email app, copy the visible address into your email service.
If you send the draft, our monitored mailbox receives your message and sender address for manual handling of your launch-update request. You may include a preferred reply address in the draft. Your email provider and our mail service process the message. It does not create an app account, reserve an outing, promise priority access or trigger an automatic reply.
To withdraw permission or ask us to delete your notification request, email help@metrolore.com from the address you used. No app sign-in is needed. We manage these requests manually; no fixed retention period or automated campaign is represented here.
Account and invitations
The connected app uses a verified phone number and a stable account ID. Roster membership, invitations, phone verification, gameplay messages and marketing choices are kept separate.
Purchases
Apple or Google handles payment. metrolore uses store and transaction identifiers, the verified amount and currency, and refund or revocation status to grant and support the correct outing. Do not send payment credentials by email.
Gameplay and teams
Team membership, lead authority, progress, evidence unlocks, answers, hints, score and timing may be saved so a team can continue and recover. Sibling teams do not receive each other's private progress.
Location and photos
A Team Lead requests one foreground location check by tapping Arrived. Raw precise coordinates are used for that check and are not continuously tracked; a derived arrival result may be saved. Customer photos remain on the device or in the user-chosen share flow unless a later feature receives separate review.
Support and feedback
Email and in-app support may use the details you choose to send, along with a safe case reference and coarse app state. Never send a one-time code, receipt token, invitation token, payment details, puzzle answer or exact continuous location.
