Recording Consent and the Law

Before you transcribe a meeting, you should tell everyone in it that you are recording and that the speech will be turned into text. Consent is a legal issue, a courtesy issue, and a trust issue โ€” and none of them are solved by processing the audio locally.

Tell people first

The simplest rule is: announce it before the recording starts. Say you are recording the meeting for notes and that the transcription happens on your device. Give people a chance to object, to speak off the record, or to leave the recording for a later segment. A recording that surprises people is a recording that damages trust, whatever the law says.

The law varies by jurisdiction

Recording rules differ between countries, states and provinces. Some places require only one party to consent; others require everyone in the conversation to agree. Because this site cannot know where you or your participants are, it cannot give you a definitive answer. Check the rules for your own jurisdiction, and for the jurisdictions your participants are in, before you record.

This is not legal advice

Nothing on this page is legal advice, and it should not be treated as a substitute for speaking with a lawyer or a local authority. If you are recording meetings in a regulated industry โ€” healthcare, law, finance โ€” the obligations may be stricter still, and you should confirm them before you press record.

What local processing changes

Transcribing locally means the audio is not uploaded to a server, so there is no third party holding a copy of your recording. That materially reduces data exposure: the recording cannot be intercepted in transit, scraped from a provider's logs, or used to train someone's model. But it does not remove the consent obligation. The person speaking still has an expectation about whether their words are being captured, and local processing does not change that.

When in doubt, ask

If you are unsure whether you may record, ask. A short sentence at the start of the meeting โ€” "I am recording this so I can write notes afterwards; is everyone comfortable with that?" โ€” covers most cases. When someone objects, respect it: turn the recording off, or agree that the objectionable part stays off the record.

Consent is about people, not technology

Consent questions exist before the first line of code is written and after the last byte is deleted. The obligation belongs to the person who decides to record, not to the tool they record with. Local processing removes a third party from the chain; it does not remove the conversation that needs to happen before the chain starts.

Different rules for different settings

A team meeting inside one company, a client call across a border, and a doctor's appointment are governed by different expectations and, often, different laws. Healthcare, financial services and legal work can carry stricter obligations about what may be recorded and how long any record may be kept. The tool cannot advise on your situation; a local professional can.

Keep the recording only as long as you need it

Consent to record for notes is not consent to keep the recording forever. Once the notes are written, consider whether the audio still needs to exist. A recording you no longer need is a recording you no longer need to protect, and deleting it is the strongest retention policy there is.

What local processing does not change

Local processing means no third party holds a copy of the recording. It does not mean the people in the room agreed to be recorded. Consent is still required, the audio should still be deleted when it is no longer needed, and the fact that nothing was uploaded does not by itself make a recording lawful.

Transcribe a meeting locally โ€” free and private

← All meeting-notes guides