Inspect data handling
Read the stated AWS regions, explanation-processing role, access posture and current certification status. Confirm customer-specific details in the security review.
For Security / compliance
Understand the controls behind the claim.
Know where data goes, how decisions are explained and who can change the system. Start with SENTR’s public security facts, then work through the evidence your deployment needs with our team.
Clear answers make a better risk decision.
Your assessment needs a clear separation between product behaviour, deployment configuration and contractual commitments. SENTR makes that conversation explicit: inspect recorded attribution, review access and data handling, and resolve open controls before production.
Inspect the decision and the system around it.
Explore the capabilities behind the promise, then put them to work on your own questions.
Trace the decision
Stored attribution and human override records support investigation and governance review. The explanation model renders the recorded reasoning; scoring and configured decision policies remain separately inspectable.
Check requirements early
SOC 2 and ISO 27001 certification are in progress and planned to complete before the end of the year. Check current product boundaries against mandatory requirements.
Picture the work in practice.
A focused evidence request
Share a questionnaire or list of required controls with the team. Identify which answers need contracts, architecture detail or supporting evidence.
- Questionnaire / controls
- Contract vs product
- Open items list
- Before production access
A shared evidence list lets engineering, procurement and risk make the same informed decision.
Not your decision alone? Prepare a team brief.
Take the relevant links into your internal discussion. No signup, no email gate. These links use the public website address.
Bring the questions that determine approval.
Bring the question that determines your next decision. Request a focused conversation—or take the evidence links into your team’s discussion first.