If this category is not applicable for this technology, please select 'Yes'.
If you are not sure what personal data is, click here. If your technology registers personal data you have to be aware of privacy legislation and the concept of privacy. Personal data can be interpreted in a broad way. Maybe your technology does not collect personal data, but can be used to assemble personal data. If you are collecting special personal data (like health or ethnicity) your should be extra aware.
Are you aware of the main privacy and data principles you need to adhere to? If not, click here. Do you think the invasion of privacy of your technology is allowed? Do you think people will feel that their privacy is invaded? Did your think about things like proportionality and subsidiarity?
In Europe (for example) data collections have to be GDPR - compliant. Do you think that your technology is compliant? How do you know? Did you provide for the appropriate measures to make sure compliancy is in place.
Privacy is often implemented by design which means for example that only the bare minimum of data is collected and used and this process is continously improved upon. Do you (really) need all the personal data you are processing to provide the functionality of your technology (data minimalisation)? Did you consider other principals considering privacy by design?
Are you creating data that could follow users throughout their lifetimes, affect their reputations, and impact their future opportunities? Will the data your tech is generating have long-term consequences for the freedoms and reputation of individuals?
The idea of the technology impact tool is that it stimulates you to think hard about the impact of your technological solution. This can lead to design - changes, which is a good thing. Please list them here.