
- Transparency – Be transparent on why you collect the data, how it is collected, where it is stored, and its use. Based on the context, indicate the authority available to gather and process this information and conditions where it would be made available to other parties
- Data minimisation – Request and obtain only the minimal data required to perform the outcome expected. If the desired result is to generate an email with an attachment, do not ask for the phone number and NIC! The design of information collection must match the intended use of the information
- Restrict access – Restrict the access of PII to only the individuals who need to work with this data. For example, the entire organization should not view contacts in the Customer Relationship Management (CRM) system
- Data security by design – Implement administrative, technical and physical safeguards, which will restrict access and protect your data. While these activities overlap with information security management practices, measures to protect data from unauthorised access, modification, or loss must be in place
- Map data flows – Map the users and activities performed at each processing stage. Verify the model with those in data processing roles on completeness and potential risks. For example, it is pointless if access to the CRM system is highly controlled and secure, but a spreadsheet of the contacts needs to be downloaded and shared with someone else to complete the processing
- Geolocation restrictions – Comply with the regulatory or contractual obligations relating to where the data can be stored and processed. These restrictions are more relevant for FinTech applications where financial data is on the cloud
