Posts in Uncategorised
DataBuyer v2.0

Released 16 August 2017

Release notes

New features in this release:

  • Reworked API data structures, authentication procedure and available endpoints
  • Revamped offer creation flow for data buyers
  • Fresh user interface
  • Supports offer filters based on merchant code
  • Coordinates offer management with DEX service
  • Collects available offer data from HATs and stores it in a private S3 bucket
HATTERS v2.0 release

HATTERs gets streamlined with v2.0

- A completely new User Interface for getting a HAT

- Rebuilt backend for API-based interactions

- Modular membership options support based on runtime dependency injection for extensibility and different payment/subscription methods

- Rebuilt Database Access Layer for typesafe abstractions

Milliner v1.4.0

Released 28 July 2017

Release Notes

  • CloudFormation infrastructure revamped to match security guidelines
  • Patching Policy setup for daily updates
  • DDoS mitigation via default AWS services
  • Clarified policies:
    • Data Location policy
    • Backup Location policy
    • Data Retention policy
  • Implemented Log retention and Archiving
  • Improved Database monitoring features
  • Improved HAT scaling monitoring features
  • Setup Host Intrusion Detection System for Docker hosts
  • HAT signup directly on Milliner supported
  • Customised Milliner front pages for different HSPs
HAT Data Browser v2.0 ‘Rumpel’ available on the app store and online

8 Feb 2017: The Hub of All Things (HAT) today announced the release of version 2.0 of its Data Browser, ‘Rumpel’. Rumpel is the private dashboard for users’ HAT data, allowing HAT personal data store customers view and manage their personal information, whilst providing a valuable case study for the viability of the HAT's privacy-preserving data infrastructure. The HAT is a personal data ecosystem sitting on top of technology that stores individuals' personally-identifiable information in private data containers, to which only they have access. HATs provide individuals with increased control and unique data services, and businesses limit their liability to cyber attack while improving their access to contextual information.

Inside the ecosystem HATs can be used to sign into any app or device, and all of the information that's stored in them can be made accessible to the connected device in a secure fashion. HAT infrastructure modularises the user’s account away from their services, so that access can be granted to both while the whole system behaves normally. Upon modularisation, a global standard of exchanges can emerge between these personal data stores and the Internet applications that use them. The HAT is a creator and a champion of these standards. It has tasked itself with rebuilding the Internet's trust for exchanging personal data online, upon which “the foundation of the data economy must be built.”

HAT applications are built on top of a massive platform capability, but are still perfectly normal, as Rumpel 2.0 shows. This release of the product signs on, pulls, and pushes data normally, while behind the scenes the data for the application is coming from private and secure HAT data containers, not the Rumpel service. It is a demonstration of how an application can function and behave in exactly the same way any other app would, but with a completely privacy-preserving backend.

Feature releases in version 2.0:

  • Rumpel allows new users to sign up for a HAT via iPhone
  • Text-based content created in-app is sharable via Twitter
  • New Social Feeds capture user data shared via Facebook and Twitter
  • Some new data streams available for connection into the HAT
  • Sharing options for social posting to Facebook and Twitter were improved

The HAT takes feature requests and hosts product conversations online at and has a public poll for features to enter the development cycle at Rumpel Lite is open sourced at Learn more at



About the HAT at

Reaching Normality

For the longest time, the HAT has talked about personal data stores -- monetising our data, exchanging our data, owning our data, and controlling our data. But there’s a problem.

Every personal data store is always asked, whether by potential customers, investors, or analysts, to be built around a use case. Sure. We get that. But there is a difference between a use case that shows what a personal data store can do, and a personal data store primarily for the use case. The former is about building a platform. The latter is about building an application.

Most personal data stores are content to exist as an application. They work hard to prove the use case of their application, and they build their backend narrowly for that use case alone. Usually, the use case for a personal data store is security, or privacy, or the exchange and monetisation of data. These wonderful, beautiful use cases are more easily seeded, Angel-funded, and attractive to venture capital. They create narrow, singularly-focused businesses that give everyone a sense of certainty on what is intended to be achieved.

We didn't.

By creating a single use case, you absolve yourself of the responsible to think through all of the possible use cases. Creating a single use case also means building the personal data store to be a service, and not a platform. Platforms need careful design, and careful thought, that covers all of the possible services and businesses and transactions that could be performed within their ecosystem. All types of exchange, all types of business model, and all types of interaction. And their rules.

