VΦRDIS · Security
Trust requires evidence.
Vordis applies the same discipline to its security posture that it expects from intelligence work: clear boundaries, limited claims, documented evidence, and accountable human review.
Security overview · Beta and pilot stageSecurity at the current stage
Vordis is currently in beta and does not claim certifications, audit coverage, or enterprise controls that have not been independently completed. Security requirements for a pilot will be defined before data access or integration begins.
Design priorities
The product roadmap prioritizes data minimization, explicit evidence boundaries, role-appropriate access, separation of observations from assessments, traceable analyst actions, and retention aligned with the purpose of each engagement.
Pilot and partner data
No organization should send confidential, restricted, regulated, or production data until scope, authority, handling requirements, approved transfer methods, retention, and deletion expectations are documented in writing.
Responsible disclosure
To report a suspected vulnerability, email contact@vordis.ai with the subject “Vordis security report.” Include the affected page or component, a clear description, safe reproduction steps, and potential impact. Do not include unnecessary personal or confidential data.
Research safety
Please avoid privacy violations, service disruption, social engineering, destructive testing, accessing data beyond what is necessary to confirm an issue, or publicly disclosing an unresolved report. Vordis will review good-faith reports and coordinate next steps as practical.