onshore
Products / Core

Same record. Different answer for each person.

A policy looks at who is asking, for which field, from which network, at what time and for what stated purpose. The answer is the real value, a masked one, the token, or no.

Who sees this BVN?support-agents@v3
PersonGetsResult
Support agent*******6789Masked
Fraud analyst22123456789Real value
Data teamtok_bvn_7Hq2…Token only
Contractor—Denied
Purpose requiredApproved networks200 reveals an hour
The problem

Most insider exposure comes from staff who can see everything because nobody could express anything narrower.

How it works
01

Default deny

With no policy allowing it, the answer is no.

02

Build the rule

Each rule has four parts: who, what, when and what it returns.

03

Publish with review

Changes can go through a second person, and every version is kept.

In code

A policy, as admins read it

policy "support-agents-nigeria" v3
  allow DETOKENIZE on fields[bvn, nuban]
    when role == "support_agent" and network in approved_ng_networks
    return MASKED
  allow DETOKENIZE on fields[phone_ng]
    when role == "support_agent" and purpose is set
    return PLAINTEXT
  limit 200 reveals per user per hour
What's included

Four outcomes

Plaintext, masked, token only, or denied, decided per caller and field.

Purpose required

A person can be made to state a reason or ticket number before a value appears.

Approved networks

Limit reveals to your office ranges, VPN or private links. Location is recorded, not trusted.

Rate limits

Cap how many values one person can reveal in an hour.

Test a decision

Ask what a policy would return for a given person before you publish it.

Two-person rule

Sensitive changes can require a second approver.

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.