Municipal Data Exclusivity .

1. Introduction

Municipal data exclusivity arises when a municipality, municipal authority, or a public undertaking gives one entity exclusive access to, control over, or commercial rights in data generated, collected, or maintained through municipal functions.

Examples include:

  • exclusive access to municipal property and land databases;
  • exclusive access to parking or traffic data;
  • exclusive access to waste-collection data;
  • exclusive access to public-transport usage data;
  • exclusive access to building-permit or planning data;
  • exclusive access to municipal GIS/maps;
  • exclusive access to environmental or utility data;
  • exclusive access to datasets generated through smart-city infrastructure;
  • exclusive rights to commercialise municipal datasets;
  • discriminatory API access to municipal databases;
  • giving one technology provider privileged access to municipal data while excluding competitors.

The competition concern is strongest where the municipality's dataset is unique, difficult to reproduce, commercially important, and capable of being used by several downstream competitors.

EU public-sector data legislation expressly recognises the competition problem: exclusive arrangements concerning certain public-sector datasets are generally prohibited, subject to narrowly defined exceptions where exclusivity is necessary for a service or product in the general interest. Conditions for reuse must also be transparent, proportionate, objectively justified and non-discriminatory.

2. What Is Municipal Data Exclusivity?

Municipal data exclusivity can be understood as:

An arrangement under which one undertaking receives exclusive or preferential rights to access, obtain, process, reuse, commercialise, or technically exploit data controlled by a municipality, thereby potentially restricting competing undertakings' access to an important input.

The exclusivity can be:

A. Express exclusivity

The municipal contract expressly states:

"Only Company X shall have access to the municipal dataset."

B. Functional exclusivity

There is no express exclusivity clause, but the municipality:

  • gives one firm the only API;
  • provides data in a usable format only to one company;
  • refuses comparable access to competitors;
  • gives one provider real-time feeds;
  • allows one company to integrate its software directly with municipal databases.

C. Contractual exclusivity

A concession, procurement contract, data-sharing agreement, or public-private partnership grants one undertaking exclusive commercial exploitation rights.

D. Technical exclusivity

The municipality technically prevents competitors from accessing data through:

  • API restrictions;
  • authentication systems;
  • incompatible formats;
  • proprietary interfaces;
  • restricted feeds;
  • delayed publication.

E. De facto exclusivity

The municipality formally makes data available to everyone, but one incumbent receives:

  • earlier access;
  • more granular data;
  • real-time data;
  • historical archives;
  • higher-quality data;
  • machine-readable data;

while competitors receive only limited information.

3. Why Municipal Data Can Be a Competition Asset

Data can constitute an important competitive input because it may provide:

  1. Scale — large historical datasets;
  2. Accuracy — information collected directly by public authorities;
  3. Uniqueness — information unavailable elsewhere;
  4. Real-time value — traffic, parking, transport or environmental information;
  5. Network effects — more data improves the quality of digital services;
  6. Entry advantages — incumbents may become difficult to challenge;
  7. Algorithmic advantages — data can improve AI and predictive systems.

EU policy materials recognise that exclusive control over datasets can create competition problems where alternative sources do not exist and access restrictions prevent competing businesses from entering or competing effectively.

4. Relevant Legal Framework

Municipal data exclusivity may potentially engage several areas of competition and public law.

A. Abuse of dominance

Where the municipality or a municipal undertaking is an undertaking and occupies a dominant position, exclusive control over an indispensable dataset may raise issues analogous to:

  • refusal to deal;
  • denial of access;
  • discriminatory access;
  • leveraging;
  • foreclosure;
  • tying;
  • exclusionary conduct.

The essential-facilities doctrine is particularly relevant.

However, not every municipal dataset is an essential facility.

B. Anticompetitive agreements

If the municipality and a private undertaking enter into an agreement giving the undertaking exclusive data rights, authorities may examine:

  • exclusionary purpose;
  • foreclosure;
  • duration;
  • market coverage;
  • alternative data sources;
  • competitive effects;
  • procurement conditions.

An exclusive data agreement is therefore not automatically unlawful, but its competitive effect matters.

