# GitHub Copilot

## Kurzbeschreibung
**"Your AI accelerator for every workflow, from the editor to the enterprise."**


**GitHub Copilot** is an AI-powered coding assistant for IDE, GitHub.com, CLI, Mobile, and Windows Terminal. It offers code completion, chat, code review, agentic workflows, pull request summaries, MCP integration, and a cloud agent that can analyze repositories, make changes on branches, and prepare pull requests.


The product is clearly focused on software development and team workflows, not on general text or office applications.

## Claim
Your AI accelerator for every workflow, from the editor to the enterprise

## Geeignet für
- API Integration
- Automation / Workflows
- Programming / Software Development

## Kernfunktionen
- App Development
- AI agents
- Programming

## Preismodell
- **free:** **GitHub Copilot Free** Limited entry-level option for personal use; according to GitHub, includes up to 2,000 inline suggestions per month and limited premium requests. Not suitable for enterprise use.


**GitHub Copilot Student** For verified students; includes unlimited completions, Copilot Chat, additional models, and monthly premium requests.
- **subscription:** **GitHub Copilot Pro** For individual developers with unlimited IDE completions, Copilot Chat, additional models, and premium requests.


**GitHub Copilot Pro+** Everything in Pro plus full access to available models in Copilot Chat, higher premium request limits, and priority access to advanced AI features.


**GitHub Copilot Busine**ss For teams and organizations; includes Copilot Cloud Agent, centralized management, and Copilot policy control for organization members.


**GitHub Copilot Enterprise** For companies on GitHub Enterprise Cloud; includes everything in Copilot Business plus additional enterprise features and centralized assignment at the organization, user, and team level.
- **other:** **GitHub AI Credits / usage-based billing **Copilot plans include GitHub AI credits or quotas; for Business and Enterprise, credits are pooled per user at the billing unit level.


**GitHub Enterprise Server** Self-hosted GitHub platform for enterprises, on-premises or in a Virtual Private Cloud; important: according to GitHub, Copilot is currently not available for it.

## DSGVO und Datenschutz
**Gesamteinschätzung:** Conditional

**On-prem / local hosting: indirect / not available**

An on-premises, local, or self-hosted deployment of GitHub Copilot is not listed on the website.

**Private Cloud / Data Center: Partially**

For GitHub Enterprise Cloud with Data Residency, region-specific processing is documented; Copilot requests are then routed to model endpoints within the specified region. However, a dedicated customer-owned private cloud instance in the strict sense is not described on the website.

**EU SaaS / Managed: Covered**

GitHub documents Copilot usage within the European Union region for GitHub Enterprise Cloud with Data Residency. When the policy is enabled, code, prompts, and responses remain within the specified region during inference, and Copilot-related logs and telemetry are stored in accordance with regional requirements.

**Hybrid: Indirect / Not Available**

A documented hybrid operating model, in which part of the service runs locally or in the customer’s own private cloud and another part runs as an external service, is not specified on the website.

**T&C / DPA: Covered**

GitHub publishes a GitHub Data Protection Agreement, which, according to the website, applies to GitHub Copilot. GitHub also states that GitHub and customers can enter into a Data Protection Agreement that supports compliance with the GDPR and similar laws.

**No training: partially**

For Individual subscriptions, interaction data may be used for training and improving AI models, according to the website, unless the user has opted out. At the same time, GitHub specifies restrictive retention standards for Business and Enterprise customers and documents agreements with several model providers regarding the non-use of GitHub data for training or zero data retention. However, the website does not provide a blanket statement regarding a consistent exclusion for all modes and models.

**Open Source / Transparency: Partial**

GitHub documents technical transparency regarding model hosting, subprocessors, data residency, and compliance reports. However, the website does not specify a true open-source or self-hostable Copilot path.

**Data Processing**

The website describes GitHub Copilot as a cloud-based service. Depending on the model, processing is handled via GitHub’s Azure infrastructure as well as through connected providers such as OpenAI, AWS, Anthropic, and Google Cloud. For Enterprise Cloud with Data Residency, Copilot can be restricted to the European Union region; in this case, inference data and associated logs/telemetry are intended to remain within the specified region. Without this configuration, the website does not indicate that processing is consistently local to the EU. For Business and Enterprise customers, the default retention policies are usage-based; according to the website, prompts and suggestions are not retained for IDE chat and code completions, but are retained for 28 days for other access methods.

**Conclusion**

For an EU/EEA tool directory, GitHub Copilot **cannot** be **categorically** classified as a completely unproblematic standard SaaS offering, but there is a robust compliance path for larger organizations: DPA/AVV plus GitHub Enterprise Cloud with EU data residency. This supports a “conditional” rating. EU/EEA users who prioritize data residency, contractual safeguards, and minimal data usage require the appropriate enterprise settings; without them, the documentation remains too limited from a European perspective.

**Sources**

