# EU Tech Giants Lobby for GDPR Loopholes in Digital Omnibus

Investigations reveal intense lobbying efforts to bypass data consent for AI model training.

- **Source:** [INCRYPTED](https://brifing.si/source/7cd4625d-3f08-4cc1-983d-4c7d991839ba)
- **Published:** 2026-10-28
- **Topic:** [Business](https://brifing.si/c/business)
- **Original article:** <https://incrypted.com/v-es-razoblachyly-masshtabnoe-lobbyrovanye-yzmenenyy-v-zashchyte-personalnykh-dannykh-v-ynteresakh-yy-kompanyy/>
- **On Brifing:** https://brifing.si/s/4944286d-b450-4aef-897e-f9963749fffd

## Lobbying Investigation Findings

Corporate Europe Observatory and LobbyControl revealed that major tech firms held 655 meetings regarding the Digital Omnibus package since November 2025. Data shows 83% of these interactions involved business representatives, while only 11% included public interest groups. Google, Meta, and Apple were identified as the most active participants in these parliamentary discussions.

## Strategic Influence in Germany

Between May 2025 and September 2026, the German government conducted 85 meetings involving 11 non-European tech companies. OpenAI CEO Sam Altman personally held five meetings with high-ranking German officials within a four-month span. These interactions highlight a coordinated effort to shape legislative outcomes in favor of AI-driven commercial interests across Europe.

## Proposed GDPR Regulatory Shifts

The Digital Omnibus aims to simplify digital regulation but faces criticism for potentially weakening GDPR protections. Proposed changes would allow companies to process personal data for AI training under the guise of legitimate interest. This shift would remove the requirement for explicit user consent, fundamentally altering how personal information is utilized by automated systems.

## Specific Corporate Intervention Tactics

Internal documents show targeted lobbying efforts, such as Meta representative Martin Ruby contacting Danish officials in March 2026 to influence specific amendments. Similarly, Google lobbyists expressed concerns in April 2026 regarding the potential exclusion of legitimate interest provisions. These actions demonstrate a direct attempt to steer legislative language during the drafting process.

## Data Privacy Risks Identified

Rights group noyb warns that the proposed changes prioritize commercial AI interests over fundamental user rights. Beyond training, the regulations could permit the use of personal data for the actual operation of AI systems. Critics fear this creates a broad legal loophole allowing companies to do almost anything with user data without oversight.

## Pseudonymized Data and Third Parties

Another contentious proposal involves excluding certain pseudonymized data from GDPR scope when transferred to third parties. Privacy advocates fear this provision will empower data brokers to trade sensitive information more freely. This change could effectively dismantle the protections currently afforded to European citizens regarding the secondary use of their digital footprints.

## Industry Rationale for Reform

Tech giants argue that these regulatory changes are essential to simplify compliance and boost the competitiveness of the European AI market. They claim that current restrictions hinder innovation compared to global peers. However, regulators remain skeptical, noting that these arguments often serve to mask the erosion of established privacy standards for profit.

## Legislative Timeline and Outlook

The Council of the EU agreed on a negotiating position in October 2026, signaling a potential weakening of GDPR. The European Parliament is expected to finalize its stance in early 2027, followed by further negotiations. This process follows the implementation of the EU AI Act in August 2026, marking a critical juncture for digital rights.

## Sources covering this story

- https://incrypted.com/v-es-razoblachyly-masshtabnoe-lobbyrovanye-yzmenenyy-v-zashchyte-personalnykh-dannykh-v-ynteresakh-yy-kompanyy/ — 

---

_Summary written by Brifing from the original reporting. Copyright in the original article belongs to its publisher; read the full piece at the link above._
