Data Residency in EU

Data Residency refers to the physical/geographical storage location of an organization's data or information. Read on to learn how to ensure you are enrolled in our EU Data Residency program. 

As a Mixpanel customer in the EU, you have the option to send your data to Mixpanel's EU data center, and have your data stored exclusively in the EU. You do not automatically get Data Residency and are not automatically set up in the EU data center. Read on to learn how to ensure you are enrolled in our EU Data Residency program. 

Mixpanel is at feature parity between the product experience we offer to our EMEA and North American customers. You do not lose any product capability because you choose to store your data in the EU.

If you are coming to use it from a Customer Data Platform (CDP), Mixpanel cannot guarantee that data ingestion, processing and storage will always stay within the EU region. Please work with your CDP to make sure they are sending your data to the EU endpoint. 

The following diagram shows how Mixpanel's Data Residency works:

Screen_Shot_2020-02-05_at_11.06.21_AM.png

New Customers

You do not automatically start sending your events to the Mixpanel data center in Europe. If you are creating a new project from the EU, you will be presented with an option to be enrolled in EU Data Residency. You must opt-in to Data Residency at this time to ensure you are enrolled.

Your developers must also implement the Mixpanel tracking code so that data is ingested, processed and stored in the EU data center. Implementation documentation can be found here

Existing Customers

Mixpanel can migrate all your historical data and set you up in our EU data center. If you are an Enterprise customer, you must reach out to your Relationship Manager, Account Executive, or Sales Representative to begin the migration process. If you are not an Enterprise customer, you must reach out to Mixpanel support to begin migration.

Once your historical data has been migrated, you will also be required to make tracking implementation changes as described here. It is important to wait to make this tracking change until after the historical data has been migrated, as updating your tracking early may lead to inconsistency in your data. 

Did this answer your question?

Comments

0 comments

Article is closed for comments.