Trust and data handling
Clear boundaries before we inspect any work.
Lemonbrand measures work before recommending or implementing AI. That order applies to data handling too: before any access is granted, you should understand exactly what the engagement does, what it does not do, and where its permissions end. This page states the boundary and answers the five questions a firm asks before it connects anything.Free inbox audit: the boundary.
Four facts define the free inbox audit. They are the whole boundary, and nothing beyond them is implied.
Confirmed free-audit facts
Free60 minutesRead-only accessReport only
What the boundary meansThe audit is free and lasts 60 minutes.Access is read-only and the output is report-only: the audit inspects one inbox and produces a report, nothing more.Nothing is sent, edited, deleted, built, or activated during the audit.One inbox is not represented as a complete team workflow. The report describes what one inbox shows, and only that.
Read-only describes the access requested. It is a boundary statement, not a claim that granting access carries no considerations for your organization.How your data is handled.
Five questions a firm asks before it connects anything. The answers are the same for the free inbox audit and the Team Workflow Audit; only the scope of what is read changes.
Answered, and the same in writing before you grant accessConnection methodA read-only connection to Google or Microsoft, held by Pipedream. You grant it from your own admin and revoke it there, without asking us. The read stops when you do.ProcessingSoftware reads the messages and returns counts and patterns. A person at Lemonbrand sees the resulting map, not your mail. Claude does the reading and clustering; OpenAI is used only where a workflow you asked for lives in ChatGPT or Codex.Model trainingTraining is disabled on every model connection we run, ours and the vendors. Your data is not used to train anything.Retention and deletionThe derived map, meaning clusters, counts and recommended workflows, is kept for 12 months so a before-and-after comparison is possible. Raw message content is discarded once the audit is delivered. Ask us to delete the derived data sooner and we do, within seven days.Providers and residencyPipedream holds the connection, Anthropic and OpenAI run the models, and processing happens in North American regions. No advertising, no data brokerage, and no analytics vendor with access to message content. Tell us you need a specific region and we answer before you connect anything.
Scope, by engagementFree inbox auditOne inbox you choose, inspected live with you for 60 minutes. Read-only, report only.Team Workflow AuditOne recurring workflow, up to five inboxes, and twelve months of relevant evidence. Nothing is built, sent, edited, deleted, or activated.
If a question is not answered on this page, the answer comes from a person before access is granted, not from a default. Ask a data-handling questionTeam audit and implementation are separate.
The free inbox audit covers one inbox, once. Broader measurement across a team or business unit, and any implementation, each require a separate scope with its own terms and its own access decision.The free session does not authorize ongoing access or automation. When it ends, so does its permission.We sign your confidentiality terms before we see an inbox.
Start when the boundary is clear.
The free inbox audit is free, lasts 60 minutes, uses read-only access, and produces a report only. Nothing is built or activated during the session.Audit my inbox, freeFree · 60 minutes · read-only · report only
Free inbox audit: the boundary.
Four facts define the free inbox audit. They are the whole boundary, and nothing beyond them is implied.Confirmed free-audit factsFree60 minutesRead-only accessReport only
What the boundary meansThe audit is free and lasts 60 minutes.Access is read-only and the output is report-only: the audit inspects one inbox and produces a report, nothing more.Nothing is sent, edited, deleted, built, or activated during the audit.One inbox is not represented as a complete team workflow. The report describes what one inbox shows, and only that.
Read-only describes the access requested. It is a boundary statement, not a claim that granting access carries no considerations for your organization.How your data is handled.
Five questions a firm asks before it connects anything. The answers are the same for the free inbox audit and the Team Workflow Audit; only the scope of what is read changes.Answered, and the same in writing before you grant accessConnection methodA read-only connection to Google or Microsoft, held by Pipedream. You grant it from your own admin and revoke it there, without asking us. The read stops when you do.ProcessingSoftware reads the messages and returns counts and patterns. A person at Lemonbrand sees the resulting map, not your mail. Claude does the reading and clustering; OpenAI is used only where a workflow you asked for lives in ChatGPT or Codex.Model trainingTraining is disabled on every model connection we run, ours and the vendors. Your data is not used to train anything.Retention and deletionThe derived map, meaning clusters, counts and recommended workflows, is kept for 12 months so a before-and-after comparison is possible. Raw message content is discarded once the audit is delivered. Ask us to delete the derived data sooner and we do, within seven days.Providers and residencyPipedream holds the connection, Anthropic and OpenAI run the models, and processing happens in North American regions. No advertising, no data brokerage, and no analytics vendor with access to message content. Tell us you need a specific region and we answer before you connect anything.
Scope, by engagementFree inbox auditOne inbox you choose, inspected live with you for 60 minutes. Read-only, report only.Team Workflow AuditOne recurring workflow, up to five inboxes, and twelve months of relevant evidence. Nothing is built, sent, edited, deleted, or activated.