Trust
Security & Data Handling
Varethon is being built for serious operational work, with a deliberately narrow data boundary during the Founding Pilot.
Last updated September 9, 2026
Founding Pilot boundary
The current Varethon Founding Pilot is intended for unclassified, non-CUI business and program execution data.
Do not submit
Do not place classified information, Controlled Unclassified Information, passwords, API secrets, private cryptographic keys, export-controlled technical data, regulated health information, or similarly restricted data into the current pilot environment unless Varethon has explicitly approved that use in writing.
Access
Customer command surfaces are designed to sit behind authenticated access. Public marketing, pilot, and trust pages are intentionally separated from authenticated operational workspaces.
Payments and specialized services
Functions such as payment processing may be handed off to specialized third-party providers rather than handled directly inside Varethon.
Security reporting
If you believe you have identified a security or data-handling issue, use the Contact page and include enough non-sensitive detail for the issue to be triaged. Do not include credentials, restricted customer data, or exploit payloads in an initial report.
Future environments
Additional security, deployment, compliance, and data residency requirements may be evaluated separately for future customer environments. The public Founding Pilot should not be interpreted as certification for those environments.