The Hub of All Things is trying to change the entire infrastructure of all of the apps that use personal data. We want it all to sit on a single, personal data store platform. We don’t have just one use case, we have many. We don’t want to build the beautiful vertical application. We want to build the beautiful horizontal platform, on top of which all verticals can sit. That was the technology that the 6-university RCUK HAT research project needed us to build.

As we started to enter the commercial environment with this vision, early conversations with potential funders began to highlight something of a dilemma. Most of the startup industry, before believing in our vision of a personal data platform, craved proof in the form of a vertical use case. Many simply did not believe that this project of ours was feasible.

Sure, everyone likes the idea of a personal data store. Who doesn’t think that personal data is valuable, or that empowering the individual to take advantage of it is important? But they look at what it would take to build a platform capability that can support an entire ecosystem of users and say, “no, it’s too hard.” Most of the data stores heard this message, and retreated -- back to the single use case, a business that can be “later developed into a platform, or not, if we make it -- who cares.” They compromised, and usually for the sake of funding. Those who didn’t went back to preaching the ecosystem in books, papers, and slideware. It went back to being conceptual again.

Because even beyond funding challenges, this is a daunting technology to build. Many believe that Google, Apple, Facebook, and Amazon (GAFA) are too big to beat; that these are simply the platforms that control the Internet ecosystem. Many believe that it would take too long and cost too much to build the security, privacy, and confidentiality capability that is required of a platform of this sort, if it is to be at a capacity that can be usable and acceptable to the market. And many believe that a team with the engineering, economics, and ecosystem design expertise is simply too rare a commodity. The combination of it all is too much. The risks are too high.

We accepted that. And it has made us profoundly grateful to all of those who took the early risks with us when they came out in support almost a year ago. 8 founders, 42 community members, friends, family, and 300 indiegogo supporters gaves us the £150k we needed to get started, and we haven’t looked back since.

With our tall order in front of us and some change in our pockets last year, we went about building the horizontal personal data platform we wanted. We knew that we had to prove that it was possible from an engineering and economics perspective, and we had to de-risk future investments so that this grand vision for the ecosystem could come to pass. We had barely a year or so to do it.

We did it. It is built. A fully-functioning platform for the personal data store ecosystem, with secure protocols for data exchanges between HATs and Internet applications. We are ready to scale.

In the end, as it turns out, we were never out to fight GAFA. We were there to offer an alternative to the "future Internet" so that companies who have IoT devices, and apps, and data-sensitive services could build them in a way that is technically secure, and robust in how it holds onto and uses personal data. We aren’t interested in the Internet of the now. We are interested in the Internet of the future. And with due respect to GAFA, the future isn’t theirs yet.

Rumpel Lite iOS app
Rumpel Lite iOS app

We have seen a future where instead of being forced to use applications built on GAFA, Internet users can benefit from apps built on an open, privacy-preserving Internet. Instead of having to dump our information into databases of accounts, and suffering the security and administrative risks that result, we can gain these services without sacrificing data control. And instead of being left out of the data economy, instead of having one account for every device and application that is out there, instead of the cybersecurity nightmare of 500 different devices and accounts for every one of the millions of Internet users that are out there on this planet, we have seen an alternative.

In the HAT ecosystem, each Internet user's own personal data store can be used to sign into any app or device, and all of the data in it can be accessible to, and usable by, and controllable for the user. They can exchange, use, and analyse all their information. They can buy services and intelligence and analytics for themselves with it, and they can offer it to the companies, governments, and organisations that they give custom. The companies themselves can still use the data their app or device generates, subject (of course) to the data privacy laws of their customers, but individuals will have freedom to do so as well. Personal data, after all, is co-produced.

With this technology platform, the devil is in the details; specifically the engineering and economic details. This has to be a capability, not just a concept. The ability to create infrastructure that modularises the user’s account away from the service or device, so that access can be granted to both while the whole system behaves like a normal service, is a major innovation. And upon modularisation, a global standard of exchanges can emerge between these personal data stores, and the Internet applications that use them. The Hub of All Things is a creator and a champion of these standards, upon which are built strong rules to ensure that personal data is protected, and that protection is enforced, and the free transaction of personal information online can be relied upon. We have tasked ourselves to rebuild the Internet's trust for exchanging personal data online. The trust upon which “the foundation of the data economy must be built.”

