Browser-local records

For privacy or data-rights assistance, contact support@veteranmissioncontrol.com. Describe the help you need without sending Social Security numbers, medical records, claim evidence, or backup files by email.

Calculator inputs, conditions, dependents, SMC designations, historical scenarios, payment records, award attribution, planning records, service-identity overrides, activity history, accessibility evidence, and pre-restore safety copies use browser storage.

Portable JSON backups and browser-native PDF reports are created locally. They may contain sensitive veteran, medical, dependent, claim, payment, and planning information and are not encrypted by VMC after download.

Clearing browser storage, private-browsing data, or the browser profile may remove these records. Use Data & Backup for reviewed export and recovery.

Native iOS and Android apps

The VMC native apps use this page as their public privacy-policy URL. Each Apple App Store and Google Play submission must describe the actual behavior of the version being submitted and remain consistent with this policy.

Native VMC features are expected to follow the same local-first principle as the website. Device permissions must be requested only when a feature actually needs them, and permission to use a device capability does not authorize unrelated collection, advertising use, or transmission of Veteran disability, medical, claim, document, payment, or profile information.

A native feature that would introduce a new category of collection, cloud storage, third-party processing, analytics, advertising, or cross-device transmission is not approved for release until its data flow is reviewed and this policy and the applicable store privacy disclosures are updated.

VMC does not sell Veteran personal information and does not authorize use of Veteran disability, medical, benefits, claims, documents, ratings, SMC, TDIU, P&T, dependent, or payment information to build advertising audiences.

Operator and advertising boundary

Veteran Mission Control is developed and operated by BiloxiKingHoldings, LLC and is an independent veteran-built platform. It is not affiliated with or endorsed by the Department of Veterans Affairs, Department of Defense, or any Military Service.

VMC publishes its Google AdSense publisher authorization in the root ads.txt file and may publish the corresponding google-adsense-account verification metadata so Google can verify site ownership. These public verification identifiers do not, by themselves, load Google advertising code, create an ad request, or place an advertising cookie.

Google ad-serving code remains disabled until the site is approved, VMC's explicit production enablement gate is turned on, and the required consent, security, and document-isolation controls are active. VMC does not authorize automatic advertising across the application.

If advertising is activated, the initial advertising allowlist is limited to the queryless, fragment-free public User Guide and the bare public VA Diagnostic Codes catalog. Private, personalized, administrative, document, claims-management, calculator, payment, profile, symptom, clinical-record, report, and other sensitive Veteran workflows remain ad-free.

If ad serving is activated, third-party vendors including Google may place and read cookies on a visitor's browser, use web beacons, process IP addresses, or use other identifiers as a consequence of ad serving. Google's advertising cookies may be used to serve ads based on a user's visits to VMC and/or other sites, subject to the user's choices and the applicable ad-serving mode. VMC's application policy is to request non-personalized ads only and not to build advertising audiences from Veteran disability, medical, benefit, claim, document, or profile information. The initial VMC advertising release authorizes Google AdSense only; no separate third-party ad network is approved. Users can control personalized advertising through Google Ads Settings and can review how Google uses information from sites that use its services.

Non-personalized ads can still use cookies or similar identifiers for purposes such as frequency capping and aggregated ad reporting. Where consent is legally required, VMC must keep advertising requests blocked until the applicable consent or privacy choice is collected. European, UK, and Swiss consent and applicable U.S. state privacy choices must be configured through the approved consent-management controls before ad serving is enabled.

VMC does not intentionally provide Veteran disability conditions, medical information, ratings, SMC, TDIU or P&T status, dependents, payment history, claims, documents, extracted text, report contents, free-text notes, account identifiers, or authentication information to Google advertising systems. VMC does not build personalized advertising audiences from Veteran disability, medical, benefit, claim, document, or profile information.

Privacy-preserving product analytics

When production analytics is enabled, VMC may measure sanitized route templates, public Knowledge Base content identifiers, body-system keys, coarse feature actions, campaign or organization-level referral tags, generic file type categories, bounded technical-failure categories, and aggregate performance information.

