# Disclosed

> Disclosed is a compliance tool for websites with AI chatbots. A script tag
> shows visitors a clear "you're talking to an AI" disclosure (EU AI Act
> Article 50, plus US state bot-disclosure laws), logs tamper-evident proof it
> was shown, and exports audit-ready PDFs from the dashboard.

## Integrate the disclosure

Get your site key from the dashboard: open a chatbot and use "Install snippet".
The disclosure wording is supplied by Disclosed and must not be changed — that
is what keeps the evidence valid. Brand color, position, and theme are
configured in the dashboard, not in code.

- Managed widget (one tag, renders the badge + notice for you):
  `<script src="https://cdn.disclosed.sh/widget.js" data-site="site_live_xxxx" defer></script>`
  Load it on every page where the chatbot appears.
- Embedded (in-page) chat with no floating launcher: add
  `data-anchor="#your-chat"` (a CSS selector) so the disclosure renders above it.
- Headless SDK (build your own UI): `https://cdn.disclosed.sh/widget-headless.js` installs
  `window.Disclosed`. Render your own element with `content.notice`, then call
  `Disclosed.get().observe(el)` so Disclosed verifies and logs the render.
- React: `npm install @disclosed/widget`, then the `useDisclosure({ siteKey })`
  hook — attach its `ref` to the element holding the notice.

## Docs

- [How to install the AI disclosure snippet on any platform](https://disclosed.sh/learn/install-ai-disclosure-snippet): Exact steps for plain HTML, Google Tag Manager, WordPress, Shopify, Webflow, Framer, Squarespace, and React or Next.js, plus how to verify it worked.
- [Build your own AI disclosure UI with the headless SDK](https://disclosed.sh/learn/headless-ai-disclosure-sdk): Render your own disclosure component while Disclosed supplies the wording and logs a tamper-evident, verified record. Vanilla JS and React examples.
- [EU AI Act Article 50: what chatbot owners actually have to do by August 2](https://disclosed.sh/learn/article-50-chatbot-disclosure): The chatbot disclosure duty in plain language: who it covers, what counts as a proper notice, and the two-layer pattern regulators expect.
- [The Digital Omnibus did not delay chatbot disclosure](https://disclosed.sh/learn/omnibus-did-not-delay-article-50): What the May 2026 omnibus agreement actually changed in the AI Act, and why the August 2 chatbot deadline still stands.
- [The Article 50 compliance checklist](https://disclosed.sh/learn/article-50-compliance-checklist): Six checks that decide whether your chatbot is ready for August 2, 2026, and how to fix each one in minutes.
- [December 2, 2026: the AI content marking deadline nobody is talking about](https://disclosed.sh/learn/december-2026-marking-deadline): Article 50(2) requires machine-readable marking of AI-generated content. The omnibus gave existing systems until December 2, 2026. Here is what that means.
- [US chatbot disclosure laws in 2026: California yes, Colorado not yet](https://disclosed.sh/learn/us-chatbot-disclosure-laws-2026): The real status of the California B.O.T. Act, SB 243, Utah's amended AI Policy Act, and Colorado's repealed-and-replaced AI law.
- [Article 50 fines: what EUR 15M or 3% really means for a small business](https://disclosed.sh/learn/article-50-fines-for-smbs): The penalty numbers are ceilings, not floors, and SMEs get the lower cap. An honest look at the actual exposure, and why compliance is still the cheap move.