{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/meeting-capture.notice-and-delete/",
    "json": "https://www.anchorterminal.com/niches/meeting-capture.notice-and-delete/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/meeting-capture.notice-and-delete/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/meeting-capture.notice-and-delete/index.min.md"
  },
  "markdown": "No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.\n\n| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |\n| --- | --- | --- | --- | --- |\n| 0 | 6 | 13 | 13 | 9 |\n\n## What counts as done\n\nThe capture posts a visible notice in chat when it joins and starts recording, with text the deployer can set, can be removed mid-call by API, and a documented delete call removes recording, transcript and any debug media, with a retention setting per bot or account.\n\nHow agents ask for it: tell everyone the call is recorded; remove the notetaker from this meeting; delete the recording of that call; don't keep recordings longer than 30 days\n\n## Does the job, with a limit\n\nIt does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.\n\n- **Attendee (Attendee Labs, Inc.)**: send_chat_message lets the deployer post its own notice and leave removes the bot, but no automatic join notice exists, there's no retention setting, and delete_data works only after the bot has ended. The debug-recording leak (issue 960) was closed as fixed in September 2026.\n- **Circleback (Circleback AI, Inc.)**: DELETE /meeting/{id} removes a meeting and workspace retention sliders delete recordings, transcripts and all data on schedule, but no recording notice in chat is documented and no API call removes the bot mid-call.\n- **Meeting BaaS (SAS SPOKE)**: entry_message posts deployer text on join on all three platforms, leave removes the bot, and delete-data removes video, audio, transcripts, chat and screenshots. Retention is set by plan, not per bot, and the docs don't say what happens if the notice fails to post.\n- **MeetStream (MeetStream Corp.)**: bot_message posts deployer text after joining, send_image can show a recording card, remove-bot ends it, recording_config.retention sets per-bot expiry (30 days default) and Delete Data removes recordings and transcripts. Chat can't post where the organiser disabled it, and no fallback is stated.\n- **Nylas Notetaker API (Nylas, Inc.)**: A default notice, replaceable by on_join and on_participant_join messages, posts minutes after joining while recording runs, and a failed post is skipped. leave removes the bot mid-call, retention_time sets 5 minutes to 30 days per bot, and media can be deleted.\n- **Recall.ai (Hyperdoc Inc.)**: chat.on_bot_join and on_participant_join post deployer-set text, pinned on Meet, recording_config.retention sets per-bot expiry and delete removes media including backups. Media is kept indefinitely by default for newer accounts, and acc-41 found the notice best-effort.\n\n## Couldn't check\n\nThe docs were closed to us, or silent. These carry no mark either way.\n\n- **Read AI (Read AI, Inc.)**: The plans page names a retention policy that auto-deletes reports on paid plans, but recording notice, bot removal and delete calls couldn't be read.\n\n- not this job: Fathom (Fathom Video Inc.): Fathom can email attendees to request consent, but the API has no call to remove the recorder mid-call or delete a recording or transcript, and no retention setting.\n- not this job: Fireflies.ai (Fireflies.AI Corp.): deleteTranscript removes a meeting, but the API has no recording notice, no call to remove the bot mid-call (only pause and resume) and no retention setting.\n- not this job: Granola (Granola, Inc.): An automated chat message and a watermark can tell participants, and transcripts auto-delete after a user-set period, but there's no API call to stop capture or delete a note or transcript, so an agent can't complete it.\n- not this job: MeetGeek (AIVISION PRODUCTS SRL): DELETE /v1/meetings/{id} exists, but the API has no recording notice, no call to remove the bot mid-call and no retention setting.\n- not this job: tl;dv (tldx Solutions GmbH): The API reference has no delete call, no notice setting and no call to stop a recording, so none of the success can be done by an agent.\n- not this job: Zoom Realtime Media Streams (RTMS) (Zoom Communications, Inc.): Zoom shows its own fixed disclosure and app notifications to participants and a REST call can stop the stream, but the notice text can't be set and there's no stored media or delete call; retention sits with the app.\n\n## What stops agents finishing\n\n- consent flow left entirely to the deployer (acc-06)\n- notice posted best-effort, so a bot can record with no notice (acc-41)\n- media kept indefinitely by default (acc-07)\n- delete leaves debug recordings behind (acc-30)\n- upload import that needs a public link leaves recordings exposed (acc-55)\n\n## Around it\n\nBefore: meeting-capture.bot-to-transcript. After: agent-memory.delete-fact.\n\n## Where this comes from\n\nWeight 13 of 100 in Meeting capture \u0026 meeting infrastructure: 9 of 56 accounts (acc-06, acc-07, acc-18, acc-19, acc-20, acc-30, acc-39, acc-41, acc-55); consent comes up in every general thread on notetakers\n\nAs data: https://www.anchorterminal.com/api/v1/use-cases/meeting-capture.notice-and-delete.json, or the MCP tool get_use_case with id meeting-capture.notice-and-delete. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-16",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.8",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "For agents",
        "url": "https://www.anchorterminal.com/agents/"
      },
      {
        "name": "Niches",
        "url": "https://www.anchorterminal.com/niches/"
      },
      {
        "name": "Record with participants told, and delete everything when asked",
        "url": ""
      }
    ],
    "description": "Record with participants told, and delete everything when asked: 0 companies fully do it, 6 with a limit, 13 carry the tag. Every listing in Meeting capture \u0026 meeting infrastructure with the reason and a source.",
    "facts": null,
    "h1": "Record with participants told, and delete everything when asked",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/meeting-capture.notice-and-delete/",
    "published": "",
    "section": "agents",
    "title": "Record with participants told, and delete everything when asked |…",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/meeting-capture.notice-and-delete/"
  },
  "tokens": {
    "markdown": 1500,
    "slim": 330
  },
  "version": 1
}