C. Public procurement

Municipalities frequently distribute data through:

  • concessions;
  • PPP arrangements;
  • outsourcing contracts;
  • IT contracts;
  • smart-city contracts;
  • public-service contracts.

A competition problem can arise if the procurement structure unnecessarily gives one firm control over an important dataset for downstream markets.

D. Public-sector information/reuse rules

EU public-sector information rules are particularly relevant because they specifically address exclusive arrangements concerning public-sector data.

The principle is that exclusive rights to reuse specified public-sector datasets should generally be avoided, while exceptions may exist where exclusivity is necessary to provide a service or product in the general interest.

5. Essential-Facilities Analysis

The most important competition-law framework comes from the essential-facilities/refusal-to-supply jurisprudence.

A municipality's dataset becomes particularly problematic when the following factors are present:

1. Control

The municipality controls the dataset.

2. Indispensability

Competitors cannot reasonably obtain or reproduce equivalent data elsewhere.

3. Downstream competition

The data is necessary for competing downstream products or services.

4. Elimination of competition

Exclusivity substantially eliminates or restricts effective competition.

5. Lack of objective justification

There is no convincing reason for denying comparable access.

6. Feasibility

The municipality can provide access without compromising privacy, security, confidentiality or legitimate public interests.

The traditional EU jurisprudence applies a demanding threshold to compulsory access. Contemporary EU materials continue to rely upon Bronner, IMS Health, Microsoft, Clearstream, Slovak Telekom and related cases in analysing refusal-of-access questions.

6. Six Major Case Laws

Case 1 — Oscar Bronner GmbH & Co. KG v Mediaprint

Case: Oscar Bronner GmbH & Co. KG v Mediaprint Zeitungs und Zeitschriftenverlag GmbH, C-7/97

Principle

The Court of Justice established a stringent test for imposing access obligations on a dominant undertaking.

A refusal to provide access is not automatically abusive merely because competitors would benefit from access.

The facility must be effectively indispensable and duplication or creation of an alternative must not be realistically feasible.

Application to municipal data

Suppose a municipality possesses a unique database of:

  • parking spaces;
  • traffic movements;
  • municipal buildings;
  • waste collection;
  • public transport.

A competitor cannot simply argue:

"The municipal data would make my business easier."

It must demonstrate something much stronger:

"The relevant municipal dataset is genuinely indispensable and there is no realistic alternative."

This is especially important because municipalities may legitimately protect:

  • privacy;
  • cybersecurity;
  • confidential information;
  • public safety;
  • administrative integrity.

The Bronner threshold therefore prevents every refusal of municipal data from becoming a competition-law violation.

7. Case 2 — IMS Health GmbH & Co. OHG v NDC Health GmbH

Case: IMS Health GmbH & Co. OHG v NDC Health GmbH & Co. KG, C-418/01

Principle

The Court developed the circumstances under which refusal to provide access to an important protected resource may constitute abuse.

The case is especially relevant where the resource is protected by intellectual-property rights.

The jurisprudence considers factors including:

  • indispensability;
  • prevention of a new product or service;
  • elimination of effective competition;
  • absence of objective justification.

Municipal data relevance

Municipal datasets may sometimes be protected by:

  • copyright;
  • database rights;
  • confidentiality;
  • personal-data rules;
  • contractual restrictions.

But intellectual-property protection does not necessarily provide an unlimited competition-law shield.

If a municipality or municipal undertaking uses exclusive control over a protected database to prevent the development of competing services, IMS Health provides an important analytical framework.

8. Case 3 — Microsoft Corp. v Commission

Case: Microsoft Corp. v Commission, T-201/04

Principle

Microsoft was required to provide interoperability information to competitors under circumstances involving the ability of rivals to compete effectively.

The case is important because it demonstrates that information necessary for interoperability can have competitive significance.

Municipal data application

Consider a smart-city platform where:

  • the municipality owns the underlying data;
  • Company A operates the municipal platform;
  • Company B wants to provide competing services;
  • Company A receives complete API access;
  • Company B cannot obtain equivalent information.

The issue may not merely be "data ownership."

