Privacy Policy

1. Introduction

This Privacy Policy explains how Pyre Fitness ("Pyre Fitness," "we," "us," or "our") collects, uses, shares, and protects information when you use the Pyre Fitness mobile application, pyrefitness.com, and related services (together, the "Service").

Pyre Fitness is operated by Pyre Fitness LLC, the developer and legal entity responsible for the Service. If you have questions about this policy or your data, contact us any time at support@pyrefitness.com.

This policy describes our information practices; it is not a request for blanket consent. Where applicable law requires consent for a particular use of information, we will request it separately. If you do not want Pyre to process the information required to provide the Service, please do not use Pyre Fitness.

2. Information we collect

Depending on how you use Pyre Fitness, we collect the categories of information described below to operate, personalize, secure, and improve the Service:

Account information

• Your name, username, email address, Firebase user ID, and sign-in-provider identifiers. Pyre no longer asks for or stores a phone number in your account profile and does not use phone numbers for contact matching.
• During signup, you provide a date of birth and confirm that it is accurate. The date is evaluated on your device; we do not retain the full birth date. We store your age in whole years at signup, age-eligibility markers (13-or-older, and 18-or-older where applicable), and the time and method of the declaration so age-based restrictions can be enforced.
• Pyre does not currently request or store an Apple or Google platform age-range signal. A future version may use a platform-provided age range or eligibility signal where required or made available by law, an app store, or an operating-system platform. Such a signal would not be identity verification, and Pyre may apply the more protective experience when signals differ. We will update this policy if that changes the information we collect or how we use it.
• Profile details you add, such as a profile photo, title, and social-display preferences, subject to the App's age-group and audience controls.

Parent permission & age groups

• Users aged 13–17 may use Pyre Fitness only with the permission and involvement of a parent or legal guardian. Pyre does not independently contact, authenticate, or verify the parent or guardian through signup.
• In version 2.0, social interaction is separated into ages 13–17 and adults 18 and older, subject to friendship, blocking, participation, and other audience controls.
• Automated weight-change planning remains restricted to adults 18 and older. Optional Firebase usage analytics is disabled for all accounts in Pyre Fitness 2.0.

Health & fitness data

• Workout and run data — exercises, sets, reps, logged weights, distance, pace, duration, elevation, and workout history.
• Training and body profile — goals, equipment, schedule, sex selection, height, body weight and measurements, calorie and macro targets, and meal logs you enter.
• Progression data — XP, levels, attributes (STR, AGI, END), streaks, quests, and other in-game stats derived from your activity.
• Health integrations — if you grant permission, the App reads steps, walking and running distance, active energy, and, on iOS, heart rate and completed workout summaries from Apple Health or Android Health Connect. Eligible Apple Health workouts and runs can award XP and update attributes, lifetime totals, quests, and workout history; Pyre stores the workout source, activity type, times, duration, distance, calories, and derived rewards needed to prevent duplicate credit and maintain progression. Pyre can also save completed runs and workouts to Apple Health.

Garmin watch companion

• If you choose a paired Garmin watch, Garmin Connect handles device authorization and Pyre exchanges the current run or workout state, live heart-rate samples, set actions, rest-timer actions, and run-finish requests directly between the Pyre mobile app and watch on supported devices. Pyre and the watch may temporarily retain the latest mirrored state and pending actions so they can recover from a disconnect.
• During an active mirrored session, the watch may use its heart-rate and GPS sensors and save a standard FIT activity; that activity can sync to your Garmin account under your Garmin Connect settings. Pyre does not use the Garmin Connect cloud Activity API to import your Garmin account history in this version.

Location data

• If you grant permission, Pyre uses precise GPS location during an active run, including while that run continues with the screen locked or the App in the background, so it can map route, distance, and pace.
• Once permission has been granted, Pyre may also request your current or last-known location when the App opens or resumes and when you use trail discovery, route generation, trail challenges, directions, or trail-photo verification. Coordinates may be sent to our backend and mapping or trail-data providers to return nearby results.
• Outside an active run, Pyre does not continuously track location in the background.

Camera & photos

