A personal data store is a service or app where a person keeps their own data and decides which organisations may read it. Solid pods and digital identity wallets are the best-known examples.
It is one answer to the wider question of data privacy: instead of trusting every company to guard a copy of your details, you hold the original and lend access.
What a personal data store is
Most online services work the same way. You type your name, address, birth date and preferences into a form, and the company stores them in its own database. Each new service builds another copy. Over the years a person ends up with many partial profiles, each controlled by someone else, each a possible target for a breach, and each hard to correct or delete.
A personal data store reverses that pattern. The data sits in one place that the individual controls, and services come to the data rather than the other way round. When an app needs a delivery address, it asks the store. The person approves, limits or refuses the request, and can withdraw access later. The store acts as a gatekeeper, a record of who asked for what, and a single place to correct information once.
The term covers several designs. Some are online storage with fine-grained permissions. Some are apps on a phone that hold verified documents. Others are services run by a trusted third party that manage consent on a person’s behalf. What they share is the idea that the individual, not the service provider, is the centre of the arrangement.
Solid and the pod model
Solid is an open project built around this idea. Its own description says that users have personal online data stores called Pods. The project compares the arrangement to carrying all your data in a rucksack with lots of pockets: each app may open only the pocket you allow, and the rest stays private.
The same page explains the mechanics in plain terms. Solid works like a file system for the web, and the person has control over which people, applications and AI agents can read and edit the documents inside it. Because the data lives in the pod rather than inside an app, changing to a different app does not mean starting again or leaving your history behind.
Interoperability is what makes that promise workable. The project states that all data in a Solid Pod is stored and accessed using standard, open and interoperable data formats and protocols, as set out in the project’s overview. If two apps understand the same format, both can use the same data without a private agreement between their makers. Anyone can run a pod server, so the person is also free to move their store from one host to another.
For developers and students, the pod model is a practical area to explore. A small app that reads a calendar or a reading list from a pod, rather than from its own database, shows how an application can be built without hoarding user data. That design choice also shrinks the amount of personal information the app has to protect, which connects to the habit of collecting only what you need.
The MyData idea
Where Solid is a technical architecture, MyData is a broader movement and a set of principles. Its declaration states that MyData wants to build a world where people are empowered with their own data. It sets out goals such as using your data independently in dealings with organisations, asserting your legal data rights effectively, being protected from imbalances of data power, and understanding how your data is collected and used.
The MyData approach is less about one product and more about the relationship between people and organisations. It imagines a world where an individual can see which organisations hold their information, grant and revoke permissions in one place, and reuse their own data for their own purposes. A personal data store is one way of building that world, but so are consent dashboards, intermediaries and open standards for data sharing.
This framing matters because it separates the goal from the technology. A pod, a wallet or a managed service can all fit the MyData vision, provided the person keeps meaningful control. A product that merely stores your data in a nicer interface, while the provider still decides how it is used, does not.

