Trust center
How SESA handles project information, protects access, and keeps people responsible for every requirement decision.
- SESA claims no ownership of project content.
- Project content is never used to train models.
- No requirement closes without a person's review.
How SESA handles your data
These are SESA's published commitments. The linked policies provide the full terms for each area.
Data & privacy
Your organisation directs how its project content is used in SESA.
Your content stays yours
Your organisation retains the rights it has in project content and the requirement records built from it. SESA claims no ownership and uses that content to provide the service to your organisation.
Read policy: Your content stays yoursConnected systems
Your team authorises each connection. SESA reads the agreed records needed to match evidence. Removing a connection stops new reads.
Read policy: Connected systemsRetention and deletion
Our terms provide a 30-day export window after termination, followed by deletion or anonymisation subject to required retention and any different signed agreement.
Read policy: Retention and deletionPrivacy rights
People can request access to, correction of, or deletion of their personal information where applicable. Requests about project content go through the customer organisation that controls it.
Read policy: Privacy rights
Security controls
The published controls for protecting project records and limiting access.
Encryption
Project records are encrypted in transit and at rest.
Read policy: EncryptionAccess and audit
Access is role-based and limited to what each role needs. Access is logged and auditable, and internal access is reviewed.
Read policy: Access and audit
AI & human review
Automated analysis supports a review decision made by your team.
No model training
Project content is not used to train, fine-tune, or improve models, or to serve another customer. Providers processing that content are bound by the same restriction.
Read policy: No model trainingHuman approval
SESA proposes requirement matches. A person on your team accepts, rejects, or reassigns them. No requirement closes automatically.
Read policy: Human approvalSources you can inspect
Requirements cite their source clauses and proposed matches cite supporting documents so your team can review the result.
Read policy: Sources you can inspect
Documents & contact
Read the public policies or contact us with a security review.