• Photos you choose for profile media, shared workouts or runs, community trails, and meal analysis; camera input used for those features and food barcodes. Social and community sharing is subject to the App's age-group and audience controls.
• Submitted images may be automatically screened for safety. Meal-scan image bytes are sent to Amazon Nova models through Amazon Bedrock for analysis, but are not saved to your Pyre account or Firebase Storage after the result is returned.

Contacts & social graph

• Contact matching is optional. When you choose it, Pyre reads contact details on your device and sends up to 120 unique normalized email addresses per request to a protected Pyre backend matching service. Those email addresses are used transiently to find existing Pyre users and are not stored as an uploaded contact list. Matching and interaction remain subject to age-group and audience controls.
• When you use invitations, contact names and phone numbers stay on your device for the invite interface. Pyre never sends invitations for you; tapping Invite opens your Messages app and you decide whether to send.

User content

• Feed posts, share images, likes, comments, direct messages, challenge messages and participation, GIFs, community trails and reviews, reports, and other content you submit. Social interaction is subject to the App's age-group and audience controls.
• We process reports, blocks, and automated or human moderation results to enforce our rules and protect users.

AI prompts & processing data

• Prompts, meal images, relevant fitness-profile inputs, and workout or trail context sent to features such as meal scanning, workout analysis, training-plan generation, trail or trial lore, area briefs, and trail insights, and boss narratives. Amazon Web Services (AWS), using Amazon Nova models through Amazon Bedrock, processes these requests and the safety checks associated with these features and community-trail photos.
• In version 2.0, proposed usernames, social text, profile and social images, decoded GIF frames, and text extracted from images are sent to Amazon Web Services (AWS) for safety checks using Amazon Bedrock Guardrails and Amazon Rekognition. Submitted text or images may contain personal information or workout metrics, including content that is subsequently rejected. We do not separately attach your date of birth or stored health/workout profile to these moderation requests.
• Generated meal results, plans, lore, and moderation results may be returned to you, stored with the relevant account or content, or cached to operate the requested feature.
• If you report a displayed AI result, the selected reason and a bounded excerpt of that generated result are stored in the safety queue and sent to our monitored support channel for review.

Purchases & subscription state

• Subscription and purchase status processed through the Apple App Store, Google Play, and our subscription provider RevenueCat. We do not receive or store your full payment card details — those are handled by Apple and Google.

Diagnostics & crash data

• In release builds, diagnostic, performance, log, and crash data collected through Firebase Crashlytics to help us find and fix bugs. This data is used for reliability and support, not advertising.

Device & network information

• Operating system, device model, App version, an operating-system or device/build identifier that is not an advertising ID, IP address, App Check signals, notification token, and related security logs.
• To protect accounts and prevent abuse and ban evasion, Pyre keeps a per-account device record when you sign in or open the App — the device model, OS version, platform identifier signal, the IP address our servers received, and first-seen and last-seen times — along with security events (for example, a sign-in from a new device) and short-lived per-action rate-limit counters.
• We use these for service delivery, support, security, fraud prevention, abuse investigations, and reliability — never for advertising.

Usage analytics

• Optional first-party usage analytics through Firebase Analytics is disabled in Pyre Fitness 2.0, including for adult accounts.
• This version does not send Firebase Analytics events, and Settings → Privacy shows the feature as unavailable.
• This does not disable crash diagnostics, account and security records, or mapping-provider telemetry described below. Analytics data collected by earlier versions remains subject to the retention terms below.

Website & communications

• Firebase Hosting and normal internet infrastructure receive technical request data such as IP address, browser, requested page, and time.
• If you join the launch list, your email address and any optional name or fitness goal you submit are processed by Formspree and retained so we can send the updates you requested.
• The website loads fonts and code from Google Fonts and jsDelivr, which receive ordinary request information such as your IP address and browser headers.

3. How we use your information

We use the information above to:

• Provide and operate core features — the Lair, quests, campaigns, workouts, run tracking, trails, food tracking, squads, and other social features, subject to age-group and audience controls.
• Calculate XP, levels, streaks, attributes, progression, and leaderboard results, subject to the App's access controls.
• Map your runs and surface nearby trails and routes.
• Power AI features, including meal scanning, training-plan generation, and trail or trial lore.
• Manage your account, subscriptions, and entitlements.
• Keep the Service secure, prevent fraud and abuse, and debug problems.
• Send you service messages and, where permitted, product updates you can opt out of.
• Comply with legal obligations.

