← Dashboard · Print this page for a paper packet (browser File → Print).

Counsel review summary — Lead program & embed capture

Not legal advice. This page summarizes product behavior for orientation only. It does not constitute a compliance opinion or TCPA / privacy-law determination. Repository copy may include updates under docs/COUNSEL-LEAD-PROGRAM-REVIEW-PACKET.md.

1. Template versioning

Merchant program configuration carries publish counters; the public embed config returns program_template_version (bumps on each dashboard save) and capcha_lead_disclosure_version (CapchaCloud-built disclosure text generation) alongside disclosure HTML.

2. What the visitor sees (Door B)

After the merchant completes dashboard setup, the embed may show server-built disclosure HTML, structured fields (name, email, phone), consent checkboxes, and a Turnstile gate before submit. OAuth sign-in to CapchaCloud is a separate “Door A” path and is not merchant TCPA consent.

If setup is incomplete or the program API cannot be reached, the widget shows a brief plain-text note under the sign-in card directing the operator to the dashboard (Lead program / allowlists) instead of leaving the lead block empty with no explanation.

3. Data collected on submit

Category	v1 contents (summary)
Structured lead & consents	JSON `context` (e.g. lead name/email/phone; consent booleans).
“Web recording”	DOM snapshot of the consent panel and bounded `visual_recording` entries — not full-screen video.
Server / edge evidence	Timestamp, IP, geo hints where available, Turnstile outcome, integrity hash over stored payload bytes.
Tenant list / triage	Optional denormalized `lead_email` / `lead_phone` on index rows for authorized dashboard search (`GET /api/v1/audit?q=`).
Operator excerpt	From the dashboard Evidence payload modal after opening a vault row: Copy triage summary pastes a short plain-text handoff (hash, integrity line, coarse vault jurisdiction when opened from the table, IP, timestamps, template stamps, structured lead fields, consent flags, snapshot/DOM sizes, edge metadata pointers). Pasting a bare hash into Open record still loads JSON but omits the vault-row jurisdiction line.

4. Webhooks

When configured, webhooks can include structured lead fields for CRM triage, plus optional lead_program_version and capcha_lead_disclosure_version when present on capture context (template-generation triage without a vault round-trip). Securing webhook URLs and downstream compliance remains the merchant’s responsibility.

5. Limitations (non-negotiable messaging)

DOM snapshot ≠ screen video.
Feature availability does not guarantee regulatory compliance; counsel must approve copy and program fit.

6. Open items for counsel

Final checkbox and disclosure wording.
Whether DOM + structured + server evidence suffices for the merchant’s use case and jurisdictions.
Retention, deletion, and cross-border considerations.

CapchaCloud — lead program counsel packet (printable HTML; repo source docs/COUNSEL-LEAD-PROGRAM-REVIEW-PACKET.md, v1.1+).