Pactora Beta
Security
Security practices for Pactora's beta contract review and decision-support service.
Effective date: 7 March 2026
Last updated: 7 March 2026
Security Overview
- Data is encrypted in transit.
- Access is restricted to authorised systems.
- Uploaded documents are processed securely.
- Controls are evolving as the product scales.
1. Security overview
Pactora processes uploaded contracts to extract contract terms and generate structured review outputs. Security controls are applied across this workflow to protect uploaded files, derived outputs, and account data.
2. Encryption in transit
Data sent between your browser and Pactora is encrypted in transit using HTTPS/TLS provided by our hosting stack and service providers.
3. Access controls
Operational access is limited to authorised personnel with role-appropriate permissions. Pactora follows least-privilege access principles and maintains authentication controls for internal systems.
4. Confidential handling
Uploaded agreements are handled as confidential business information and processed to extract terms and generate review outputs. Customers remain responsible for assessing what they upload.
5. Monitoring and response
Pactora uses logs and operational monitoring to detect abuse, investigate incidents, support availability, and respond to security events.
6. Third-party infrastructure
Pactora relies on third-party infrastructure and service providers to run the service. Their controls form part of Pactora's overall security posture. See Subprocessors for provider details.
7. Beta security posture
Pactora is not yet positioned as an enterprise-certified platform. During beta we prioritise pragmatic protections, clear disclosures, and continuous improvement over certification claims.
8. Security contact
For security questions or vulnerability reports, contact contact@pactora.com.
Related pages: Terms · Privacy · Subprocessors