Sell everywhere. Keep customers' details home.
A store sends phone numbers, emails and names to analytics, support desks, ad platforms and delivery partners, many of them hosted in another country. Most privacy laws set conditions on each of those transfers. Onshore lets the tools that only need to count or match work on tokens.
- EUSource: EU General Data Protection Regulation
Customer data may go to tools outside the EU only with adequacy, standard contractual clauses or another Chapter V ground.
- USSource: California Consumer Privacy Act, as amended by the CPRA
Californians can ask to see, delete and correct their data, and limit the use of sensitive information.
- BRSource: Brazil LGPD
Data leaving Brazil on contract terms must use the ANPD's standard clauses, required since August 2025.
- NGSource: CBN rule on data localisation in payments
From 1 January 2027, payments transaction data generated in Nigeria must be stored and managed in the country. If you take payments there, ask your payment provider and your counsel how it applies to you.
A few examples from the countries we support, not a full list and not legal advice. Your counsel decides what your obligations are. See every country.
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.