Security and data handling
Current public-site posture and pilot roadmap
Hexalveo is early-stage. This page separates current public-site behavior from controls planned for enterprise pilots.
Hexalveo is currently in private MVP development. We are working with prospective design partners to validate decision workflows, domain requirements, and evaluation methods.
Practices
Verified practices and controls still to be documented
No compliance certifications, customer-security approvals, or production-enterprise guarantees are claimed here.
Data isolation
Pilot workspace isolation, tenant boundaries, and access-review procedures will be documented before enterprise pilot onboarding.
Encryption
The public website is designed for HTTPS deployment. Pilot storage and encryption controls will be specified in pilot data terms.
Model providers
Model provider choices and data-processing boundaries will be disclosed to pilot participants before production workflow use.
Data retention
Retention periods for pilot decision data are not finalized on the public site and should be set by pilot agreement.
Training usage
The static public contact form does not transmit data to a model. Pilot data training terms must be documented separately before launch.
Access control
Role-based access, workspace membership, and audit-log requirements are part of the enterprise pilot roadmap.
Incident contact
Report security concerns through the configured launch contact.
Security reports can be sent to the configured security mailbox.