Data storage location

Every team picks a data region when it is created. That choice decides which database and which analytics store hold your projects, your orders, your customers and the events your visitors generate.

The two regions

You choose one in onboarding, under Data region, when you create the team. Every project belongs to a team, so a project always inherits its team's region — there is no per-project setting.

You can see which region a team is in at any time under Team settings → General.

What is stored in your region

Everything that belongs to a project lives in your team's region:

• Projects and their settings — currency, tracking mode, attribution model, retention.
• Orders — totals, status, currency, line items, expenses and the tracking context attached to each sale.
• Customers — the name, email, phone, address and identifiers you send with an order or through clakta.identify().
• Products and the per-product analytics derived from your orders.
• Analytics events — page views, clicks, scrolls, form submissions, ecommerce events, identify calls and the sessions built from them. This includes IP address, the geolocation derived from it, user agent, referrer and ad click identifiers.
• Tracking sources — your data streams, their allowed domains and their auto-tracking switches.
• Ad accounts — connected Meta, Google and TikTok accounts, including the encrypted OAuth credential, plus the campaign, ad set, ad and spend data synced from them.
• Assistant conversations — chats, messages and the action items generated from them.
• Dashboard presets, custom event definitions and per-project member access.
• Activity log — the audit trail of changes to your projects.

What is always stored in the United States

Clakta runs a single control plane in the US. It holds the records that identify you and route requests, and it does not hold the project data above. Regardless of the region you pick, the following is stored in the United States:

• User accounts — name, email, password hash, passkeys, linked Google, Apple or SAML identities, and active sessions.
• Teams and billing — team name, slug, logo, plan, billing identifiers, plan limits, SSO configuration, invitations, memberships and roles.
• API keys and OAuth applications.
• Assistant usage counters used for billing. These are totals only; the conversations themselves stay in your region.
• The routing directory — which region owns each project and each tracking source. To let the ingestion endpoint accept an event without first reaching into a regional database, this record also carries the project slug, the hostnames allowed to send events, and the project's tracking mode.
• Sales platform connections — the encrypted credentials and webhook secrets for Shopify, Stripe, Kiwify and every other platform you connect. The orders those connections produce are written to your region.
• Product feedback you submit from inside the app.
• Support conversations. Anything you share with us in a support ticket or chat is stored in the US.

Shared services

A few parts of Clakta are not region-specific:

• Uploads. Team logos and user avatars go to a single global object store.
• Event ingestion. Events are buffered in a shared queue for a few moments before being written into your region's analytics store. Nothing is retained in the queue once it has been processed.
• Email. Invitations, verification links and alerts are delivered by our email provider, which operates from the US.

Region and the API

There are no region-specific domains. You always use www.clakta.com for the app and api.clakta.com for the API, whichever region your team is in — Clakta resolves the region from the project in your request and routes it internally.

The tracking script URL is the same in both regions too, so nothing on your site has to change either way.

Reducing what you store

Where your data lives is one question; how much of it you hold is another. Three settings control the second:

• Tracking mode — privacy-friendly mode collects no cookies, no browser storage and rejects personal data on orders. See Tracking modes.
• Consent management — gate first-party identifiers behind the visitor's decision. See Consent management.
• Data retention — shorten how long events stay queryable, per project. See Data retention.