Aurelis Enterprise
Trust Center
Every statement on this page describes what is actually in force today. No aspirational claims, no badges we have not earned.
Security practices in force
- Role-based access control with least privilege: staff roles are denied by default on routes not explicitly granted to them.
- Two-person approval for critical records: rates, form versions, and rules require approvals from two different reviewer accounts before release.
- Tamper-evident evidence ledger: snapshots, proposals, approvals, releases, and key events are recorded in an append-only hash chain that is verifiable end to end.
- API credentials are high-entropy keys stored only as keyed hashes; raw keys are shown once at issuance and never logged.
- Per-key quotas and burst rate limits; immediate revocation; suspension at the tenant level.
- All traffic is encrypted in transit (TLS). Secrets live in environment configuration, never in source control.
- Application error monitoring and audit logging of administrative actions.
Compliance posture, stated accurately
- Our controls are designed to align with SOC 2 and NIST practices. We do not claim SOC 2, FedRAMP, or Section 508 certification, and we will not claim any certification we have not earned.
- Accessibility: public surfaces follow WCAG 2.2 AA practices; a draft Accessibility Conformance Report is available to customers on request, labeled as a draft.
- Legal documents provided during procurement (data processing terms, pilot agreements) are drafts prepared for attorney review.
Privacy architecture: no veteran PII
- The platform is designed so veteran personal information is never required, accepted, or stored.
- Rule evaluation accepts only de-identified policy attributes (for example a rating percentage). Fields that look like identifiers, such as names, SSNs, file numbers, or contact details, are rejected at the schema level with instructions to resubmit de-identified.
- Tenant data is never used to train models and is never sold. Tenant deletion on contract end is part of the standard terms.
Data provenance policy
- Every published fact carries lineage: the official source, a locator describing where in the source it appears, the retrieval date, and the hash of an archived snapshot.
- Government works are public domain and are never claimed as proprietary. What we license is the maintained intelligence layer: temporal organization, validation, provenance, change detection, and delivery.
- Conflicting official sources are recorded as conflicts and flagged for review; they are never silently resolved.
- Records that cannot be verified say so plainly. We publish gaps rather than estimates.
Subprocessors and infrastructure
- Application hosting: Emergent platform (Kubernetes, US region).
- Database: MongoDB.
- Email delivery: Resend. Payments and invoicing: Stripe. Error monitoring: Sentry.
- A current subprocessor list is provided to customers during procurement and updated on change.
Reliability, honestly
- We publish engineering targets to customers under contract rather than public uptime marketing claims.
- We do not display uptime badges, certification logos, or customer counts that we cannot substantiate.
Security contact
Report a vulnerability or request procurement documentation: admin@veteranbenefitdesk.com. We acknowledge security reports and do not pursue good-faith researchers.