Difference between revisions of "General Data Protection Regulation (GDPR)"

From SmartWiki
Jump to: navigation, search
Line 13: Line 13:
  
 
=Feature Descriptions and Requirements=
 
=Feature Descriptions and Requirements=
 +
SmartSimple has created two categories of features that are GDPR-compliant: features related to '''Personal Data Management, '''and those related to '''Consent and Compliance. '''
 +
 
==Personal Data Management Features==
 
==Personal Data Management Features==
 
'''Personal Data Management '''features are focused on managing your data effectively and automating your data governance model. To make the most use of the following features, we recommend identifying all personal data fields in the system and organizing them into data categories. 
 
'''Personal Data Management '''features are focused on managing your data effectively and automating your data governance model. To make the most use of the following features, we recommend identifying all personal data fields in the system and organizing them into data categories. 

Revision as of 16:22, 26 August 2019


Construction warning.png Please note that this page is currently under construction. There is more information to come.

Please see Configuring Privacy, Confidentiality and Other Policies for related information. 

Overview

One of the largest aspects of SmartSimple's privacy configuration is our compliance with the General Data Protection Regulation (GDPR). The GDPR is an EU legislation that is designed to protect the fundamental rights of citizens and their personal data. This law ensures that people not only know where their private data is kept, but it also holds organizations accountable and transparent in their practices.

EUGDPR.org lists the key changes brought about by the enforcement of the GDPR, which began on May 25, 2018. As a directly binding regulation, the GDPR stipulates that controllers of personal data must put in place appropriate technical and organizational measures to implement its data-protection principles.

This article describes which features and policies SmartSimple has implemented into our platform to help you comply with the GDPR.

For more information about SmartSimple's implementation of GDPR-compliance, see our website

Feature Descriptions and Requirements

SmartSimple has created two categories of features that are GDPR-compliant: features related to Personal Data Management, and those related to Consent and Compliance. 

Personal Data Management Features

Personal Data Management features are focused on managing your data effectively and automating your data governance model. To make the most use of the following features, we recommend identifying all personal data fields in the system and organizing them into data categories. 

Feature Description GDPR Regulation
Personal Data Field (Indicator)

This will indicate whether a field contains personal data and add a processing description.

This allows you to quickly differentiate between personal and non-personal data fields, and allow internal and external users to view the description. Adding an indicator makes it easier to ensure that all personal data fields are accounted for when erasing personal data, adding policies, enabling pseudonymization, or searching/reporting.

Data Categories

Organizing the data you collect into data categories such as the following: Contact Data, Financial Data, Highly Sensitive Data, etc.

This feature will allow you to tailor highly specific security and data retention policies to different classes of data. You are able to apply any number of policies to a category.

Data Retention Policies A data retention policy defines how long your organization will need to retain the data of this category in the system before it is erased. A data retention policy can be placed on any field in the system, and the erasure will be completely automated. Retention is based on the number of months or days after a specific date.
  • (5)(1)(e) Storage Limitation
  • (5)(1)(b) Purpose Limitation
Data Security Policies

A data security policy defines who can see and/or modify the data of this category in the system.

Security policies support SmartSimple's role-based security. We can configure your security policies to help you achieve the principle of principle limitation and integrity and confidentiality by ensuring that only those who need to access data for legitimate, specified purposes will be allowed to do so.

  • (5)(1)(b) Purpose Limitation
  • (5)(1)(f) Integrity and Confidentiality
Pseudonymization

Pseudonymization allows you to mask personal data fields, so that the data you retain on an individual is rendered unidentifiable.

Pseudonymization allows for a nuanced approach to data management. Deleting a entire profile and all the data associated with a person is often unnecessary and will create gaps in reports. Utilizing pseudonymization enables you to render specific fields unidentifiable, retaining the effectiveness of long-term reporting while meeting data retention requirements.

  • (5)(1)(e) Storage Limitation
  • (5)(1)(f) Integrity and Confidentiality
  • (5)(1)(b) Purpose Limitation

Consent and Compliance Features

These features are catered towards managing your data subject's consent, as well as managing your overall compliance.

Feature Description GDPR Requirements
Personal Data Field (Information & Access)

It is essential that the end user understands why and how you will process their personal data in order for them to make an informed consent decision. 

The Personal Data Field Indicator gives you the ability to indicate any field that will hold personal information and set a description of the uses of that field. 

When the user displays any page in the system that uses personal information fields, they have the ability to see all of the explanations that you have added. On their profile, the user can view a list of personal data fields that you hold on them. 

This feature is automatically available in every instance of SmartSimple. 
  • Informed consent
  • Data subject's right to transparent information
  • Information to be provided where data is collected from the data subject
  • Right of access 
Policy Consent

After establishing a policy internally, you can enforce it by having your users agree to it upon login. The policy can be set to mandatory, ensuring that if a user does not accept the policy, they will not be able to access the system or enter personal information.

Any number of policies can be added, and they can be enforced one time, or at timed intervals. Once a user accepts a policy, the system will create a PDF of the acceptance with a time/date stamp, creating a fully auditable consent collection process. 

  • (7)(1) informed consent, demonstration of consent
  • (2) Accountability
Cookie Policy

Cookie Policy is a feature to alert users to the use of cookies on the SmartSimple application. It will alert users landing on the login page and require them to accept the use of cookies. 

We have also introduced a policy template that you can use to create your own cookie usage policy within your Privacy and Security Policies

  • Informed consent
Personal Data Erasure

The personal data erasure is used in order to comply with requests to delete user data. This new feature can be enabled on UTA Level 2 types as an individual's data erasure request. 

Within this Level 2, an administrator would then be able to review these Level 2 requests and have an option available that would delete the user profile of the Level 2 owner.

A certificate of data erasure is then created in order to reference this activity.

  • Rights of the data subject
Request Tracker UTA
 This is a customized feature that must be requested by the client to be configured into their specific instance of SmartSimple. 

We are able to build a Request Tracker Universal Tracking Application™ to help you manage Data Subject Requests, such as the following: Right of Access; Right to Rectification; Right to Erasure; Right to Restriction of Processing, etc. 

  • Obligations of the controller
  • Rights of the data subject

See Also