Data Debits are the cornerstone of the permission-based, data contracts platform. As the rights to the HAT PDA database are fully owned by the HAT PDA owner, any data acquisition from the database would require permission. When permission is granted, a legitimate contract is agreed upon. This is not the same as consent. The HAT PDA Data Debit process flow enforces a strictly-defined format defining the specific data requested for the owner to review and confirm. Once the data-sharing permissions are given, the contract between the HAT PDA owner and the application provider is logged and Data Debits becomes the only way data can be retrieved from a HAT PDA by anyone other than the owner.
The standard approach is for applications to have access to a single designated namespace. It is
possible to have data access to other unrelated
namespaces. This can be achieved through a domain-specific
mechanism. By default, all applications have read and write access to the
namespace specified upon creation but if
for example, the application needs to read users' facebook posts, then a
data debit will have to be created by the
application developer and be accepted by the users.
Notables application has a
data debit in order to fetch and display the HAT profile information.
Data debit confirmation process is incorporated into the HAT PDA Microserver Instructions
HMI) agreement screen that details which application requests access to what data. Users have to agree in order for
data plug to function as intended.
The more general process of creating a Data Debit is:
The general process of getting the values from a Data Debit is: