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.
Customer data may go to tools abroad only with adequate protection or another lawful condition, and you must record the basis for each transfer (section 41).
Source: Nigeria Data Protection Act 2023From 1 January 2027, the CBN requires payments transaction data generated in Nigeria to be stored and managed in the country. If you take payments, ask your payment provider and your counsel how it applies to you.
Source: CBN circular, June 2026
This is a summary, not legal advice. Your counsel decides what your obligations are.
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.