A neighborhood cooperative decides to introduce a loyalty card. The idea seems small: record purchases to offer discounts and learn which products to order. Within a few months, the information also helps adjust opening hours, negotiate with suppliers, and decide which campaigns receive a budget. None of those decisions is odd on its own. What usually leaves the conversation is that the knowledge making them possible did not appear by magic in a spreadsheet. People produced it, through their routines, doubts, and needs, when they passed a card through a reader.
Talking about data only as privacy leaves an important part unnamed. Privacy asks who may look, for how long, and under what limits. It is an essential question. But there is another one: when millions of tiny traces become forecasts, savings, bargaining power, or new services, who receives the benefit and who bears the costs? The invisible economy of our data is not only about targeted advertising. It is about turning collective experience into an asset an organization can monetize while the community barely knows the process or can discuss its terms.
This perspective does not require paying for every interaction as if it were a separate task, nor does it require us to stop sharing useful information. It asks us to see the whole circuit. One person contributes a signal; many signals together create knowledge; that knowledge changes prices, access, priorities, and opportunity. If value travels along that route in only one direction, dignity is reduced to accepting or rejecting a box. Justice begins when the people making the resource possible can understand the exchange, question its consequences, and take part in the returns that affect them.
Data does not arrive at the warehouse by itself#
We say a platform “collects” data, as if it were lying on the ground waiting to be picked up. In reality, most information is born in a relationship. It is created when someone explains a symptom to a health service, marks a street as dangerous on a map, corrects a delivery address, or learns which button prevents an error in an app. Even apparently automatic records rely on collectively funded infrastructure: networks, schools, rules, family care, and work that allow someone to be connected and act.
We say a platform “collects” data, as if it were lying on the ground waiting to be picked up.
Recognizing that production does not mean claiming absolute individual ownership over every record. Much data is relational: a shared route, a neighborhood trend, or a mobility pattern speaks about more than one person. It can also create real public benefits, such as detecting an accessibility problem or improving a service. The point is to prevent the collective character of knowledge from becoming an excuse to privatize it without limits. When a company concludes that an area can pay more, a profile deserves less attention time, or a group is a risk, that conclusion returns to social life as a concrete decision.
That is why consent, although necessary, cannot carry all the responsibility. A long screen does not explain how today's data will interact with tomorrow's sources. Nor does it enable genuine negotiation for someone who needs a service to work, study, or receive a benefit. A fair arrangement requires obligations for those who combine, retain, and monetize information. The practical question is not only, “Did the person agree?” It is also, “What decision-making capacity did the organization acquire through that agreement, and what safeguards keep it from being used against the community that generated it?”
Following the value chain changes the conversation#
Imagine a municipal app that invites residents to report broken streetlights. Neighbors send photos and locations because they want safer streets. The city can use reports to plan repairs: that is the expected purpose. But if a vendor keeps the images, combines them with other databases, and sells analysis of night-time activity, another business has been born. It may be legal under a remote contract. Yet the community contributed observation work to solve a public problem and ended up feeding a product that was never explained.
A responsible review draws the chain before the service launches. It should show which signal enters, what inference follows, which third party participates, what decision it enables, and what economic or strategic value appears at every step. It does not require revealing technical secrets to say whether photos are reused, data is aggregated with commercial sources, or a vendor may train its systems on them. The map turns a vague promise to “improve the experience” into answerable questions: what leaves the project, who controls it, and what returns to those who participated?
It also helps separate revenue from benefit. A company may never sell a database yet gain an enormous advantage by lowering costs, anticipating demand, or strengthening its position against competitors. A university may train a tool with civic contributions and then license results to another organization. Value does not vanish because there is no invoice attached to each row. Naming these advantages prevents the rhetorical trick of saying that “nobody buys your data” while hiding the power created by their combinations.
From symbolic payback to shared benefit#
The answer does not have to be an individual reward for every click. That model can turn financial need into pressure to accept invasive uses and it does not resolve collective harms. More sensible ways of returning value exist. A transport project that learns from journeys can fund verifiable improvements in the neighborhoods contributing information. An education platform can share materials, audits, and aggregate findings with schools and families instead of enclosing learning in a proprietary product. Research using community contributions can reserve resources for local follow-up and open access to useful findings.
The standard is not to hand out a promotional perk. It is to link the return to the purpose and let the community discuss it. If data helps decide where in-person service will be reduced, a benefit does not compensate for the harm with a voucher. Representation in the decision, assessment of effects, and a route to correct course are needed. If records instead identify a dangerous crossing, the return may be a prioritized repair, a clear public report, and a commitment not to reuse images for surveillance unrelated to the goal.
Collective mechanisms are especially important when people do not have equal bargaining capacity. Consumer associations, data cooperatives, unions, libraries, and neighborhood organizations can review terms that one person lacks the time or expertise to read. Their role is not to authorize everything on the community's behalf; it is to create a table with information, mandate, and accountability. An organization seeking to use a group's data should be able to explain why that group is not merely supplying material but also helping define limits and return.
Measure harm before celebrating efficiency#
Value extraction becomes more serious when it produces a classification other institutions treat as truth. A purchase history can feed a risk calculation; a connection pattern can become suspicion; an area with less digital activity can seem less profitable and receive poorer service. These consequences are not always present in the first contract. They emerge from later links, purchased models, and automated decisions that turn a limited observation into a prediction about a person.
That is why responsible economic assessment must include a distributional assessment. Who gains time, money, or information? Who is exposed to different prices, exclusion, or profiles that are hard to correct? Which groups contribute more sensitive signals because they depend more on a service? The answer cannot come from a single overall satisfaction figure. It requires reviewing edge cases, comparing effects across groups, and maintaining a human route with authority to stop a use that drifts from its purpose.
An organization can adopt a simple operating rule: no secondary use is approved merely because it is technically possible or profitable. It must pass three tests. The first is necessity: is there a less intrusive way to achieve the goal? The second is legitimacy: would reasonable people who contributed recognize this use as part of the exchange? The third is return: does the benefit stay entirely with the infrastructure operator, or does it verifiably improve conditions for the people who made the knowledge possible? If one fails, the work is redesign, not a longer notice.
An account the community can inspect#
Useful transparency is not publishing an unreadable policy. It is offering a readable account of the data cycle: original purpose, combined sources, meaningful inferences, recipients, retention period, affected decisions, and benefits gained. Alongside it there must be a review channel with deadlines, staff able to respond, and power to correct. A person does not need a model's source code to know that their data helped build a rule that now restricts their options.
This account must be revisited when context changes. Information gathered to improve deliveries can acquire a different meaning when combined with debt, health, or location. Those responsible need expiry dates, reuse inventories, and audits that do not rely only on the interested vendor. Publishing which uses were rejected matters too: it shows that limits exist before a scandal and that caution is not a communications slogan.
The concrete first step is not asking everyone to read another policy. An organization can choose a dataset it already uses, gather the people managing it, and answer six questions on one page: what was contributed, what was inferred, what decision it enabled, who received value, what risk emerged, and what return or limit was agreed. It should then test that page with people affected and change it if it is not understood. Turning data into a shared resource does not eliminate innovation; it gives innovation a more honest foundation. The invisible economy stops being inevitable when we make visible who works, who decides, and who benefits.
