MyData, and what a \"personal data operator\" is supposed to be

Somebody named this pattern before we existed, and it was not us. A European non-profit defined what an operator of personal data should be, and implementers were building to it years before Solidus.

What the organisation is

A non-profit, not a vendor. It has over 100 organisation members and nearly 400 individual members across more than 50 countries, and it publishes a Declaration setting out its mission and principles.

It ships no infrastructure. That is not a shortfall, it is the role. Somebody has to define the vocabulary and the principles before a market can form around them, and the definitional work is genuinely harder to fund than the code.

And a correction to our own note, which recorded roughly five hundred members across forty-plus countries: the composition is about a hundred organisations and nearly four hundred individuals, across more than fifty countries. Different shape, and worth getting right on a page whose whole purpose is giving credit accurately.

What an "operator" is supposed to be

The party that acts for the person rather than for the data's consumers. It holds or brokers access, executes permissions, and answers to the individual, structurally, not as a marketing posture.

The idea is older than most current products and it is the frame most of this field is now working inside, including this one. A pod is one implementation of that idea, and it is Solid's implementation, not ours.

What the award is, and what it is not

An annual recognition running since 2021, with 76 service providers recognised to date.

Here is the part worth stating plainly: holders must be members of the organisation and must have signed its Declaration.

So it is a recognition scheme within a membership body, awarded against a shared set of principles, not an independent audit of anybody's software.

That is precision, not a criticism. It is exactly the distinction this estate is obliged to make about its own credentials, a registry entry is an entry in a list, not a standard, and the same care is owed to somebody else's badge. Applied honestly it means the award tells you an organisation aligned itself publicly with a set of principles. It does not tell you their code does what they say.

The implementation that deserves the credit

An open-source personal data store built by a Japanese consortium, with deployments trialled in health, finance and tourism, and recognised under this award.

It predates us, it is open source, and it is a working implementation of the operator model. Anyone reading this estate should know it exists, and we are not comparing ourselves to it on this page, because a comparison would need measurements we have not made.

Where we sit, which is outside all of it

We hold no Operator Award. We are not recorded as a member in our own memberships list. We have signed no declaration here and are certified as nothing.

A page about a recognition scheme is exactly where an estate like this would be tempted to imply alignment, "we share these principles" costs nothing to write and means nothing. We share the principles in the sense that anybody can say so, which is not a membership and not an award.

Why the model matters more than the badge

Because the operator question is the one this whole field keeps failing. Deployments exist, products have died of economics rather than engineering, and the surviving pattern in every case is somebody accountable to the individual rather than to the data's buyers.

That is a governance property, not a technical one, which is why we cannot ship our way into it, and why the trust that makes an attribute useful is granted rather than built.