- [https://github.com/customer-terms/github-data-protection-agreement](https://github.com/customer-terms/github-data-protection-agreement)
- [https://docs.github.com/en/site-policy/privacy-policies/github-subprocessors](https://docs.github.com/en/site-policy/privacy-policies/github-subprocessors)
- [https://docs.github.com/en/enterprise-cloud@latest/admin/data-residency/github-copilot-with-data-residency](https://docs.github.com/en/enterprise-cloud@latest/admin/data-residency/github-copilot-with-data-residency)
- [https://docs.github.com/en/copilot/reference/ai-models/model-hosting](https://docs.github.com/en/copilot/reference/ai-models/model-hosting)
- [https://github.com/features/copilot](https://github.com/features/copilot)
- [https://docs.github.com/en/enterprise-cloud@latest/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/accessing-compliance-reports-for-your-organization](https://docs.github.com/en/enterprise-cloud@latest/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/accessing-compliance-reports-for-your-organization)

For the European region**, the conditions for** GDPR-compliant use of GitHub Copilot have been documented. Positive aspects include the DPA/AVV that explicitly applies to GitHub Copilot, a documented EU data residency for GitHub Enterprise Cloud with Data Residency, and statements that, in cases of enforced data residency, code, prompts, and responses do not leave the region during inference. At the same time, standard usage is not consistently documented as being local to the EU; the list of subprocessors mentions several processing operations in the U.S., and individual model paths or functions have differing retention rules. Therefore, usage by EU/EEA users is not generally proven to be fully GDPR-compliant, but only with appropriate enterprise configurations and contractual frameworks.

**Positive**

GitHub documents that the GitHub DPA also applies to GitHub Copilot. For GitHub Enterprise Cloud with Data Residency, a Copilot policy is described that routes all Copilot requests to model endpoints within the specified region; supported regions are the U.S. and the European Union. GitHub also states that, when data residency is enforced, code, prompts, and Copilot responses do not leave the region during inference, and that Copilot-related logs and telemetry are stored in region-compliant storage. For Business and Enterprise customers, GitHub also specifies restrictive retention policies by default for certain types of usage—for example, no retention of prompts and suggestions when accessing the IDE for chat and code completions.

**Negative**

The website does not provide blanket assurance that all standard SaaS usage of Copilot within the EU/EEA takes place locally within the EU without further measures. GitHub’s list of subprocessors lists several processing locations in the U.S. Additionally, data is retained for varying lengths of time depending on the interface; for Copilot access other than IDE chat and code completions, GitHub specifies a retention period of 28 days for prompts and suggestions. For individual subscriptions, interaction data may be used to train and improve AI models, provided that opt-out has not been selected. The website does not indicate that GitHub Copilot offers true on-premises or self-hosted operation.

**Server Location**

For GitHub Copilot with Data Residency, the website lists the United States and the European Union as regions. With enforced data residency, code, prompts, and responses remain within the specified region during inference. However, the general list of subprocessors lists processing locations in the U.S. for several subprocessors. Specific EU countries or individual data center locations for Copilot are not specified on the website.

## Hosting und Daten
- **On-Prem / lokales Hosting:** unknown
- **Private Cloud / Rechenzentrum:** teilweise / indirekt
- **EU SaaS / Managed:** abgedeckt
- **Hybrid:** unknown
- **AVV / DPA:** abgedeckt
- **Kein Training auf Kundendaten:** teilweise / indirekt
- **Open-Source / Transparenz-Pfad:** teilweise / indirekt

## Standort
**Land:** USA

**Taxonomie:** USA

GitHub, Inc., 88 Colin P. Kelly Jr. St., San Francisco, CA 94107, United States. EU address according to the Privacy Statement: GitHub B.V., Prins Bernhardplein 200, Amsterdam 1097JB, The Netherlands.

## Vorteile
- Very broad integration spectrum: IDE, GitHub, CLI, Mobile, Terminal.
- Strong feature set beyond pure autocomplete: Chat, Code Review, Cloud Agent, PR summaries, Spaces, MCP.
- Centralized control, policies, audit logs, and usage metrics for enterprises.
- Multiple current frontier models selectable.
- For Enterprise/Business customers, no use of customer data for model training without authorization.

## Nachteile
- Not available for GitHub Enterprise Server; therefore no classic on-prem offering for Copilot itself.
- Pricing and consumption logic have become more complex: Premium Requests, per-request add-ons, model multipliers, and possible additional costs via GitHub Actions.
- Individual plans are more critical to assess from a data privacy perspective, because starting 24.04.2026 GitHub may use interaction data for model training unless users actively opt out.
- Several features are still in Preview/Public Preview and therefore subject to change.
- Currently no new Pro trials.

## Quellen
- Offizielle Website: https://github.com/

## Letzter Datenstand
2026-04-15

## Originalseite
https://kifox.ai/en/ki-tools/github-copilot-en/
