How to access PDA data with the Dataswift One platform.
There are currently 3 supported methods of Data Access on the Dataswift One platform:
- First-party read and write by applications
- Zero-party read via data debits
- Third-party write by data plugs
First-party access involves read-and-write data access to a namespace that an application "owns" within the user's PDA. The application has both read-and-write access that allows them to pull and deposit data within the designated namespace, with there being a one-to-one relationship. This data access is privileged to Applications. The application actively generates (or co-creates) data with the user.
Zero-party access describes data access that involves read-only permissions from a PDA, albeit across namespaces. The access permits only the reading (or pulling) of data from the PDA but it can access multiple namespaces. This access is specifically designated for Data Debits. It means that an application can essentially "debit" data from multiple namespaces (i.e., folders) co-created by the PDA user and another application. The application does not actively create, but is a mechanism whereby data is consensually "debited".
Third-party access describes data access that involves write-only permissions to a user's PDA, but only to a specific namespace. The access permits only the depositing of data into the PDA and into a single namespace (i.e. folder). This access is specifically designated for Data Plugs. It means that an application can store data within a PDA. The application does not create as such, but instead just deposits data that is generated outside the Dataswift One infrastructure.