Our capability needs to satisfy the technologists, the businesses, the lawyers, and the regulators, all at the same time. It has to just work. And what we have built, does. We called it the HAT – the Hub of All Things. If you have an iOS device, and you use Facebook and Twitter, go and download Rumpel Lite here or, if you're on the browser, get a HAT here and then use web Rumpel here. Try the HAT technology for free, and grab your data from these great social services, and see what you can do with it. Take control of your words, by posting to social media through your HAT and having it take your posts back from them after a few days. See what an application -- a small, minor functionality on top of a massive, platform capability -- can do with the even a little bit of control over our personal data. Our app was not created to be a beautiful, functional, vertical use case, but to show you how normal an app can look when it takes data from this new ecosystem. Rumpel signs on, pulls, and pushes data normally -- but on the backend, it is not normal. The data for the application is coming from your HAT, and not from the Rumpel service. What we seek to demonstrate is that an app can function and behave exactly the same way any other app would, but with a completely different backend. Go and experience it for yourself.  Click here if you want to know the background of the innovation, and the suite of services we have built to create this data infrastructure.

It is not enough to simply rely on good engineering. Technology demands user experience, a proper economic model, and ecosystem governance, all aligned with what the players in this market economy need, if the ecosystem itself is going to gain legs, leap forwards, and become self-regulatory and self-reinforcing. But the mundane, seamless normality of signing into an app, pushing data into it, and pulling it out in turn, is the result of some amazing engineering. I know it sounds crazy that we spent all of this time building something that will behave like every other app on the planet, but that is the point. If HATs can't work seamlessly and behave normally in a standard live environment, that has real users, and a real market, and an actual value proposition, then we will have no cause to think of it as a serious alternative to the status quo. But in just one short year of build, we have achieved that level of normality.

Next, our opportunity will be to watch as a HAT ecosystem of individual personal data stores allows us to exceed normality, and move to a new normal where users can access bots, analytics, and services on top of their HATs. The ecosystem is ready -- for companies, application builders, and individuals. You can build on us, and host HAT services and applications to your customers. We have already welcomed the first four HAT providers to the table: Welcome B.Heard, Noggin, Surrey and Warwick Universities, and we are in conversation with the financial services, security, and identity management industries as well. Maybe you will become the first in your industry to become a trusted HAT Provider to your customers.

Welcome to the future of the Internet.

- Team HATDeX -

HATDeX is now on its strategic investment funding round to raise £800k. The round will close when it's fully subscribed. Interested parties please email

Here is a diagram of how the HAT ecosystem works when personal data sits within HATs and synchronised with all the different apps and services out there. More on the technical architecture will follow.

UncategorisedIrene Ng
A new data infrastructure for personal data exchanges

Privacy could be unworkable.

One of the paradoxes of a privacy-preserving data exchange is that users can be private to the point that the exchange is unworkable. The analogy goes like this: think of your HAT as a private cabin in the woods. You get your privacy, but if you do not have a way of communicating with others, no one will know that you have bins to empty, or need logs or fuel to warm the cabin, or even if you wish to talk to someone. You are private, but that privacy has cut you off from the rest of the world. And no wi-fi either. You are truly. Very. Private.

With today's Internet, of course, you are not at all private, as someone is always watching you and you are never in your own private cabin. When you sign up for an Internet service, they create an account for you, which is like giving you a little space in their common room, usually with a camera installed! Sometimes your landlord even knows what you want before you even want it. You are. Not. Private.

Privacy and Anonymity

Some people think that the solution might be anonymity. So you get to sit in the corner of someone's common room, but you can mask yourself. Sometimes, that could work. But anonymity generates a whole host of other problems because when you think you're anonymous, you have an incentive to behave badly. We think there is a different way. One where you can be private, but not anonymous. Much like the way we are in physical life.

Privacy AND Internet Services

To create a world where you can have privacy and Internet services, we have to create specialist software to retrieve and share your HAT data in a way that ensures privacy. To use the analogy, it means someone checking in with you at your cabin and asking if you have any items to share or give away, and to whom. It's like a concierge service that runs to all the cabins in the woods (the HATs), passes messages (data) to the right people from the right people according to instructions, and also collects other messages (data) to give to organisations, if you wish. And the concierge service makes sure that the data is completely encrypted, private, and that he, the concierge, does not benefit from looking at the messages at all. In other words, to operate the HAT ecosystem, HATDeX has to create new ways of exchanging data, incentivising sharing but with no peeking, and make them the defacto standard for all HAT providers and services so that everyone can benefit. HATDeX services are therefore set up to do just that. We create these services so that our HAT Application Providers can use the exchange to build a whole range of new services: from really simple services based on calendar, notes and messaging, to really complex but awesome Internet services around your data, such as bots and artificial intelligence, whilst always conforming to these new privacy-preserving data exchange standards on the HAT ecosystem.

