Generative AI
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 Typebot.
Free · No account · Result in ~30s
Typebot is open source and gets used as a bubble, as a popup and as an embedded form. Those three embed modes behave differently: only the bubble has a preview message next to the launcher, and that preview message is often the only thing a visitor reads before deciding to click.
We have not yet scanned enough sites where Typebot 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.
cdn.jsdelivr.nettypebot.ioviewer.typebot.iowindow.Typebottypebot-bubbletypebot-standardThe first message block of your flow, plus the preview message in the bubble embed config.
Open your flow in the Typebot editor.
Select the first message block of the start group.
Put the AI notice in it, ahead of the first question.
Go to Share, embed settings, and fill in the bubble preview message.
Publish the flow; the embed serves the published version.
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 Typebot: Typebot bubbles sometimes show a preview message next to the launcher. Put the same sentence there, because that is what people read first.
Typebot documentation: docs.typebot.io
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.
The preview and the first block are two separate fields. We see bots where the preview still shows the old sales line while the first block carries a tidy AI notice. Visitors read the preview first.
In the embed mode without a bubble there is no preview and no launcher. The only place outside the flow is the page itself. Put a line above it, or everything hangs on the first block.
On a self-hosted Typebot the viewer sometimes runs an older build than the editor, so an updated preview message never appears. After a change, always check the live embed rather than the editor preview.
Test on your real page rather than in the editor preview, because those two can run different builds. Use an incognito window and first wait without clicking: on the bubble variant the preview message should appear next to the launcher, and that is a separate field from your first block. Only then click it open and read the first block. Running a popup or an embedded form, check that the line on the page itself is visible without scrolling.
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.
Same place: the first block of the flow. Do check that your viewer and editor run the same version, or you will not see your change.
Then whether it is an AI system is arguable. The notice is cheap; the argument is not. Wire a model into the flow and the argument is over.
The bubble, because there you can fill both the preview message and the first block. With popup and embed you only have the first block and the page itself.
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.