Data region
Every Tapbar's reaction data lives in one of two places: global, spread across Cloudflare's network so it sits close to whoever is reading, or the EU, pinned to EU-located infrastructure. You pick when you create the Tapbar, and on Plus or Pro you can move it later.
Moving is a real move — the counts, each visitor's own reaction state, and your usage history all travel. It isn't a fresh start in a new region.
What "EU" covers
EU hosting pins the Tapbar's rooms (the Durable Objects holding live counts) and its rollup database to EU-located infrastructure. Reaction data stays resident there.
Two things still run on the global edge: minting a session token when a page loads, and the cached copy of your Tapbar's configuration. Neither holds reaction history — the config is your colours and reaction set, and the token is a short-lived signed blob. We describe EU hosting as a locality choice rather than a compliance product, and we would rather say that plainly than let you infer more than it does.
Your account itself — your email, your billing details, support email you send us — is global regardless of which region a Tapbar uses. Region is a property of a Tapbar, not of your account.
Moving a Tapbar
In the console, open the Tapbar, go to Set up, and find Data region at the bottom of the Traffic card. From an agent, it's the migrate_app_region MCP tool.
Here's what happens when you start a move:
Reactions pause. Your bar disappears from your pages for the duration — for a typical site that's well under a minute, longer if you have thousands of pages with reactions on them. Visitors see no error, just no bar, and it comes back on its own.
Your data is copied to the new region, and the Tapbar switches over. Counts, per-visitor state (so nobody who already reacted can react again), and your daily usage history all come across.
The old region is kept for 24 hours. Inside that window you can move back, and everything comes with you — including reactions collected after the move. After 24 hours the old copy is deleted.
You can cancel a move while it's still copying. Reactions stay paused for a moment longer while the old region is put back in service, then the Tapbar carries on where it was.
How often
Moving a Tapbar rewrites every reaction row it has, so it's rate-limited rather than free:
| Plan | How often you can move a Tapbar |
|---|---|
| Free | Not available |
| Plus | Once every 90 days |
| Pro | Once a day |
Moving back inside the 24-hour window doesn't count against the limit — undoing something shouldn't cost you your next move.
Two things worth knowing
If a visitor has a page open while the move runs, a reaction they tap in that moment may not carry over. It's a narrow window and only affects taps made during the move itself.
Unique-reactor counts can double-count a visitor who reacts in both regions during the few minutes around the switchover. Tap totals are exact; it's only the distinct-reactor number, and only for reactions in that window.