GDPR check for TYPO3

TYPO3 itself is data-frugal. The critical points arise through extensions, embedded fonts and content elements for videos or maps.

Is this a risk?

Common findings: sitepackages that load Google Fonts or Font Awesome icons from external CDNs; tracking extensions with no link to a consent status; the “YouTube” and “Vimeo” content elements that load on page view. § 25 (1) TDDDG applies to all non-necessary access.

What you can do

• Serve fonts and icon fonts locally, remove external CDN calls from the sitepackage.
• Use a consent extension (e.g. wacon/sg_cookie_optin) that blocks tracking scripts until consent.
• Enable the built-in click-before-load option for the video content elements.
• After each deploy, check the home page source for external calls before consent.

How consentglass helps

The free scan checks the delivered HTML and shows which services are embedded, whether a cookie banner is detected and whether privacy-policy and legal-notice links are present — with context for each finding. It is not a substitute for legal advice.