Resources
Search…
⌃K

Dataswift ONE APIs

Dataswift ONE is a patent pending technology that exists in three parts. First is the provisioning of "HAT Microservers" as Personal Data Accounts (PDAs) for individuals at the request of websites and applications, (data rights); second, the technical, economic, and legal services for collecting, storing, processing and sharing i.e. the movement of data into and from PDAs (data mobility) and third, the access controls and visualisation of PDA Data by individuals through their PDA dashboard, called the HAT App (data control).
Data into and out of PDAs can only be enabled with the authorisation of PDA owners through their acceptance of a legally binding contract for data exchange, called the HAT Microserver Instruction Contract (HMIC). This contract enables PDA owners to license the data from namespaces or folders within their PDAs to applications, or specific bundles of data, or the use of the namespace itself to the application. When PDA owners confirm their contracts, dataplugs can be enabled to bring data in from open APIs, websites/applications can read or write data from/into the PDA, and tools can be installed and enabled in PDAs to create private analytics and insights. Dataplugs, websites/applications and tools may be supplied by any person or organisation (called “merchants”), but they would all need to go through Dataswift governance services before going live.

Principles

The Dataswift ONE Platform uphold the following operating principles subject to regulation and oversight by the HAT Community Foundation (current implementation level as of June 2020 - 80%)
  • 1. Ensuring data rights of PDA owners
    ‌PDA owners own their personal data servers legally and have intellectually property rights over the content of their database, including the right to give rights, ensuring that the personal data within forms part of their asset.
  • 2. Ensuring data mobility of PDA Data
    PDA owners have the ability to contract their data and create value with their data safely and securely.
  • 3. Ensuring control of data by PDA owners
    PDA owners have control over their data through a PDA dashboard to disable access to third party tools, apps and plugs
  • 4. Upholding trust and credibility of the platform for the collective
    The platform must build trust and credibility to ensure PDA owners’ safety in transacting on personal data
  • 5. Preservation of identity/persona choice by PDA owners
    PDA owners can authenticate themselves through their servers but have the choice to be identified, not identified or identified through personas
  • 6. Preservation of privacy by design
    The platform and applications that integrate with the platform should ensure that privacy and informed choice must go hand in hand
  • 7. Ensuring portability of PDAs
    PDAs must be portable ie downloadable to PC, taken off the cloud, move between issuers.
  • 8. Upholding standards for responsible and transparent data conduct
    Platform and applications must transparently explain how they handle users personal data.