Constrain access
Identity, tenant, role, and resource boundaries determine who can see and act on evidence.
Controls apply from intake through calculation, investigation, approval, export, and retention—without depending on users to rebuild context later.
Identity, tenant, role, and resource boundaries determine who can see and act on evidence.
Encryption, provenance, versioning, and tamper-evident history preserve the integrity of investigation work.
Material reads, changes, approvals, exports, and administrative actions remain reviewable.
Security marketing is full of badges. We are deliberately not running that play. The teams ReturnValue is built for evaluate software the way a security team would: they look at how it operates, where the boundaries are, what is recorded, and what happens when a decision has to be defended later.
ReturnValue is shaped around that evaluation. The workspace is the unit of isolation. Access is scoped per resource on top of role. Audit trails are built into core platform workflows, not a feature your team has to wire up. Conclusions stay linked to the inputs and joins that produced them, so the path from source to claim is observable instead of reconstructed.
We are deliberate about the language we use. Where a control is in place, we describe what it does. Where readiness work is still in progress, we say so. ReturnValue is designed to use encryption in transit and encrypted storage across core systems, with platform-managed key practices. Compliance support is designed to help teams prepare; specific certifications are claimed only when issued.
ReturnValue makes protection and accountability part of the daily investigation path rather than a separate layer teams must remember to use.
Sensitive financial work is safer when the secure path is the normal path.
Illustrative view. Values shown are examples, not customer data.
Identity · isolation · protection · audit