On your device
YellowQuest stores your profile, preferences, quests, discoveries, badges, rewards and journey summaries to run the app. Saved GPS samples are retained for active or recoverable journeys and removed when a journey is saved as completed or discarded. The current route may remain in memory for an optional overlay export until you clear it, start another journey or close the app. Recorder diagnostics contain counts and error codes, not precise coordinates.
Reminders and local measurement
Optional quest reminders use saved quest progress, your chosen schedule and notification permission. They do not start location tracking. Reminder preferences, experiment assignment and engagement counts stay on this device and are excluded from iCloud gameplay saves. They contain no routes or coordinates. Nothing is uploaded automatically; Export reminder results shares a copy only when you choose to share it.
Deleting local data turns reminders off and clears engagement records, while retaining the original experiment assignment and first-launch marker so a reset is not counted as a new install. You can change reminder choices in the app and notification permission in iOS Settings.
Adaptive quest selection keeps a bounded local record of habit targets, progress, availability and coarse completion measures. Deduplication and temporary destination exclusions use keyed hashes. This record is outside iCloud gameplay saves and contains no coordinates, routes, raw destination identifiers or inferred home or work locations. No adaptive analytics are uploaded. Local data deletion and player replacement erase this record. Saved quest destinations retain the normal gameplay-save behavior described below.
Private iCloud sync
When sync is enabled, Apple CloudKit stores your private save so devices using the same iCloud account can share progress. This includes your profile and optional photo, rewards, quests, adventures, home and quest destinations, discovered map cells and associated times. Raw GPS recordings are excluded. Private saved locations are still location data, even though raw routes are not uploaded.
Maps and location
With your permission, location supports discovery, journeys and quest check-ins, including background check-ins when allowed by your settings. Apple MapKit handles maps, area searches and place lookups. Search terms, the searched area and requested places are sent to Apple. Opening navigation sends the chosen destination to your selected map provider. You can change location access in device Settings.
Public rankings and parties
Your Profile username and optional photo also identify you in public rankings. Personal rankings are free and enrollment is automatic when iCloud sync is connected to your save. Your username, photo, ranking stats and a stable public identifier are shared with everyone. Edit your username and photo in Profile; there is no separate ranking profile or enrollment control. Joining a party publishes the party name and photo, member ranking stats, membership identifiers and join dates used to verify group scores. Rankings do not publish your coin balance, home, quest destinations or live location.
When you share an adventure, its quest destinations become available to your party through CloudKit sharing. Party members can see membership names and shared quest check-in progress. Optional location sharing is off by default. When you turn it on for a party, your latest location, accuracy, update time and photo from Profile are shared with all current and future members through the private CloudKit share, including while the app is in the background with Always location access. YellowQuest keeps one latest location record per member, not a route history. Locations older than two minutes disappear from the app’s map; this display expiry does not itself erase the CloudKit record. Sharing controls apply to each device. If multiple devices share, the newest fix is displayed. Stopping sharing clears the coordinate and photo when the latest fix came from this device; another device may continue sharing until you stop it there too. Leaving, removal or ending the party deletes the location record when the cloud operation succeeds. A failed stop stops this device’s GPS sharing immediately and shows a connection message. Invitation links give access to an invitation; send them only to people you intend to invite.
Reports and blocking
Public names are filtered, and Apple’s on-device Sensitive Content Analysis checks public photos when enabled in iOS Settings. Screening results are not uploaded. Reports send your selected reason, optional details, the reported name and photo, and account identifiers to CloudKit for moderator review. Reports are not public listings. Your blocked-account list is stored privately for your iCloud account. Blocking hides that person’s public content, invitations and location marker; it does not leave or remove members from an existing party. Members of a CloudKit share retain access to its shared records. Stop location sharing or leave/remove the member to end that sharing relationship.
Deleting your YellowQuest data removes your reports and blocked list. Minimal moderation identifiers may remain to enforce restrictions and prevent abuse. Reports remain until deleted by their author through account deletion or removed by a moderator.
Your controls
Edit your username and photo in Profile and leave a group in Party. Sync and deletion controls are in Settings. Delete All Local Data clears this device only; cloud and public data remain. Delete YellowQuest Data, in iCloud settings, removes your cloud save, public profile, your party data and this device’s progress. It disbands parties you lead. An interrupted deletion stays pending for retry, with sync paused. Minimal deletion markers prevent old devices from uploading erased progress again. Start Fresh creates an empty save.
Other devices may retain offline copies until they reconnect and complete the deletion flow. Exports or copies held by other people cannot be recalled.
Optional rewarded ads
YellowQuest includes Google Mobile Ads and User Messaging Platform SDKs for optional rewarded ads. When the ad integration is used, Google may process IP addresses (including approximate location), device identifiers, ad interactions, product interactions, crash reports and performance diagnostics for advertising and analytics.
YellowQuest does not send quest destinations or precise coordinates to AdMob. Access to the advertising identifier and cross-app tracking require your permission through Apple’s tracking prompt. Declining tracking does not change bonus rewards. Where available, revisit ad privacy choices in the app and change tracking permission in iOS Settings. See Google’s SDK data disclosure and Google’s privacy policy.
Photos are optional; the system photo picker gives access only to images you select. Live Activities can display quest information on your Lock Screen when enabled.
This website
This website stores your selected theme and appearance in your browser’s local storage. It uses no analytics scripts, advertising cookies, or tracking pixels. You can clear these preferences in your browser settings.
GitHub Pages logs and stores visitor IP addresses for security. Learn more in GitHub’s hosting documentation. Emailing support shares your email address and the information you choose to include so we can respond to your request. Contact us to request deletion of support correspondence.
Questions about your privacy?
This policy describes the current YellowQuest app and this website. Operator: Jeric Hernandez.
For access, deletion, or other privacy questions, include only the information needed to explain your request. Do not send passwords, verification codes, payment details, or private party invitation links.