The next phase of the Internet

We do this not because we want to rebuild the Internet, but because we think that with even more devices connected to the Internet, this new way of exchanging data will help dispel fears, rebuild trust, create better services and help the digital economy to grow. We like to think that we are building the next phase of the Internet.

Implementing new processes and standards for privacy preserving data exchange

Our services run on 4 platforms. [table id=12 /]

UncategorisedIrene NgBlog
HATDeX - A Review of the Year 2016

What a year this has been. Back in February, when the HAT project ended, and was passed from the 6 Universities to the HAT Foundation, we knew that translating 6 briefing papers, developing the tech and implementing the design principles into an actual ecosystem was going to be a challenge of huge proportions. 2016 was the year we embraced the challenge. 2016 was the move from design to implementation; from concept to capability. From the written word to reality.

2016 was the beginning of a very hard journey.

To begin with, how do we make it real? Much of what the HAT is conceptual. The IDEA was so appealing that the reality must surely disappoint. How does one make control, empowerment and privacy with personal data real, visual and tangible? What does it mean when we tangibilize it? How does it feel like? look like? I felt, often during the year, that we were building something to meet the expectations of so many, that we were obviously doomed to fail. It was like making a movie of a book that everyone had imagined differently in their minds. Here's a chronological account of our thought processes. TL;DR perhaps, but we felt we needed to document it!

February 2016: Building the digital body container, avatar, whatever. I guess we have to start somewhere. Little steps right? We knew we had to keep the idea of the HAT separated from the services that used it. Even if we were building the services as well. So.... practice what we preached. To us, the HAT is a person's digital body. It had its own set of APIs and so could connect with different services, but the HAT was a digital embodiment of the person; owned, controlled and empowering the person, and was therefore the most sacred entity. We wanted a world that respected that. And we wanted a world that built services to respect that. So we built the HAT with containers, so that there are clear legal and technical boundaries. (See tech and security architecture). And technically containerising HATs also made it portable, so that the individual would never be held captive by any HAT provider. We also started to embed the containers in the cloud, using Amazon web services, ensuring, every step of the way, that no one could peek into the HAT, without the individual allowing it. And all other services that used data on the HAT, were all separated from it, and communicated with it through a set of HAT protocols.

March 2016: Indiegogo - were there others that thought like us? We launched Indiegogo campaign to see if there were other like-minded people. And by 16 April, we hit the target of £50k. Great. Now, some 300+ people want HATs and are supporting us and we still have no idea how it looks like. Building continues....Faith is a wonderful thing...

May 2016: Can we see this HAT thing, please? We started building the HAT's first service. - Rumpel, the HAT dashboard. Gus joined the team, together with Mike, who designed the UI. Rumpel finally allowed a user to 'SEE' his HAT and made a HAT tangible for the first time. We can click on something. We can see our data. Yay us....

Rumpel brought in a whole new set of problems. Yes, there were 11 design principles from the research. But so many other questions remained. If it was a dashboard for HAT data, how should it be presented? Would users be happy to see their own data when they see it? How does it look like on the HAT that could be different from how it looked like where the data came from? What was the point of it? Stop shouting 'use case' at us! We're still building the platform! With Rumpel came the invention of new 'terms' that didn't exist on the Internet, but needed to have a name. Like data exchanges. How should it feel like? Should it feel like the way we exchange money? Or should it feel like the way we fill forms to give our information away? At some point we thought about the people who invented modern banking and invented terms like direct debit, standing orders, credit and debits - who named them? Naming became an obsession for us. Naming something that was too alien wouldn't help with adoption. Naming it too close to what exists risk misunderstanding it.

Then came MarketSquare. The principle business model of the HATDeX was to facilitate data exchanges, so MarketSquare was crucial for HATDeX. Even though it had a web front end, many of the middleware services on the HAT ecosystem (e.g. collecting, sorting, allocating metadata) had to be built before any service could be built on the HATs. That meant we had to name and explain again. Data debits describe the way data is exchanged. Data offers for those wanting data, data plugs for data coming into the platform. DeXter was the service that crawled the system to find out which HAT wanted to share what data with whom. HAT2WEB posted stuff from HAT to websites..... argghhhh! We could just hope that everyone can understand what they are. Even in simplifying, we needed to think about how to educate through interactions. We felt the weight of our own aspirations. Like an albatross over the neck....

