# Data Residency for European Customers

**URL:** <https://community.make.com/t/data-residency-for-european-customers/68767>\
**Category:** Questions\
**Tags:** api, connections\
**Created:** [February 7, 2025, 1:26pm UTC](https://community.make.com/t/data-residency-for-european-customers/68767 "2025-02-07T13:26:22Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![smohaking](https://avatars.discourse-cdn.com/v4/letter/s/da6949/32.png) [@smohaking](https://community.make.com/u/smohaking)\
**Post date:** [February 7, 2025, 1:26pm UTC](https://community.make.com/t/data-residency-for-european-customers/68767/1 "2025-02-07T13:26:22Z")

</div>

Hi there,

I tried contacting [Make.com](http://Make.com) sales/accounts team and they were not able to answer my question.

1. I can see that Make has EU datacenters, so when I subscribe to it, it gets a EU datacenter ([eu1.make.com](http://eu1.make.com)) but I would like to ask if all data that is stored and processed is done in the EU datacenters? Or any of it goes to the US datacenters?

2. When we use actions and sign in with the credentials such as OpenAI, Microsoft 365, using OAuth, does the credentials get saved in MAKE? If so, how and where is it stored securely?

If anyone has information about this it would be great and helpful.

Thank you,

Best regards,  
Syed.

---

<div class="post-metadata">

**Author:** ![royce](https://avatars.discourse-cdn.com/v4/letter/r/b5ac83/32.png) [@royce](https://community.make.com/u/royce)\
**Post date:** [February 7, 2025, 3:36pm UTC](https://community.make.com/t/data-residency-for-european-customers/68767/2 "2025-02-07T15:36:22Z")

</div>

From what I recall from asking them a bit back, if you are using the EU servers then everything is stored on the EU servers. The only part that may not be is your initial login credentials because you need to login first then before you get redirected to the proper data centers.

---

<div class="post-metadata">

**Author:** ![DavidGurr\_Make](https://dub1.discourse-cdn.com/flex013/user_avatar/community.make.com/davidgurr_make/32/4624_2.png) [@DavidGurr\_Make](https://community.make.com/u/DavidGurr_Make)\
**Post date:** [February 7, 2025, 4:56pm UTC](https://community.make.com/t/data-residency-for-european-customers/68767/3 "2025-02-07T16:56:00Z")

</div>

Everything relevant is on or linked to from the [Privacy and GDPR link](https://www.make.com/en/privacy-and-gdpr) at the foot of the Make website. You might need to click through a number of documents to find exactly what you want.

If you’re using an API key, that does get stored securely within the Make infrastructure.

OAuth 2.0 is a much more secure auth mechanism - that’s where you get redirected to the service you’re connecting with to enter your login and password.

In OAuth 2.0 the login and password aren’t visible to Make. Instead the remote service sends a temporary access token back to Make, which Make refreshes automatically. Again, that token is stored securely within the Make infrastructure.

---

<div class="post-metadata">

**Author:** ![Make\_Bot](https://dub1.discourse-cdn.com/flex013/user_avatar/community.make.com/make_bot/32/14661_2.png) [@Make\_Bot](https://community.make.com/u/Make_Bot)\
**Post date:** [February 28, 2025, 9:46am UTC](https://community.make.com/t/data-residency-for-european-customers/68767/4 "2025-02-28T09:46:50Z")

</div>