It may become:

Does control over the information prevent effective interoperability and foreclose downstream competitors?

Microsoft therefore provides an important analogy for:

  • municipal APIs;
  • smart-city platforms;
  • transport data;
  • digital permitting systems;
  • municipal payment platforms;
  • public-service applications.

The EU jurisprudence continues to identify Microsoft among the leading authorities relevant to refusal-of-access analysis.

9. Case 4 — Clearstream Banking AG v Commission

Case: Clearstream Banking AG and Clearstream International SA v Commission, T-301/04

Principle

Clearstream concerned access to infrastructure and services necessary for competitors' ability to operate effectively.

The case is relevant to the broader principle that a dominant operator controlling an important infrastructure may have competition-law obligations concerning access.

Municipal data application

A municipality might control a database that is effectively the gateway to a downstream market.

For example:

Municipal authority → exclusive database → data-processing provider → competing downstream services.

If competitors cannot realistically operate without the municipal dataset, the refusal or discriminatory provision of access becomes more significant.

The EU's current competition guidance continues to cite Clearstream alongside Bronner and IMS Health when discussing refusal-of-access cases.

10. Case 5 — Slovak Telekom v Commission

Case: Slovak Telekom a.s. v Commission, C-165/19 P

Principle

The case concerns access to telecommunications infrastructure and the relationship between general abuse-of-dominance principles and the stricter Bronner criteria.

The Court clarified important aspects of refusal/access analysis involving infrastructure controlled by a dominant undertaking.

Municipal data relevance

The case is useful because municipal data can function as a form of digital infrastructure.

For example:

Municipality → data platform → API → downstream digital services

If an undertaking obtains exclusive control of that infrastructure, the competitive assessment may examine:

  • the undertaking's market position;
  • the nature of the access obligation;
  • whether competitors depend on the infrastructure;
  • whether access conditions discriminate against rivals;
  • whether alternative infrastructure exists.

The Court emphasised the importance of the circumstances in which access obligations are imposed on dominant undertakings.

11. Case 6 — Lietuvos geležinkeliai v Commission

Case: Lietuvos geležinkeliai AB v Commission, C-42/21 P

Principle

The case concerns the removal of infrastructure and its competitive consequences.

It is significant because EU jurisprudence distinguishes between an ordinary refusal to deal and conduct that can effectively eliminate competitive access to an important input.

Municipal data application

Imagine that a municipal authority previously makes a valuable dataset available to multiple providers but then restructures its system so that:

  • only one provider can access the data;
  • competitors cannot obtain equivalent information;
  • the change materially impairs their ability to compete.

The legal analysis should examine the actual competitive effect, not merely the formal wording of the arrangement.

The EU Court has continued to cite Lietuvos geležinkeliai in the context of refusal-of-access analysis.

12. Case 7 — Lukoil Bulgaria / Lukoil Burgas

A recent CJEU judgment concerning access to infrastructure is also useful by analogy.

The Court confirmed that infrastructure originally developed by public authorities can fall within refusal-of-access analysis where it is subsequently controlled by a dominant undertaking, subject to the conditions identified by the Court.

Importance for municipal data

This is particularly relevant to municipal privatisation and concession models.

For example:

Municipality creates data infrastructure → private operator receives exclusive concession → operator controls access → competitors request access.

The fact that the underlying infrastructure originated with a public authority does not, by itself, resolve the competition question.

13. Municipal Data Exclusivity — Step-by-Step Competition Test

A competition authority can analyse the arrangement through the following framework.

Step 1 — Identify the data

What exactly is exclusive?

Examples:

  • raw data;
  • historical data;
  • real-time data;
  • metadata;
  • APIs;
  • analytical outputs;
  • geospatial information.

Step 2 — Identify the data controller

Is it:

  • municipality;
  • municipal company;
  • concessionaire;
  • private contractor;
  • public-private partnership?

This matters because competition law generally focuses on the economic activity and the relevant undertaking rather than simply the entity's public/private label.

Step 3 — Define the relevant market