June 2016: ANOTHER sprint? Many sprints at HAT central. Thanks to those who fed and watered us. Loads of late night discussions. And of course alcohol.

July 2016: Release? And Crashed! We have something half decent but very buggy and released HAT and Rumpel to 136 beta users. Boy was that a disaster. Half didn't understand what the HAT was meant to do, the other half couldn't get it to work. We worked through it. Bug by bug. Functionality by functionality. Created some screen tutorials. Probably alienated quite a few people who wanted something more 'polished'.

We knew the dashboard and the exchange infrastructure was completing soon, and it was time to design the first ervice on the HAT that could show how it would be useful (even though minimally) and would serve as the first point of adoption for users and yet showed what the platform could do that was different from others. Yes, yes... it's use case time.....

Shout this out loud to feel the frustration of the HAT product team: "It's the person's digital body. If you want me to tell you the use case, why don't you tell me what your physical body's use case is. Have you figured out what you're put on this earth for?"

Our CEO very calm response to the product team....." we do need just ONE......."

Point taken. Humph. The thing about inventing something is that there really aren't many useful guidelines on how to create something new. We felt like artists with a colour palette and a blank canvas. Time for long bike rides.

August 2016: Notables born. At last we had ONE. It wasn't perfect, but it was something. It meant we took a very different turn with personal data. We came to the conclusion that personal data as we knew it was the most boring thing in the world and went towards personal data that was more meaningful. Words. Numbers. Images. And we started with words. Notables was born. With Notables, we felt it ticked the boxes to show off the platform. There was meaning in the personal data (you see your own words). There was sharing (posting on social media). And there could be analysis (with sentiment bots for mental health for example) for both the user to benefit and for sharing with others. That meant a singular use case for the HAT to go into the public domain that could demonstrate what a HAT-enabled future could be about. It also meant people might just use it.

September 2016: Getting interest.... We had conversations with potential HAT providers. An insurance company. A bank. Things were moving. It's amazing how things move when you can touch and feel something.

November 2016: Wider release... Marios joins us to build the iOS app Rumpel Lite. We released a proper working application on web and on iOS for HAT and Rumpel w/Notables. We further fine tuned our message. And on the data plugs side, we were bringing in Facebook, Calendar, Location, Twitter, LinkedIn and others....

All through the year, we battled with how we should describe the HAT in simple ways, without dumbing it down too much. Personal data wallet, personal data platform, personal data server,..... so many terms came and went... until someone said - why not just call it a HAT :D. In the end, we stuck with personal data store to describe what it is, but committed to calling it a HAT and to make it our mission to get everyone to call it a HAT. One. full. circle.


December 2016: Ready now....The platform is finally ready to start scaling in the new year, and we move into the next phase of getting market traction and next round of Angel funding. The HATs in the backend are being optimized for resource usage and the system stress tested. Based on conversations, 2-3 HAT providers will come online next year offering HATs to their customers and HATs will begin the scaling up.

The year was more art than science. As a multi-sided platform, we knew we had to have a proposition for firms and for individuals that was beyond just privacy and control. We now have it for both. Firms here. Individuals here. We knew we had to mimic services on the Internet and yet create something that didn't yet exist. We had to do it visually and with interactions. It had to achieve an outcome where the user feels familiar interacting with it, but yet feels he is doing something completely new, and yet useful. If the interaction was too new, it would deter the user from clicking on it. If it was too familiar, the user may not feel any different from another Internet service that used and abused their data. We called the build strategy a combination of mimicry and scaffolding. We mimic the old, to scaffold the user into the new.

