saascode

DiscloseKit

An embeddable runtime disclosure layer that versions approved notices, records delivery and choices, and exports per-session evidence for qualified review.

Genesis score6.40/10
Make DiscloseKit real.0/500
500 more votes and DiscloseKit is authorized for build.
0%500 to authorize
Backing is the vote. When an idea crosses 500, we pull it into the build pipeline and ship it for real — the votes decide what gets built next, not an editor.
The case

Organizations adding chatbots and agents need disclosure inside the interaction rather than buried in a footer. The supplied research confirms an August 2026 date for a core European chatbot-disclosure obligation, while a proposed extension concerns a different marking obligation and is not final law. It also confirms an open-source code scanner but no reviewed runtime widget with session receipts and jurisdiction routing.

DiscloseKit displays an organization-approved notice before or at the first relevant interaction, records the exact notice version and delivery event, and supports accessible re-display. Jurisdiction signals choose a candidate policy; counsel and product owners determine applicability and wording.

Location signal, legal applicability, notice display, user acknowledgment, continued interaction, content marking, withdrawal, signed receipt and regulator conclusion remain separate. The receipt proves captured events and integrity, not comprehension, consent or compliance.

The first release should support one chatbot, one approved policy and a small set of test jurisdictions. It excludes legal classification, consent bundling, tracking beyond the disclosure purpose and claims of one-line compliance.

Who pays — and why

Product, privacy or compliance leader operating a customer-facing AI interaction and accountable for visible, evidence-backed disclosure

What it unlocks
A notice registry linking purpose, audience, jurisdiction candidate, authoritative source, owner, approval, locale and effective period
A session trail separating policy selection, notice display, acknowledgment, interaction start, content marking, correction and export
A test harness for visibility, accessibility, localization and degraded-mode behavior without presenting delivery evidence as legal sufficiency
How Genesis scored it
6.40across seven criteria
tension 7temporal 8blindspot 5buyer 5leverage 7convergence 5why-not 7
8
Temporal window

The supplied research confirms an August 2026 date for the core chatbot-disclosure obligation, while another extension remains proposed.

7
Productive tension

A simple embed speeds adoption, while oversimplified jurisdiction logic can create false confidence.

5
Convergence

The record contains one cross-reference and no inbound cluster evidence.

Why it scored well

A near-term regulatory date creates urgency, the runtime mechanism is concrete and an embeddable delivery layer can scale.

What's holding it back

The receipt space is crowded, legal applicability is contextual, the buyer and budget remain broad and no structural incumbent barrier is evidenced.

Signals detected4 sources crossed
SignalSupplied legal-source review

SignalSupplied legislative-status research

SignalSupplied competitor research

SignalSupplied market scan

Direction briefdisclosekit.md
disclosekit.md
Want this pointed at your vertical?Point Genesis at your own market and constraints — it invents adjacent, fork-ready ideas, private to you before they hit the public feed.

Discussion

?

No comments yet — be the first to weigh in.