Define geographical scope of Copilot Servers #165658
Select Topic AreaQuestion Copilot Feature AreaGeneral BodyHi Team Our organization is based in Europe and most of our customers are located also in Europe. One of our customers agrees with the usage of Copilot to help us to create our solution but he poses a requirement.
We have enable many options on the Copilot configuration and I wonder if there is a way to define the scope for that. Looking forward to hearing from you. Carlos. |
Replies: 3 comments 2 replies
|
Hi Carlos, That's a great question, and it's an important consideration for EU-based organizations subject to data residency and GDPR compliance. As of now, GitHub Copilot does not offer regional (e.g., EU-only) data residency controls. When using Copilot, data such as code snippets and telemetry may be processed in data centers located outside the EU, including in the United States. Key Points: If EU data residency is a strict requirement, it might be best to: You can also reach out to GitHub Sales or Support directly for more formal guidance if your organization needs a binding data processing agreement (DPA) or Enterprise options. |
|
I know this is late, but @carlos-garcia-flw, having local servers in the EU does not solve the data sovereignty issue at all. Your data is at risk in the EU if a US based company has access to it, because of the 2018 Cloud Act. The correct response to this statue is to run your own inference. You can do that on MS Azure, or AWS, or OCI, GCP, or other providers, but you must have control of your data (i.e encrypted at rest and in transit), and you lose that if you use inference as a service because of the Cloud Act. |
|
GitHub Copilot runs on Microsoft Azure servers, and right now you cannot force all Copilot traffic to stay only in the EU.
👉 In short: repository data can stay in the EU, but Copilot’s AI processing may not be limited to EU servers yet. For strict compliance, you’ll need GitHub’s official confirmation. |
Hi Carlos,
That's a great question, and it's an important consideration for EU-based organizations subject to data residency and GDPR compliance.
As of now, GitHub Copilot does not offer regional (e.g., EU-only) data residency controls. When using Copilot, data such as code snippets and telemetry may be processed in data centers located outside the EU, including in the United States.
Key Points:
->GitHub Copilot relies on cloud infrastructure, and Microsoft (GitHub’s parent company) may process data in various global regions.
->GitHub's Trust Center and Copilot Privacy Statement provide details on how user data is handled.
->Copilot does not currently support restricting inference or proc…