onshore
Industries / Insurers, brokers and insurtechs

From quote to claim, identifiers stay home.

Insurers collect BVNs and NINs for KYC, bank details for payouts and health information for life and health cover. Claims documents travel to loss adjusters, reinsurers and software vendors, often abroad. Onshore tokenizes the identifiers and gives you a record of every access.

What changes
KYC at onboarding
BVNs and NINs stored in policy systems
Secure components collect them, and you store a token
Claims documents
Scans with names and account numbers go to adjusters and reinsurers
File redaction removes identifiers before they're shared
Payouts
Account numbers copied into many systems
One token, revealed only at the payment step
Agent and broker access
Wide access to policyholder records
Masked by role, with a reason on every reveal
What you'd use
The rules

This is a summary, not legal advice. Your counsel decides what your obligations are.

Questions
Can reinsurers still price risk on tokenized data?+

Often, yes. Amounts, dates and categories stay readable, and tokens keep records linked. Share real values only where a contract requires them.

What about scanned claim forms?+

File redaction handles PDFs and images, and replaces identifiers before a file leaves.

Does this make us compliant with NAICOM's rules?+

No product can do that alone. Onshore gives you controls and evidence, and your counsel decides what your obligations are.

Start with one leak.

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