A Symfony 3|4 bundle for classifying entity parameters according to GDPR requirements and encrypting data

Fund package maintenance!

Installs: 4 422

Dependents: 0

Suggesters: 0

Security: 0

Stars: 55

Watchers: 13

Forks: 8

Open Issues: 3


v2.1.3 2019-08-07 19:44 UTC

This package is auto-updated.

Last update: 2020-09-19 01:15:28 UTC


A bundle to aid with the General Data Protection Regulation requirements.

Features include:

  • Written for Symfony version 3|4
  • Provides annotation for adding to entity parameter doc blocks - this method is being deprecated.
  • Uses a PersonalData object and data transformers.
  • Records values for Data Protection Impact Assessments of entity parameters.
  • Uses SpecShaper\EncryptBundle to encrypt sensitive data

Version History

Version 1

Version 1 of this project used annotations to classify entity parameter personal data.
This unfortunately could not be extended to managing live data, it runs into problems where data become expired. What should get displayed instead? How can live data status be reported with annotations?

Version 1 Features:

  • Generate a entity parameter coverage report.
  • Generate a summary report of all entity parameters and GDPR annotations.

Version 2

Version 2 uses a PersonalData entity to store the GDPR parameters associated with the personal data parameter.

A custom twig function can be used to:

  • Decrypt any encrypted data
  • Display current data in its correct format.
  • Display deleted/aggregated/annonymised data once it has been sanitised

Version 2 Features:

  • Create a storage entity
  • Create twig templates for entity to handle displaying expired data.
  • Create a migration command to create new database fields, and convert PersonalData attributes to PersonalData entity rows.
  • Create disposal classes and service
  • Create a command to dispose of data
  • Implement a cron task to dispose of data
  • Generate activity report
  • Create consent forms
  • Generate consent report
  • Export data command


  • This bundle has not been unit tested.
  • It has only been running on a Symfony v3.4 project, and not backward compatibility tested.


The source of the documentation is stored in the Resources/doc/ folder in this bundle.


This bundle is under the MIT license. See the complete license in the bundle:



GdprBundle has been written for Parolla website to encode users private data.

Reporting an issue or a feature request

Issues and feature requests are tracked in the Github issue tracker.

When reporting a bug, it may be a good idea to reproduce it in a basic project built using the Symfony Standard Edition to allow developers of the bundle to reproduce the issue by simply cloning it and following some steps.


Step 1: Download the bundle

Open a command console, enter your project directory and execute the following command to download the latest version of this bundle:

$ composer require specshaper/gdpr-bundle dev-master

This command requires you to have Composer installed globally, as explained in the installation chapter of the Composer documentation.

Step 2: Enable the bundle

Then, enable the bundle by adding it to the list of registered bundles in the app/AppKernel.php file of your project:

// app/AppKernel.php

