We sell trust. It starts here.
This page answers what your security team will ask: what the platform touches, what never leaves your boundary, how it is protected, and where our certifications stand today. If a question is missing, ask it and we will add the answer.
Your rows never leave.
Your rows never leaving is architecture, not a promise in a clause. Watch what crosses the boundary, and flip the toggle to see the whole platform run inside your perimeter.
As managed SaaS, only metadata, results, and pass/fail counts cross the boundary, encrypted and held under your keys; your rows never do. Flip the toggle to see the other deployment.
What moves, what never does, and who holds the keys.
This is the map your risk, security, and procurement teams keep. The map shows the boundary; the four clusters open with the details, stated the way we state them in writing.
The controls your review expects.
- Your rows never leave
- Only metadata crosses the boundary. Rules run inside your systems and return pass or fail counts, never rows.
- Encryption
- Data is encrypted in transit and at rest, with keys held separately from the data they protect.
- Your keys
- Bring your own keys, including a kill switch that you hold. Revoking the key cuts our access, immediately and provably.
- Access control
- Single sign-on and directory sync, role and attribute based entitlements, and access grants that expire on schedule.
- Supply chain
- Signed releases with a published software bill of materials, and no telemetry that phones home.
- Audit trail
- Every access and action is recorded and exportable to your SIEM in formats your security team already uses.
Where we stand, stated plainly.
We are an early company, and we would rather tell you exactly where our assurance program stands than imply more than we hold.
- Independent certification
- SOC 2 Type II and ISO 27001 certification work is in progress. We will state plainly what is complete and what is not; ask us where we are today.
- Penetration testing
- Annual independent penetration tests, with findings tracked to closure.
- Security questionnaires
- Prefilled SIG and CAIQ responses are returned within five business days.
- Availability
- A 99.9% availability target, with a four hour recovery time objective and a one hour recovery point objective.
- Data processing
- A standard data processing agreement and a published subprocessor list.
- Deletion
- Deletion on exit within a 30 day service level, with a certificate.
Written for the people who sign off.
- Audit rights
- Contractual audit rights and incident notification terms are part of our standard agreement, written for bank procurement and operational resilience reviews.
- Exit terms
- Your graph, rules, policies, and evidence export in open formats, with 90 days of transition help. That is a contractual term, not goodwill.
- Model documentation
- The logic behind trust scoring and derivation ships with documentation your validation team can review. Nothing material is a black box.
- Accessibility
- The product and this site aim for WCAG 2.1 AA. If something gets in your way, tell us and we will fix it.
Start with proof, not a promise.
There are three ways in, and each one earns the next. You approve the exit criteria before we spend any more of your time or budget.
A 60-minute working session
Bring one report that is expensive to prove. We walk the mechanism against it. Nothing is required from your side.
A two-week guided sandbox
Your team works hands-on against a synthetic sample bank. It requires zero access to your systems and zero procurement.
A six-week proof on your systems
We use read-only metadata across five systems and one priority report, scored against criteria both sides sign first. The decision it produces is yours.