After a year of coding, designing, eating, drinking, sprinting and fixing bugs; a year of long bike rides, cucumber water, train travels, HAT central cooking, barbecues, pubs, wet socks (the team's term for a 'not-quite-there' product) and a lot of arguing, we've built it. With the platform now built, we know we have to incentivise the creation of day-to-day use of services on the Internet - calendar, social media, emails, chats, browsing - so that privacy seeking individuals have a choice, a choice of bringing control back to themselves while still getting the same services they now have on the Internet. A platform that, as Internet users, we never had (and therefore it was easy to exploit us, data wise). We are optimistic because advances in tech are on our side. Our community can build services faster and better because HAT centric Internet services could actually mean better Internet services than the current ones. With the HAT technical infrastructure now built, we can look forward to services that not only consolidate our own data for messaging, for calendars or for browsing, we can bring in more data - IoT data, finance, health and other data that the Internet currently doesn't have. We can build AI bots on our data and other cool services. We do not need to rely on apps built on GAFA for services. There is now a choice. For future app builders and future Internet Services.

We have built the capability we talked about in the last 3 years.

The HAT is both a tech and a economic/business model innovation. The HAT is now beyond slide ware, books, papers, and power points. It now exists. A full iOS app and web version will be released in January 2017 and marketing will start. 2017 will finally be the time for HAT services. And community. We would like to involve the community of app makers, startups, digital natives, and liberal-minded individuals who believe in personal data empowerment, and who believe in an Internet that is very different from what it is today. A world where many firms would build services on HATs because there are more revenues in data exchanges than selling data for advertising. Most of all, we want to build a community of people who wanted a change from this data exploitation regime that the Internet economy has become. We are clearly a David amongst Goliaths, but we can only try.

2017 would probably tell us if we can succeed. Happy New Year from the HATDeX team.

What do I do with my HAT?

So you've got your HAT, what do you do now? I thought I'll pen a few notes to help you get started. First thing I did was to go to Rumpel, my private dashboard. On the top corner, you will see 'New to Rumpel'. Click on it and it will give you an overview of what you can do on Rumpel. I did the tutorial just to be a little familiar with Rumpel but I was really very impatient to get into things. Thankfully, it wasn't a long tutorial.

Data Plugs

First thing I did was to pull in my data. I brought in my Facebook data, my calendar data (you need to bring in an iCAL link), and I have an iOS phone, so I downloaded the Rumpel Lite app and yay! I have my location synchronised with my HAT! And I also linked my HAT to all the photos on dropbox.


Identity Management

PHATA (click here to learn what is PHATA)! PHATA is my personal HAT address and I set up my PHATA page by going to the profile page on Rumpel. A few clicks where I decide what is public and what is private and I have my own PHATA page! No more telling everyone my LinkedIn, Facebook, Twitter,.....from now on I just say 'you can find me on my HAT at'. My PHATA page is also where I can see the apps that use my HAT data and the data plugs I've brought in. Move aside plain old websites, I have my own microserver now!



I like to click around my mashup. I get to see where I've been and what I've been up to, which is great to keep a record of my history. Now if only I can get search and some smart services on this.... (coming soon?)



After browsing around Rumpel, I thought I'll head out to the second service: MarketSquare! I went to the Notables@MarketSquare and read some of the public broadcasted notes from other HATTERs - everyone looked like they're having fun. So I tried to post a note myself from Rumpel. I went to Notables to write something, setting it to be shared and it not just came out on MarketSquare, it was on my PHATA page as well! I can now use my HAT as a blog as well, which is cool. All my words in one place!


I'm certainly using it to life log private thoughts, shopping lists and also post public blogs and notes as well. And I love it that it has my history, my words and my data that I can buy services for later. Can't wait for more services! You can check out our product plans here.


The NextGen Digital Challenge Awards

As you may have seen from our delighted Social Media posts recently, HAT has received recent accolades in the form of the O2 NextGen Digital Challenge awards. The awards was accompanied by a fantastic evening in the company of the upcoming experts in the digital field. The categories for the evening including Digital Healthcare, Economic Development and Rural connectivity. HAT received the nomination in the category Innovative Digital Applications in June, before even Beta HAT's had been launched. So it was a definite surprise and honour to receive the Runner-Up position for this category.

“Imagination and innovation in applied digital technologies is often the result of a collaboration between two or more specialist fields. Time and again this inter-disciplinary process is demonstrated in the case studies that come before the judging panel – new ways of applying digital expertise and insight in unexpected corners of the economy and communities.” is a signature quote made by Lord Erroll that evening, and we believe it is almost perfectly reflect our goals of combining digital and economic fields.

Moving on from here, HAT will continue to strive to be innovative in the way we roll out services on the platform. We will do this by growing our digital capabilities to provide better personal data services with the help of our community.

The NextGen Digital awards press release can be found here, along with the list of the 2016 winners here.