Soundly RunSound familiar?

The client contract bans AI

A client's contract forbids putting their data into AI. Your teams use AI every day, and nobody can prove the line held.

InsteadContent marked for that client is checked before an AI request reads it, and each request is logged for the client’s audit.

The video

Video planned58 secondsHow every video is made
The script
The one point
A contract’s AI ban becomes a mark on the client’s content, checked before an AI request reads it.
Why a video
Cause and effect rippling: one unread clause while a client file passes team to team into AI. Then the same moment twice: the identical file, stopped at its mark.
  1. Intro0:00-0:03sting

    Picture
    Brand mark and sound, then the heading ‘The client contract bans AI’ on the site’s background, fading straight into the guide with no black.
    On screen
    The client contract bans AI
  2. The moment0:03-0:11person

    Picture
    Guide in the usual place, medium shot. Lower third: guide’s first name, Soundly Run guide.
    Voice
    A client’s contract forbids putting their data into AI. The clause sits with legal; the teams using AI every day never see it.
    On screen
    AI clause in the signed contract; the people doing the work never see it
  3. The cost0:11-0:19motion

    Picture
    A contract page, one clause glowing, slides into a drawer. A client file icon moves from sales to delivery to support, each time dropped into an AI box. An audit form arrives; its evidence box stays empty. No numbers.
    Voice
    The file travels through three teams and into AI tools. When the client audits, there is no evidence to show.
    On screen
    No evidence for the client’s audit
  4. The mechanism0:19-0:37screen

    Picture
    Drawn Needs you screen, Example tag top left, context ‘Mei’s crew’. Step band on prepare, then review. Cursor down the rows in order: Clause, Applies to, Drafted mark (new), Unclear (warn), AI requests.
    Voice
    A helper read the signed contract. Its AI clause is drafted as a mark: never leaves. Eighteen unclear meeting notes go to Leo, the account manager. Each AI request is logged.
    On screen
    Example: Northwind’s contract bars its data from AI
  5. The decision0:37-0:46person and screen

    Picture
    Step band on decide. Apply ‘never leaves’, Change and Pass visible. Mei clicks Apply; held two seconds. Split screen: left, the file sent to AI before; right, the same file stopped at its mark. Guide in picture-in-picture.
    Voice
    Mei, in legal, decides: apply ‘never leaves’, change it, or pass. Applied. The same file now stops at its mark.
    On screen
    Applied. AI requests check the mark first.
  6. The difference0:46-0:54person

    Picture
    Guide back in the same place and framing as The moment.
    Voice
    Nobody guesses which client data may go into AI, or hunts for audit evidence, any more. The helper drafts; Mei decides. It checks the content: it does not watch, score or replace anyone.
    On screen
    Content marked for that client is checked before an AI request reads it, and each request is logged for the client’s audit.
  7. Outro0:54-0:58sting

    Picture
    Standard end card, the same in every video: the page title, the brand mark and one small line, ‘Example screens’.
    On screen
    The client contract bans AI

On screen as proof

  • Drawn Needs you screen, tagged Example: Northwind’s contract bars its data from AI
  • The AI clause drafted as the mark Never leaves: no AI reads it
  • Before and after split: the same file sent, then stopped at its mark; 0 AI requests on Northwind content since 19 Oct

Before and after

Before
AI clause in the signed contract; the people doing the work never see it
After
Each AI limit drawn out of new and existing contracts
Before
Teams guess which client data may go into AI
After
Restricted content marked ‘never leaves’; AI requests check the mark first
Before
No evidence for the client's audit or security questionnaire
After
A log of each AI request, per client, ready to produce

How it works

The contract’s AI limit becomes a mark on the client’s content, checked before AI reads it.

  1. At signing, the AI clause becomes a limit on that client’s content; whoever reads your contracts confirms it.
  2. Every file, note and channel for that client carries the limit; the account manager decides anything unclear.
  3. An AI request checks the mark before it reads anything; for an audit, the client’s log is produced as it stands.
Needs youExample

Mei's crew

Northwind's contract bars its data from AI

Clause
No client data in any AI tool
Applies to
Northwind workspace: 1,240 files, 3 channels
Drafted mark
Never leaves: no AI reads it
Unclear
18 meeting notes that mention Northwind, sent to Leo, account manager
AI requests
Logged per request, ready for Northwind's audit

Source: Northwind’s contract, signed 19 Oct

Apply 'never leaves'ChangePass

Built to work in the email, calendar, chat, finance and sales tools you already use.

What it never does

  • Acts alone only inside limits a person sets; asks first for anything else.
  • Reaches only what its job needs.
  • Never watches, scores or replaces anyone.