onshore
Industries / Online stores, marketplaces and loyalty programmes

Sell everywhere. Keep customers' details home.

A Nigerian store sends phone numbers, emails and names to analytics, support desks, ad platforms and delivery partners, most of them hosted abroad. The Nigeria Data Protection Act asks for adequate protection and a recorded basis for each of those transfers. Onshore lets the tools that only need to count or match work on tokens.

What changes
Checkout
Card and bank details touch your servers
Secure components collect them, and you store a token
Analytics events
Phone numbers and emails flow to analytics abroad
Events carry stable tokens that still join up
Customer support
Customers paste account numbers into chats
Identifiers are replaced as tickets arrive
Partner APIs
Every integration receives full customer details
The proxy swaps identifiers for tokens on the way out
What you'd use
The rules

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

Questions
We run on a global store platform. Does this still help?+

Where Onshore can sit in the data path: the forms you embed, your logs, and the data you send on to other tools. Tell us your setup and we'll say what fits.

Will our email and SMS campaigns break?+

Tools that must contact a customer need the real address or number. Keep those few with real values, and send tokens to the tools that only need to count or match.

Do we need developers?+

Some, for the first integration. After that, the console handles daily work.

Start with one leak.

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