AuthGuard is published by an independent iOS developer (Apple Developer Team ID ZM8LF8494F). For any privacy-related question, write to captainlongevity@gmail.com.
We do not collect, transmit to a server we control, store on a server we control, sell, share, or analyze:
All records you enter are stored locally on your iOS device using Apple's SwiftData framework. AuthGuard does not transmit your records to any server we operate, and the app contains no integration with any cloud sync service. Your records may be included in your standard iOS device backup (iCloud Backup or Finder), subject to a usable completed backup and successful restoration. We do not have access to your device backups.
Device-backup contents and recovery depend on your system settings, a successfully completed usable backup and Apple’s restoration process; enabling backup alone does not guarantee recovery of every record or original file. We cannot retrieve or restore your device backups.
AuthGuard does not request, store, or use your insurance carrier login credentials. The app does not connect to any insurance carrier API, portal, claims system, or pharmacy benefit manager. All PA, denial, approval, and appeal information is entered by you (typed or photographed). This is by design — many of our users are mid-dispute with the carrier they would otherwise be asked to log into.
The app does not run any artificial-intelligence or machine-learning model on your denial letters, approval letters, peer review notes, or call notes. There is no OCR text extraction, no document parsing, no automatic categorization, and no appeal-letter generation. You read the documents; you enter the values; you write the appeal. We make no decisions about your case.
These features process data locally on your device; paid and free availability is described in the Terms:
AuthGuard uses Apple StoreKit for a monthly subscription and a one-time non-consumable Lifetime purchase. Loading products, checking offer eligibility, purchasing, restoring and verifying access communicate with Apple. The app reads verified product and entitlement information, including expiration or revocation status where applicable, and keeps local access state. Apple processes payment; AuthGuard does not receive your payment-card details or Apple Account password. Current and supported historical purchase access depend on verified transactions. See the AuthGuard terms for the available plans and subscription handling.
You can revoke any of these permissions at any time in iOS Settings > AuthGuard.
AuthGuard is designed to be used by adults — patients managing their own care or family caregivers (for example, an adult child managing a parent's Medicare Advantage PA decisions). The app has no child account or developer-operated record collection. Contact support if a child has sent personal information to us. Records are stored locally, with no App-managed iCloud sync. Apple device backups and files you explicitly export have the separate handling described in this policy.
For United States users: HIPAA applies to "covered entities" (health plans, providers, clearinghouses) and their business associates — not to patients documenting their own records. AuthGuard facilitates that patient record-keeping; it is not a covered entity, business associate, or healthcare provider, and does not transmit records to any covered entity.
Because data lives on your device, you control retention completely. To delete all records, delete the app from your device; the data goes with it. If you have iOS device backup turned on, you may also want to remove the AuthGuard data from your most recent backup. There is no copy on any server we operate for us to delete.
The app does not transfer your data internationally because it does not transfer your data anywhere we control. The app is published in English and is primarily marketed in North America.
AuthGuard is a personal documentation tool. The Insurance Glossary, the 12-category denial reason library, the Deadline Engine, and any in-app text about prior authorization rules, appeal levels, or federal and state time limits is general information only. It is not legal, financial, medical, or insurance advice. Consult a licensed advocate, attorney, or healthcare provider for your specific case.
If we ever change how the app handles data — for example, if a future version adds a feature that transmits data to a server we control — we will update this policy and surface the change in the app before you can use that feature. The "Last updated" date at the top of this page reflects the most recent revision.
Settings offers JSON archive export and import. The file includes structured treatment, prior-authorization, denial, appeal, step-therapy, communication, and complaint records. It is readable JSON, not a password-encrypted backup. Attachment-file binaries are not included, so that file alone is not a complete copy of attached PDFs or scans. Import validates the schema and identifiers before adding records. If any imported record identifier already exists locally, the App rejects that archive rather than skipping or overwriting those records. It does not recover missing attachment files. Save attachments separately if you need them. A generated archive can remain in the app's local Backups folder, and any copy you save or share must be protected and deleted at its destination. This user-directed file handling is separate from automatic sync; we do not receive the file.
AuthGuard's widget displays locally prepared summaries of app records. The app and its widget exchange the relevant summary and preferences through an on-device shared container; this is not a developer-operated record upload. Information displayed by a widget can be visible to people able to view the Home Screen or Lock Screen where it is placed. Use the widget and device display settings to control that visibility. Screenshots and independent copies remain separate from the records you later edit or delete.
Privacy questions: captainlongevity@gmail.com
These AuthGuard legal pages are served by Vercel. Opening a page sends ordinary request information, such as IP address, browser information and the requested URL, to the host for delivery and security; see Vercel's Privacy Notice. These pages contain no advertising or analytics scripts. If you email support, we receive the address and information you choose to send to answer your request. Avoid including sensitive records that are not needed for that request.
Treatment and PA deletion creates supported child snapshots as well as the selected parent snapshot. Restoration is record-by-record and may require the original treatment or PA to be restored first; unreadable or ambiguous snapshots are not a guaranteed recovery path. Snapshots contain record fields and attachment references rather than separate original-file backups. Removing a snapshot does not by itself erase every referenced attachment, previously exported archive or Apple backup copy.
Removing an attachment attempts to delete its local file separately from saving the record change. File removal is best effort: it can fail and leave a local file, while a later database-save failure cannot recreate bytes already removed. Permanent deletion or expiry of a Recently Deleted snapshot removes the snapshot record, not a guaranteed purge of every referenced original file. The current implementation has no guaranteed automatic retry or orphan-file sweep. Imported files or scans can also exist before a parent record is saved. Existing exports, backups and recipient copies remain separate.