Warning: You are browsing the documentation from version 4 to 10 of Pimcore. Please visit https://pimcore.com/docs/platform/ for the latest versions of Pimcore.
Version: Edit on GitHub

Data Protection and GDPR

Pimcore provides several tools and settings to provide GDPR compliance and support implementation providers and users with corresponding tasks.

Please note: Since Pimcore is a framework, therefore the final responsibility for GDPR compliance is always with the solution provider, implementation partner and owner of an actual solution.

Restriction of Access

Restriction of data access is achieved with Pimcores extensive permission system. It allows to restrict accessing, changing and deleting information on user and role level. For details see User and Roles documentation.

The Permission Analyser allows to analyse the actual permissions of a Pimcore user for a certain element. Permission Analyser

Right of Access by the data subject

For searching and exporting person related data, Pimcore provides the GDPR Data Extractor. GDPR Data Extractor

It allows ...

  • ... to search for person related data based on search terms for ID, Firstname, Lastname and E-Mail.
  • ... to list all found data from different data sources and open details for the found data directly from the result list.
  • ... to export all data of a found item as json.
  • ... delete the data directly from the result list if possible.

The search is a word based search. This means only complete words are found, no parts of words. For example if you search for Chris, records with Christian will NOT be found. All search terms (ID, Firstname, Lastname and E-Mail) are connected with AND, so they all need to occur for a data record to be shown in the result list.

Supported data sources by Pimcore core are:

  • Data Objects
  • Sent Mails
  • Pimcore Backend User Data

This list always can be extended. For more information concerning configuration and extension see your GDPR Data Extractor Development Docs.

Right to Rectification

Pimcore follows the principle of single source publishing. Therefore information should be stored only once in the system and linked to all places where it is needed. As a result, rectification of data is made easy since it only needs to be done in one place. Once updated and published, the information is delegated to all places where it is used and Pimcore takes care of the rest.

Right to Erasure

Also in terms of erasure of information, Pimcores single source publishing comes in handy. Once a data element (e.g. data object) is deleted, Pimcore automatically cleans up all related data (e.g. versions, etc.) and updates the places where
it used.

For email logs cleanup use Pimcore Console command pimcore:email:cleanup with required option older-than-days to delete the logs older than x days

./bin/console pimcore:email:cleanup --older-than-days=12

Of course Pimcore cannot cleanup external data copies or backups. This has to be taken care of by the owner of the actual solution.

Deactivation of Usage Log

Pimcore logs information about every action that is done in Pimcore backend for audit trail and traceability reasons. The logged information concludes timestamp, user id, called action and can be used to reproduce things if something goes wrong.

This feature can be deactivated in system settings. See Logging Docs in the Development Documentation for more details.

It is not recommended to turn off this feature.

Deactivation of Versions

For every save action of data elements (documents, assets, data objects) Pimcore writes a version for traceability, audit trail and the possibility to go back to older versions. The version information concludes timestamp, user and the actual data.

This feature can be deactivated in system settings. See Versioning Docs in the Development Documentation for more details.

It is not recommended to turn off this feature.

Pimcore provides a special data type for its data objects to store consents given by a user. See Consent for details.