Privacy policy and terms for the VetClaim app
Last updated: 22 August 2026
Your claim information — your conditions, your ratings, your dates, your dependants and your payment figures — never leaves your device. There is no account, there is no server holding your claim, and there is no way for us to look yours up.
The app does send two things, and only two: anonymous crash reports, and anonymous counts of which features get used. Neither one carries your claim information. Exactly what is in them, and what is not, is set out in What we collect.
That is not a promise about our intentions. It is a property of the build, and you can check it yourself — see How to verify this below.
Of your claim: nothing. We never receive your ratings, your conditions, your claim dates, your dependants or your payment figures. There is no account to create and no email address to give us.
Of diagnostics: two narrow things, so that faults get found and fixed rather than silently suffered.
| What is sent | What is never sent | |
|---|---|---|
| Crash reports | the error, where in the code it happened, the app version, the device model and OS version | screenshots, the contents of the screen, your claim data |
| Usage counts | that an event happened — for example “a condition was added”, “a rating was calculated”, “the summary was shared” — and that the app was opened or closed | which condition, what rating, what amount, or any other value you entered |
The events are built to carry a name and nothing else. “A condition was added” is recorded. “PTSD at 70%” is not, and cannot be, because no value is ever attached to an event.
Nothing identifies you. We do not send your name, and we have no account to attach anything to. Each installation gets a random identifier so that two reports from the same phone can be recognised as related. It is not linked to your identity, and reinstalling the app replaces it.
No advertising, no tracking, no brokers. None of this is used for advertising, sold, or combined with data about you from other apps or companies.
Everything you enter, and only on your device:
| Stored | Not stored |
|---|---|
| Condition names and percentages | Your Social Security number |
| Diagnostic codes and effective dates | Your VA file number or EDIPI |
| Claim stages and deadline dates | Your date of birth |
| Which limb a condition affects | Your address |
| Counts of dependants | Dependants’ names or dates of birth |
| Your display name, if you choose to enter one | Bank or payment details |
The fields in the right-hand column are not “collected and protected”. They do not exist as properties anywhere in the app’s data model, so there is no code path that could store them even by mistake.
Dependants are stored as counts only — “one spouse, two children under 18” — because that is all the compensation tables need.
Android. The database file is encrypted with SQLCipher (AES-256 page encryption, HMAC page authentication). The passphrase is generated once from a cryptographically secure random source and sealed with a key held in the Android Keystore, marked non-exportable so the raw key material cannot leave the device’s secure hardware. Only the sealed blob is written to storage. Copying the database file off the device yields ciphertext.
iOS. The database file is protected with iOS Data Protection at the
completeUntilFirstUserAuthentication class, so it is encrypted by the operating system with
a key derived from the device’s hardware identifier and your passcode. This is a different
and weaker mechanism than the Android one: it defends a powered-off or freshly booted
device and physical extraction of the storage chip, but not a running device that has been
jailbroken. Application-level encryption on iOS is planned. We would rather tell you the
difference than describe both platforms with one comfortable sentence.
The app can generate a plain-text summary of your claim to hand to a Veterans Service Officer. That summary is passed to your device’s own share sheet. We do not upload it. Where it goes next is entirely your choice — email, messages, a printer, a file. There is also a “Without my name” option that removes your display name from the summary.
The crash reports and usage counts described above are handled for us by two services. They act only on our instructions, and they never receive your claim information, because it is never sent.
| Service | What it handles | Where it is processed |
|---|---|---|
| Sentry | crash reports | European Union |
| PostHog | anonymous usage counts | European Union |
No one else receives anything. We do not sell data, and there is no advertising network in the app.
Removing a condition moves it to a trash that holds it for 30 days, so a mis-tap is recoverable. After 30 days it is purged.
To delete everything, use the app’s delete-everything function. On Android this discards the Keystore key as well as the file. That matters: deleting rows from a database leaves recoverable pages behind, whereas destroying the key makes the remaining bytes unreadable by anyone, including us. There is nothing for us to delete on our side, because we never had it.
Uninstalling the app also removes its data, as with any app.
VetClaim is intended for veterans and is not directed at children under 13.
Some of what you enter — diagnosed conditions, disability percentages — is health-related. It is stored under the protections described above and is never transmitted. VetClaim is not a covered entity under HIPAA and does not exchange data with any covered entity.
VetClaim is an independent tool. It is not affiliated with, endorsed by, or connected to the U.S. Department of Veterans Affairs or any government agency. It cannot file a claim, check the status of a claim, or represent you. Only a VA-accredited representative may represent a veteran before VA for a fee (38 CFR 14.629).
The figures the app produces are informational estimates calculated from the published rating schedule (38 CFR Part 4) and the published compensation tables. Your award letter is the authoritative record. Always check it, and talk to an accredited Veterans Service Officer — their help is free.
If this policy changes we will update this document and the “last updated” date. Because your claim data lives only on your device, any change to how it is handled would require a new app release, which you would have to install — we cannot change it remotely.
You do not have to take our word for the central claim.
INTERNET, and that exists only for the crash and usage reports above. There is
none for your contacts, your files, your location, your camera or your microphone — open the
app’s entry on Google Play and read the list. (The build also carries an app-internal
permission generated by Android’s own support libraries, named after the app itself. It is
signature-level, it lets the app talk to its own components, and it grants nothing to anyone
else.)Questions about this policy can be sent to the contact address on the app’s store listing.