Table of contents
Key takeaways
- Identify a lawful basis for each use of personal data and assess cookie consent separately.
- GDPR compliance starts with understanding what data your video widget actually collects.
- Check the actual configuration, data flow and processing agreement before publishing your greeting.
What does the data show about gdpr video widgets?
GDPR obligations depend on what your widget processes and why. Start by mapping the personal data, purposes, recipients and retention periods. Cookie consent is a separate question from the lawful basis for processing personal data.

A widget may add scripts, analytics, forms or chat to the page.
A video bubble widget may use cookies, process IP addresses or send interaction data to service providers. Article 6 provides six lawful bases: consent, contract, legal obligation, vital interests, public task and legitimate interests. Choose an applicable basis for each purpose and meet its conditions. Where you rely on consent, it must be freely given, specific, informed and unambiguous. Pre-ticked boxes do not provide valid consent.
In December 2024, the Irish Data Protection Commission imposed €251 million in fines on Meta following a personal-data breach reported in 2018. The findings concerned breach notification and documentation, and data protection by design and default under Articles 33 and 25. This was not a finding about ordinary video-widget tracking.
For cookies that require consent, prevent them from being set until valid consent is given. EU guidance distinguishes these from cookies used solely for transmission or strictly necessary for a service the visitor explicitly requests. EU hosting or a consent banner alone does not establish compliance.
Check your widget’s data flow. Which scripts and requests run on page load, after consent and after interaction? Where is personal data processed, who receives it and what transfer arrangements apply?
What do you need to check before adding video to your site?
GDPR compliance starts with understanding what data your video bubble widget actually collects. Check IP addresses, identifiers, submitted messages and interaction records. Whether a record is personal data depends on whether it relates to an identified or identifiable person.