Possible markets include:

  • parking applications;
  • waste-management technology;
  • transport applications;
  • urban mapping;
  • building-information services;
  • energy-management systems;
  • environmental analytics;
  • smart-city software.

Step 4 — Determine whether the data is indispensable

Ask:

  • Can competitors obtain the data independently?
  • Can they collect equivalent data?
  • Is the municipal dataset unique?
  • How costly is duplication?
  • Is historical data impossible to recreate?
  • Does the data have real-time characteristics?

Step 5 — Examine foreclosure

Does exclusivity:

  • prevent entry?
  • raise rivals' costs?
  • reduce innovation?
  • disadvantage SMEs?
  • protect an incumbent?
  • prevent multi-homing?

Step 6 — Examine discrimination

Compare:

Incumbent access

with

Competitor access

Differences in:

  • timing;
  • quality;
  • quantity;
  • API functionality;
  • fees;
  • format;
  • frequency

can be competitively significant.

Step 7 — Examine justification

Possible legitimate justifications include:

  • personal-data protection;
  • cybersecurity;
  • national/public safety;
  • confidentiality;
  • intellectual property;
  • administrative costs;
  • data accuracy;
  • protection of public infrastructure.

But the restriction should generally be necessary and proportionate to the legitimate objective.

14. Exclusive Municipal Data Concession

Consider:

A city gives Company A a 10-year exclusive right to commercialise all parking data generated by municipal parking meters.

Company B requests the same data to develop a competing parking application.

Competition concerns

The authority should investigate:

  1. Is the data unique?
  2. Can Company B obtain equivalent data elsewhere?
  3. Does Company A operate in the downstream market?
  4. Does exclusivity prevent competing applications?
  5. Why was the 10-year exclusivity necessary?
  6. Was the concession competitively tendered?
  7. Could a shorter period achieve the municipal objective?
  8. Could anonymised data be supplied to competitors?
  9. Is the restriction proportionate?
  10. Does the arrangement create a protected incumbent?

15. Municipal Data and Public Interest

Municipalities are not ordinary commercial data holders.

They may have legitimate reasons to restrict data access.

For example:

Privacy

A municipal dataset may contain personal information.

Security

Detailed infrastructure information may create security risks.

Confidentiality

Procurement or commercial information may require protection.

Public safety

Real-time information about sensitive infrastructure may need restrictions.

Data integrity

Uncontrolled modification or redistribution may undermine public databases.

Therefore, competition law should not be interpreted as requiring unrestricted publication of every municipal dataset.

Instead, the central question is often:

Can the municipality achieve its legitimate public objective through a less restrictive and non-discriminatory mechanism?

16. Duration of Exclusivity

Duration is particularly important.

A short exclusive arrangement may be easier to justify where it is genuinely necessary to:

  • develop infrastructure;
  • recover investment;
  • establish a new public service;
  • develop a specialised processing system.

A long-term exclusivity arrangement can create greater foreclosure concerns.

EU public-sector data legislation specifically addresses exclusive arrangements and requires exceptional circumstances for exclusivity; the framework also requires transparency and appropriate limitations on the duration of exclusive rights.

17. Exclusive Data vs Exclusive Service

An important distinction is:

Exclusive service contract

The municipality may legitimately appoint one contractor to perform:

municipal waste collection.

Exclusive data right

The municipality additionally grants that contractor:

exclusive rights over all waste-related data for commercial exploitation.

The second restriction requires a separate competition assessment.

The fact that a company has been awarded a municipal service contract does not automatically mean that it should receive perpetual or unrestricted exclusive rights over all data generated in performing that contract.

18. Data Exclusivity and APIs

API restrictions are increasingly important.

Suppose:

Municipal database → API → Company A

Company A receives:

  • real-time access;
  • historical data;
  • bulk downloads.

Competitors receive:

  • weekly CSV files.

This may amount to functional discrimination even if the municipality technically claims that the data is "available to everyone."

The relevant question is whether the access conditions provide equivalent competitive opportunities.

19. Municipal Data and Self-Preferencing

A municipality may also create concerns where it owns a platform and simultaneously favours one commercial service.

Example:

