Your Data Security is Our Priority
We use managed infrastructure controls and application safeguards that are documented, reviewed, and strengthened as the platform matures.
Encryption In Transit
- Reviewed application configuration enables HTTPS redirects and HSTS. Vercel provides certificate and transport controls at platform level; this configuration review does not verify a particular live deployment.
Encryption At Rest
- Managed encrypted storage for application data and documents
- Managed cloud providers with documented security programs for core infrastructure
- Sensitive credentials and tokens are protected using encrypted storage and access controls
- SSN partial redaction (only last 4 digits stored)
- Operational backups and retention controls are handled through the platform data layer and hosting providers
Access Control Approach
Access to sensitive application data is designed around least-privilege and role-based controls. Logging coverage is reviewed by control area rather than described as universally complete.
When you type in chat on the web, ValorAI runs a privacy filter directly on your device. Detected names, Social Security numbers, street addresses, phone numbers, email addresses, and other personal identifiers are replaced with reversible placeholders (for example [SSN_1] or [GIVEN_NAME_1]) before your message leaves the browser. This filter runs on every message by default, but detection is not guaranteed. Review your message before sending sensitive details.
How it works
- Redaction happens client-side, in your browser, before any text is transmitted to the AI model
- The original values stay in a temporary table on your device and are restored into the assistant’s reply only when it is shown back to you
- Broad geography (city, state, ZIP) and public links such as va.gov pages are kept so the assistant can still reason about eligibility
- If the on-device model cannot load, a pattern-based fallback still strips structured identifiers (SSNs, card and phone numbers, emails) and names that follow a self-identification cue (for example “My name is …”). Names written in a narrative without a cue may still be sent; the server applies the same fallback again
- In the ValorAI mobile app, Valor's servers remove identifiers like your SSN, VA file number, phone, email and date of birth, plus your own name when you're signed in, before text is sent to Grok (SpaceX Super Intelligence). Names of other people may not always be caught.
Health Data Safeguards
Built with safeguards that support protection of sensitive health-related information, including encryption, access controls, audit logging, and least-privilege access patterns.
Privacy Rights Workflows
Our policy targets processing account deletion requests within 30 days for covered active account and workflow data. Limited records may remain for unsubscribe suppression, legal acceptance, financial reconciliation, security and dispute obligations. Backups remain until overwritten under platform retention controls; deletion from active data is separate from backup expiry and provider processing.
Transparent Data Handling
We do not sell personal data. We support user privacy rights and provide clear data collection disclosure and opt-out mechanisms.
Federal Security Alignment
Internal controls are being aligned to NIST 800-53 security control patterns. The VA integration path is being prepared to support federal review expectations.
SOC 2 Readiness
We are working toward SOC 2 readiness while relying on security-reviewed infrastructure providers today.
User Authentication (Clerk)
- Multi-factor authentication (MFA) support
- Social sign-in (Google, GitHub) with OAuth
- Email/password authentication with strong password requirements
- Session management with automatic timeout
- Account lockout after failed login attempts
VA.gov connection (not live in production)
- Official production VA.gov Lighthouse OAuth is not available to veterans yet. You do not need a VA.gov login to start prep.
- Personalize today with a DD-214 or decision letter. You still file on VA.gov or with accredited help.
- Sandbox OAuth (PKCE, encrypted tokens, TLS) exists for operators and demo fixtures only, not as a consumer Connect path.
- When production access is approved, disconnecting will clear app-side VA connection state.
Role-Based Access Control (RBAC)
- User roles: user, admin, support
- Principle of least privilege
- Audit logging on implemented security-sensitive paths
Data Minimization
We only collect data necessary for functionality:
- Sensitive records are protected using encrypted storage to support disability claims and benefits analysis
- No storage of financial account details
- SSN partial redaction (***-**-1234 format)
- PII minimization throughout the platform
- Health data used solely for VA benefits assistance, never for clinical decisions
Health Information Notice
Important: This service is for educational and informational purposes only, not for clinical decisions. ValorAI is not a healthcare provider.
Your Data Rights
- Access: View all information we have about you
- Delete: Request deletion of covered personal data, subject to the exceptions described in our Privacy Policy
- Export: Download a copy of your data in portable format
- Modify: Update or correct any information
- Disconnect: Revoke VA account access at any time
Data Sharing Practices
We do not sell your personal data. We only share data with service providers necessary to operate the platform, subject to contractual privacy and security safeguards. Our business model is built on subscriptions, not data monetization.
No-training policy
ValorAI policy prohibits using uploaded veteran documents and VA-connected records for model training. New application-side training-content capture is suspended, and optional sharing consent is off by default. This describes application policy and reviewed implementation. Inference processing is subject to applicable provider terms and configured controls; these are distinct from internal training capture. Suspending new capture does not by itself delete previously retained records.
Monitoring scope
- Application error tracking with Sentry where configured
- Rate limiting on documented public and protected routes
- Dependency, code, and source review
- Security-event logging on implemented paths
- Hosting-provider monitoring and mitigation controls inherited from managed providers
Incident Response Plan
Our incident response process is documented and continues to be formalized around:
- Detection and alerting paths where configured
- Severity classification system
- Containment and eradication procedures
- Escalation and notification procedures for high-severity incidents
- Post-incident root cause analysis
Security Reviews
We use code review, dependency review, targeted security testing, and documented follow-up to identify and address weaknesses. The scope and date of each review are tracked internally.
ValorAI isn't a Silicon Valley project chasing a quick exit. It's a mission-first platform built by veterans, for veterans. Every decision we make is filtered through one question: Would I trust this with my own file?
We're building ValorAI in the open. Veterans in our early user group help shape features, vet our decisions, and hold us accountable. You're not handing your data to a faceless app. You're trusting a veteran-built product that stays close to the people it serves.
ValorAI documents application controls for HTTPS, access patterns, logging coverage, and privacy-focused data handling. Some infrastructure controls are inherited from managed providers. Our framework alignment work remains in progress and is not a certification.
ValorAI policy prohibits using uploaded veteran documents and VA-connected records for model training. New application-side training-content capture is suspended, and optional sharing consent is off by default. This describes application policy and reviewed implementation. Inference processing is subject to applicable provider terms and configured controls; these are distinct from internal training capture. Suspending new capture does not by itself delete previously retained records.
Questions About Security?
If you have security concerns or questions, please contact us:
Email: security@tryvalor.ai
For security vulnerabilities, please include "SECURITY" in the subject line.
Last updated: October 11, 2026
