DisabilityLog is published by an independent iOS developer (Apple Developer Team ID ZM8LF8494F). For any privacy-related question, write to captainlongevity@gmail.com.
The App does not upload the following to the developer or an analytics / advertising service:
Saved claims, daily logs, appointments and medications use a local SwiftData store in an App Group container. Preferences, onboarding-completion flags, App Lock settings and cached purchase access use on-device UserDefaults. The App also stores dates of completed logging milestones and the last system-review request locally to limit rating prompts. Widget summaries use shared on-device preferences. These are not all stored in the records database. The App does not provide cloud record sync. Some local data may be included in a system device backup; we cannot access those 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.
These features process data locally on your device; paid and free availability is described in the Terms:
The updated App offers an Annual subscription and, when available from Apple, a Lifetime non-consumable purchase using StoreKit 2. Existing valid monthly subscriptions continue to grant access and can be restored. Apple processes payment and sends the App verified transaction information, such as product identifiers, expiry and revocation status, to determine access. The developer does not receive your Apple ID, payment method or billing address through the App. Purchase status is cached locally. Apple handles its services under Apple’s Privacy Policy. Restore Purchases restores access rights, not journal data.
The app does not request Camera, Photo Library, Location, Microphone, Contacts, HealthKit, or any other sensitive permission. You can revoke any permission at any time in iOS Settings > DisabilityLog.
PDF generation uses a snapshot of the active claim, daily logs in the selected Insights period and that claim’s logged appointments and medications, regardless of their dates. The daily timeline includes category notes, symptoms, sleep, activities and medication notes where present; these are user-entered records, not medical findings. CSV exports daily-log fields; the free Markdown export is a summary. These exports omit App preferences and are not restorable full backups. There is no reachable import or journal-restore action.
Generated files are written to the system-managed temporary directory before sharing and are not encrypted with an App-specific export password. The updated PDF exporter uses a distinct filename for each generation and shares only after writing succeeds. A failed PDF write attempts to remove its partial file; cleanup can fail and residual temporary files may remain. The App does not guarantee immediate deletion of completed export files or exported copies. User-selected share / save destinations control their own retention and processing. Restore Purchases cannot recover these files or records.
DisabilityLog 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.
The daily-log, appointment and medication editors provide permanent deletion of the selected record. They do not delete the claim, other independent records or preferences, and there is no Recently Deleted or in-App data-recovery feature. Daily logs and medical records store claim identifiers rather than cascading parent-child relationships; the release interface does not offer a whole-claim or complete-data wipe. After a successful daily-log deletion, the shared widget summary is recalculated, subject to system refresh timing. Existing widget displays or screenshots can remain visible separately. Removing the App through iOS storage controls is separate from deleting records and does not erase user-saved exports, support correspondence or prior device backups. There is no developer-hosted journal copy for us to erase.
The App does not route records through a developer-operated record server. Apple services, legal-page hosting, support correspondence and any sharing destination you choose may process information outside your country under their own policies. Those services are separate from the App’s local record storage. The app is published in English. The seven SSA-3373 categories reference the United States Social Security Administration's Adult Function Report, but the journal and evidence-PDF features work for any user worldwide.
DisabilityLog is a personal documentation tool. It does not provide legal or medical advice, determine disability eligibility, communicate with the Social Security Administration, the Department of Veterans Affairs, or any insurance carrier, or auto-fill any government form on your behalf. All values, conditions, dosages, and statuses are entered, edited, and interpreted by you.
If we ever change how the app handles data — for example, if a future version adds an opt-in cloud backup feature — 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.
DisabilityLog'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 legal pages are hosted on Vercel. Opening a page sends ordinary request information, such as the IP address, browser information and requested URL, to the host for delivery and security; see Vercel’s Privacy Notice. This website request is separate from App record storage. If you email support, we receive the address and information you choose to send so we can respond. Send only the details needed for that request.
The updated App reports claim creation, daily-log upsert and medical-record save failures instead of returning a success-looking record or closing the entry form. A failed daily-log or medical-record delete keeps that record for retry. The daily-log upsert checks the existing entry before changing it and does not treat a database read error as proof that no entry exists. Relevant operation-specific recovery preserves unrelated pending edits. Temporary form values remain available while the form stays open but are not a durable backup. Existing separately stored claim identifiers and independent medical and daily-log records are not converted into a new cascade-deletion scheme.
These save and cleanup changes require the updated App binary. Publishing this document does not update an older installed version.