> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gobihq.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Capturing with people around

> How to capture considerately — and what to tell the person across the table.

Gobi captures conversations, and conversations involve other
people. Here's how to do it well — because capture works best when
everyone in the room is comfortable with it, including you.

## Ask first

A simple, natural version works best:

> "Mind if I capture this? I use an app that summarizes our
> conversations so I don't have to write while we talk."

Most people say yes — usually because the alternative is watching
you type. Asking isn't just polite: in many places it's legally
required (more below), and a conversation where everyone knows
works better than one where someone wonders.

<Tip>
  The honest framing helps: you're not capturing them for
  posterity — you're freeing yourself to actually listen.
</Tip>

## What to say when they ask questions

People are curious, and the answers are good news:

**"So it's listening?"** — It captures. The conversation becomes
a Summary — what mattered, next steps, who said what. You can
offer to send it to them afterward — it's a genuinely useful
thing to share, and offering it usually ends the question.

**"Who can hear this?"** — No one. It lands in your private core,
visible to you alone unless you deliberately share it. Nothing is
posted, nothing is public, and
[nothing trains on it](/privacy/models-and-training).

**"Can you delete it?"** — Yes, completely, any time. If someone
asks you to, do it. A capture is never worth more than the
relationship.

## When to pause

Some moments shouldn't be captured, and the pause button exists
for exactly this: when someone shares something plainly off the
the table, when the conversation turns personal in a way that isn't
yours to keep, or when anyone seems uneasy. Pause, keep talking,
resume when it's right. You lose thirty seconds of transcript and
keep the trust — the trade is always worth it.

## The legal part, plainly

Consent laws vary by place. In much of the world — and
in many US states — one-party consent applies: you being part of
the conversation is enough. Other places, including several US
states, require everyone's consent. Asking first, every time,
keeps you clear everywhere and is simply the better habit — the
law is the floor, not the standard.

<Warning>
  This isn't legal advice, and rules differ by country, state, and
  context (calls often differ from in-person). If you capture
  professionally — client work, regulated industries — know your
  local rules.
</Warning>

## Meetings and groups

For a meeting, one sentence at the start covers the room: "I'm
capturing this so we get a Summary and action items — sent
afterward if anyone wants it." In recurring meetings, say it once,
then it's simply how the meeting works. If one person objects,
don't capture — a partial room's consent isn't consent.

***

The pattern under all of this: capture is something you do *with*
people, not *to* them. Handled that way, it stops being a gadget
behavior and becomes what it actually is — you, paying better
attention.