Privacy policy

A VA claim runs on documents that identify you completely: service treatment records, decision letters, personal statements. Ready214 needs none of them. It works from the conditions you name and the dates on your claim, and that is a deliberate design choice, not an oversight. The less it holds, the less there is to lose.

When you upload a decision letter or a photo of a document, the text is extracted inside your browser and used to fill in dates and percentages. The file itself is never transmitted and never stored. There is no file storage in this app at all. Close the tab and it is gone.

Your account through Firebase Authentication, the conditions you track with their diagnostic codes and percentages, claim dates, document checklist status, symptom logs, reminders, daily check-ins, quick notes, and app preferences. New reminder saves keep only a derived title and date with a generic confirmation note. Older reminder excerpts are replaced the next time that account opens. If a screen crashes, an automatic report is filed with the error text (Social Security numbers, phone numbers, and email addresses are removed from it; other text from the screen that failed can remain), the page path, the user-agent string the browser sends (browser, version, and operating system), and your account id when you were signed in. It exists only so a white screen can be traced, and it is not part of the export or the account deletion.

Social Security numbers, phone numbers, email addresses inside your notes, medical records, and uploaded files. Quick notes and symptom logs refuse known identifier patterns and explain why. Planner and check-in text remove those patterns before syncing. Database rules separately enforce the closed account schema and reject sensitive text in every field they can inspect; text nested inside lists receives the app check because database rules cannot inspect it directly. Personal statements drafted in the statement builder are generated in your browser and never saved to your account at all.

Your data is never sold, your health information is never shared with advertisers, and your claim content is never used to target ads. Ready214 makes no claim to be HIPAA compliant, because HIPAA governs healthcare providers and insurers rather than an organizing tool you choose to use, the protection here comes from not collecting the data in the first place.

Your theme and app preferences live in your browser’s local storage. If you continue without an account, your chosen track, claim stage, and confirmed milestone dates also stay there until you clear the on-device plan in Settings or clear this site’s browser data. Firebase Authentication sets a cookie or token so signed-in users stay signed in. The advertising partner sets its own cookies. See below. Ready214 also uses Google Analytics 4 to count visits: which pages are viewed, a rough location (city or region, never a street address), and the kind of device and browser used. That is the whole list, and Google Analytics does not log your IP address. Analytics never sees your claim data, your notes, your conditions, or anything else inside your account, and Ready214 sends it no names, no emails, and no user IDs. To opt out, block cookies for ready214.com in your browser settings, use a tracker-blocking extension, or install Google’s opt-out add-on at tools.google.com/dlpage/gaoptout.

Ads on READY214 are served by Google AdSense. Third-party vendors, including Google, use cookies to serve ads based on your prior visits to this and other websites. Google’s use of advertising cookies (including the DoubleClick DART cookie) enables it and its partners to serve ads to you based on your visit to READY214 and other sites on the Internet. You can opt out of personalized advertising at Google Ads Settings, or opt out of third-party vendor cookies at aboutads.info/choices. Google’s own terms are described in the Google advertising and privacy policy. You can also turn ad personalization off in Settings. You will still see ads, just untargeted.

The site is hosted and served by Cloudflare; your account and data are stored in Google Firebase (Authentication and Firestore). These providers process data on Ready214’s behalf under their own security terms.

Signed-in users can export everything as JSON or permanently delete their account and all data at any time from Settings. Guests can clear their on-device plan and claim-stage dates there without creating an account. Deletion is immediate and irreversible.

READY214 is built for veterans and is not directed at children under 13. It does not knowingly collect information from them.

Questions about your data can be sent to support@ready214.com. READY214 is a small independent project, so replies come as promptly as they can.