A group of neighbors wants to share electricity consumption records to study ways to save energy. Before handing over the information, they need answers to several questions: Who can see it? For what purposes? For how long? Above all, who will decide whether to grant a new request for access?
A data cooperative offers a way to organize those decisions. Its members jointly govern services related to their data and agree on conditions for sharing it or allowing others to use it. The organization can help them understand proposals, negotiate terms, and manage access. Its legal form and specific powers depend on the country and the rules it adopts.
What sets the model apart is members' participation in governing the service. An agricultural cooperative that uses a customer database, for example, is not automatically a data cooperative.
From individual contributions to common rules
Return to the hypothetical example of the neighbors. Each household has consumption records and could try to negotiate separately with researchers or providers. By organizing, participants can establish a common process for evaluating requests.
The process might work like this:
- Define the purpose. Participants agree to study consumption habits to identify opportunities to save energy. They also establish which uses fall outside the project.
- Limit the information shared. They decide which records are needed and how detailed they should be. Sharing a monthly total is different from sharing hourly readings associated with each home.
- Evaluate a request. A research team explains what it needs, what analysis it will conduct, how long it will retain the information, and what results it will provide in return.
- Apply the authorizations. The cooperative checks that the request complies with its rules and that the necessary authorizations and other applicable requirements are in place. It then manages access within those limits.
This process can make coordination easier, but it needs people responsible for carrying it out and technical means to control access. A vote alone does not configure permissions, monitor uses, or resolve incidents.
Nor should consumption records always be assumed to be non-personal data. If they make it possible to identify a person, different obligations must be considered. Combining many records does not automatically remove their personal character. That is why data minimization is useful from the outset: requesting and sharing only what is necessary reduces the information exposed.
Key idea: The cooperative organizes who can make decisions and under what conditions access is allowed. Its usefulness depends on those rules being enforced in practice.
What the cooperative decides and what each person retains
The organization needs to distinguish two levels. One is governance of the entity: electing representatives, approving budgets, setting criteria for accepting projects, or overseeing those who manage the service. The other is the processing of each participant's data.
A majority can approve a general policy without thereby gaining permission to authorize any use of everyone's personal information. In the European Union, for example, the Data Governance Act recognizes data cooperative services as a form of intermediation, but does not itself create a legal basis for processing personal data. That distinction appears in Articles 1(3), 2(15), and 10(c) of Regulation (EU) 2022/868.
Control and ownership also need to be distinguished. A person may have powers to authorize access, request information, or demand compliance with a contract. That is not the same as holding a universal property title over personal data, as though it were an object that could be sold with identical consequences in every country.
From a liberal perspective, voluntary association allows people to coordinate their interests without requiring each individual to negotiate alone. But that advantage depends on limits to representatives' power and respect for the rights of those who join. The word “cooperative” does not resolve that tension by itself.
Consent, withdrawal, and leaving are different decisions
Consent is one possible legal basis for processing data, though not the only one. Under the European framework, the GDPR allows consent to be withdrawn without making processing previously carried out under valid consent unlawful. The right to erasure also has conditions and exceptions. These distinctions appear in Articles 6, 7(3), and 17 of the General Data Protection Regulation.
Exit rules should therefore explain separately what happens to membership, permissions for future uses, and information already used. Promising that leaving the organization undoes all past uses would be misleading.
Key idea: Voting on common rules, authorizing a use of data, and leaving the organization are distinct decisions. A credible cooperative explains how they relate to one another.
Who pays and who is accountable
Storing information, maintaining systems, reviewing requests, and handling complaints all cost money. A cooperative must explain how it covers those costs: through membership fees, service charges, project funding, or other sources. Each option can create different incentives.
If it relies heavily on one client, for example, members may ask how much freedom it retains to reject that client's proposals. High membership fees might exclude some participants. These risks should be assessed in each design; they are not inevitable outcomes of the model.
Before joining, a prospective member can use these questions to assess the cooperative’s rules:
- Representation: Who can vote, and how are those who manage the service elected or removed?
- Transparency: What information do members receive about requests, access, expenses, and conflicts of interest?
- Accountability: Who handles misuse, and what process is available for complaints?
- Exit: How are permissions revoked, and which obligations continue after someone leaves?
Participation also takes time and knowledge. Meetings may be formally open while few people understand the technical decisions. Understandable reports, oversight, and procedures for challenging decisions help make member control practicable.
How data cooperatives differ from other intermediaries
The most useful comparison asks who governs the service and to whom it is accountable. A commercial platform, a data broker, and a cooperative can all be involved in access to information, but their users do not necessarily have the same power to direct them.
In a data cooperative, the model gives members a role in governing the organization. In other intermediaries, decisions may rest with the company's owners, and the relationship with users may depend chiefly on contracts and applicable regulation.
That difference does not prove that every cooperative protects information better or that every commercial intermediary acts badly. A comparison requires examining permissions, obligations, controls, and avenues for complaints. Even within a cooperative, being a service user can differ from being a member with a vote.
MIDATA: a documented case with a specific scope
MIDATA provides an example of the distinction between use and membership. Its 2019 statutes, available in an unofficial English translation, describe a nonprofit cooperative in Zurich, Switzerland. They provide for accounts for members and nonmembers; each member has one vote at the general assembly.
A 2021 case study by Gille and Vayena describes its relationship with health data and distinguishes between users and members. It helps explain the institutional design, though it is not an independent evaluation of outcomes.
The case shows how collective governance of an organization and individual decisions about information use can coexist. The documents cited are not enough to certify current rules, effective member participation, or absolute security.
What a cooperative would need to earn trust
A cooperative can pool knowledge and help negotiate terms that would be difficult to discuss individually. The value sought need not be a payment: it might consist of supporting research, receiving useful services, or better understanding proposed uses.
These are possibilities, not guaranteed benefits. Access to more information can increase exposure risks; administration can be costly; and low participation can concentrate decisions in a small group. Each project needs to explain what participants gain and what commitments they take on.
Key idea: Value is not measured by income alone. A real ability to decide, obligations on those managing data, and the ability to leave also matter.
For a neighbor considering sharing electricity records, the test is concrete: being able to understand a request, knowing who approves it, understanding the limits on access, and having a useful procedure if something goes wrong. These conditions help determine whether the cooperative turns a willingness to share into an agreement its members can control.
Share