ScreenJournal

Call-Recording Addendum

Version 3.2 · Effective 9 November 2026

This Addendum forms part of the ScreenJournal Business Terms of Service (the "Terms"). It binds the Customer whenever audio capture is on for any of its Members, including audio turned on before this version. Capitalised terms not defined here have the meanings given in the Terms. This Addendum allocates responsibility between the Customer and us; it cannot make an unlawful recording lawful.

1. Definitions

  • "Call" means a voice or video conversation between two or more people through a calling or meeting application.
  • "Meeting" means a Call scheduled for a group, whether internal or with outside participants.
  • "Webinar" means a broadcast session, in an application or website, with presenters and an audience.
  • "Participant" means any person whose voice or words are captured on a Call, Meeting or Webinar, including the Monitored User, colleagues, customers, presenters and attendees.
  • "Listed Application" means a meeting or calling application, or a website, that the Customer lists in its audio settings.
  • "Listen Capture" means the setting under which the desktop app records whole Meetings or Webinars in Listed Applications, even when the Monitored User does not speak.
  • "Recording Notice" means the notice the desktop app shows the Monitored User before a recording starts, for the Monitored User to read aloud to the Participants.
  • "Ask Mode" and "Automatic Mode" are the two ways a recording can start, described in section 3.

2. Why this Addendum exists

Recording conversations is regulated by wiretapping, interception and recording-consent laws that differ by country and region. Some require the consent of every party. In the Philippines, the Anti-Wiretapping Act (Republic Act No. 4200) is criminal law: it is an offence to record a private communication without the authority of all parties to it, and to possess, replay or share such a recording. Consent or notice under the Philippine Data Privacy Act does not cure an RA 4200 violation. In the United States, federal law requires one party's consent, but California, Connecticut (for civil claims), Delaware, Florida, Illinois, Maryland, Massachusetts, Montana, Nevada, New Hampshire, Oregon, Pennsylvania and Washington require the consent of every party. California applies its rule to any call with a person in California wherever the recording is made (Kearney v. Salomon Smith Barney, 2006), to any call with a cellular or cordless leg whether or not it is confidential (Penal Code section 632.7), and to a recording of only one side of a call (Gruber v. Yelp, 2020); the civil remedy is USD 5,000 per recorded call with no proof of harm. California courts also treat a recording tool that keeps or reuses conversations for its own purposes as a participant in the recording; we do not, and our model providers are bound not to train on them.

As we understand it, in India the interception of communications is governed by the Information Technology Act, 2000 and the Telecommunications Act, 2023, and a recording is personal data under the Digital Personal Data Protection Act, 2023, which requires notice to the people recorded. In the United Kingdom, as we understand it, a business may record communications on its own systems for permitted purposes under the Investigatory Powers Act 2016 and the regulations made under it, provided it makes reasonable efforts to inform the users of those systems, and the UK GDPR requires transparency towards everyone recorded. The Customer must take its own advice for every country where its Members and Participants are located.

