Recording, Consent and Attendance

Two people read this, and they want different things from it.

If you are in a meeting and the recording indicator just appeared: the host has started a recording. What it captures, what Meet Buddy does not capture, where the file goes and what you can ask for are set out below. You do not need an account to be entitled to any of it.

If you host meetings: pressing record is a legal act in most of the world, and in some places it is a criminal one when you get it wrong. Meet Buddy gives you an indicator and an in-room notice. Those are notice. In a good part of the world what the law asks for is consent, which is a different thing, and no software can obtain it for you.

Almost every legal system treats recording a conversation as different from being in one. The systems differ on whose agreement is needed, and that difference is the single most expensive thing to get wrong.

One-party consent

It is enough that one participant — which can be you — knows about and agrees to the recording. This is the rule under the United States federal wiretap statute (18 U.S.C. § 2511(2)(d)), which also removes the protection where the recording is made in order to commit a crime or a tort.

All-party consent

Every participantmust agree. A number of US states work this way — California’s Penal Code § 632, which protects “confidential communications”, is the most frequently cited — and in those places recording without everyone’s agreement can be a criminal offence as well as a civil wrong.

We are not reproducing a list of all-party jurisdictions here, on purpose. Those lists change, the details differ by the kind of communication, and a stale list printed on a page like this one is worse than no list at all, because somebody will rely on it. Check the jurisdictions that actually apply to your meeting, or ask a lawyer who can.

Which jurisdiction even applies

A Meet Buddy room routinely holds people in several countries. Whose law governs a call between a one-party state and an all-party state is a genuinely contested question, and the answer that keeps you out of trouble is not to litigate it: assume the strictest rule that could plausibly apply to anyone on the call.

Outside the United States

The framing is often different rather than looser. In the EU and the UK, a recording of an identifiable person is personal data: you need a lawful basis for making it, you must tell people before you do, and extra rules apply if what is discussed is health, biometrics or another special category. In Australia, listening- and surveillance-devices law is state and territory law and the rules genuinely differ across borders. In Canada, the Criminal Code permits recording where one party consents, while separate privacy legislation governs what a business may then do with the recording. This paragraph is orientation, not advice, and it is not exhaustive.

You can comply with the strictest version of all of the above without knowing which version applies, by doing five things. They cost about fifteen seconds.

• Say it out loud, before you start.“I am going to record this — is everyone happy with that?” An indicator in a corner of the screen is notice; a question is consent.
• Start the recording after you have asked, not before. Then the agreement is captured on the recording itself, which is the only record of it that survives the meeting.
• Mean the question. If someone says no, stop — or let them leave without it counting against them. A request nobody can refuse is not consent in any system that uses the word.
• Say what happens to it. Who will see it, how long it is kept, whether it leaves your company. People agree to a recording they understand and object to one they do not.
• Tell late arrivals too.Meet Buddy puts the notice in the room’s state as well as broadcasting it, so somebody who joins at minute twenty is shown it — but they have not heard you ask, and they have not answered.

Every item here is a behaviour of the software, described so you can check it against what you see in the room.

Only a host can start one

The control is a host control. It is authorised on the server against your live role in the workspace, re-read at the moment you press it rather than at the moment you joined — so somebody whose access was removed during the meeting cannot start a recording with the rights they had an hour ago.

A visible indicator, for everyone

Recording state lives in the room’s shared state, so it is the same for every participant. Nobody sees a room that says it is not recording while it is.

An in-room notice, including for late joiners

The notice is broadcast to the room when recording starts, and it is also written into the room’s state, so somebody who arrives afterwards is shown it rather than walking into a recording nobody mentioned.

A record of whether the notice appeared

Meet Buddy stores the moment the notice actually went out, and stores nothing there if it did not. That field is deliberately not inferred from the recording’s start time: “we started recording” and “we told the room” are different claims, and only one of them is worth having in a dispute.

Recording can be disabled for a meeting

A meeting carries its own switch, so a workspace can run a conversation that cannot be recorded at all rather than relying on everybody remembering not to.

It may not be available at all

Recording needs object storage and a separate recording worker alongside the media server. Where a deployment has not configured them, the control is disabled and says why. It is never a button that appears to work and produces nothing.

This section exists because the absence of a feature is exactly what people assume wrongly, and assuming wrongly here has consequences.

• It does not transcribe your meetings. No speech recognition runs on your audio, in the room or afterwards. There is no transcript to search, and none is produced for us either.
• It does not caption live. Where live captions exist at all they are a capability of your own browser, and Meet Buddy tells you when your browser cannot do it rather than showing a control that does nothing.
• It does not analyse who you are. No voice identification, no speaker matching, no sentiment or attention scoring, no facial recognition. Nothing derives a profile from how you sounded or looked.
• It cannot record covertly.There is no mode in which a recording runs without the room’s state saying so.
• It cannot stop somebody recording you by other means. A participant can run screen-capture software, point a phone at the screen, or take a photograph, and no meeting product on any platform can detect or prevent that. The indicator tells you about Meet Buddy’s recording, and it is the only recording it can tell you about.

A meeting leaves a record whether or not anybody presses record, and that record outlives the room. It is short, and it is worth knowing.

Attendance

Who joined, when they joined and left, and how long they were present. A participant who drops and rejoins produces several spans, and a total. Hosts can see this per meeting.

In-meeting chat

Messages sent in the room are stored against the meeting, with the sender’s name recorded alongside — so a line still reads even after that person’s account is gone. Treat in-meeting chat as written down, because it is.

The meeting itself

The code, the room name, when it started and ended, and which booking it belongs to.

Audio and video are not stored unless a recording is running. Attendance and chat are stored either way.

The file is written to the workspace’s own area of object storage, under a path that begins with the workspace’s identifier. That prefix is built by a shared helper rather than assembled by hand anywhere in the code, which is what makes one workspace’s recordings structurally unable to land in another’s.

Meet Buddy stores the object’s key and never a URL. Playing a recording mints a short-lived signed link at the moment you press play, so access can be withdrawn by changing who is allowed to ask — not by hunting down links that have already been handed out.

How long it is kept

Meet Buddy does not delete recordings automatically. There is no retention timer in the product. A recording is kept until somebody deletes it or the workspace is deleted, at which point the workspace’s stored objects are scheduled for removal along with its rows. If your organisation has promised a retention period — [recording retention period] — that promise is currently kept by a person, not by the software.

The host’s organisation controls the recording — not Meet Buddy, and not the operator of this deployment. In data-protection terms they decide why it exists and what happens to it, so they are who to ask.

• Ask them to delete it. Say which meeting, and when. Depending on where you live you may have an enforceable right to erasure or to object; even where you do not, most hosts will simply do it.
• Ask what it was for and who has seen it. A host who cannot answer that has a problem independent of you.
• If you cannot reach the host, contact this deployment’s operator at [contact address for privacy requests]. They can usually reach the workspace, and they are the right escalation if a workspace is unresponsive. What they can do unilaterally is limited — see the privacy policy for the split.

Objecting during the meeting is also legitimate, and is the point at which it is easiest to fix. Say so, and the host can stop.

By recording a meeting through Meet Buddy you are confirming that you have whatever agreement the law where your participants are requires, and you accept responsibility for having it. The acceptable use policy makes recording without the consent the law requires a breach in its own right, and the terms put the consequences of getting it wrong on the workspace rather than on the operator.

That is not the operator disclaiming an inconvenience. It is the only arrangement that reflects reality: whoever was in the room, what was said, what was promised about the file and which laws applied are facts that only the host knows.