That's simple. If it is a model that was trained with only that person's data and is therefore connected to it, it is PII (personally identifiable data) and must be deleted.
If the model aggregates the data of multiple people and is disconnected from the individual it does not constitute PII and can be kept.
Most projects in the blockchain space focus on working towards an ICO to finance the operation. For many projects that makes sense. Sometimes however gearing the concept towards an incentive structure suitable for an ICO leads to non-optimal outcomes.
It also leads to a lack of generic infrastructure that is designed to be soundly engineered and easily reuseable.
What would you like to tackle during such a workshop?
That might bring make me bring back part of my browsing to Firefox. The identities functionality was what made me use Chrome almost exclusively the last two years.
handcheque | Senior Backend/Frontend/Embedded | Vienna, Austria | Full Time, Remote Possible
handcheque (https://handcheque.com/) will simplify the wallet by combining all payment and loyalty cards into one. We are currently raising a seed round and are looking for principal engineers in the three main areas of development who would report directly to the CTO (me).
We have a hardware prototype that is working and agreements with MasterCard in place.
Our stack will be:
Backend: Clojure/Cassandra/Docker
Frontend: Ionic or React(Native)
Embedded: TI MSP430 and CC2640
If you are interested just mail me at christoph.witzany@handcheque.com
At that time we are only interested in people to join the team as full time employes. Please no consultnacies :)