Trust center
Trust documents in one place.
A single public hub for the policies, controls, and operating signals teams need before they paste code into Sensei.
Last updated · October 22, 2026
Privacy
Code-first
Customer code is not used for model training
Data rights
Export, delete
JSON export and account deletion from Settings
Status
Public
Service components and issue reporting at /status
Program
Trust pillars
Sensei separates trust into clear surfaces: security controls, privacy commitments, reliability status, and legal documentation.
Security posture
Controls for protected sessions, scoped data access, key separation, and secure API boundaries.
Privacy and data rights
Plain-English privacy commitments, data retention, export, deletion, and third-party processing.
Reliability
The service components (web app, analyzer API, authentication, and storage) and how to report an issue.
Legal documents
Terms, DPA, acceptable use, cookie policy, and sub-processor documentation.
Posture
Current posture
These signals describe how Sensei handles data today. Enterprise-specific reviews can be handled through the contact path.
Row Level Security
Scoped data access
In real mode, database policies return only the rows that belong to the signed-in user, so one account cannot read another account's analyses.
Data rights
Privacy alignment
Policies are structured around access, export, deletion, sub-processor transparency, and data minimization.
No training
Code handling
Customer code submitted for analysis is not used to train foundation models or sold to third parties.
Documents