Embedding YouTube and Google Maps
Embedding a video or map loads content from Google when the page opens, sending an IP address and usually involving cookies. Section 25(1) TDDDG requires consent **before** this happens.
What actually happens
A conventional YouTube embed contacts several Google domains and stores identifiers in the browser as the page loads. This happens before the visitor presses Play, often even if they never watch the video.
The two-click approach
Initially, show a preview image from your own server with an explanation. Only load the actual embed after someone clicks and consents. The first click gives consent; the second starts the video.
Cards are often completely without
Directions rarely require an interactive map. A screenshot linked to a map application serves the same purpose without loading external content or requiring consent. OpenStreetMap is another option and can also be served from your own infrastructure.
If you include it
- Obtain consent first, with equally prominent Yes and No buttons.
- Name the service and explain transfers to the USA in the privacy policy.
- Make withdrawal as easy as giving consent.
Suitable tools
Further in Legal & privacy
- Legal notice – Who needs a legal notice, what it must contain and the mistakes that can lead to legal demands.
- Privacy policy – What Article 13 GDPR requires and why generic templates rarely fit.
- Google Fonts – Why loading fonts from Google’s servers can cost money and how to fix it in ten minutes.