3. What the Services do, and do not do

  • Audio is off by default. An owner or administrator turns it on in the Customer's desktop policy settings, after a warning about recording laws. This Addendum is accepted by that owner or administrator when audio is first enabled for the organisation, and the acceptance is recorded with its version and the time; if it cannot be recorded, audio stays off. A team manager can enable audio for a team only after that acceptance.

  • The Recording Notice. When audio is on and a Listed Application uses the microphone, the desktop app shows the Monitored User the Recording Notice before anything is recorded. Its current text is: "This call will be recorded and transcribed using AI. Please tell us if you do not agree." The Services do not play the Recording Notice, or any other announcement, to Participants. It reaches them only if the Monitored User reads it out, and the Services cannot tell whether it was read, heard, understood or accepted.

  • How a recording starts. The Customer chooses a start mode for the organisation and may set a different one for a team:

    • in Ask Mode, nothing is recorded until the Monitored User presses Start recording; if they do not, nothing is recorded;
    • in Automatic Mode, recording starts 15 seconds after the Recording Notice appears, or sooner if the Monitored User presses Start now, unless they press Don't record.

    Listen Capture always waits for the Monitored User to press Start recording, in either mode.

  • All-party-consent states. Where the Customer's organisation location is California, Connecticut, Delaware, Florida, Illinois, Maryland, Massachusetts, Montana, Nevada, New Hampshire, Oregon, Pennsylvania or Washington, the Services apply Ask Mode, which cannot be changed, and keep Listen Capture off. Current versions of the desktop app also apply Ask Mode to a Monitored User whose location on record, usually derived from their sign-in IP address, is in one of those states.

  • Nothing before the start. No audio from before a recording starts is kept, transcribed or sent to us.

  • What is recorded. Once a recording starts, the desktop app records every Participant it can hear. With Listen Capture it records whole Meetings and Webinars, every presenter and every attendee, even when the Monitored User never speaks.

  • While recording. The Monitored User sees that audio is recording, with the application's name and the time recorded, and has two controls the Customer cannot hide: Mute my mic, which leaves the Monitored User's own microphone out of the recording while the Meeting still hears them, and Stop. Stop ends recording for the rest of that Meeting; audio recorded before Stop is kept and transcribed as usual. If the same Listed Application takes the microphone again within 30 seconds of releasing it, for example after a change of headset, the Services treat it as the same Meeting and keep the Monitored User's earlier answer.

  • Older desktop apps. Versions of the desktop app released before the Recording Notice cannot show it. While the Customer uses Ask Mode they do not record meeting audio, and we discard any they send; they never use Listen Capture; and in Automatic Mode they keep recording as before, without the Recording Notice, until the Monitored User updates the app.

  • Records of each recording. Each transcript carries how its recording started (by the Monitored User, at the end of the Automatic Mode countdown, or by the Monitored User for Listen Capture), when, the version of the Recording Notice shown and when the Monitored User muted their microphone. We also keep a separate record of each recorded Meeting: the Monitored User, the application, the start mode, how and when recording started, when it ended and the notice version, with no audio, transcript or Participant details. That record is kept after the recording is deleted, as our Retention & Deletion Protocol sets out, and we give it to the Customer's owners and administrators on request. These records show what the Services displayed and did; they do not show that any Participant heard, understood or agreed to anything.

  • Transcripts. Recorded audio is transcribed. Transcripts attribute each passage to the member or to the other party. The transcription model also separates the voices it hears and may label a passage with a name spoken in the conversation; that label is stored with the transcript, and the Audio page shows only the member's name or "Other party". We do not match voices against voiceprints or identify anyone biometrically. Transcripts are produced by an AI model and can be inaccurate or incomplete.

  • Keeping and downloading audio. The Customer chooses whether to keep the audio file or only the transcript. Where audio is kept, the Customer's managers can download it, and downloaded copies are outside our control.

  • Retention. Audio and transcripts are kept for the subscription term unless deleted earlier, as set out in our Retention & Deletion Protocol.

4. Before enabling audio

Before turning audio on, the Customer must:

  1. establish, for every country and region where its Monitored Users and their Participants are located, whether and how recording is lawful, including whether Listen Capture of Webinars is lawful and permitted by the Webinar organiser's terms;
  2. list only the applications and websites it has a lawful reason to record, leave Listen Capture off where it cannot lawfully record every attendee, and use Ask Mode, or keep audio off, wherever it cannot establish that Automatic Mode is lawful;
  3. tell each Monitored User, in its own notice, that their Calls, Meetings or Webinars may be recorded and how the recordings are used;
  4. put in place a method of informing Participants, and obtaining their consent where the law requires, such as the Monitored User reading the Recording Notice aloud at the start, a notice in the meeting invitation or the calling platform's own recording notice, and train Monitored Users in it. The Recording Notice supports that method; showing it is not a representation that any Participant was told or agreed;
  5. obtain from each Monitored User with audio on an undertaking to comply with the recording laws that apply where they and the people they speak with are located, and to give any legally required notices and obtain any required consents before recording others. The Services show this undertaking at every desktop sign-in and record the acknowledgment, but that does not replace the Customer's own instruction and training;
  6. for Philippine Members or Participants, keep audio off unless the Customer has confirmed with Philippine counsel that its method satisfies RA 4200. We recommend that Philippine customers keep audio off until they have done so; and
  7. keep its organisation location in the Services accurate, since the Services apply Ask Mode by it, and, for Members or Participants in a US state that requires every party's consent, use Ask Mode, have the Recording Notice or an equivalent announcement given at the outset of every Call, Meeting or Webinar, before recording starts, and keep Listen Capture off; for Calls over the public telephone network with a person in California, use the periodic tone or the opening announcement that the California Public Utilities Commission's General Order 107-B prescribes.

