Suppose you want to know how many cars travel across a certain road. You could build a system that registers all license plates driving by. But you could opt for a system that will simply place a tally mark for every car that passes by. Both systems serve the same function: they count cars. However, the first one is a privacy nightmare. The second system is designed in such a way that it cannot document any personal information. Privacy is not a factor that you can just tack on a system after the fact; it needs to be included in the design phase as a requirement. This design philosophy is called privacy-by-design. Can we work towards Tada-by-design?
We think we can.
Read all about it on the Tada blog:
Hi Douwe,
Thanks for sharing your insights and I'm really interested to give our contribution to the TADA Privacy by Design principles.
Many data policies, standards and regulations are out there and the complexity for the Business is to keep up and comply in real-time. The problem: Privacy by Design by Default, is something we are supporting for quite some years now from a technology perspective.. Every business has to comply to new data regulation, like EU - GDPR, Brazil - LGBT, US - CCPA or want to support standards like Qiy Foundation or Tada.city.
My question is how can we support your program with privacy compliant software so your contributors can easily comply to your principles and to any standards / regulations to create new data from human centric applications in a smart city context. Privacy by design principles for technology / software is a Paradigm shift and let's not think blockchain only will solve this.
Bob Nieme
www.datastreams.io