Intro to HAT User Level


We would like to encourage everyone to ask any questions they have and share their thoughts about the HAT experience in our social media channels:

The HAT and its personal data ecosystem are designed to allow individual HAT Users to collect, contextualise and exchange our personal data. The enabling technology for the HAT sits within the HATPDP (mostly referred to as “HAT”). The Personal HAT is a person-“oriented” personal data platform, owned by the individuals, that allows to unpick the silos in which our personal data sits and to collect all this data which we can acquire from internet connected objects or services. The HAT then allows the transformation of this acquired data for individuals to contextualise and organise, to mate it meaningful and useful for control decisions and actions. With that data, individuals can buy apps to analyse, view, create scenarios, trade or make important decisions based on our own data for a smarted and more effective life. The HAT is therefore fully scalable platform that allows firms to offer individuals services for our personal data, and yet enables us as individuals to personalise that data to our own needs.

A HAT can be described as being analogous to an email account. As an individual HAT User we can choose our HAT provider (also known as HPP in the HAT ecosystem) just like we choose our email account provider, and we can switch HPPs as there maybe be many such providers. Or, if you want to host your own HAT, your Personal HAT can be configured to sit on your private server. In essence, individual HAT Users get to decide where we want out HAT, how to access our HAT and how to organise our HAT.

How can the HAT be hosted?

The HAT may be hosted in three different ways (depending on the providers). There are several types of Personal HATs:

  1. Hard HAT: a HAT that is a fixed server with a fixed IP address, for example a smart home hub for home sensors. Likely to be on the HAT User’s LAN network.
  2. Sun HAT: a HAT that is cloud based. The Sun HAT is expected to be the most popular Personal HAT model, where every HAT potentially sits on a micro cloud server owned by the individuals and hosted by HPPs. For example, Virtual Machine based cloud servers operated in data centres.
  3. Straw Hat: a hybrid of fixed and cloud based HAT. E.g. some HAT data will be stored in a home hub, while other data will be stored in a cloud service. A straw HAT can also be a HAT that access personal data (without the need to store it) from distributed networks and where personal data can sit at the source of where it was generated (Note: Straw HAT will not be part of the initial release).

What happens when I sign up for a HAT?

Technically, by signing up for a HAT with a HPP, you will be provided with:

  1. Universally Unique Identifier (UUID) to serve as the identification for a particular HAT in the ecosystem. A UUID in a HAT may take a DNS (domain name service) type approach; for example, Alice’s HAT may be certified as This naming convention is designed for all parties in the ecosystem, e.g. for a developer Paula, and for HPPs Noggin and Enable ID respectively.
  2. A HAT Database built on the HAT Database Schema. Depends on the chosen HPP; the actual database engine may differ as long as the HAT Database Schema is followed. The HAT Database schema (currently at alpha stage) is issued under the Creative Commons Attribution-NoDerivatives 4.0 International ( Future schema (beyond beta version) will be released under Creative Commons Attribution-ShareAlike 4.0 International (
  3. APIs to access your data (Input and Output) for other parties, as well as “Management” level APIs for the individuals (Input, Output and Management).
  4. A Hyper Data Browser, where you can see your data in your HAT, delete or move your HAT to a different HPP.