Consent Surface Mapping

Consent Surface Mapping treats every meeting assistant deployment as a question of where audio and transcripts physically travel, not how good the summary reads. Agencies must map three surfaces before rollout: the capture surface (bot joins the call versus device-level audio capture), the processing surface (vendor cloud versus on-device inference), and the retention surface (searchable vendor archive versus local export). Each surface carries a different consent obligation, and client contracts rarely distinguish between them. A therapy practice using Kith for clinical SOAP notes faces HIPAA-grade consent language that a marketing retainer never triggers, while Scrieb keeps recordings on the operator's own machine and sidesteps third-party processing entirely. Keen Bean captures through the Mac's own audio channel, so no bot appears in the participant list, which changes what clients are told. Map the surfaces first, then pick the tool that matches the strictest client in the portfolio.