Data storage location
Choose whether your team's data is stored in the United States or the European Union, what stays in your region and what is always stored in the US.
Every team picks a data region when it is created. That choice decides where your projects, orders, customers and your visitors' events are stored.
The two regions
| Region | Where your data is stored |
|---|---|
| United States | Data centers in the US |
| European Union | Data centers in the EU |
You choose it when you create the team, under Data region. Projects always follow their team's region; there is no setting per project. You can check a team's region at any time in Team settings → General.
A team's region is set once, when it is created, and never changes. No migration or support request can move an existing team.
If you need your data in the other region, create a new team there and set it up again: new projects, the tracking script installed again, and your ad and sales platforms connected again. The history doesn't come with you.
What stays in your region
Everything that belongs to a project:
- Projects and their settings
- Orders, with their values, products and tracking details
- Customers: the name, email, phone and address you send
- Products and their sales numbers
- Events and sessions: page views, clicks, scrolls, forms and purchase steps, including IP address, location, browser, referrer and ad click ids
- Scripts and their allowed domains
- Ad accounts connected (Meta, Google, Pinterest, Snapchat), their access and the campaigns and spend Clakta reads from them
- Assistant conversations
- Dashboard presets, custom events, project access and the project activity log
What is always stored in the US
Clakta has one central system in the US that identifies you and routes requests. It doesn't hold the project data above. Whatever region you choose, this is stored in the US:
- User accounts: name, email, password and login methods, and active sessions
- Teams and billing: name, slug, logo, plan, billing details, single sign-on settings, invitations, members and roles
- API keys and OAuth apps
- Assistant usage totals used for billing (the conversations stay in your region)
- The routing directory: which region each project and script belongs to, plus the project slug, allowed domains and tracking mode, so incoming events can be accepted quickly
- Sales platform connections: the encrypted credentials for Shopify, Stripe, Kiwify and the others (the orders they bring are stored in your region)
- Feedback you send from inside the app
- Support conversations
Shared services
- Uploads: team logos and user photos are kept in one global storage.
- Receiving events: events wait a few moments in a shared queue before being stored in your region. Nothing stays in the queue after that.
- Email: invitations, confirmation links and alerts are sent by our email provider, which works from the US.
Same addresses in both regions
You always use www.clakta.com for the app and api.clakta.com for the API,
whatever your region. The tracking script address is also the same, so nothing on
your site changes.
Related articles
Members and roles
Invite people to your team, see what each of the four roles can do, and choose which projects each person can see.
API keys
Create keys so your system can talk to Clakta, choose what each key can do, and keep them safe.
Plans and limits
What each plan includes, which limit you are likely to reach first, and when to upgrade.