Every deck you write is read by a roomful of people you can’t see in advance. One reads only the title slide. One nitpicks the chart axes. One asks the question you were hoping no one would ask. By the time you find out who was in the room, the meeting is over.

DeckNotes assembles that room before the meeting. Nine reviewers, each watching for something different — fluff, logic, design, the question in Q&A. They read your deck and leave comments in Google Slides, the same place your real reviewers would. You see the panel’s notes the way you’d see a colleague’s: in context, in your own file, with the same affordances you already use to reply, resolve, or push back.

One reviewer catches a third of what you’d want caught. A panel catches most of it. That is the entire premise.

Generic “AI feedback” tells you everything is wrong at once. A panel of nine reviewers tells you who thinks what. When Jason flags a sentence as fluff and Maya thinks it’s load-bearing, you can see the disagreement and decide. When Yvonne skims past your most important slide, you know to lead with it next time.

Names also let us draw a line. Charles isn’t going to leave you a comment about your numbers. That’s Lin’s job. Each reviewer has a beat, and they stay in it.

Feedback that lives in another app is feedback you have to remember to check. DeckNotes writes its notes as native Google Slides comments — the same threads your colleagues use. You can reply, resolve, @-mention a real person to weigh in, or argue back. The reviewers fit into the workflow you already have.

We don't store a copy.

When you point DeckNotes at a Slides file, we read the slides at review time and let them go. We don't keep a copy of your presentation on our servers. We keep the metadata — file ID, who ran the review, when, which reviewers participated — because we need it to count your readings and show you a history. We don't keep the contents.

Prompts are anonymized.

To generate feedback, slide content is sent to Anthropic's Claude. Before we send it, we strip metadata that would identify you, your company, or the deck — your name, the file title, your email. Claude sees the words on your slides and not much else. Anthropic's API doesn't retain content for training in our configuration.

Comments live in your Drive.

Reviewer feedback is written as native Google Slides comments in the file you already own. Delete the file, delete the conversation. Revoke DeckNotes' access in Google, and we lose our handle on the file. Your Drive is the system of record; we're a participant.