FlareLog Privacy Policy

Effective date: 2026-05-14 · Last updated: 2026-05-14

Short version: FlareLog stores your autoimmune archive — conditions, flare entries, medications, lab values, imaging, prior-authorization events, provider communications, photos, and documents — locally on your iPhone. Your archive is included in your standard iOS device backup (iCloud Backup or Finder/iTunes). FlareLog has no servers and no analytics; we never see your archive. The only network call the app makes is to Apple's StoreKit servers for subscription verification.

1. Who we are

FlareLog is published by an independent iOS developer (Apple Developer Team ID ZM8LF8494F). For any privacy-related question, write to captainlongevity@gmail.com.

2. Information we do not collect

We do not collect, transmit to our servers, store on a server we operate, sell, share, or analyze:

Your conditions, diagnoses, flare entries, symptoms, severity sub-scores (SLEDAI, EDSS, PASI, BSA, stool frequency, joint counts), or recovery notes
Your medications, biologic names, prescribing providers, pharmacy sources, copays, or out-of-pocket costs
Your lab values, reference ranges, imaging reports, imaging photos, or document attachments
Your prior-authorization events, denial reasons, step-therapy required medications, appeal letters, peer-to-peer outcomes, or external review decisions
Your insurance plan name, insurance plan ID, or any insurance correspondence
Your name, email, phone, date of birth, address, or any account identifier
Device identifiers (IDFA, IDFV) for advertising or tracking purposes
Location data
Crash reports or analytics events sent to any third party

We have no servers. The fields above never reach us.

3. No data sharing with pharmaceutical companies or insurers

FlareLog does not share any records with pharmaceutical companies, insurance carriers, specialty pharmacies, healthcare providers, professional medical associations, government agencies, or research databases. There is no advertising SDK, no analytics SDK, and no marketing-data partnership in the app. If a future release ever introduces any such integration, it will be strictly opt-in, with a clear in-app notice before any record leaves your device.

4. Information stored on your device

All archive data you enter is stored locally on your iOS device using Apple's SwiftData framework. This data is included in your standard iOS device backup (iCloud Backup or Finder/iTunes encrypted backup) if you have device backup enabled — that is how a multi-year archive survives a new device. We recommend keeping device backup on. You can also export the entire archive as a JSON file at any time via Settings > Export full backup.

5. On-device processing

Several features process data locally on your device only:

Document scanning uses Apple's VisionKit on-device.
PDF report generation uses Apple's PDFKit on-device. No archive content is transmitted during generation. The PA Defense Pack, New Provider Onboarding Pack, Annual Disease Activity Summary, Lab Trend Report, Multi-Condition Overview, and Provider Communication Summary are all built from your local records and rendered on-device.
Lab trend charts use Apple's Swift Charts framework. No record content is transmitted during chart rendering.
App Lock uses Apple's LocalAuthentication framework. Your Face ID or Touch ID biometric data never leaves Apple's Secure Enclave; the app only receives a success or failure signal.
PA renewal reminders are scheduled via Apple's UserNotifications framework and fire locally on your device. No remote push servers are involved.

6. AuthGuard schema coordination (Pro)

Pro users can export their FlareLog archive as a JSON file ("FlareLog-AuthGuard schema") for use with AuthGuard, a separate iOS app for single-event prior-authorization appeals. The JSON file is generated on your device. It is exchanged between apps via the iOS Share Sheet or Files app, never via a remote server. AuthGuard is a separate application with its own privacy policy; we do not receive any data exchanged between the two apps. The reverse direction (importing an AuthGuard appeal outcome back into FlareLog's PA Battle Log) operates the same way.

7. Subscriptions and StoreKit

FlareLog offers an optional Pro subscription (Monthly, Annual, or Lifetime one-time) via Apple's StoreKit 2. When you subscribe, restore a purchase, or when the app verifies your entitlement, your device communicates directly with Apple's servers. FlareLog receives only the entitlement status (active or inactive) and a purchase identifier. We do not see your Apple ID, payment method, billing address, or transaction history. Apple's handling of subscription information is governed by Apple's Privacy Policy.

8. Permissions the app requests

Camera — only when you tap "Scan document" on a lab, imaging, or document entry.
Photo Library — only when you tap "Import photo" or "Import document".
Face ID — only after you enable App Lock in Settings (Pro).
Notifications — only after you enable PA renewal or flare-followup reminders.

You can revoke any of these permissions at any time in iOS Settings > FlareLog.

9. No AI, no automatic medical inference

FlareLog does not predict flares, recommend medications, calculate official disease activity scores, infer triggers, generate appeal letters, or perform any artificial-intelligence analysis on your archive. Severity sub-scores you record (SLEDAI, EDSS, PASI, BSA, stool frequency, joint counts) are your own self-estimates and are stored as text/numbers without further processing.

10. Children's privacy

FlareLog is not directed to children under 13. We do not knowingly collect any information from anyone, including children. The app's age rating reflects this.

11. Data retention and deletion

You control retention completely. Deletes are permanent — tapping "Delete this record" in any editor surfaces a confirmation dialog, and confirming removes the record immediately. To remove every trace, delete the app and remove the associated entry from iOS device backup. There is no remote copy on our servers for us to delete because we do not have servers.

12. International users

The app is published in English and is primarily marketed in North America. Because we operate no servers, we do not transfer your data internationally. iOS device backup routing is governed by Apple under your Apple ID.

13. Changes to this policy

If we ever change how the app handles data, we will update this policy and surface the change in the app before you can use the affected feature. The "Last updated" date at the top of this page reflects the most recent revision.

14. Contact

Privacy questions: captainlongevity@gmail.com