Skip to content
Security by design

Protect every source and investigation boundary.

ReturnValue treats financial evidence as sensitive by default, with tenant isolation, least-privilege access, traceable actions, and explicit human control built into the platform.

Evidence-grade intelligence · Human validation · Traceable decisions
Security / evidence viewIllustrative view
protected evidence perimeter
Evidence protectedtenant · identity · policy
Access evaluatedleast privilege
Action recordedreviewable outcome
  • IsolationTenant by design
  • AccessLeast privilege
  • EvidenceEncrypted and traced
  • ActionsAuditable end to end
The ReturnValue approach

Security follows the evidence everywhere it moves.

Controls apply from intake through calculation, investigation, approval, export, and retention—without depending on users to rebuild context later.

01

Constrain access

Identity, tenant, role, and resource boundaries determine who can see and act on evidence.

02

Protect the record

Encryption, provenance, versioning, and tamper-evident history preserve the integrity of investigation work.

03

Make action visible

Material reads, changes, approvals, exports, and administrative actions remain reviewable.

Security model

Architected, not marketed.

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.

Workspace isolation
Workspaces are logically isolated with strong access controls and scoped data boundaries. Access does not leak between workspaces by default.
Scoped access
Access is granted per resource, designed around least-privilege defaults rather than broad organization-wide grants.
Audit trails
Core activity events are captured as part of platform workflows, with timestamps for review and traceability.
Traceable conclusions
Insights, datasets, and exports stay linked to the inputs that produced them, so claims can be traced back through joins and transforms to source.
Connected investigation

A control system, not a security appendix.

ReturnValue makes protection and accountability part of the daily investigation path rather than a separate layer teams must remember to use.

  1. 01IdentifyUser verified
  2. 02AuthorizeScope evaluated
  3. 03IsolateTenant enforced
  4. 04ObserveAction recorded
  5. 05ReviewControl evidenced
Evidence in context

Clarity at every decision point.

Sensitive financial work is safer when the secure path is the normal path.

Illustrative view. Values shown are examples, not customer data.

Security posture

Controls healthy
4/4

Identity · isolation · protection · audit

See ReturnValue in your environment

Follow your first financial signal.

Security | ReturnValue.ai