Data privacy/DSGVO compliance extension for TYPO3
| ujamii_dsgvo | TYPO3 |
|---|---|
| <= 1.0 | >= 8.7 <= 9.5 |
| >= 2.0 | >= 9.5 <11 |
| >= 3.0 (planned) | >= 11 |
On 25th of May 2018 the new laws regarding data privacy protection will be in place. With fines up to 20 Mio. €, or 4% of global revenue for international corporations, every organization (commercial AND non-commercial) operating in the European Union must comply with the regulations described in the linked documents.
For TYPO3 websites this has several implications:
- private data in the database needs to be deleted (instead of setting
deleted=1) - transmissions of the data to the webserver or a mail service needs to be encrypted
- imprint and data privacy information needs to be on separate website (at least in Germany)
- users must be notified about permanent cookies and have a possibility to opt out for tracking services
- ...
This extension aims to help identify possible issues as well as perform regular tasks like cleaning up the database and delete "deleted" records as well as older data submitted in forms.
- Get the files
- install via composer:
composer require ujamii/ujamii-dsgvo - install via archive: Download and extract in
typo3confdirectory, rename folder to ujamii_dsgvo
- install via composer:
- activate the extension in the backend (may need to clear the autoloading cache
- a new submodule "DSGVO" in the main module "web" will appear
The extension can count, anonymize or really delete records in the database. The backend module uses the select mode to display the overview. With the two buttons below the table overview, you can start the process of overwriting the records with dummy data (anonymization) or deleting.
Deleting records may be harmful for the data integrity as TYPO3 does not use constraints on database level by default.
Thus, the delete mode is NOT the default mode! If you really want to delete the records, use this mode/button explicitly.
Please be aware, that if you add more tables to the config, the anonymization mode will do nothing as long as there is no
anonymize part set! Also, you have to care for the correct data format yourself. Writing wrong data types in the field = value
list may lead to errors.
The anonymization mode also writes to the tstamp and crdate fields (if configured in the TCA). The new value of those fields will
be 0. This value is also the indicator that those rows have already been handled. Thus, rows with tstamp = 0 AND crdate = 0 will
not be counted/handled. If you create records from outside the TYPO3 datahandler yourself, please check those fields are not 0
after your database write.
For more flexibility, the values for overriding data in the database are configured via PageTS.
So if you want to add your own table, just add the anonymize part and the extension will care for your data as well.
Click on the module icon in the main backend menu (inside "web"). You will see an overview for each configured extension and database table. Green rows mean nothing to delete, red rows mean something would be deleted/anonymized if you click the red "delete" or the orange "anonymize" button at the bottom of the page. The amount of affected rows is also shown on the overview page.
A call like vendor/bin/typo3cms cleanup:cleandatabase --page-uid=1 --mode=select will output something like:
2018-04-06 17:27:01
FALSE means Extension not installed, integer is amount of affected records.
array(5 items)
core => array(2 items)
fe_users => 0 (integer)
be_users => 0 (integer)
powermail => array(1 item)
tx_powermail_domain_model_mail => 0 (integer)
formhandler => FALSE
tt_address => FALSE
comments => FALSEPossible values for the --mode= parameter are:
- select (just counts rows, does no alter the database)
- anonymize (overwrites rows with configured values, see pagets.ts)
- delete (does what it says, really DELETEs the rows from the database)
To extend the database cleaning which could be done in the backend or via CLI/Scheduler, you just need to write some typoscript and add it into the pageTS of your website.
You can add several tables, grouped by extension. Starting level is module.tx_ujamiidsgvo_dsgvocheck.settings.db
and the next level is the extension name (e.g. powermail) and then the table name.
The option allDeleted can be 0 (default) or 1. If set to 1, all deleted=1 records in this table will be used
on every run of the process. The delete field name is read from the TCA.
Setting the andWhere option will limit the rows in the database which are covered in the process. So if you leave
this empty ALL THE RECORDS IN THIS TABLE WILL BE HANDLED!!! So you better think about it beforehand ;-)
Example for powermail extension:
module.tx_ujamiidsgvo_dsgvocheck {
settings {
db {
powermail {
tx_powermail_domain_model_mail {
allDeleted = 1
andWhere = crdate < UNIX_TIMESTAMP(DATE_SUB(now(), INTERVAL 6 MONTH))
anonymize {
sender_name = anonymized
sender_mail = anonymized
//...
}
}
}
}
}
}
To see which tables are covered by default, take a look into the pagets.ts.
You may skip the anonymize part completely if you only want to really delete records for a certain table.
This feature is deprecated and will be removed in the next major version! If you need cookie management in TYPO3, use something like Wacon Cookie Management.
If you use cookies on your website, you will at least have to notify your users and provide an opt-out to cookies that are not essential to the website/service itself and/or contain some sort of private information of the user. Sadly, even dynamic IP addresses are considered a private value of information (at least in Germany).
So utilizing a third party ready-to-use solution may be enough for you. This extension provides an example based on cookieconsent.insites.com. To use it in your TYPO3 project, just copy the partial template. to your project partial path and then include it in your fluid template like this:
<f:render partial="Frontend/CookieConsent" />If you want to directly use the example, just add the partial folder to your fluid paths:
10 = FLUIDTEMPLATE
10 {
file = ...
partialRootPaths {
0 = ...
1 = EXT:ujamii_dsgvo/Resources/Private/Partials/
}
layoutRootPaths.0 = ...
}
To configure the target page, just set page.privacyInfo = xyz in your typoscript constants,
where xyz is the uid of the page. If you want to change how this cookie consent is included,
have a look at the setup.ts
To opt out for tracking cookies, you need to add some lines of JavaScript code and provide a link or button for the user which triggers the Opt Out functionality. In the TYPO3 backend, this could easily done by creating a new content element on the privacy information page. Add a new element of type "HTML" and paste something like the example below: (assuming using Bootstrap CSS)
<a href="javascript:gaOptout();window.alert('Tracking has been disabled.');" class="btn btn-danger">I do not want to be tracked</a>
<a href="javascript:gaOptout();window.alert('Tracking wurde deaktiviert.');" class="btn btn-danger">Ich will nicht getrackt werden</a>You may want to add a more detailed description like:
You can deactivate Google Analytics tracking. To deactivate it, please click the button below. A cookie will be created in your Browser. If it is set, Google Analytics will no longer log any data.
or in German:
Sie können das Web-Tracking von Google Analytics abschalten. Klicken Sie dazu auf den unten stehenden Button. Es wird dann ein Cookie in Ihrem Browser gesetzt. Wenn der Cookie erstellt wurde, wird Google Analytics keine Daten mehr erheben.
Matomo provides a ready-to-use snippet directly inside the tracking application itself, so just follow the instructions on their website and you're done.
Have a look at the issues list on GitHub.
Icon downloaded from https://www.flaticon.com/free-icon/database-protection_1825
Icons made by Freepik from www.flaticon.com is licensed by CC 3.0 BY
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent