InfusionLog 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 only on your iOS device using Apple's SwiftData framework. The app does not use Apple's CloudKit framework, does not sync records across your devices, and does not maintain any copy of your data on a server we operate.
Your data may be included in your standard iOS device backup if you have device backup enabled (iCloud Backup, iTunes, or Finder). We do not have access to your device backups. We recommend keeping device backup on to support possible recovery through the system Restore flow on a lost or replaced phone.
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.
InfusionLog does not request, store, or use your specialty pharmacy login credentials. The app does not connect to any specialty pharmacy API, portal, fulfillment system, claims system, or pharmacy benefit manager. All shipment, breach, call, and missed-dose information is entered by you (typed or photographed). This is by design — many of our users are mid-dispute with the pharmacy they would otherwise be asked to log into.
The app does not run any artificial-intelligence or machine-learning model on your shipment receipts, cold chain photos, provider documentation, or call summaries. There is no OCR text extraction, no document parsing, no automatic categorization, and no complaint-letter generation. You read the documents; you enter the values; you write the complaint. We make no decisions about your case.
These features process data locally on your device; paid and free availability is described in the Terms:
InfusionLog uses Apple StoreKit for a yearly 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; InfusionLog does not receive your payment-card details or Apple Account password. Current and supported historical purchase access depend on verified transactions. See the InfusionLog terms for the available plans and subscription handling.
You can revoke any of these permissions at any time in iOS Settings > InfusionLog.
InfusionLog does not record phone calls. The Customer Service Call Log allows you to attach an audio file you recorded yourself; the app simply stores the file path. You are responsible for compliance with your state's call-recording laws. Some U.S. states require two-party consent for recording; the in-app field surfaces a notice to that effect.
InfusionLog is designed to be used by adults — patients managing their own specialty medication regimens or family caregivers (for example, a parent managing a child's cystic fibrosis or hemophilia infusions). The app has no child account or developer-operated record collection. Contact support if a child has sent personal information to us. The records you enter live on your device and (optionally) in your private iCloud account; we never receive them.
For United States users: HIPAA applies to "covered entities" (health plans, providers, clearinghouses) and their business associates — not to patients documenting their own records. InfusionLog 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.
Deleting a pharmacy also deletes its linked shipments, SLA breaches, calls and missed-dose records after a successful save. Separate document-vault records remain, and the parent cascade does not guarantee cleanup of referenced attachment files. Direct shipment or vault-document deletion attempts file cleanup separately after saving; editors can remove old files before a later save. Failed cleanup can leave files, and a failed save cannot recreate an already removed file.
Removing the App normally removes its local container, not independently kept original media, exported files, recipient copies or older backups. Manage those copies separately. Device-backup recovery requires a usable completed backup; the developer has no record archive to retrieve.
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.
InfusionLog is a personal documentation tool. The Specialty Pharmacy Catalog, the 11-category SLA breach library, complaint-pack templates, and any in-app text about state insurance commissioner procedures, ASHP / URAC accreditation processes, or call-recording state laws 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.
InfusionLog'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.
Archive import skips each existing matching record identifier without updating that record, while missing child records can still be added under an existing parent. Embedded files are processed separately before record writes: missing safe paths may be restored even when their record is skipped; an existing file at the same path is kept without replacing or verifying its contents against the archive. A failed import rolls back database changes and attempts removal of newly written files. File rollback is best effort and can leave residual files; record and file changes are not one atomic operation. Exports include only the original files that were available when generated, not a guarantee of every earlier attachment.
Privacy questions: captainlongevity@gmail.com
These InfusionLog 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.
The updated App pauses the normal record interface if its persistent database cannot be opened and only a temporary in-memory store is available. New recording and editing through that interface are blocked. The App keeps the existing database and attachment files rather than treating the temporary empty store as your archive. Database-dependent startup work in that interface is paused; previously scheduled reminders, widget snapshots or independent copies may remain.
Check available device storage, close and reopen the App, and contact support before deleting or reinstalling it. This recovery screen is not a backup, a repair guarantee or an automatic restoration of missing records. Older installed versions may behave differently until updated.