VMC also uses Metricool on the production website for aggregate traffic measurement. Metricool records the page viewed and derives visitor country from the connection IP; its website tracker does not use cookies. Metricool is limited to an explicit public route allowlist. The local dashboard, calculators, claims, profile, symptoms, medical-code lookup, documents, evidence, reports and recovery pages are private and are not tracked. Administrative, authentication, test, unknown, or arbitrary pathnames are not tracked.

Pages with functional, search, email, document, claim, or other unapproved query parameters are not tracked by Metricool. When a landing URL contains only approved, bounded campaign or partner tags, those query tags are removed before Metricool loads. Metricool therefore receives only the approved queryless page path rather than the campaign values.

A page containing any URL fragment is not tracked by Metricool, because fragment text can carry arbitrary page-local data. The provider is loaded only for an eligible allowlisted, queryless, fragment-free page view and is removed again afterward so later navigation is evaluated independently. Crossing between public reference pages and private case tools opens a fresh document before the destination tools can read local case storage. Public reference pages do not mount the calculator storage provider.

The approved analytics design does not send your condition list, disability percentages, SMC, TDIU or P&T status, dependents, payment history, scenario names, report contents, document names or contents, extracted text, free-text notes, raw search queries, email address, account identity, claim identifiers, authentication secrets, or other Veteran benefit facts to the product-analytics provider.

VMC does not use session replay, keystroke capture, DOM recording, advertising pixels, or a persistent VMC analytics user identifier in this analytics foundation. Viewing a public diagnostic-code page is treated only as interest in public content and is not interpreted as evidence that a visitor has that diagnosis.

Campaign and VSO/partner attribution is organization- or campaign-level only. Partners do not receive Veteran diagnoses, ratings, documents, calculations, individual browsing histories, or other private benefit information through this analytics system.

Development and preview separation

Post-UAT development and preview deployments are kept separate from production analytics. Production analytics transmission is fail-closed outside the approved production environment, and preview/development traffic is not treated as normal production product usage.

Archived testing infrastructure and historical test records are not part of the active production analytics path and must not receive copied production Veteran workspace data.

Controlled local sharing

Reports includes a Controlled local share foundation for activated V3 cases. You choose exact shareable items, see the full selected payload and every available item you did not select, identify the intended recipient and purpose, and then deliberately download a local JSON copy. VMC does not upload, email, message, or otherwise transmit that bundle and does not create a recipient account or access grant.

Controlled Sharing v1 hard-excludes original document bytes, document/OCR narrative and captured decision excerpts, Veteran-authored draft or form bodies, credentials and secrets, recovery/backup artifacts, private activity history, and unverified suggestions. The downloaded JSON is unencrypted and unsigned. Once a copy leaves VMC, VMC cannot remotely revoke, delete, expire, or control that independent copy; protect and deliver it deliberately.

Choosing “Representative / VSO,” a health care provider, a family/support person, or another recipient records only your intended handoff label. It does not verify identity, accreditation, appointment, clinical role, authorization, disclosure permission, or legal authority. Future cloud collaboration, share links, provider delivery, recipient workspaces, and remote revocation remain separately gated.

Prohibited transmission

VMC does not approve calculator facts, condition names, ratings, payment records, report contents, backup bytes, document text, claim identifiers, authentication secrets, or personal information for product analytics, advertising, session replay, public URLs, source control, or unrestricted logs.

Any future document processing, email integration, encrypted cloud storage, AI service, advertising activation, or collaboration provider remains subject to its approved architecture, minimum-necessary data review, retention and deletion rules, consent analysis where applicable, and accurate privacy disclosure before activation.

Privacy questions and rights

For privacy, data-rights, or app-store privacy questions, contact support@veteranmissioncontrol.com. Please describe the request without emailing medical records, claim evidence, Social Security numbers, VA file numbers, passwords, or VMC backup files.

Because core Veteran workspaces are local-first, VMC may not possess a server copy of information stored only in your browser or device. The Data & Backup tools are the primary way to review, export, restore, or clear those local records.

Open the VMC Support Center for product support, app-store support, and issue-reporting options.