Example Dental Co. (example-dental.test)

At a glance

1. Summary

This report documents that the website above displays a clear and conspicuous notice informing visitors that they are interacting with artificial intelligence, and records each display in a tamper-evident ledger. During the reporting window of 7 years, 354 notices were shown, 270 were acknowledged by visitors, and 44 were repeat disclosures during continuing sessions. First logged event: 2026-09-15T14:12:22.000Z; most recent: 2026-10-14T23:08:05.000Z.

2. Ledger integrity

Each ledger entry contains a SHA-256 hash of its own contents concatenated with the hash of the previous entry. Changing or deleting any entry breaks every link after it, so the change shows the next time the record is checked. Re-computing the chain across all 864 stored entries at generation time: VALID: no entries altered or removed.

How anyone can check an entry

1. Take the entry from the CSV export (or the table in section 5).
2. Join these values with a "|" between them: site ID (5a3e0c1d-7b2f-4e91-9c55-0d1e2f3a4b5c), event, page, country, region, visitor code, time, the previous entry's hash, then the conversation ID if there is one, then "v2", channel, notice version and meta, then, on entries that have them, "v3", vendor, vendor conversation ID, linkage and the time the ID was read.
3. Run SHA-256 on that line. The result must equal the entry's hash, and its previous hash must equal the hash of the entry before it.

5a3e0c1d-7b2f-4e91-9c55-0d1e2f3a4b5c|link|/insurance|US|WA|f69f55bfd26cadc2|2026-10-14T23:08:05.000Z|6f1f9cb94eecd778b0398443a92bea44913a6b1f871646e98cad86d5e8d16e73|bn_mv8pyoyw03216214bd1f2fa3|v2|chat|9127|{"style":"card"}|v3|livechat|MTQ9Z9A9W4|vendor_id|2026-10-14T23:08:05.000Z

87357d619389488fb5c503c3580e4fd01de8c0c8d7d0b275edbe310f0a1950c5

Retention. Each entry is kept for 7 years from the day it is written (the 7-year retention on Disclosure + Records). Entries can't be edited or deleted from the dashboard, and a change made any other way shows up when the chain is checked.

3. Notice configuration in effect

4. Legal frameworks addressed

5. Most recent ledger entries

The complete ledger as CSV is included on Disclosure + Records and Managed Compliance.

6. Linking a notice to one conversation

Each chat entry says how firmly it is tied to one conversation. A chat vendor's own conversation ID is read in the visitor's browser where the vendor makes one available (the ID only, never messages, names or emails); when it arrives after a notice was recorded, it comes as a separate "Linked to chat vendor" entry for the same session, and the earlier entries are left as they were.

In this period: 176 of 398 chat notices (44%) are tied to the chat vendor's own conversation. An ID shown as h: and 32 characters was personal data (an email or a phone number), so only a hash of it, salted for this site, was kept. Looking it up by the original ID still finds it.

7. Off-site backup copies

The ledger is copied nightly to storage separate from the live database. Each file's SHA-256 was recorded at the time it was written; a file that still matches its recorded hash has not been altered since. The 10 most recent are listed.

8. Independent monitoring and bot probes

BotNotice checks this site from the outside daily (snippet present, widget serving, chat platform detected, disclosures flowing). Of the last 30 checks: 30 passed, 0 warned, 0 failed. Most recent (2026-10-15): pass, Snippet present, widget serving, 91 disclosures logged in 7 days.

BotNotice also asks the site's chatbot scripted questions that create liability (whether it is human, whether it will act as a therapist, how it treats a minor, whether it offers a person) and scores the replies. Recent results:

9. AI-generated content register

No AI-generated content items are registered for this site.

10. About this sample

This is a sample. Example Dental Co., example-dental.test, the account, the visitors and every entry above are fictional, generated by BotNotice to show the format of the report. It describes no real website or person. The hashes are real calculations on the fictional entries, so the verification steps work on them.