Activity sharing

In version 2.0, completing an ordinary workout or run saves your activity privately. You can choose Post to Squad to share its summary and optional photos. Challenge workout-day and lift-completion flows also publish an activity summary when you record those challenge results. Summary fields can include the workout title, exercises, total volume, personal-record count and duration, or run distance, pace and time. Published summaries can appear in your allies' Stories for about 24 hours and as a short recent-activity line on your in-App profile. The basic summary does not include your route, precise location, community-trail identity, heart rate or photos. If a text-only summary cannot be posted because of a temporary network problem, your device retries it for up to seven days and then discards it.

Optional route and heart-rate sharing

Pyre does not post your completed-run route, community-trail identity, or average heart rate to the social feed merely because you recorded a run. Only an explicit feed or share action can include the full route, trail name, and average heart rate in a post or image. A route may still be processed privately for map display, trail or challenge validation, safety, and rewards.

Social visibility and moderation

In version 2.0, social interaction is separated into ages 13–17 and adults 18 and older, subject to friendship, blocking, participation, and other audience controls. Teens can use social features within their age group; automated weight-change planning remains restricted to adults.

Accepted, unblocked friends in your age group may see feed posts, activity summaries and comments. Community trails, trail photos, reviews, and other community content may be available more broadly within Pyre. Direct messages are intended for conversation participants. Challenge participant lists and chat are intended for the creator and members. Authorized administrators or moderators may access content for support, safety, and enforcement.

Shared media links: Avatars, run or workout share images, community-trail images, some chat images, and published social GIFs are delivered through public or tokenized file URLs so they can render in the App or in shares. Anyone who obtains a valid file URL may be able to view or copy that media even if they are not signed in or in the original in-App audience, until the file is deleted or its access token is revoked. Do not include information you do not want redistributed.

Automated systems and authorized reviewers may examine submitted content, account signals, and reports to detect abuse, enforce the Terms, respond to safety issues, and comply with law. Automated checks can make mistakes; you can report content in the App or contact support about a decision.

We do not use your data — including health, fitness, location, photos, or contacts — for cross-app tracking or for advertising.

4. Health & fitness data (HealthKit / Health Connect)

If you choose to connect Pyre Fitness to Apple Health (HealthKit) or Android Health Connect, the App reads fitness data to keep your progress in sync. This includes steps, walking and running distance, and active energy. Heart rate and completed workout summaries are read from Apple Health on iOS only — for example, from an Apple Watch during a run — and heart rate can be used to show an average for that activity. Eligible Apple Health workouts and runs can award XP and update attributes, lifetime totals, quests, and workout history; Pyre stores the workout source, activity type, times, duration, distance, calories, and derived rewards needed to prevent duplicate credit and maintain progression. Pyre can also save completed runs and workouts to Apple Health.

If you explicitly share a run or workout, an average heart-rate value or share image containing it may be stored with that post. Pyre does not publish that value merely because you connected Apple Health or recorded an activity.

You control this connection and can revoke it at any time in your device's Health settings.

5. We do not sell your data or track you across apps

We do not rent or trade your personal information, and we do not track you across other companies' apps or websites for advertising. We use information to provide and secure the Service, perform moderation, communicate with you when requested, and meet legal obligations. We disclose it only to the service providers described below, at your direction, when required by law, or to protect the rights, safety, and security of users and the Service.

6. Service providers

We rely on service providers to operate Pyre Fitness. They receive information only as needed to deliver their services, at your direction, or for the legal and safety purposes described in this policy:

