0DATA.APP vs Zero Data Protocol: User-Owned Data

What is 0DATA.APP?

0DATA.APP, also presented as Zero Data App, is a directory and community reference for applications that keep data under the user’s control. Instead of requiring a person’s information to live inside a provider-controlled account, a compatible app can request permission to access storage chosen by the user.

The approach changes the traditional relationship between applications and personal information. The app becomes a tool that works with the user’s data rather than the permanent owner and exclusive gateway to it.

TRADITIONAL MODEL

Data locked behind the app

The provider stores the information. Access, continuity and export depend heavily on the application and its account.

0DATA MODEL

The app comes to the data

The user controls storage and authorizes an application to access the necessary information.

The six principles behind 0DATA

1Data stays with the userThe application is not intended to become the exclusive custodian of the user’s information.

2User-chosen storagePeople decide where their data is stored instead of accepting one mandatory provider silo.

3Bring your own identityThe model favors access without the usual signup, password, captcha and account funnel.

4Open protocolsInteroperable standards create flexibility between applications and storage providers.

5Data freedomUsers should be able to access, move and use their own information whenever they choose.

6Application independenceData should remain accessible even if a particular application stops operating.

0DATA demonstrates these ideas through applications and examples using open protocols such as remoteStorage, Fission and Solid.

What Zero Data Protocol adds

Zero Data Protocol is an independent architectural framework. It does not prescribe one storage protocol or application ecosystem. It evaluates the lifecycle of personal and sensitive information through three structural principles:

Zero CollectionDo not request or capture personal data that the intended function does not genuinely require.

Zero RetentionWhen processing is necessary, avoid persistent storage beyond the required operational moment.

Zero ExploitationDo not reuse data for profiling, advertising, unrelated training or other secondary purposes.

ZDP therefore asks questions that remain relevant even when the user owns the storage: does the app need access to this field, must the information remain identifiable, should the result persist, and may another service reuse it?

0DATA.APP vs Zero Data Protocol

Dimension	0DATA.APP model	Zero Data Protocol
Primary objective	User ownership, portability and application independence	Remove unnecessary personal-data dependency from system design
Meaning of “zero data”	The app does not control the user’s data silo	Zero unnecessary collection, retention and exploitation
Where data lives	In storage selected or controlled by the user	Preferably absent; otherwise in the least exposed necessary environment
Persistent storage	Often intentional so the user can retain and reuse information	Challenged unless persistence is functionally necessary
Application access	Granted by the user as necessary	Limited to the minimum fields and duration required
Identity	Bring your own identity; no mandatory app-specific account	Prefer anonymous or unlinkable operation whenever identity is unnecessary
Interoperability	Central principle supported by open protocols	Valuable when it also preserves minimization and purpose boundaries
Secondary use	Depends on the app, permissions and implementation	Unrelated exploitation is structurally rejected
Type	Application directory, principles and user-owned-data ecosystem	Independent architectural framework
Relationship	Strongly compatible in spirit, but compliance with one does not establish the other

Where 0DATA and ZDP strongly align

Control over custodyBoth challenge the assumption that every application should permanently control a central copy of user data.

Reduced lock-inOpen and portable architectures can preserve access when a provider changes, closes or becomes unsuitable.

Permission boundariesApplications should receive only the access needed to perform the function chosen by the user.

For ZDP, a well-designed 0DATA application can be a strong architectural foundation because it separates the application from permanent custody. The remaining work is to verify necessity, retention and secondary use at every interaction.

The decisive difference: ownership is not absence

User-owned data can still be abundant, persistent, identifiable and highly sensitive. Moving custody away from an application provider changes who controls the information, but it does not automatically minimize how much data exists.

An app may also receive temporary or continuing access to the user’s store. The technical permission must therefore be examined: can the application read more than it needs, create a copy, generate identifiable logs, send data to another processor or retain derived profiles?

In one sentence: 0DATA asks, “Who controls the data and where does it live?” ZDP also asks, “Why must it exist, how long may it persist, and what may be done with it?”

How to evaluate a user-owned-data application

Identify the storage authority. Confirm who operates the storage, who holds credentials and who can recover or revoke access.
Inspect permission scope. Grant access to the smallest necessary dataset rather than an entire personal store.
Test for hidden copies. Determine whether data is cached, indexed, logged, backed up or transmitted to analytics and support services.
Separate identity from function. Check whether the app can work with a pseudonym, local key or anonymous session instead of a stable identity.
Map derived data. Recommendations, scores, embeddings and profiles can remain sensitive even when raw data stays with the user.
Define revocation. Ensure the user can remove access and understand what remains after permission is withdrawn.
Apply the ZDP test. For every field and output, question collection, persistence and secondary exploitation.

Frequently asked questions

What is a 0DATA application?

It is an application designed so that data remains under the user’s control. The user chooses or controls storage and gives the app permission to access information as necessary.

Does 0DATA mean that no data is stored?

No. User-owned data may be stored persistently by design. The difference is that the application does not have to become the exclusive owner or gateway to that storage.

Which protocols are associated with 0DATA?

The official 0DATA site highlights remoteStorage, Fission and Solid as examples of open protocols that support user-controlled or decentralized storage.

Is 0DATA the same as Zero Data Retention?

No. Zero Data Retention concerns whether a provider keeps content after processing. 0DATA concerns user control over storage and application access.

Can a 0DATA app follow Zero Data Protocol?

Yes, potentially. It would also need to minimize requested fields, avoid unnecessary persistence and prevent unrelated secondary exploitation.

Are 0DATA.APP and Zero Data Protocol affiliated?

No affiliation or endorsement is implied. This is an independent architectural comparison based on publicly available principles.

About the author and framework
Lajos Nagy develops and documents Zero Data Protocol as an independent architectural framework. ZDP is not a product certification, a regulatory approval or a substitute for legal and security assessment.

Editorial notice: 0DATA.APP, remoteStorage, Fission, Solid and their respective names may be trademarks or project names belonging to their owners. They are cited for identification and comparative analysis only. No commercial relationship, endorsement or equivalence with Zero Data Protocol is claimed. Implementations can differ; review each application and protocol before making security or privacy decisions.