We are currently evaluating the use of OpenAI’s API for business-critical applications and are particularly interested in ensuring full compliance with European data residency requirements, specifically with regional storage in Dublin.
We understand from your documentation that:
Data residency is configured per project within our API organization,
And that requests must be sent via https://eu.api.openai.com/ for processing within the Europe region.
We would appreciate your assistance with the following:
Confirming the availability and scope of data residency in Dublin for our organization;
Ensuring that our API usage and data processing are fully contained within the EU/EEA;
Clarifying any contractual or configuration steps required to activate and guarantee regional storage (e.g. via project setup, enterprise terms, or DPA addendum).
We are ready to align our setup accordingly and would appreciate your guidance to proceed.
Hi OpenAI,
I am astonished by the response we have had to Sales enquiries submitted through your contact form for this topic and at a loss as to how to proceed. Clearly the Sales team are not using OpenAI to process the enquiries that they receive. We are established users of OpenAI - our clients are submitting hundreds of OpenAI API queries each day, but a dependency for our continued growth is to establish EU residency for our OpenAI usage. I have outlined this twice to the sales team in some detail and on both occasions received boiler plate responses suggesting that I create a developer account and experiment in the OpenAI playground - completely inappropriate.
Can I ask, how do we proceed to be able to use the OpenAI EU API from our application?
Same here. We would like to configure data residency for EU. As stated in the docs https://platform.openai.com/docs/guides/your-data we appealed to the sales team but only got an automated response. VERY disappointing.
I have exactly the same situation. Contacted them three times, same automatic reply a day later from a no-reply email suggesting that we should create a developer account…
We have the same problem of receiving acces to set up the data resedency which we require while developing ai driven platforms for the financial services sector. After getting only generic responses from the sales contact form, I started to dig a little and found the DPA, let my boss sign it and searched through the signed document for email addresses to get into contact und got finally a response from a human to redirect me towards their support team.
Hey @folks, we can see why this is confusing since the setting isn’t very visible unless you’re specifically looking for it.
Right now, Data Residency for the OpenAI Platform is configured at the org/project level and typically needs to be enabled for your organization by OpenAI’s Sales team.
A few important things to know:
Data residency is mainly for API Platform usage, not standard ChatGPT consumer chats
Availability depends on your org setup and supported features
Some services support storage residency only, while others also support inference residency
If you want to enable it for your organization, the next step is to contact the Sales team so they can review eligibility and help configure the appropriate regional setup.
We already contacted the sales team, and in fact we now have a tenant in the EU. However, we are still waiting for several answers in terms of GDPR compliance. How can we have formal documentation regarding this topic?
Hi @Inoberga, we get why you’re looking for something more formal here, especially once legal/compliance reviews start getting involved.
For GDPR, DPA, subprocessors, residency details, and related compliance documentation, the best place to check is the OpenAI Trust Portal. That’s where the official docs and attestations are maintained and updated.
If something specific is still unclear after reviewing those docs, it’s worth continuing the thread with your sales/contact team so they can route the exact compliance question internally.
Hey @Mark_G , thanks very much for the answer (I’ve been looking for it for a while). Is there any specific info to include in the reach-out email so that it saves your team some time in the review process?
Hey @sergeliatko, yes! To help speed things up on our side, it’s really helpful if you include the Organization ID, Workspace ID, and the Residency Region in the initial email.
Also, it’s best if the outreach comes directly from the account owner’s email address. That usually helps avoid extra back-and-forth for ownership approval during the review process.