• Google Firebase and Crashlytics — authentication, App Check, database, file storage, Cloud Functions, push messaging, crash reports, and diagnostics. Optional Firebase Analytics collection is disabled in Pyre Fitness 2.0.
• Amazon Web Services (AWS) — Amazon Nova models through Amazon Bedrock process meal images, workout and training-plan inputs, trail and trial content, boss narratives, and related content and image safety reviews. Amazon Bedrock Guardrails and Amazon Rekognition check proposed usernames, social text, profile and social images, GIF frames and image-extracted text for prohibited content. These moderation requests are processed in the United States; Bedrock Guardrails may route them among supported U.S. AWS Regions. We have opted out of AWS using our Rekognition inputs to improve or develop its AI services. This opt-out does not eliminate processing or retention needed to provide and maintain the service.
• RevenueCat — subscription and purchase management.
• Map and trail services — Mapbox, Google Places, OpenStreetMap and Overpass, openrouteservice, Mapillary, Wikimedia, and U.S. National Park Service data sources for maps, routing, geocoding, trail discovery, elevation, and trail imagery. Mapbox may collect location and usage telemetry under its own privacy practices. Its telemetry choices are available through the map’s attribution control; the Pyre Usage Analytics setting does not control Mapbox.
• Open Food Facts — barcode and food-search lookups.
• Apple and Google platform services — App Store and Google Play distribution, store purchases, sign-in, and optional HealthKit or Health Connect integrations.
• Garmin — paired-watch authorization through Garmin Connect, direct app/watch communication on supported devices, watch-side activity recording, and Garmin Connect activity sync under your Garmin settings.
• Website providers — Firebase Hosting, Formspree, Google Fonts, and jsDelivr.

We may also disclose information when legally required, in an emergency involving imminent serious harm, to investigate fraud or abuse, or as part of a merger, acquisition, financing, bankruptcy, or sale of assets.

We do not give service providers permission to use HealthKit, Health Connect, or Garmin wearable data for advertising, marketing, or their own unrelated purposes.

This list may change as the Service evolves; we will update this policy to reflect material changes.

7. Data retention

We generally keep account data and user content while your account is active or as needed to provide the Service. Contact-match inputs are handled transiently rather than stored as a contact list. Meal-scan image bytes are not saved to your Pyre account after analysis. Launch-list submissions are retained until you unsubscribe, request deletion, or the list is no longer needed.

Specific retention periods:

• Device and security records (per-device sign-in records, IP addresses, security events) — up to 12 months after the device was last seen, then deleted automatically.
• Per-action rate-limit counters — up to 30 days.
• Analytics data collected by earlier versions — user-level data for up to 14 months; aggregated statistics that identify no one may be kept longer.
• Crash and diagnostic reports — about 90 days.
• Reports, moderation, and enforcement records — up to 5 years, or longer where reasonably necessary for legal, safety, or compliance obligations — including child-safety reporting laws. Records needed to enforce an active permanent ban, including device signals associated with ban evasion, are kept for as long as the ban remains in effect.
• Stories — about 24 hours. Unsent text-only share retries — up to 7 days.
• Generated lore cache — generated lore may be cached to reduce repeated AI processing. Pyre reads a cached result for up to 30 days; older cache records may remain in backend storage until overwritten or removed.
• Age-eligibility records — age in whole years at signup, age-eligibility markers, and the declaration method and time are generally kept while the account is active so age-based restrictions can be enforced. They are deleted or de-identified with the account, subject to the limited exceptions described below.

Transaction and accounting records may be retained as required by store or tax obligations. When information is no longer needed, we delete or de-identify it.

8. Account & data deletion

You can delete your Pyre Fitness account and associated data at any time:

• In the App: go to Settings → scroll to the Account section → Delete Account.
• By email: contact support@pyrefitness.com with the subject line "Account Deletion Request" and include the email or username tied to your account.

Deletion removes or de-identifies the account and associated data from active Pyre systems, except limited records that must be retained for legal, transaction, security, fraud-prevention, or safety purposes.

For a full walkthrough, see our Account Deletion page. Note that deleting your account does not automatically cancel an active Apple App Store or Google Play subscription — you must cancel that separately through Apple or Google (see section 10).

9. Security

We use reasonable administrative, technical, and organizational safeguards — including encryption in transit, access controls, and established infrastructure providers — to protect your information. No method of transmission or storage is completely secure, so we cannot guarantee absolute security.

Where your device supports it, we use Face ID, Touch ID, or your device passcode to confirm sensitive actions such as deleting your account. This authentication is performed entirely by your device's operating system — Pyre never accesses, receives, or stores your biometric data.

If we ever become aware of a data breach affecting your information, we will notify you and the appropriate authorities as required by applicable law.

10. Your rights & choices

Depending on where you live, you may have the right to:

• Access the personal information we hold about you.
• Request correction of inaccurate information.
• Request deletion of your information.
• Request a copy of your information in a portable format.
• Object to or restrict certain processing.
• Withdraw consent where processing is based on consent.

