Frequently asked questions

Yes, and we open-sourced the banner and the labels so you can. What you pay for is the proof that they were live: timestamped, hashed captures, verified by our crawler rather than self-reported, and exportable as one report. A free banner shows a notice today, but it cannot show that your disclosures were in place last month on the page a complaint is about. That record is what the paid plans provide.

No. We hold the register for you. Each scan cycle writes its captures to a write-once, hash-indexed store, and you export a report for whatever period an authority or client asks about. You do not download or store anything on a schedule. You export when you need to.

Snapshots are sealed the moment they are taken: no one can alter or delete them afterwards, including us. We keep your full history while you are subscribed, so a multi-year report is possible. The seal on each snapshot is guaranteed for at least six months, the minimum an Article 50 evidence trail calls for, and any PDF you export is self-contained, so it stays valid proof even after you cancel. If you do cancel, you get a grace window to export your complete register first.

No. Every report opens with a capture timeline: one row per scan cycle, with its date, item count, and manifest hash. Full-resolution screenshots are included for the most recent cycles. Older captures stay in the register and appear in full when you export their period. The report stays readable whether you have one cycle or two hundred.

There are three. Level 1 · Declared: a valid manifest is served. Level 2 · Rendered: the declared disclosures are visible on the page. Level 3 · Evidenced: Level 2 plus a retained, hash-indexed evidence trail. A site with no manifest is not started; the levels begin at 1.

The snippet is a single script tag, so it runs anywhere you can add header code: WordPress (we ship a plugin), Webflow, Squarespace (Business plan), Shopify, custom sites, or Google Tag Manager. The manifest must be served from your domain. Platforms with root access serve the file directly; the rest use the spec’s fallback or a small reverse proxy. Wix sandboxes third-party scripts, so support there is best-effort. The install guide covers each platform.

No, and that protects you. AI-content detection is statistically unreliable, and a wrong call either way would become part of your compliance record. The manifest is a declaration: you state which AI systems you operate, and we audit whether those disclosures render, stay visible, and are localized. Coverage you can prove beats classification you cannot.

No. AIDisclose is operational tooling: it renders and evidences disclosures. Whether a system is in scope of Article 50, and which exemptions apply, is a question for your counsel. The wizard records your reasoning either way, so the decision is documented.

The transparency obligations of Article 50 of Regulation (EU) 2024/1689 become applicable. Enforcement falls to national market surveillance authorities; Article 99(4)(g) provides for administrative fines of up to €15 million or 3% of total worldwide annual turnover, whichever is higher.

Article 50(1) does not require disclosure where it is obvious from the point of view of a reasonably well-informed, observant and circumspect person. Obviousness is a judgment call you must be able to defend. The manifest records your rationale as an exemption entry. We still recommend the banner: it costs nothing and removes the argument.

The disclosures themselves cover all 28 languages: the snippet renders the banner and labels in each of them, and the PDF evidence report exports in the language you choose. This site and the dashboard are available in all 28 languages too. Article 50 requires disclosures to be clear and distinguishable at first interaction or exposure. The EU Code of Practice standardises the localized AI acronym (KI, IA, ИИ, …), which the snippet implements exactly.

Providers build AI systems or place them on the market. Deployers use them under their own authority. A site running a vendor chatbot is usually a deployer (Articles 50(1), 50(4)). A company shipping its own generative features may also be a provider (Article 50(2) marking). The manifest records a role per system, and both can apply at once.

Yes. Set noAiDeclared in your manifest and AIDisclose renders a Made by humans badge stating that your site operates no AI systems and publishes no content generated by AI. AIDisclose does not verify this. We cannot detect the absence of AI, so the badge reflects your own statement, published openly and dated. A manifest that declares no AI must list zero AI systems, or it will not validate.