Skip to content
Holding·last review26 May 2026

As of mid-2026, the consumer-tier and small-team AI tools most 1-15 person teams use on client work (ChatGPT, Claude, Notion AI, Cursor, customer-service bots) retain context across sessions by default in ways that can carry one client's information into another's work, with each tool exposing a different memory default in a different settings location and a different cross-context behaviour. Most operators have not sat down to align them, and the 30-minute Monday hygiene routine (settings pass per tool; no-client-identifiers rule on every persistent custom-instructions field; per-client reset checklist) closes the operational gap using only the tools already in use.

Claim is scoped to the operator-level capability of a 1-15 person team to reach a defensible client-confidentiality posture on AI tool memory using existing tools and ~30 minutes of work. Does not assert the routine substitutes for an enterprise data-retention register, an Article 30 record of processing activities, or a contractual data-protection impact assessment when those obligations apply. 45-day review cadence calibrated to the pace of consumer-tier AI tool memory feature changes (defaults shifted three times across 2024-2025 on the major platforms). Trigger conditions: (1) the major consumer-tier AI tools ship per-client or per-project memory isolation as a default rather than an opt-in — would move toward Partial because the configuration burden moves from operator to vendor; (2) a small-business or small-agency confidentiality incident specifically traceable to cross-client memory in a consumer-tier AI tool gets publicly disclosed — would confirm the operational exposure; (3) a major SMB-targeted client procurement questionnaire adds explicit questions on AI tool memory handling — would change the operator-side incentive map and move the routine from discretionary to required for client retention; (4) a regulator (ICO, CNIL, FTC) issues guidance specifically naming consumer-tier AI tool memory in a small-business context — would change the structural shape of the routine.

Published
26 May 2026
Last reviewed
26 May 2026
Next review
+45d· 10 Jul 2026
Cohort
1-15 person services agency, solo founder, or small in-house team running AI tools (ChatGPT, Claude, Notion AI, Cursor, customer-service bots) on paid client work
Cadence
45-day
Sibling claim
AM-170Agent memory governance: the data class with no retention schedule, residency policy, or audit-evidence pipeline
Embed this claimiframe + oEmbed
HTML iframe
Paste-the-URL (Substack, Medium, Notion, WordPress)

The card auto-updates when the claim's status, last-reviewed date, or correction log changes. Embedders never need to refresh — the card is rendered live from the canonical record.

Watch this claim

Email-me when OPS-079's status, next review date, or correction log changes. One email per change. No newsletter subscription, no other mail.

The claim: As of mid-2026, the consumer-tier and small-team AI tools most 1-15 person teams use on client work (ChatGPT, Claude, Notion AI, Cursor, customer-service bots) retain context across sessions by default in ways that can carry one client's information into another's work, with each tool exposing a different memory default in a different settings location and a different cross-context behaviour. Most operators have not sat down to align them, and the 30-minute Monday hygiene routine (settings pass per tool; no-client-identifiers rule on every persistent custom-instructions field; per-client reset checklist) closes the operational gap using only the tools already in use.

About this register

The Operators register tracks claims published from practitioner-advisory pieces addressed to solo founders, micro-SMB, and small businesses up to around fifty people. Claims are reviewed on a 30–45 day cadence — tooling and SMB-relevant pricing shift faster than enterprise procurement signals.

Recent corrections in Operators

  • OPS-036 · Partial · 29 Apr 2026

    Initial publication 29 Apr 2026. Status set to Partial at publication because clause 6 commentary references an order-of-magnitude remediation-cost gap derived from the IAPP 2024 AI Governance Profession Report; the report characterises the gap as material but does not publish a precise multiple, so the wording is annotated source: our-estimate.

  • OPS-035 · Holding · 29 Apr 2026

    Initial publication 29 Apr 2026. Status set to Partial at publication because category 5 lacks the same regulatory/cited-consequence anchor as categories 1-4.

  • OPS-034 · Holding · 29 Apr 2026

    Initial publication 29 Apr 2026 with status=partial. Cost-side claims (vendor pricing) verifiable against the four cited pricing pages on the publication date. Time-recovery claim (90+ min compressed to ~20 min) drawn from published productivity-blogger benchmarks rather than Peter-run measurement; first-cohort replication on the publication's tracked operator cohort due by 13 Jun 2026.

Reviews coming up in Operators

  • OPS-005 · Holding · next +0d (26 May 2026)

    At sub-1M tokens per month (typical SMB agent volume) in 2026, the absolute dollar gap between Claude Haiku 4.5, GPT-4o…

  • OPS-003 · Holding · next +0d (26 May 2026)

    For a solo founder choosing exactly one consumer AI subscription at around $20/month in 2026, the choice between Claude…

  • OPS-002 · Holding · next +0d (26 May 2026)

    For a 5-person consultancy already on either Notion or ClickUp in 2026, the AI features alone do not justify a workspac…