March 2018
Hello world!
May 2017
Hello world!
May 2016
Hello world!
November 2015
Hello world!
October 2013
Hello world!
  • Your Cart Is Empty!


Cyber SecurityIdeas

The evolution of personal information safekeeping and sharing

Today, many companies store information about the user, some would argue too much information and on most occasions that information is not relevant to the services provided to the user.
In 2013 GDPR did not exist, and companies were hogging data for the sake of analytics and tailored experiences.

That is where Prson came into play. the idea of was simple; we will give the user one platform to safekeep his personal data (completely decentralized from his identity to prevent PII leak) and than enable him to share specific subsets of data with the vendors upon agreement from the user to share the data. Vendors which are a part of the platform can now tailor their e-commerce experience directly to the user's taste thus increasing their conversion ratio dramatically.

Now consider if you could share your t-shirt size and favorite color with someone that wants to buy you a Christmas present? or more importantly, immediately sharing your medical records with the hospital in case of an emergency.
All of that becomes possible with Prson, but never perpetually.

Technical Assessment:


  1. User Mobile application & Browser plugin - The mobile application enables quick access, creation and sharing of data sets by the user. the browser plugin combines those capabilities and the ability to associate itself with the vendors website through Javascript (which will then enable the website to tailor the experience to the user if the user agrees).
  2. Vendor mobile application & web application - The mobile application act as a BI tool for the vendor whilst the web application is responsible for the integration between the vendor and Prson. For vendor's there are 2 integration methods; pre-built plugins for leading commerce websites (magento, woocommerce etc.) and a custom API toolkit for the vendor to create integrations on his own.


  1. Data security relies on a different encryption key per user using the KEK/DEK method and tokenization of the data using those keys.
  2. The identities are being kept in a different repository entirely and are not exposed to anyone (logic is that to offer a tailored experience the name of the person is not relevant but he's properties)
  3. In terms of infrastructure, The system was designed to be fully in the cloud and based on microservices (needless to say in 2013 PaaS and containers were not as mature as they are today).

If you are looking for more information about this project, please ping me via LinkedIn



Project Name