Chat widget
Article 50 asks that visitors know they are talking to an AI. Scan your site free, and read below exactly where that notice goes in Tawk.to.
Free · No account · Result in ~30s
Tawk is free and therefore sits on an enormous number of small sites, often installed years ago and untouched since. The classic setup is live chat with a person, which Article 50(1) does not cover. Since Tawk started offering an AI assistant, though, the same widget can quietly have become an AI interaction without anyone deciding so.
We have not yet scanned enough sites where Tawk.to was the first widget we detected to say anything meaningful here. As soon as the sample is large enough it will appear, counts included. We would rather publish nothing than a percentage based on two sites.
Our scanner looks for these signals on your public page. Two independent signals are required for a match, so a blog post that merely names the vendor does not count.
embed.tawk.tova.tawk.towindow.Tawk_API#tawkchat-container.tawk-min-containerAdministration, Chat Widget, Content, welcome message or triggers. Tawk uses triggers for the opening message, so look there if the text does not change.
Log in to dashboard.tawk.to and pick your property.
Go to Administration, Chat Widget.
Open the Content tab and find the welcome message.
Also check Triggers: that is often where the message actually sent lives.
Save and reload your site without cache.
The sentence you paste
You are chatting with an AI assistant, not a person.
The welcome message only appears after opening. The banner snippet from the Compliance Kit covers the moment before that with a single script tag, and your AI transparency statement covers the question that comes after.
Watch out with Tawk.to: Tawk is free and often runs without a bot. With no AI bot, Article 50(1) does not apply, but with Tawk's AI assistant it does.
Tawk.to documentation: help.tawk.to
Three mistakes we run into on sites that did set the notice. Each one costs points in the scan, and each one takes minutes to fix.
On Tawk we hit this more often than with any other vendor: the widget runs, but the credentials are lost or sit with a former agency. Sort out access first; without the dashboard you can only place the notice via the banner on your own page.
If you edit the welcome message and nothing changes, you usually have a trigger that fires its own message after a few seconds. That message is what visitors read. Edit the trigger, or switch it off.
Enabling Tawk AI changes what the widget is: a person is no longer the first to answer. The welcome message then commonly stays on the old, human phrasing.
Open your site in an incognito window and wait half a minute without clicking. If a message appears that you did not put in the welcome message, a trigger is overriding it; you find that under Triggers in the dashboard. Then click the launcher and read the message inside the window. If you are unsure whether the AI assistant is enabled, ask an open question outside office hours and see whether an answer arrives on its own.
After that you can scan again. Our scan looks at the same public page a visitor does, so what you see in an incognito window is roughly what we see.
Then there is no AI interaction. The banner is optional, but it costs nothing and covers the moment you do switch the AI assistant on.
That is a Tawk plan question, not a compliance one. The notice is separate and is equally easy to place with or without branding.
You can still put the notice on your own page with a banner beside the launcher. That covers the moment before opening; the message inside the widget stays out of reach.
The Compliance Kit contains a copy-paste disclosure banner (NL/EN/DE), an AI transparency statement, an AI system inventory and a step-by-step guide per widget.
See the Compliance Kit (€149)Technical compliance tooling and templates. Not legal advice.