To exercise any of these rights, email support@pyrefitness.com. We will respond within the timeframe required by applicable law. We will not discriminate against you for exercising your privacy rights.

Age-group controls

Social interaction is separated into ages 13–17 and adults 18 and older. If you believe the age information attached to an account is inaccurate, contact us using the privacy-request address above. We may ask for information reasonably needed to protect the account and evaluate the request.

Subscriptions

Subscriptions purchased through the App are billed and managed by Apple or Google. To cancel a subscription, use your Apple App Store or Google Play account's subscription settings. Deleting your Pyre Fitness account does not cancel a store subscription.

11. Permission controls

Sensitive features are opt-in and stay under your control. You can grant or revoke each of these permissions at any time in your device settings or within the App:

• Location — active-run tracking (including an active background run), nearby trail discovery, routing, directions, trail-photo verification, and location-related challenges. If permission already exists, the App may prefetch nearby trail boards when it opens or resumes.
• Camera & Photos — meal analysis, food barcodes, profile media, workout or run sharing, and community-trail images, subject to the App's audience controls.
• Contacts — optional friend matching, subject to age-group controls. Up to 120 normalized contact email addresses per request are sent transiently to Pyre's protected matching service. Contact names and phone numbers stay on your device for the invite interface. Pyre does not retain an uploaded contact list or send invitations for you.
• Health data — optional HealthKit (iOS) / Health Connect (Android) sync of steps, walking and running distance, and active energy. Heart rate and completed workout summaries are read from Apple Health on iOS only. Pyre can save completed runs and workouts to Apple Health. An average heart-rate value appears in social content only if you explicitly share content containing it.
• Garmin watch — optional watch mirroring. You can change or remove an authorized Garmin watch at any time from Settings → Watches → Garmin Watch in the App and in Garmin Connect.
• Notifications — reminders, streak alerts, and squad or social activity.
• Usage analytics — optional Firebase usage analytics is unavailable in Pyre Fitness 2.0. Mapbox telemetry choices are available through the map’s attribution control; the Pyre Usage Analytics setting does not control Mapbox.

If you revoke a permission or remove a watch, the related feature may stop working, but the rest of the App will continue to function. Revoking a permission or removing a watch does not remove data already submitted or an activity already synced to Garmin Connect — use the relevant deletion control or contact us for that.

12. Age restriction & children's privacy

Pyre Fitness is for ages 13 and older. The Service is not directed to children under 13, and anyone under 13 may not create or use an account, even with parent or guardian permission. Users aged 13–17 may use the Service only with the permission and involvement of a parent or legal guardian. Pyre does not independently contact, authenticate, or verify the parent or legal guardian through signup.

The full birth date supplied during signup is evaluated on-device and is not retained. Pyre stores age in whole years at signup, age-eligibility markers (13-or-older, and 18-or-older where applicable), and the declaration time and method. Pyre does not currently request or store an Apple or Google platform age-range signal; these account markers are not a statement that Apple or Google independently verified your age.

In version 2.0, social interaction is separated into ages 13–17 and adults 18 and older, subject to friendship, blocking, participation, and other audience controls. Automated weight-change planning remains restricted to adults 18 and older. Workouts, runs, nutrition and meal tracking, and meal-photo analysis remain subject to their feature permissions and other limits described in this policy and the Terms.

Pyre shows no third-party ads and performs no cross-app advertising tracking. We do not knowingly collect personal information from anyone under 13. If we learn that an account belongs to someone under 13 or that we collected personal information from someone under 13, we will restrict or delete the account and associated information, subject to limited retention required for legal, safety, fraud-prevention, transaction, or child-safety reporting obligations.

If you believe someone under 13 has provided information to Pyre, contact support@pyrefitness.com.

13. Changes to this policy

We may update this Privacy Policy as Pyre Fitness evolves or as requirements change. When we make material changes, we will update the "Last updated" date and revision above. Where applicable law requires consent for a particular use of information, we will request it separately. This Privacy Policy describes our information practices; use of Pyre Fitness remains governed by the Terms of Use.

14. Contact us

Questions, requests, or concerns about your privacy? We are happy to help.

• Email: support@pyrefitness.com
• Operated by: Pyre Fitness LLC
• Support: pyrefitness.com/support

Email a Privacy Request