RoamXP

Privacy Policy

Effective date: October 29, 2026

Operator: Puzzle Tech Studios LLC

1. Introduction

This Privacy Policy explains how RoamXP (“RoamXP,” “we,” “us,” or “our”) handles information in connection with the RoamXP mobile application (iOS and Android) and this website. It describes current product behavior as implemented today and is not a guarantee that every practice will remain unchanged forever.

RoamXP is primarily a device-first self-improvement app. You can use core features with data stored on your device. Optionally, you may sign in with Apple or Google to create a RoamXP account powered by Supabase Auth and enable Cloud Save backups of selected progress and user content, as described below.

2. Device-First Design and Optional Cloud Save

Much of your RoamXP activity is stored locally on your device. Local app data may also be included in device backups depending on your Apple, Google, or device backup settings.

If you choose to sign in, RoamXP can automatically back up an allowlisted Cloud Save snapshot to Supabase-hosted storage tied to your account. Cloud Save is optional. Signing out, uninstalling the app, or never creating an account does not require Cloud Save.

3. Information Stored on Your Device

Depending on how you use RoamXP, the app may store locally:

  • journal text
  • journal photos
  • journal audio
  • nutrition logs
  • workout logs
  • goals
  • progression / XP, rewards, and related progression state
  • campaign / quest state
  • achievements and collectibles
  • onboarding state
  • step totals
  • Focus / Screen Time or distraction-protection selections (where available)
  • preferences
  • entitlement/cache state
  • Cloud Save backup status and restore journals (device-side)

4. Accounts and Authentication

RoamXP offers optional account sign-in with Apple and/or Google. Authentication is handled through Supabase Auth. RoamXP does not operate a separate email/password registration system.

When you sign in, we may process account identifiers such as your Supabase user id, linked Apple or Google identity references, and any email address provided by the sign-in provider (including Apple Hide My Email / private relay addresses when Apple supplies one).

Account features may be limited by platform, build, or feature flags. Where Accounts are unavailable, gameplay can still run with local data only.

5. Cloud Save Contents

When Cloud Save is enabled for a signed-in account, RoamXP may automatically upload a versioned snapshot that can include:

  • player profile and progression / XP
  • goals, rewards, cosmetics, and related progression unlocks
  • quest, campaign, challenge, and journey-related progress
  • journal text entries (text and metadata only)
  • workout history and related workout preferences
  • nutrition logs and nutrition goals
  • selected tools / wisdom saves and profile appearance settings
  • selected preferences needed to restore progress

Cloud Save is intended to protect progress across devices linked to the same signed-in account. Conflict handling may require you to choose between local and cloud progress when both contain data.

6. Journal and User Content

Journal text may be stored on your device and, when Cloud Save is enabled, included in Cloud Save as text-only entries.

Journal photos and journal audio remain device-local. They are not included in Cloud Save and are not intentionally uploaded to RoamXP cloud storage. RoamXP does not claim end-to-end encryption of journal or other user content.

Journal text, photos, and audio are not sent to PostHog.

7. Focus / Screen Time and Device-Only Controls

On supported Apple devices, Focus and distraction-protection features may use Apple APIs such as FamilyControls, ManagedSettings, and DeviceActivity. Related selections and opaque tokens are stored locally and, where required by Apple, in Apple App Group storage.

Focus / Screen Time selections and tokens are device-only. They are not included in Cloud Save and are not intentionally sent to PostHog or Superwall. Availability and behavior depend on platform permissions and system settings. RoamXP does not guarantee uninterrupted blocking of all apps.

8. Apple HealthKit and Health-Related Data

On iOS, RoamXP may request Apple HealthKit permission to read step count only. In the current implementation, RoamXP does not write data to HealthKit. Step values are used locally for walking, Journey, and progression features.

Raw HealthKit values are not sent to PostHog, are not used for advertising, and are not sold. RoamXP is not a medical device and does not provide medical advice, diagnosis, or treatment.

9. Product Analytics

RoamXP currently uses PostHog for limited anonymous or pseudonymous product analytics to understand onboarding, feature use, and subscription-related interactions.

Analytics may include:

  • onboarding progress and screen/step metadata
  • explicitly instrumented feature interactions
  • coarse paywall/subscription interactions
  • purchase/restore status
  • permission outcomes
  • app version, build number, platform, and OS/device-type metadata
  • a pseudonymous PostHog installation/distinct identifier

Current PostHog configuration includes:

  • no identify() calls
  • no alias() calls
  • no group calls
  • personProfiles = never
  • session replay disabled
  • lifecycle autocapture disabled
  • surveys disabled
  • remote feature flags disabled
  • automatic error capture disabled
  • push capture disabled
  • GeoIP enrichment disabled

Network requests inherently may make an IP address transiently available to infrastructure providers, but RoamXP configures its analytics service not to retain client IP data for product analytics.

