SSO, MFA, role design, joiner and leaver controls and privileged access are agreed and evidenced before production.
← Trust Centre
Security assurance
Security built as an operating discipline.
Tenvia is being designed for sponsor and CRO environments where access, isolation, provenance and recovery must be clear before a study enters the platform.
Assurance position
Architecture and deployment controls are disclosed at the right level of detail. Public principles sit here. Sensitive evidence belongs in a controlled diligence process.
Control register
What buyers need to know.
Statuses distinguish product direction from commitments and evidence for a specific deployment. They are not certification labels.
Control domainCurrent statusPublic position
Sponsor, study and role boundaries form part of the intended architecture and require technical verification before production use.
Hosting, residency, encryption and key management details are recorded in the security schedule for the selected deployment.
Source, status, rationale, review and approval context are designed to remain attached to consequential study decisions.
Secure development, dependency management, testing and vulnerability response material is confirmed and shared through controlled diligence.
Backup, recovery, continuity, incident contacts and notification commitments are defined before production.
Prospect FAQ
Direct answers for due diligence.
These answers describe the current public boundary. Contracted controls and evidence must match the actual deployment.
Request deeper evidenceTenvia does not currently make either certification claim on this website. Certifications and independent reports will only be listed when achieved, current and available for the relevant service scope.
Evidence room preview
Review sensitive assurance under controlled access.
The index below shows the material a diligence review can request. Scope and availability are confirmed item by item before access is granted.
01Architecture overviewAvailability confirmed in diligenceControlled
02Security testing summaryAvailability confirmed in diligenceControlled
03Incident response overviewAvailability confirmed in diligenceControlled
04Business continuity and recovery evidenceAvailability confirmed in diligenceControlled
05Secure development overviewAvailability confirmed in diligenceControlled
Security and diligence
Request the right level of access.
Start with a public product review. Add confidentiality when the discussion includes sensitive study or security information.
How access works
01Explore publiclyReview the product using fixture data. No NDA is required.02Discuss confidentiallyPut a mutual NDA in place before sharing study material.03Review evidenceReceive controlled access to the relevant assurance material.
Access is granted only after Tenvia confirms the request, confidentiality route and available evidence.