onshore
Products / Core

When the auditor asks, show the record, not a slide.

Every access writes an append-only, hash-chained entry saying who asked, for what, why, and what they got. Reports are computed from that log and never from a separate counter.

Audit log Log intact
09:41:07Ada O.Revealed BVNa41f…
09:40:52Tunde B.Viewed masked NUBAN7c02…
09:38:15svc-loansTokenized 240 valuese9b1…
09:36:44Musa K.Reveal refused03dd…
09:31:02Ngozi E.Published policy v35fa8…
The problem

Saying where your data lives is easy. Showing who touched it, and that nobody altered the record, is the hard part.

How it works
01

Record every access

Each reveal, denial, export and policy change adds an entry that holds no sensitive value.

02

Chain the entries

Each entry includes the hash of the one before, so a change anywhere breaks the chain.

03

Export the proof

Download signed reports, verify the chain, or stream events into your own SIEM.

What's included

Who saw what

Filter by person, action, field, result, network and time.

Signed checkpoints

The log's position is signed daily. Add a SIEM copy to cover the time between checkpoints.

Residency reports

See which data types were caught on the way to each destination, before and after you turned on protection.

Person-level history

Open a person's record and see each access, with the reason given.

SIEM export

Send events to your own tools as they happen.

Webhooks

Get a signed event when a value is revealed or an access is refused.

Reports give you evidence to work with. Whether that evidence satisfies a regulator remains a question for your compliance team and counsel.

Who uses this

Start with one leak.

Tell us which flow worries you most. We'll show you what it would take to keep it onshore.