Municipality operates a mobility platform → municipal platform gives preferred data access to its affiliated service provider → independent providers receive delayed information.

Potential concerns include:

  • discrimination;
  • leveraging;
  • foreclosure;
  • self-preferencing;
  • unequal access.

The analysis would depend heavily upon whether the municipality or its affiliated entity is engaging in an economic activity and whether competition law applies to that conduct.

20. Municipal Data Exclusivity and SMEs

Exclusivity can have disproportionate effects on smaller firms.

A large incumbent may possess:

  • alternative datasets;
  • proprietary analytics;
  • greater financial resources;
  • established customer relationships.

A startup may depend heavily upon municipal data.

Therefore, denying municipal data can raise barriers to entry even when the incumbent can survive without it.

However, dependence alone is not enough to establish an essential-facilities violation; the demanding requirements derived from the refusal-to-supply jurisprudence remain important.

21. Remedies

Where problematic municipal data exclusivity is established, possible remedies can include:

1. Non-exclusive licensing

Allow qualified competitors access.

2. Equal-access obligation

Provide equivalent data to similarly situated firms.

3. API access

Create standardised technical access.

4. Data portability

Permit competitors to obtain usable datasets.

5. Interoperability

Require compatible technical standards.

6. Reduced exclusivity period

Shorten the duration of the arrangement.

7. Transparency

Publish the existence and terms of exclusive arrangements.

8. Non-discrimination

Require identical access criteria.

9. Data separation

Separate public-service data from commercially exploitable information.

10. Structural or contractual remedies

In serious cases, modify or terminate an exclusive concession or contractual arrangement.

22. Key Distinction: Data Ownership ≠ Competition Immunity

A municipality's ownership or lawful control of data does not automatically answer the competition question.

The relevant issues are:

Control → Market power → Importance of data → Indispensability → Foreclosure → Justification → Proportionality

Similarly, a private operator cannot necessarily claim:

"I paid for the infrastructure, therefore I can permanently exclude competitors from all data generated through it."

The legal analysis depends upon the applicable contractual, property, procurement, data-protection and competition regimes.

23. Practical Examples

Municipal datasetPotential competitive concern
Parking dataExclusive mobility-app access
Traffic dataExclusive navigation services
Waste dataExclusive recycling analytics
Building-permit dataExclusive property analytics
GIS dataExclusive mapping services
Public-transport dataExclusive journey-planning platform
EV-charging dataCharging-platform foreclosure
Energy-consumption dataEnergy-management exclusion
Environmental dataExclusive environmental analytics
Smart-city sensor dataAI/service-provider foreclosure

24. Important Case-Law Principles

CaseMain principleMunicipal data relevance
Bronner v MediaprintStrict conditions for compulsory accessIndispensability of municipal dataset
IMS Health v NDC HealthExceptional access obligation involving protected resourcesProtected municipal databases
Microsoft v CommissionInteroperability information can be competitively importantMunicipal APIs/platforms
Clearstream v CommissionAccess to important infrastructureMunicipal digital infrastructure
Slovak Telekom v CommissionRefusal/access obligations and dominanceExclusive municipal platforms
Lietuvos geležinkeliai v CommissionExclusionary conduct involving important infrastructureWithdrawal/restriction of municipal data access
Lukoil Bulgaria/BurgasPublicly developed infrastructure can remain relevant to access analysis after transferMunicipal concession/privatisation models

The EU Commission's current competition materials continue to cite Bronner, IMS Health, Clearstream, Microsoft, Slovak Telekom and Lietuvos geležinkeliai in its refusal-of-access framework.

25. Conclusion

Municipal data exclusivity is not automatically unlawful, because municipalities may have legitimate reasons to restrict access to particular datasets.

However, competition concerns become significant where:

a unique municipal dataset + exclusive access + substantial market power + downstream competition + lack of reasonable alternatives + significant foreclosure + inadequate justification

combine to restrict competition.

The central legal principles come from Bronner, IMS Health, Microsoft, Clearstream, Slovak Telekom and Lietuvos geležinkeliai, supplemented by the developing European public-sector-data framework.

LEAVE A COMMENT