Privacy Policy
XploreR — Last updated: September 9, 2026
1. Introduction
XploreR (“we”, “us”, “our”) operates the XploreR mobile application (the “App”) and website (together, the “Service”). This Privacy Policy explains what personal data we process, why we process it, how long we keep it, and the choices available to you.
Privacy contact: privacy@xplorer-app.com
2. Data Controller
The data controller responsible for this processing is:
XploreR
Email: privacy@xplorer-app.com
3. Minimum Age
The Service is intended for users aged 13 and older. We do not knowingly collect personal data from children under 13. If we learn that a child under 13 provided personal data, we will delete it. A parent or guardian who believes this has happened can contact privacy@xplorer-app.com.
4. Data We Collect
4.1 Account and Profile Data
| Data | Purpose | Legal Basis |
|---|---|---|
| Email address | Sign-in, verification, password reset, and service messages | Performance of our contract |
| First and last name | Your display name in the Service | Performance of our contract |
| Password | Authentication; stored as a cryptographic hash, never in plain text | Performance of our contract |
| Optional profile photo, bio, phone, profile location, and language | Profile personalization and communication preferences | Consent or performance of our contract |
| Internal user and session identifiers | Keep you signed in and associate data with the correct account | Performance of our contract; security interests |
4.2 Location Data
Precise location is necessary for XploreR’s location-based treasure hunts.
| Data | When Collected | Purpose | Legal Basis |
|---|---|---|---|
| Precise foreground GPS location and accuracy | On location-dependent screens, and continuously during an active quest | Show your position and nearby quests; navigation, route recording, distance, and progress | Performance of our contract |
| Precise background location | During an active quest if you grant the additional OS permission | Continue the same gameplay and route tracking while the App is minimized | Consent |
| Location history and timestamps | During active quest gameplay | Route history, statistics, and quest analysis | Performance of our contract |
| Recent device location | During active gameplay, including a Control Room session | Show live quest progress to authorized quest coordinators | Performance of our contract |
Continuous, server-synced tracking starts when an active quest needs it and stops when the quest is completed, stopped, or abandoned. Outside an active quest, the App may obtain a foreground fix to show your position or nearby quests, but that fix is not added to server location history. Background access is optional and can be changed in your device settings.
Location updates are batched and stationary samples are downsampled before storage to reduce unnecessary transmissions and database writes.
4.3 Device and App Data
We process a device registration identifier, device name and type, model or brand, operating-system information, App version, battery level, online/background status, and last-seen timestamps. We use this to connect an installation to your account, support offline sync, show Control Room status, enforce minimum supported App versions, troubleshoot compatibility, and secure the Service.
4.4 Gameplay and User-Generated Content
- Quest attempts, start/completion times, status, scores, waypoint arrivals, mission completions, answers, and timing data
- Photos you choose to take or upload for photo missions
- Quests, missions, points of interest, route data, reviews, and reports you create
- Control Room sessions, messages, recipients, and read receipts
We use this data to provide gameplay, creator tools, moderation, leaderboards, history, and Control Room coordination. Content that you publish or share with a group can be visible to other users or authorized coordinators according to the feature you use.
4.5 Sensor Data Processed Locally
Compass/magnetometer, accelerometer, gyroscope, barometer, pedometer, brightness, and similar sensor readings used by sensor-based missions are processed on your device and are not uploaded as raw sensor streams. Mission results derived from them may be stored as gameplay data.
4.6 Diagnostics, Logs, and Website Requests
The App keeps troubleshooting logs locally for up to 7 days, capped at 50 MB. They can include timestamps, errors, and a random session identifier. The log feature does not upload them unless you explicitly export and share them.
Separately, we use Sentry for crash, error, session-health, and performance monitoring on the App and website. Sentry may receive errors, stack traces, release/environment, operating system, device or browser information, route/request context, performance timings, and diagnostic breadcrumbs. Mobile Sentry is configured not to send default personally identifying information or screenshots. Website monitoring may process IP address and request or account context when present in an event. We do not use Sentry Session Replay.
Our website infrastructure also receives normal network request data, including IP address, browser/user-agent, requested page, and timestamp, for delivery, security, and troubleshooting.
4.7 Map, Search, and Route Requests
Map features request tiles and mapping files from external content services. Place search may send your search text to OpenStreetMap Nominatim, and route calculation may send quest waypoint coordinates to OpenStreetMap-based routing services. Those providers also receive normal network data such as IP address and user-agent. Do not enter personal or sensitive information into place-search fields.
5. How We Use Data
- Provide accounts, gameplay, offline sync, and creator tools
- Record progress, routes, statistics, leaderboards, and attempt history
- Coordinate active quests through the Control Room
- Verify email addresses and send password-reset messages
- Moderate reports and protect users, accounts, and the Service
- Diagnose crashes, errors, performance, and compatibility
- Meet legal obligations and respond to rights requests
We do not sell personal data, serve targeted ads, use advertising identifiers, track you across other companies’ apps or websites, or use Session Replay. We do not make decisions that produce legal or similarly significant effects solely by automated means.
6. Service Providers and External Services
| Service | Purpose | Data Processed |
|---|---|---|
| Convex | Authentication, database, file storage, server functions, and real-time sync | Account, device, gameplay, location, content, and other core Service data |
| Sentry | Crash, error, session-health, and performance monitoring | Diagnostic and technical context; website events may include IP or request/account context |
| Resend | Email verification and password reset delivery | Recipient email, verification/reset message content, and delivery metadata |
| Expo / EAS | App build and developer infrastructure | Build, release, and developer project metadata; not core end-user data |
| OpenStreetMap-based services | Map tiles, place search, and route calculation | Viewport/tile requests, search text, waypoint coordinates, IP, and request metadata as applicable |
| UNPKG | Delivery of the Leaflet map library used in the App | IP address, user-agent, and request metadata |
Provider policies: Convex, Sentry, Resend, Expo, and OpenStreetMap Foundation. These companies act under their own terms or as our service providers, depending on context. We do not permit them to use our data for advertising on our behalf.
7. Storage and Security
Core Service data is stored on Convex infrastructure. Diagnostic and transactional-email data is processed separately by Sentry and Resend. We use HTTPS/TLS, provider security controls, access restrictions, cryptographic password hashing, and platform-appropriate local secure storage. Convex states that customer data is encrypted at rest and in transit.
No system is completely secure. Use a unique password and contact us if you believe your account has been compromised.
The App can locally store authentication tokens, device registration identifiers, cached quest data, a pending offline-sync queue, cached gameplay photos awaiting upload, and debug logs. We do not currently process payment-card information because the Service is free.
8. Retention and Deletion
| Data Type | Retention |
|---|---|
| Account, device, gameplay, location, photos, reviews, reports, and private creator-run data | While the account is active, then deleted through account deletion unless legally required |
| Published creator content | Deleted with authored text, coordinates, and uploaded media when you delete your account |
| Authentication sessions | Until logout, account deletion, or expiration after inactivity |
| Local App logs | Up to 7 days and 50 MB |
| Sentry diagnostic events | Per our Sentry project retention and only as needed for troubleshooting and security |
| Transactional email records | According to Resend's operational and legal retention periods |
Account deletion immediately revokes sessions and removes your email credentials; associated record deletion then continues in the background, normally within minutes. Delete your account in the App at Settings → Account & Privacy → Delete Account, on the account-deletion page, or by emailing privacy@xplorer-app.com if you cannot sign in.
Account deletion also removes creator content previously shared with other players. Their own gameplay records may remain, with deleted content unavailable.
9. Your Rights
Depending on where you live, and under the GDPR in particular, you may have the right to access, correct, delete, restrict or object to the processing of, and receive a portable copy of your personal data. You may withdraw consent without affecting earlier lawful processing and lodge a complaint with your local supervisory authority.
Contact privacy@xplorer-app.com to exercise a right. We may need to verify your identity. We aim to respond within the legally required period, normally one month under the GDPR.
10. Location Choices
- iOS: Settings → Privacy & Security → Location Services → XploreR
- Android: Settings → Apps → XploreR → Permissions → Location
“While Using the App” supports foreground gameplay. “Always” or “Allow all the time” supports an active quest while the App is backgrounded. “Never” disables location-dependent gameplay. Changing the permission stops future collection covered by that permission.
11. International Data Transfers
Convex, Sentry, Resend, Expo, and mapping/content providers may process data outside the European Economic Area. Where required, transfers use an applicable mechanism such as an adequacy decision or Standard Contractual Clauses, with supplementary safeguards where appropriate.
12. Changes to This Policy
We may update this policy when the Service or legal requirements change. We will post the updated policy, change the “Last updated” date, and provide additional notice when a change materially affects your rights or how we use personal data.
13. Contact
Questions, concerns, and data requests can be sent to privacy@xplorer-app.com. You also have the right to contact your local data protection supervisory authority.