Personal-data processing needs an applicable lawful basis. Cookie consent depends on the purpose and applicable rules, not simply on whether the widget displays video.
Check who acts as controller and processor, and obtain an appropriate data processing agreement where the provider processes personal data on your behalf. Review sub-processors, processing locations and any international transfers. Do not infer these from the vendor’s address or a hosting label.
A banner alone does not stop tracking. Test a clean browser session before consent, after rejection, after acceptance and after withdrawal. Inspect cookies, storage and network requests. Confirm that activities requiring consent stay blocked until consent is given. Blocking third-party cookies or changing location alone is not a complete test.
Retention policies matter too.
Ask how long your provider keeps each category of data and why. Set retention periods for the stated purposes and applicable legal duties. Delete or genuinely anonymise personal data when it is no longer needed. GDPR does not impose a general 30-to-90-day retention period for widget logs.
Review the recording itself. Identifiable people, private conversations or visible documents can disclose personal data. Establish an appropriate basis and meet applicable notice and image-rights requirements. Avoid including customers or sensitive information unintentionally.
How to set up and check your first video greeting
Start with a short recording for your video bubble widget. Say who you are, what you can help with and what the visitor can do next. Choose a length that fits the explanation rather than a claimed universal optimum.
Record on your phone in natural light. Look at the camera lens, not the screen. The slight eye contact shift makes the greeting feel personal instead of rehearsed.
Install it on a page where the explanation is useful.
Choose one relevant page and follow the installation guide. CompleteGreet documents a header snippet or the dedicated Shopify app. Check page targeting, mobile layout and the action button. The appropriate page depends on your visitors’ questions.
Write a headline that matches the page. On pricing, you could try “Questions about which plan fits?” Make only promises your team can keep. Test wording without assuming a fixed conversion advantage.
Use the display controls available for your chosen format. CompleteGreet documents timed, scroll and exit-intent triggers for supported Shoppable experiences. Do not assume every standard Bubble has those controls.
Check video opens and valid form submissions separately, with clear visitor denominators. Neither a low open rate nor a low submission rate identifies a cause on its own. Review the message, placement and form alongside the data.
A video open is not an enquiry or a sale. Compare completed actions per eligible visitor, preferably in randomly assigned groups during the same period. Use only analytics for which you have an appropriate lawful basis and any required consent.
Test your greeting on a colleague’s phone before going live. Check sound, closing controls and forms. Repeat the privacy checks after changing settings or adding integrations.
A greeting widget may process personal data through delivery, analytics, chat or forms. Showing a face does not itself establish that a tool extracts facial geometry or performs biometric identification. Check the actual functions and data flow.
This section breaks down the specific obligations that apply to video greeting tools and the technical checks that matter before implementation.
Lawful Basis and Consent Requirements
Choose a lawful basis for each processing purpose. Consent is one of six Article 6 bases. Legitimate interests requires an assessment of necessity and the balance with individuals’ rights. Processing special-category data, including biometric data used for unique identification, needs an additional applicable Article 9 condition.
Consent must be freely given, specific, informed and unambiguous, and you must be able to demonstrate it. Make withdrawal as easy as giving consent. Explicit consent is required in some particular circumstances, rather than for all widget processing.
Data Localization and Retention
Check processing locations and international transfers as well as storage. European Commission data protection guidance covers obligations that apply beyond the choice of server location. Review the provider’s processing agreement, sub-processors and applicable transfer mechanism.
Retention periods should match the stated purpose and relevant legal duties. Record the reason for each period and how deletion or genuine anonymisation works. Removing a name alone does not necessarily anonymise a recording.
User Rights and Technical Measures
Controllers must respond to rights requests without undue delay and within one month. Processors must assist. For complex requests, an extension of up to two further months may apply, with notice and reasons within the first month. Rights such as erasure and portability have conditions and exceptions.
Controllers and processors need technical and organisational measures appropriate to the risks. Consider access controls, encryption, backups, staff procedures and monitoring in context. No single measure establishes compliance.
Document personal-data breaches. A controller must notify the relevant authority without undue delay and, where feasible, within 72 hours of awareness unless risk to individuals is unlikely. High-risk breaches generally require notice to affected individuals without undue delay, subject to the applicable exceptions. A processor must notify the controller without undue delay.
CompleteGreet’s public documents describe a processing agreement, sub-processors and possible international providers. Its CookieYes description is website-only. These documents do not establish a universal widget consent-log toggle or exclusively EU processing. Check your actual configuration and agreement. The website owner must provide required notices and consent controls.
Common questions
Do video widgets collect personal data under GDPR?
They can. IP addresses, identifiers, submitted messages and interaction records may be personal data where they relate to an identified or identifiable person. Collection varies by tool and configuration. Review the documentation and actual requests rather than assuming every widget records the same data.
What should my privacy policy say about video widgets?
Explain the controller’s identity, data categories, purposes, lawful bases, recipients, retention periods or criteria, and applicable rights. Include relevant transfer information and how to contact you. Match the notice to your actual use of the widget, including forms, chat and tracking.
Can I use a video widget without showing a cookie banner?
It depends on the cookies and similar technologies used and the applicable rules. Cookies used solely for transmission or strictly necessary for an explicitly requested service can be exempt from consent. Tracking or advertising cookies generally require prior consent. Other GDPR duties still apply, and a banner alone does not block tracking.
Where is video widget visitor data stored?
Storage and processing locations depend on the provider, sub-processors and configuration. An EU business address does not prove EU-only processing. Review the processing agreement and any international-transfer arrangements. CompleteGreet’s public policy allows international service providers.
What happens if someone asks to delete their video widget data?
As controller, assess the request and respond without undue delay and within one month. Ask your processor for assistance promptly. Erasure is subject to applicable conditions and exceptions. For complex requests, an extension of up to two further months may apply, with notice and reasons within the first month. Keep a record of the request, action and response.
Do I need consent before loading a video widget?
Check the processing purpose and technologies. Personal-data processing requires an applicable lawful basis. Cookies or similar technologies may separately require prior consent. Delay activities that require consent until it is given. Clicking play is not automatically informed consent to analytics or advertising.
Are video widgets allowed on healthcare or financial websites?
Assess the actual data, risks and applicable sector rules before use. Health data may require an Article 9 condition in addition to an Article 6 basis. Check security, retention and provider arrangements for the intended use. A general video-widget description does not establish suitability for sensitive submissions.