5. For every recording

The Customer must ensure that, for every Call, Meeting or Webinar recorded through the Services:

  1. every Participant is told that the conversation is recorded, at or before the start, in a way the law accepts;
  2. every consent the law requires is obtained before recording starts, and a Participant who objects is not recorded, for example by the Monitored User pressing Don't record or Stop, or ending the Call;
  3. Calls the Customer has no lawful reason to record, such as personal calls, legally privileged calls or calls with authorities, are not recorded;
  4. payment-card details are not spoken into a recorded Call, using DTMF masking or an equivalent control;
  5. people who join after the start are told, and give any consent the law requires, in a way the law accepts, since the Services do not detect them; and
  6. Monitored Users follow the Customer's procedure, do not record when the notice was not given or a required consent is missing, and do not work around the Recording Notice or a restriction on start modes.

6. Participants' requests and recordings in the Customer's hands

The Customer is the controller of recordings and transcripts and must answer Participants' requests about them. We publish a notice for people recorded on calls and webinars, and we pass on any request we receive. The Customer must keep proportionate evidence of its own notice and consent method; our records of each recording (section 3) can form part of that evidence but do not replace it. Downloaded recordings must be handled as the Acceptable Use Policy requires.

7. Representations and indemnity

The Customer represents that it is lawfully entitled to record every Call, Meeting and Webinar it records through the Services. It will defend and indemnify us against all claims, fines, penalties and losses arising from its failure to inform Participants, obtain consents or otherwise record lawfully, as set out in the Terms. This indemnity allocates financial risk only. Criminal liability under RA 4200 or any other law rests with whoever commits the offence and cannot be transferred by contract.

8. Changes in law

If the law changes so that recording requires a step the Customer's method does not provide, the Customer must stop recording affected Calls until it has adopted that step.

9. Suspension

We may turn audio off for the Customer, immediately and without liability, if we reasonably believe recording is taking place without the notice or consent the law requires, or if a competent authority requires it. We will tell the Customer why.

Changes and previous versions

  • 9 November 2026v3.2: the meeting recording notice. Section 1 defines the Recording Notice, Ask Mode and Automatic Mode; section 3 now says the desktop app shows the Monitored User a notice to read aloud before anything is recorded (the Services still play no announcement to Participants), how Ask and Automatic modes start a recording (Automatic after a 15-second countdown), that webinar listen capture always asks first, that Ask Mode is forced and listen capture off in the thirteen all-party-consent states, that no audio from before the start is kept, the Mute my mic and Stop controls, older desktop apps, and the records kept of each recording; sections 4 to 6 conform the Customer's duties.
  • 28 October 2026v3.1: the United States paragraph in section 2 now lists the thirteen all-party-consent states and California's rules on calls with a person in California, calls with a mobile leg and one-sided recordings, with the USD 5,000 per-call remedy; section 4 adds the duty to announce the recording at the outset in all-party states, keep listen capture off there, and use the prescribed tone or announcement on California telephone calls.
  • 5 October 2026v3.0 first publication of the rebuilt Call-Recording Addendum: obligations form; no announcement is played; definitions, listen capture of webinars, transcripts and speaker labels, download, retention, India and UK notes; accepted when audio is turned on.

Questions about this document: support@screenjournal.ai. Canonical URL: /legal/call-recording-addendum.