Wi-Fi data residency, explained for operators

The moment a captive portal does more than collect an email, it starts holding personal data: a phone number, a login identity, a session history, mac address. That is the point where data residency stops being an IT detail and becomes a question your customer, and their regulator, will ask.

Residency is about location, not just security

Security asks who can read the data. Residency asks which country the data physically sits in. Many regulators, especially across the Gulf, treat the second question as its own requirement: certain categories of personal data must stay inside the national territory, on infrastructure available there.

So the honest answer to "where does our data live" is never a single global datacenter. It is: it depends on your regulator, and it can be provisioned to match.

Hold less, and the question gets easier

The strongest residency posture is to hold as little as possible. WiWallet keeps identity data and analytics, and never stores card data, that stays with certified payment providers. Fewer categories of data mean fewer places a regulator can object. You can choose our partner payment provider, which shares our commitment to storing data where it should be stored.

• User data (identity, sessions): stays in the selected region.
• Analytics: computed and stored in the same region, no export.
• Backups: same region as the primary, not a global bucket.
• Card data: never stored by us, handled by the payment provider.

Three regions, one rule

On the WiWallet home page you can see the model in one view: pick Europe, the Gulf or West Africa, and the whole WiWallet side is provisioned inside that region, with no cross-region replication and no third-party enrichment. Europe is the default deployment today; the Gulf and West Africa are provisioned per contract on infrastructure available in that territory.

Where a regulator requires strict in-country residency, the exact placement of primary, replica and backups is confirmed in writing before signature.

WiWallet data residency commitment

How to answer the question before you sign

1. List the data categories the portal will actually hold.
2. Name the region each category must stay in.
3. Get the placement of primary, replica and backups in writing.
4. Confirm card data never touches your systems.

That short checklist turns a vague worry into a clause. If you want to go deeper on the revenue side of the same portal, read how captive-portal Wi-Fi becomes a revenue stream, or see the full Wi-Fi monetization overview.