ServiceArchive Privacy

Effective 2026-05-21. Last revised 2026-05-21.

The premise in one paragraph

Your VA-claim evidence archive lives on your iPhone — service periods, service-connected conditions, witness statements, medical encounters, document scans, HealthKit-derived trend displays, the whole record. There are no ServiceArchive servers. There is no ServiceArchive cloud. There is no analytics ingestion pipeline. The single network conversation the app holds is between your iOS device and Apple's StoreKit endpoints, used to verify whether a Pro subscription is active. Everything else stays where you put it.

Who is publishing this

ServiceArchive is published by an independent iOS developer operating under Apple Developer Team ID ZM8LF8494F. Questions about anything below should be sent to captainlongevity@gmail.com.

What does not leave your device

The following categories of data never reach us, because we operate nothing for them to reach:

• Identity attributes — your name, Social Security number, VA file number, Apple ID, email, phone, date of birth, mailing address
• Service history — branch, component, MOS / rate / AFSC, duty stations, deployments, combat indicators, awards, DD-214 content
• Claim records — service-connected conditions, ICD-10 codes, onset dates, current ratings, claim status, primary and secondary service-connection theories
• Service events — witness names, locations, STR references, lay statements, buddy statements with the names and contact information of the buddies who provided them
• Medical encounter records — provider names, diagnoses, functional limitations, treatment plans, nexus letter quotations, examiner statements
• C&P exam content — pre-exam preparation checklists, post-exam reconstruction notes, range-of-motion measurements, examiner adequacy concerns
• HealthKit reads — heart rate, resting heart rate, HRV, step count, sleep analysis, active energy
• Scanned attachments — DD-214 and STR pages, VA decision letters, completed VA forms, nexus letters, DBQ, IMO, C&P exam reports, photos
• Device identifiers used for advertising (IDFA, IDFV)
• Location data
• Crash reports or analytics events routed to any third party

How on-device processing works

The features that look like they might call out to a server do not. Specifically:

• HealthKit is accessed through Apple's HealthKit framework with read-only permission. Apple Watch metrics that contribute to PTSD-biomarker, sleep-apnea, and mobility-decline displays are read, processed, and rendered entirely on-device. The framework allows ServiceArchive to read — not to write — and the values are never copied off the phone.
• The MOS Presumptive Reference Mapper and the 38 CFR Section 3.310 Secondary Connection Reference Mapper run on bundled reference catalogs derived from publicly available VA regulations. The mapper takes your service-period data as input and produces suggestion output without any network round-trip.
• Document scanning is performed by Apple's on-device VisionKit. The pixels you see in the scan preview are the only place the image exists; nothing is uploaded to OCR a remote service.
• PDF report generation — the five evidence packs (Initial Claim, Higher-Level Review, Supplemental Claim with the 38 CFR Section 3.156(c) one-year window countdown, PACT Act Presumptive, Comprehensive Service Connection) and the VA Form 21-10210 buddy statement PDF — uses Apple's PDFKit. The PDFs are assembled on your device from your local records.
• App Lock calls into Apple's LocalAuthentication framework. Your Face ID or Touch ID biometric data stays in the Secure Enclave; the app only receives a yes/no.
• Local notifications (supplemental-claim window reminders, C&P-exam reminders, etc.) are scheduled through UserNotifications and fire on the device. There is no remote push.

What you grant when you grant a permission

Each iOS permission is requested only when the corresponding feature needs it:

• HealthKit — read-only, requested after you tap “Authorize HealthKit” in Settings or during onboarding.
• Camera — requested when you tap “Scan document” on an evidence row.
• Photo Library — requested when you tap “Import photo” or “Import document”.
• Face ID / Touch ID — requested after you enable App Lock.
• Notifications — requested after you enable any reminder Toggle.

Revoke any of them at any time in iOS Settings → ServiceArchive.

Subscriptions and StoreKit

The Pro tier is offered through Apple's StoreKit 2 in three forms — Monthly auto-renewing, Annual auto-renewing with a one-month free trial, and a one-time Lifetime non-consumable purchase. When you subscribe, when you restore a prior purchase, or when the app silently re-verifies your entitlement, the conversation is between your iOS device and Apple. ServiceArchive itself receives only the binary entitlement state (active or inactive) plus a purchase identifier. Your Apple ID, payment method, billing address, and transaction history remain with Apple under Apple's privacy policy. Subscriptions auto-renew unless cancelled at least 24 hours before the end of the current period, manageable in Apple ID → Subscriptions.

What ServiceArchive will not do for you

Under 38 USC Section 5901, only VA-accredited attorneys, claims agents, and Veterans Service Organization representatives may represent veterans before the VA. ServiceArchive does not represent veterans before the VA, does not file VA forms (21-526EZ, 20-0995, 20-0996, 21-10210, 21-22, and so on) on your behalf, and does not provide legal advice. For accredited representation, look up an attorney or claims agent in the VA Office of General Counsel accreditation database, or contact a VSO — DAV, VFW, American Legion, AMVETS, MOPH, and many others provide free accredited representation.

No AI and no automated VA inference

ServiceArchive does not use artificial intelligence, machine learning, or cloud processing on your veteran, medical, health, or HealthKit data. It does not attempt to predict VA decisions. It does not produce an official combined rating the VA is obligated to accept; the in-app calculator is informational only, intended to show the user where their evidence currently sits against the VA combined-rating table. It does not draft appeal letters and does not promise any claim outcome. The mappers produce reference-only output derived from publicly available VA regulations.

Sharing with third parties

ServiceArchive does not share your records with the VA, the VBA, the VHA, the DoD, the NPRC, or any other U.S. government agency. It does not share with any commercial VA-claims service or law firm (including but not limited to VetClaims.ai, VetClaimGuide, VA Claims Insider, Hill & Ponton, Berry Law, or CCK). It does not share with any VSO, pharmaceutical company, insurance carrier, or research database. There is no advertising SDK, analytics SDK, AI provider, or marketing-data partnership embedded in the app. If a future release ever introduces such an integration, it will be strictly opt-in and disclosed in-app before any data leaves your device.

Retention, deletion, and device backup

Retention is entirely under your control. Records you delete in the app are removed permanently from the on-device store on the next save. There is no in-app trash, no soft-delete window, and no remote copy of your records on our servers, because we have no servers. To wipe every trace of your archive from your iPhone, delete the app. The SwiftData store lives within the app sandbox; deleting the app drops the sandbox. If you maintain an iOS device backup (iCloud Backup or iTunes / Finder), older snapshots of the store may persist in that backup — manage your device backups in iOS Settings.

Children

The app is not directed at children under 13. We do not knowingly collect any information from anyone, including children. The App Store age rating reflects this.

International audiences

ServiceArchive is published in English and is primarily marketed to U.S. veterans. Because we operate no servers, there is no international transfer to disclose.

Changes to this policy

If the app ever changes how it handles your data, this page is updated and the change is surfaced in-app before the affected feature can be used. The “Last revised” date above always reflects the most recent revision.

Contact

For any privacy question: captainlongevity@gmail.com