PHPackages ujamii/ujamii-dsgvo - PHPackages - PHPackages [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register) 1. [Directory](/) 2. / 3. [Utility & Helpers](/categories/utility) 4. / 5. ujamii/ujamii-dsgvo ActiveTypo3-cms-extension[Utility & Helpers](/categories/utility) ujamii/ujamii-dsgvo =================== DSGVO compliance extension for TYPO3 v2.0.0(5y ago)33.4k4[6 issues](https://github.com/ujamii/ujamii-dsgvo/issues)MITPHPPHP >=7.3.0 Since Apr 6Pushed 3y ago2 watchersCompare [ Source](https://github.com/ujamii/ujamii-dsgvo)[ Packagist](https://packagist.org/packages/ujamii/ujamii-dsgvo)[ RSS](/packages/ujamii-ujamii-dsgvo/feed)WikiDiscussions master Synced 5d ago READMEChangelogDependencies (1)Versions (13)Used By (0) ujamii-dsgvo ============ [](#ujamii-dsgvo) [![Packagist](https://camo.githubusercontent.com/b60e4e1ef6853ee0c9716f9215da098bf9dcf2b1a7cc75fe3dc4b4dc82236bf3/68747470733a2f2f696d672e736869656c64732e696f2f7061636b61676973742f762f756a616d69692f756a616d69692d647367766f2e7376673f636f6c6f72423d677265656e267374796c653d666c6174)](https://packagist.org/packages/ujamii/ujamii-dsgvo) Data privacy/DSGVO compliance extension for TYPO3 1. [Version matrix](#versions) 2. [Description](#description) 3. [Installation](#installation) 4. [Usage](#usage) 5. [Extending the database cleaning](#extend-the-database-cleaning) 6. [Credits](#icon-credits) Versions -------- [](#versions) ujamii\_dsgvoTYPO3<= 1.0>= 8.7 <= 9.5>= 2.0>= 9.5 <11>= 3.0 (planned)>= 11Description ----------- [](#description) 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. ### Links [](#links) - [German DSGVO on Wikipedia](https://de.wikipedia.org/wiki/Datenschutz-Grundverordnung) - [European law](http://eur-lex.europa.eu/legal-content/DE/TXT/?uri=uriserv:OJ.L_.2016.119.01.0001.01.DEU&toc=OJ:L:2016:119:TOC) Installation ------------ [](#installation) 1. Get the files 1. install via composer: `composer require ujamii/ujamii-dsgvo` 2. install via archive: [Download](https://github.com/ujamii/ujamii-dsgvo/releases) and extract in `typo3conf` directory, rename folder to ujamii\_dsgvo 2. activate the extension in the backend (may need to clear the [autoloading cache](#command-controller-is-not-available-in-clischeduler-after-installation-of-the-extension) 3. a new submodule "DSGVO" in the main module "web" will appear Usage ----- [](#usage) 1. [Data cleaning](#in-the-typo3-backend) 2. [DEPRECATED! Cookie consent](#deprecated-cookie-consent) 3. [Opt Out for Cookies](#opt-out-for-cookies) 1. [Google Analytics](#google-analytics) 2. [Matomo (Piwki)](#matomo-(formerly-piwik)) ### Modes of operation [](#modes-of-operation) 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](Configuration/TypoScript/pagets.ts). So if you want to add your own table, just add the `anonymize` part and the extension will care for your data as well. ### In the TYPO3 backend [](#in-the-typo3-backend) 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. ### As CommandController on the shell [](#as-commandcontroller-on-the-shell) 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 => FALSE ``` Possible values for the `--mode=` parameter are: - select (just counts rows, does no alter the database) - anonymize (overwrites rows with configured values, see [pagets.ts](Configuration/TypoScript/pagets.ts)) - delete (does what it says, really DELETEs the rows from the database) ### Extend the database cleaning [](#extend-the-database-cleaning) 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](Configuration/TypoScript/pagets.ts). You may skip the `anonymize` part completely if you only want to really delete records for a certain table. DEPRECATED! Cookie consent -------------------------- [](#deprecated-cookie-consent) 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](https://github.com/wacon-internet-gmbh/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](https://cookieconsent.insites.com/). To use it in your TYPO3 project, just copy the [partial template](Resources/Private/Partials/Frontend/CookieConsent.html). to your project partial path and then include it in your fluid template like this: ``` ``` 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](Configuration/TypoScript/setup.ts) Opt Out for Cookies ------------------- [](#opt-out-for-cookies) Google Analytics ---------------- [](#google-analytics) To opt out for tracking cookies, you need to add [some lines of JavaScript code](Resources/Private/Partials/Frontend/AnalyticsOptOut.js)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) ``` I do not want to be tracked Ich will nicht getrackt werden ``` 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 (formerly Piwik) ----------------------- [](#matomo-formerly-piwik) Matomo provides a ready-to-use snippet directly inside the tracking application itself, so just follow the [instructions on their website](https://matomo.org/docs/privacy/#step-3-include-a-web-analytics-opt-out-feature-on-your-site-using-an-iframe)and you're done. TODOs / Known issues -------------------- [](#todos--known-issues) Have a look at the [issues list on GitHub](https://github.com/ujamii/ujamii-dsgvo/issues). Icon credits ------------ [](#icon-credits) Icon downloaded from [https://www.flaticon.com/free-icon/database-protection\_1825](https://www.flaticon.com/free-icon/database-protection_1825) Icons made by [Freepik](http://www.freepik.com) from [www.flaticon.com](https://www.flaticon.com/) is licensed by [CC 3.0 BY](http://creativecommons.org/licenses/by/3.0/) ### Health Score 28 — LowBetter than 54% of packages Maintenance0 Infrequent updates — may be unmaintained Popularity22 Limited adoption so far Community12 Small or concentrated contributor base Maturity65 Established project with proven stability Bus Factor1 Top contributor holds 95.1% of commits — single point of failure How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window. **Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores. **Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement. **Maturity (30%)** — Project age, version count, PHP version support, and release stability. ### Release Activity Cadence Every ~107 days Recently: every ~260 days Total 11 Last Release 1889d ago Major Versions v0.4.3 → v1.0.02019-09-18 v1.0.0 → v2.0.02021-03-15 PHP version history (3 changes)v0.3.0PHP >=7.0.0 v1.0.0PHP >=7.1.0 v2.0.0PHP >=7.3.0 ### Community Maintainers ![](https://avatars.githubusercontent.com/u/1526725?v=4)[Michael Grundkötter](/maintainers/mgrundkoetter)[@mgrundkoetter](https://github.com/mgrundkoetter) --- Top Contributors [![mgrundkoetter](https://avatars.githubusercontent.com/u/1526725?v=4)](https://github.com/mgrundkoetter "mgrundkoetter (58 commits)")[![marionitschke](https://avatars.githubusercontent.com/u/66317219?v=4)](https://github.com/marionitschke "marionitschke (3 commits)") --- Tags composer-packagecookiecookie-consentdsgvogoogle-analyticstypo3typo3-backend ### Embed Badge ![Health badge](/badges/ujamii-ujamii-dsgvo/health.svg) ``` [![Health](https://phpackages.com/badges/ujamii-ujamii-dsgvo/health.svg)](https://phpackages.com/packages/ujamii-ujamii-dsgvo) ``` ### Alternatives [in2code/powermail Powermail is a well-known, editor-friendly, powerful and easy to use mailform extension for TYPO3 with a lots of features 982.5M38](/packages/in2code-powermail)[fluidtypo3/flux The flux package from FluidTYPO3 152982.2k20](/packages/fluidtypo3-flux)[friendsoftypo3/content-blocks TYPO3 CMS Content Blocks - Content Types API | Define reusable components via YAML 96374.6k23](/packages/friendsoftypo3-content-blocks)[derhansen/sf_event_mgt Configurable event management and registration extension based on ExtBase and Fluid 64313.9k6](/packages/derhansen-sf-event-mgt)[typo3/cms-t3editor TYPO3 CMS T3Editor - JavaScript-driven editor with syntax highlighting and code completion. Based on CodeMirror. 115.9M50](/packages/typo3-cms-t3editor)[wazum/sluggi TYPO3 extension for URL slug management with inline editing, auto-sync, locking, access control, and redirects 39488.5k](/packages/wazum-sluggi) PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)