GDPR
Overview
Any provides the features needed to build an application meeting the privacy and data security requirements of the users.
Concept
The Any platform, on its own, cannot guarantee compliance with the data protection regulations.
Compliance also depends on the organizational procedures and the usage practices set up around the product.
These procedures define, in particular:
- How the personal data must be collected, processed and stored
- How the rights of the data subjects are handled (access, deletion, portability, etc.)
- Which security measures must be applied to protect the integrity and the confidentiality of the data.
The combination of the platform and these internal processes is essential to ensure full compliance.
Managing the data privacy requirements with Any
Right of access and right to information
The Any audit finds the following information easily and exports it for a reporting:
- Every action performed on a document (search, view, download, change, approval, etc.)
- The precise date each action was performed
- The version of the document the action was run in
The audit trail can be consulted for a specific document or for the whole set of actions performed by a given user.
Any can identify the personal information held in the documents (through the full-text search), but cannot process it (anonymize, delete, etc.).
Right to portability
Any offers an archive export feature to export a set of documents. This export can result from a query selecting the whole set of contents linked to a person.
The export is generated as a ZIP file holding:
- the documents.
- a CSV file gathering all the metadata of the exported documents.
Right to rectification
Any provides a mass metadata change feature. This function updates a set of metadata on a set of documents (for instance: the result of a query).
Right to erasure / Anonymization
A document or a set of documents can be deleted from:
- a view.
- a folder.
- a query.
- a room.
The deletion can also be performed through the REST APIs, the Java API or CMIS.
When personal information must be deleted without erasing the documents, the mass update can be used, as explained in the Right to erasure / Anonymization paragraph.
Personal information can be stored in the application indexes. Its deletion requires specific operations on Elasticsearch.
Retention period management
Set retention periods: Any configures the retention period of each document.
Trigger automatic purges: for the documents on retention, they can be processed through jobs or batches that analyze the documents that reached the end of their retention period. A processing can then be applied to them (for instance, the erasure of the personal data) by triggering a lifecycle responsible for running the appropriate actions.
Trace the deletions: the Any audit traces every action performed on the documents.
Privacy by design
Any is designed to:
- limit access to the data by default.
- allow applying the security best practices (through the different security configuration modules).
- embed purge, anonymization and retention period management mechanisms.
To limit access to the personal data, some best practices must be followed.
For the users and the groups, a "User / Group" metadata must be used, to reduce the exposure of the personal data.
This mechanism only keeps the login of the user and only indexes that login in the full-text search: the full name is never indexed.
In the form configuration, the user / group metadata is handled automatically: a data list cannot be selected, nor can another user metadata to store be chosen.
Facet filtering stays possible: the full name of the user is resolved on the fly when displayed.
From the point of view of the user, the login is never displayed: only the full name appears, both in the metadata and in the audit information, but only the login is stored.