> ## Documentation Index
> Fetch the complete documentation index at: https://docs.pete.vet/llms.txt
> Use this file to discover all available pages before exploring further.

# Sensitive records and compliance

> Practical handling principles for VA disability files, medical records, and case communications.

VA disability work often includes sensitive benefits, disability, medical,
service, financial, employment-impact, and legal information.

Firms remain responsible for their own professional, contractual, and regulatory obligations.

VA API-derived records, VA-connected submission or status data, medical records, and customer case materials are restricted case data. Client data, claimant data, veteran data, and customer case data are not sold, licensed, brokered, or monetized.

The product is not a public veteran directory, marketplace, or open intake front door. Veteran-facing collection or communication surfaces are firm-originated and case-bound.

## Sensitive records

Treat these as restricted case data:

* C-files.
* DD-214s.
* Service treatment records.
* Medical records.
* C\&P exams.
* Medical opinions, DBQs, nexus letters, and other medical-source statements.
* Rating decisions and appeal materials.
* Case notes and client communications.
* Attorney notes and strategy.

## Operational rules

Use approved systems, firm-owned accounts, and case-bound workflows. Do not move sensitive case data into personal email, unsupported AI tools, or informal channels.

Use separate accounts for each firm user, grant the least access needed, and remove access when a person leaves the firm or no longer needs the workspace. Shared logins weaken audit trails and make offboarding harder.

Do not send sensitive case facts through support, status, analytics, screenshots, demos, or public documentation unless the channel has been approved for that data and the disclosure is necessary.

## Legal and professional duties

Pete is not a law firm and does not provide legal advice. Attorneys remain responsible for privilege, confidentiality, supervision, client communication, and the final use of any work product.

Firms remain responsible for determining whether their use of Pete requires client consent, a data processing addendum, data protection agreement, 38 U.S.C. 5701 or 38 U.S.C. 7332 handling, VA accreditation or representative-authority review, bar-rule review, retention rules, or other legal or contractual controls.

Pete documentation describes operating boundaries for the product. It is not legal advice, a compliance opinion, a security certification, or a substitute for the firm's own counsel, compliance program, or professional judgment.