// ...
class AppKernel extends Kernel
    public function registerBundles()
        $bundles = array(
            // ...
            new SpecShaper\GdprBundle\SpecShaperGdprBundle(),
            new SpecShaper\EncryptBundle\SpecShaperEncryptBundle(),
        // ...
    // ...

Step 2: Configure the bundle

Add an empty value for encrypt_key to your parameters file.

# app/config/parameters.yml

    # ...
    encrypt_key: ~

Geneate a 256 bit 32 character key using the command tool in the Encrypt bundle

$ bin/console encrypt:genkey

Now, replace your encryption key.

# app/config/parameters.yml

    # ...
    encrypt_key: <your_key_here>

Configure the EncryptBundle.

# app/config/config.yml

    # ...
        is_disabled: false

You can disable encryption of the database by setting deleting is_disabled or setting it true.

Configure the routing to access the reports:

# app/config/routing.yml

   # ...
        resource: "@SpecShaperGdprBundle/Controller/"
        type:     annotation
        prefix:   /gdpr

You should make sure that the /gdpr path is behind a firewall in your security settings.

# app/config/security.yml
            # ...
            - { path: ^/gdpr/, role: [ROLE_SUPER_ADMIN] }

Add the personal_data doctrine type to doctrine

# app/config/config.yml
                personal_data:  SpecShaper\GdprBundle\Types\PersonalDataType

Step 3: Create the entities if using the new personal_data type.

User the personal_data column type, and pass the options.

    // ...
    use Symfony\Component\Validator\Constraints as Assert;
    use SpecShaper\GdprBundle\Validator\Constraints as GdprAssert;
    // ...
     * Iban bank account number.
     * @var string
     * @GdprAssert\PersonalData({
     *     @Assert\NotBlank,
     *     @Assert\Iban
     * })
     * @ORM\Column(type="personal_data", nullable=true, options={
     *     "format" = "STRING",
     *     "isSensitive"=false,
     *     "isEncrypted"=true,
     *     "idMethod"="INDIRECT",
     *     "basisOfCollection"="LEGITIMATE_INTEREST",
     *     "identifiableBy"="Can be used to identify an individual if compared with third party database",
     *     "providedBy"="The employee, the employer",
     *     "purposeFor"="Used to pay employees by SEPA",
     *     "retainFor"="P6Y",
     *     "disposeBy"="SET_NULL",
     *     "methodOfReceipt"={"HTTPS"},
     *     "receiptProtection"={"TSS"},
     *     "methodOfReturn"={"HTTPS", "PDF"},
     *     "returnProtection"={"TSS","ENCRYPTED_PDF"}
     * })
    protected $iban;

Look at the PersonalData object constants for the full range of options available.

The PersonalData field can be validated from within the entity by wrapping regular constraints within the PersonalData constraint.

Step 4: Converting your database.

Use the command below to update your database.

$bin/console gdpr:update

The command will find all Column annotations of type personal_data and convert the stored value to a PersonalData object.

Use the command option 'tables' to convert specific tables and fields.
You can enter a class, to search every property in the class. Or for specific class properties then append the property name. You can also append multiple classes.

$ bin/console gdpr:update -t AppBundle/Entity/BankDetails
$ bin/console gdpr:update -t AppBundle/Entity/BankDetails:iban
$ bin/console gdpr:update -t AppBundle/Entity/BankDetails -t AppBundle/Entity/User:firstName

Step 5: Use in forms

Use the PersonalDataType in forms. Note that this is different from the doctrine PersonalDataType.

// ...
use SpecShaper\GdprBundle\Form\Type\PersonalDataType;
    // ...
        ->add('iban', PersonalDataType::class, array(
            'required' => true,
            'label' => 'label.iban',
            'attr' => array(
                'placeholder' => 'placeholder.aValidInternationalBankAccountNumber'

In most cases you validate the entered value in the enitity using the PersonalData constraint to wrap other constraints. This is because the submitted data has been through the data transformer.

If you are validating in the form then you do not need to use the PersonalData constraint. Just use your constraints as normal.

// ...
use SpecShaper\GdprBundle\Form\Type\PersonalDataType;
    // ...
        ->add('iban', PersonalDataType::class, array(
            'required' => true,
            'label' => 'label.iban',
            'attr' => array(
                'placeholder' => 'placeholder.aValidInternationalBankAccountNumber'
            'constraints' => array(
                new Iban()

Step 5: Decrypt in templates

To view your data in a twig template:

{{ employee.bankAccount.iban }}

This will call the toString method of the PersonalData object, which will convert the data to its format as set in the entity field annotation.

If you want to access the data without any default conversion then use:

{{ employee.bankAccount.iban.data }}

If you query a repository using a select method, or get an array result then the doctrine onLoad event subscriber will not decyrpt any encrypted values.

In this case, use the twig_filter to decrypt your value when rendering.

{{ employee.bankAccount.iban.data | personal_data }}

Todo: Use the twig_filter for personal_data to pass rendering options:

{{ employee.bankAccount.iban.data | personal_data("date", "d M Y") }}
{{ employee.salary.data | personal_data("currency", "EUR") }}
{{ employee.height.data | personal_data("decimal", 2) }}

Step 6: Decrypt in repository

The problem with encrypting data in the DB is that it can no longer be used for ordering or searching.

We use a trait in the entity repositories to provide common functions for dealing with PersonalData objects.

// src/AppBundle/Repository/Traits/GdprTrait.php

namespace AppBundle\Repository\Traits;

use SpecShaper\EncryptBundle\Encryptors\EncryptorInterface;
use SpecShaper\GdprBundle\Utils\Sorter;

 * Trait GdprTrait
 * Trait to provide common functions for encrypted fields in a repository.
 * - Decrypt & concatenate first and last name
 * - Sort by two fields.
 * @package AppBundle\Repository\Traits
trait GdprTrait
     * @var EncryptorInterface
    protected $encryptor;

     * Setter injection Encryptor into repository.
     * @param EncryptorInterface $encryptor
     * @return $this
    public function setEncryptor(EncryptorInterface $encryptor){
        $this->encryptor = $encryptor;
        return $this;

     * Get the Encryptor
     * @return EncryptorInterface
    public function getEncryptor()
        return $this->encryptor;

     * Function to concat two encrypted values into one new value.
     * @param array  $collection
     * @param string $firstNameField Default is firstName
     * @param string $lastNameField Default is lastName
     * @param string $outputField Default is fullName
     * @return array
    public function concatToFullName(&$collection, $firstNameField = 'firstName', $lastNameField = 'lastName', $outputField = 'fullName'){

        foreach($collection as $key => $entity){
            $firstName = $this->getEncryptor()->decrypt($entity[$firstNameField]->getData());
            $lastName = $this->getEncryptor()->decrypt($entity[$lastNameField]->getData());
            $collection[$key][$outputField] = $firstName . ' ' . $lastName;

        return $collection;

     * Sort a array hydrated query result by two columns.
     * @param array  $result
     * @param string $firstOrder
     * @param string $secondOrder
     * @return mixed
    public function sortByTwoColumns(&$result, $firstOrder = 'employeeId', $secondOrder = 'lastName')
        // Use SpecShaper\ThemeBundle\Util\Sorter:sortByTwoColumnsCallback as a callback
        usort($result, array(new Sorter($firstOrder, $secondOrder),'sortByTwoColumnsCallback'));

        return $result;

The trait is used in the repository.


namespace AppBundle\Repository;

use AppBundle\Repository\Traits\GdprTrait;

 * EmployeeRepository
 * This class was generated by the Doctrine ORM. Add your own custom
 * repository methods below.
class EmployeeRepository extends \Doctrine\ORM\EntityRepository
    use GdprTrait;


In inject the encryptor into the repository in the controller.


namespace AppBundle\Controller;

use AppBundle\Entity\Employee;
use SpecShaper\EncryptBundle\Encryptors\EncryptorInterface;

 * Employee controller.
 * @Route("/employee")
class EmployeeController extends Controller

     * Lists all Employee entities.
     * @Route("/{id}/all", name="employee_all")
     * @Method("GET")
    public function allAction(EncryptorInterface $encryptor)
        $employee = $this->getDoctrine()->getRepository(Employee::class)

Step 7: Reporting

Coverage Report

Access the coverage report by navigating your browser to '\gdpr\reporting\coverage'.
This will serve an excel file that contains all the entities and parameters managed by the entity manager. If any of the parameters contain the "personal_data" column type it will also list each of the attributes values.

Note that at the moment we are only pulling information from the default entity manager. I need to improve the coverage report to get all entityManagers.

History Report

@todo Not yet written.

A report of log entries for:

  • PersonalData object creation and updates.
  • PersonalData object disposal.
  • PersonalData objects exported.