Home › Help centre › What your client sees

Help centre

What does my client see, and when?

A consent page, before anything is recorded, and then the write-up you send them and nothing else. They never see a draft, and they never see a transcript.

The page they read

You ask for consent from the client's record, and Slide emails them a link to one page in their own portal, headed AI recording consent. It names you, and it says in plain language what is about to happen:

• Audio is captured during the session.
• It is sent securely to vetted enterprise providers for transcription and for drafting the write-up, and the providers are named on a page they can open.
• It is encrypted at rest, and the audio is deleted as soon as the write-up has been made from it.
• It is never used to train third-party AI models.
• They can withdraw at any time. Withdrawing deletes stored audio; write-ups you already sent stay with them.

The same page carries a short note about recording law, because some places require every person in a conversation to agree before it can be recorded, and a client is entitled to know that before they click.

The one button, and the record it leaves

There is a single button, and its words are theirs: it names you and says they consent to recording for their sessions with you. Once they press it, their page shows Consent granted with the date, and the same answer appears on your side before you record anything, so you are never guessing.

If they change their mind, the button becomes Withdraw consent and delete stored audio, and their page then shows Consent withdrawn with the date that happened. You can act on that yourself too: do not record their next session.

One thing to know today, September 8, 2026. There is a fault in our own database that stops this consent record from being written, so a request for consent, and a client agreeing to one, cannot be saved right now. Nothing records without an agreement, so no session has been recorded that should not have been: the product refuses to record rather than proceeding without one, and it tells you plainly when a consent cannot be saved instead of saying it has been. The attestation you give when you upload a recording yourself is stored and is not affected. The published note is section 3 of the consent policy, and it comes down on the day the fault is fixed.

When the recording is one you made yourself

Uploading a recording you captured in the room is the other path, and it asks you rather than the client. Before the upload button turns on you tick a line that says you have consent from everyone in the session to record and process it, and that affirmation is stored with the session record. The responsibility for having actually obtained it is yours, not Slide's.

How long the audio lives

Not long. Session audio is deleted automatically within a day of the write-up being drafted from it. There is no setting that keeps it for longer, and none that deletes it sooner.

The write-up outlives the recording, which is the point of it: it is kept until the account is closed.

The full policy, including how consent is stored and the plain-English overview of the rules in the United States, the United Kingdom, the EEA and Australia, is on the recording and consent page.

What they never see

The draft. Slide writes it and then stops, and the client sees nothing until you have read it and pressed send. There is no automatic send.