Data wallets and the EU Digital Identity Wallet
A data wallet is a personal data store specialised for credentials: proof of identity, a driving licence, a diploma, a bank account detail. The W3C, the web standards body, defines the building block. Its specification describes the extensible data model for verifiable credentials, a three-party arrangement in which an issuer makes claims, a holder keeps them, and a verifier checks them. The person in the middle, the holder, decides when to present a credential and to whom.
The largest public example in Europe is the European Digital Identity Wallet. The European Commission explains that Member States will be mandated to offer citizens and businesses digital wallets, which can link national digital identities with proof of other personal attributes such as driving licences, diplomas and bank accounts. The same page describes the aim as giving people full control over their data while accessing online services and eliminating unnecessary data sharing.
The legal text uses similar language. The regulation says the wallet should let people manage their identity and request erasure of their personal data under the sole control of the user, while enabling selective disclosure of personal data. Selective disclosure is the key privacy feature: you can prove one fact, such as a qualification, without handing over a full document that reveals much more.
On timing, the Commission page, last updated on 6 November 2026, says that Regulation (EU) 2024/1183 has entered into force and that Member States must provide wallets to citizens by the end of 2026. Readers who need the current rollout status in a particular country should check the Commission and national government pages, because deployment varies by country.
The page also lists benefits for citizens: they will have the power to choose which aspects of their identity and data they share with third parties. For service providers, it says they can rely less on identity services with unclear use of the obtained user data. Those are the Commission’s stated aims; how well they are met depends on how the wallets are built and adopted.
How data portability law supports the idea
Personal data stores work best when organisations can hand data over in a usable form. In the European Union that expectation has a legal footing. The GDPR includes a data portability right: the data subject has the right to receive the personal data concerning him or her in a structured, commonly used and machine-readable format, and to transmit it to another controller without hindrance, where the processing is based on consent or a contract and carried out by automated means.
Portability is the supply line for a data store. Without it, a person could create a pod or wallet and find it empty. With it, a person can request their records from one provider and place them in a store they control, then share them with a new provider. The right has conditions, so it does not cover every kind of data held about a person.
In the United States there is no single national equivalent. Several states give residents some form of access and portability right, and the details differ. The guide to us state privacy laws explains how those rules compare. Readers should check the current text of the law that applies to them, or ask a qualified lawyer, because this overview is not legal advice.
Strengths, limits and open questions
The appeal of a personal data store is easy to state. Fewer copies of your information exist, so there is less to leak. You can see and change what is held in one place. Consent becomes something you operate rather than a banner you dismiss. And if a service closes, your history does not vanish with it.
The limits are just as real. Control carries responsibility: a person who holds the keys can lose them, so recovery and backup design matter. Consent can be overloaded, because a stream of permission requests may lead people to click yes without thinking. Organisations that already hold data have little commercial reason to adopt a model that reduces their control, which is why regulation, such as the European wallet rules, plays such a large role. A store also does nothing about data that others generate about you, such as camera footage or sensor readings in public space, a problem covered in the guide to smart city privacy.
Interoperability remains the practical hurdle. A store is only as useful as the number of services that can read from it and write to it. Open formats help, but they need real adoption by the apps people already use.
Finally, there is the question of the host. A pod or wallet still has to run somewhere, whether on a public body’s infrastructure, a commercial provider or a device. Choosing a host moves some trust rather than removing it, so the rules on security, portability between hosts and independent oversight shape how much control a person really has.
Practical ways to explore the concept
Anyone curious about the model can start by reading the primary documents rather than product pages. The Solid overview, the MyData declaration and the Commission’s wallet page each explain the goals in plain language. Developers can then try building a small app that stores its data in a user-controlled location, and ask at each step what the app really needs to know.
Hackathon teams, a theme that runs through this site, have a natural fit with the topic. A weekend project can prototype a consent screen, a credential-sharing flow or a tool that shows people where their data lives. The test of a good idea is whether the person can understand what is shared, undo it, and see the record afterwards.
For everyday users, the lesson is simpler. Treat any service that asks for data as a request, not a requirement. Share the minimum, prefer tools that let you export and delete, and look for services that support open standards. As wallets and stores mature, those habits will translate directly into using them well.
Frequently asked questions
Is a personal data store the same as a password manager?
No. A password manager keeps login secrets for you. A personal data store holds the information services want about you, such as your address or credentials, and controls which services can read it.
Does a digital identity wallet replace a passport?
The Commission describes the European wallet as a way for people to choose which parts of their identity and data they share with third parties while accessing online services. Whether a given document can be replaced depends on national and EU rules, so check the current official guidance.
Who can see the data in a Solid pod?
The project states that the owner controls which people, applications and AI agents can read and edit documents in the pod. Access is set by the person who runs the pod, within the permissions they grant.
Do personal data stores make an organisation GDPR compliant?
No. A store supports individual control, but organisations that process personal data still have their own legal duties. Compliance depends on the law and on how the organisation handles data, so seek qualified advice where needed.