RoamXP does not send the following to PostHog:

  • name
  • email
  • journal text, photos, or audio
  • raw HealthKit step values
  • Screen Time / Focus selections or tokens
  • notification body text
  • StoreKit / Play receipts or full transaction payloads
  • precise GPS location
  • Cloud Save snapshot contents as a bulk export to analytics

10. Purchases and Subscriptions

Purchases and subscriptions are processed by Apple through StoreKit / the App Store and by Google through Google Play Billing (via expo-iap in the current implementation). RoamXP does not receive or store payment card information.

Limited subscription or product interaction metadata may be sent to PostHog. Full store receipts and full transaction payloads are not sent to PostHog.

RoamXP integrates Superwall (via expo-superwall / SuperwallKit) as subscription-related infrastructure, including Custom Purchase Controller support and premium entitlement synchronization. Purchases remain processed by Apple or Google. RoamXP’s existing native paywalls remain in use; remote Superwall paywalls or placements are not currently presented.

When Superwall is enabled, subscription status and other relevant technical information may be processed by Superwall so entitlement state can stay in sync. RoamXP configures Superwall to limit external data collection where the SDK allows, but Superwall may still process technical or subscription-related information needed for its infrastructure. RoamXP does not currently use Superwall for advertising tracking.

Journal content, HealthKit records, and Screen Time / Focus selections or tokens are not intentionally sent to Superwall. Subscription entitlement truth remains with Apple or Google store systems, not Cloud Save.

11. Marketing Preferences

If Accounts features are available and you are signed in, RoamXP may offer an optional marketing email preference (for example, news and offers). Marketing consent defaults to OFF. Cloud Save and account recovery do not require marketing opt-in.

When you change this preference, RoamXP may store your choice, timestamps, and related consent evidence on the account backend. You can turn marketing email off again in Settings when the control is available. Transactional messages related to security or account deletion verification are separate from marketing.

12. Notifications

RoamXP may request notification permission and may use local notifications or reminders. Notification title and body content is not sent to PostHog. Platform settings may suppress or delay notifications. This describes current behavior and is not a permanent guarantee that notification handling will never change.

13. Location

RoamXP does not request native GPS or precise location permission for tracking. RoamXP does not collect precise GPS location. PostHog GeoIP enrichment is disabled.

14. Advertising and Tracking

No advertising SDK is currently integrated. RoamXP does not use IDFA, and App Tracking Transparency (ATT) / IDFA APIs are not used in the current implementation for advertising tracking.

RoamXP does not use app data for cross-app advertising tracking and does not sell personal information for advertising. These statements describe current implementation.

15. Account Deletion and Data Retention

In-app deletion. When Accounts features are available, you may delete your RoamXP account from Profile → Settings → Account & Cloud Save → Delete account. In-app deletion uses additional verification (such as email one-time codes or provider reauthentication) before cloud account data is purged.

Web request. You may also request deletion without reinstalling the app via our Account Deletion page. A web email request is a request for deletion, not an automatic instant wipe. We verify identity before completing deletion.

When account deletion is completed, we delete the RoamXP authentication account and associated Cloud Save data for that account (including revision history where stored), marketing preferences and consent records for that account, and related account-bound cloud records. We may retain a hashed email suppression entry so we do not contact you for marketing after deletion, and we may retain limited records where required for security, fraud prevention, legal compliance, or dispute handling (for example, a legal hold).

Deleting a RoamXP account does not cancel App Store or Google Play subscriptions. Manage billing in your store account settings. Device-local data (including journal photos/audio and Focus tokens) is not automatically erased from every device solely because a cloud account was deleted.

Local data. Local data may be removable through available local controls. Uninstalling the app removes installed local app data from that device, subject to platform backup behavior.

Analytics. PostHog analytics may be retained according to configured provider retention. Because analytics is pseudonymous and not designed around RoamXP account emails, analytics records may not always be reliably associated with a particular person after account deletion.

16. Children

RoamXP is not intentionally designed to collect personal information from children where such collection is prohibited by applicable law.

17. Website Privacy

Separately from the mobile app, the RoamXP website currently uses no RoamXP analytics SDK, no advertising pixels, and no first-party tracking cookies in the site code. The website does not contain a contact form that collects passwords or one-time codes. Support and account-deletion requests use mailto links.

Hosting and network providers may process ordinary connection metadata necessary to serve the website.

18. Third-Party Services

Depending on features you use, RoamXP may interact with:

  • Supabase (authentication and Cloud Save hosting)
  • Apple (Sign in with Apple, App Store / StoreKit, HealthKit, Screen Time APIs where used)
  • Google (Sign in with Google, Google Play Billing where used)
  • PostHog (product analytics)
  • Superwall (subscription infrastructure / entitlement sync)

Those providers process information under their own terms and privacy practices in addition to this Policy, to the extent applicable.

19. Changes to This Policy

We may update this Privacy Policy from time to time. When we do, we will revise the effective date above. If you continue to use RoamXP or this website after an update, you should review the revised policy.

20. Contact

For privacy questions, privacy requests, or account-deletion help, contact: