Privacy Policy

Effective date: May 18, 2026

SweatLog (“we,” “us,” or “our”) values your privacy. This Privacy Policy explains how the SweatLog app and this website handle information.

1. Information we collect

SweatLog is designed to work without creating an account. We do not require your name or email address to use SweatLog; we only receive contact details if you choose to email us.

The app may allow you to enter or save information such as sweat logs, body areas, triggers, treatment notes, outfit logs, photos, and other health-related observations. Unless you use a feature that explicitly sends data elsewhere (for example, sharing or exporting a file you choose), this information is stored on your device and is not uploaded to our servers for routine storage or backup.

Depending on how you use the app, information on your device may include:

• Photos you add (for example, outfit photos or context photos attached to logs).
• Health & fitness information you log (for example, symptom episodes, severity, outfits, and treatment notes).
• Purchase and subscription signals related to in-app purchases. Payments are handled by Apple; we do not receive your full payment card details. Subscription entitlements may be validated via RevenueCat, which processes only information needed for purchase validation, reporting, and customer support tooling that we enable.
• Marketing attribution and performance diagnostics through AppsFlyer where that SDK is configured in the build (for example, install and campaign attribution, device and network signals, limited advertising identifiers where permitted).
• Optional product analytics through Mixpanel only if you opt in in the app. When enabled, Mixpanel may receive event data (such as taps, navigations, and feature usage summaries), coarse app version/OS context, device identifiers Mixpanel assigns, and a pseudonymous stability ID derived from your on-device SweatLog profile identifier. With your consent, Mixpanel Session Replay may also record how you interact with non-sensitive parts of the app interface (for example navigation and controls) to help us improve usability. Screens that can show your sweat logs, symptom details, photos, exports, or similar health-related content are masked in the app so they are not included in those recordings.

SweatLog may request Apple’s App Tracking Transparency permission where required for marketing measurement. If you deny tracking, attribution features that rely on the identifier may be restricted in line with Apple’s rules.

2. Legal bases & regions (EU/UK/CH)

Where European data-protection law applies (for example GDPR in the EU/UK and analogous rules in Switzerland), we process optional Mixpanel analytics only on the basis of your consent, which you can withdraw at any time in Settings → Privacy → Optional usage analytics.

SweatLog does not knowingly sell personal information within the meaning of the CCPA / CPRA (California) for monetary consideration.

3. How we use information

Locally stored SweatLog content is used to provide app functionality: saving logs, outfits, reminders, widgets, trends, insights, and exports when you initiate them.

Optional Mixpanel data is used to understand aggregated product usage so we can improve stability and UX. When Session Replay is active, recordings are limited to product-improvement purposes and exclude masked health and log screens as described above.

AppsFlyer data is used to measure marketing effectiveness and attribute installs.

We do not sell the health narratives you enter in SweatLog to data brokers.

4. Data storage

Your SweatLog health and symptom data stays on your device. SweatLog does not use iCloud or CloudKit sync for your logged content under the configuration described here. Content remains on device storage unless you export it, share it, or another feature plainly sends it elsewhere.

5. Third-party services

SweatLog may interoperate with the following categories of processors or partners:

• Apple (App Store, StoreKit) — billing, receipts, refunds, subscriptions.
• RevenueCat — subscription status, entitlement checks, integrations with Apple receipts.
• AppsFlyer — marketing attribution/measurement. See AppsFlyer’s privacy policy for specifics.
• Mixpanel — optional analytics and Session Replay when you explicitly opt in. See Mixpanel’s privacy policy for specifics.
• Hosting / CDN for this marketing website (subject to hosting provider notices).

Each provider maintains its own policy governing how it processes data on behalf of configured apps.

6. Your choices

• Optional analytics: off by default — enable or disable anytime under Settings → Privacy → Optional usage analytics.
• Advertising identifier / tracking prompts: managed through Apple Settings → Tracking and the SweatLog permission prompt shown when eligible.
• Deleting app data: use Settings → Delete All Data inside the app, or delete SweatLog from your device (and backups you manage). Clearing data removes on-device SweatLog content governed by those actions.
• Subscriptions: manage or cancel via your Apple ID subscription settings.

7. Children's privacy

SweatLog is not directed to children under 13. If you believe a child provided information to Mixpanel via the optional analytics pathway, disable analytics and contact us — we'll instruct you on vendor-specific controls where possible.

8. Changes to this policy

We may update this Privacy Policy. The revised version will appear on this page with a new effective date. For material changes affecting optional analytics, we may surface additional guidance in the app where appropriate.

9. Contact

Questions about privacy: contact@sweatlog.dev

Appendix: App Store “App Privacy” labeling (guide)

Apple’s privacy nutrition labels are submitted in App Store Connect and must match your app’s behaviour. Xcode’s Privacy Report (built from manifests, including SPM dependencies) summarizes SDK disclosures — use it together with this chart when answering Apple’s questionnaires.

Reminder: if an SDK ships its own PrivacyInfo.xcprivacy, it may surface in the aggregated report separately from SweatLog’s manifest.

Typically “Collected” (examples — verify against your Xcode Privacy Report before publishing)

• Health & Fitness: data you enter in SweatLog — Linked to you (“Data Linked to You”), used for App Functionality; not used for Tracking in the App Store questionnaire sense for that local logging path.
• Photos or Videos: attachments you add — linked, app functionality only, not used for tracking.
• Purchase History: subscription status conveyed through RevenueCat — linked, App Functionality (purchase validation/account status). Apple payment details stay with Apple.
• Product Interaction / Analytics (Mixpanel): only when the user toggles analytics on — classify as collected for Analytics; generally Linked to You because SweatLog may identify events with your on-device pseudonymous identifier. If Session Replay is enabled for your Mixpanel project, disclose it per Mixpanel’s guidance; declare not used for tracking only if Mixpanel usage does not constitute “tracking” under Apple’s definition (consult your counsel if tying events to purchases or cross-context advertising flows).
• Identifiers / Diagnostics / Advertising data (AppsFlyer & related): follow your Xcode Privacy Report and AppsFlyer’s documentation — many installs require marking at least some data as Used for Tracking where attribution ties to advertisers or brokers.

If Apple asks whether data is collected “for tracking purposes”

Answer honestly per Apple’s definition (“tracking” includes linking collected data about a user or device from your app with third-party data for targeted advertising or sharing with data brokers — see Apple’s current wording in App Store Connect). Optional Mixpanel product analytics tuned for internal improvement may qualify as analytics-only, but factual scenarios vary — reconcile with Counsel and AppsFlyer’s actual configuration.