Activities / What code does
Records calls
records_calls
Your app records, transcribes, or monitors people talking to each other, on a phone or video call or in a meeting.
- scope code
- in the registry since 1.0
- 178 laws in 100 jurisdictions name it
What triggers it
The lint's definition. It records, transcribes or monitors people talking to each other: a phone or video call, or a meeting in person or online, including a notetaker that joins one. A voice assistant, or your voice alone, is processes_voice.
This covers a call-center recording feature, a notetaker that joins a video meeting, and a tool that saves a session for later review.
What does not
A call your app only carries from one person to another, without keeping or reading it, does not count.
A voice assistant a caller talks to is Processes voice recordings, and so is recording your own voice alone: Records calls is for people talking to each other.
Often confused with Processes voice recordings and Records text chat.
The law it brings into scope
The kinds of law that name this activity in the LexLint law library, with the number of laws and jurisdictions in each, as of . The examples are chosen by rule, laws in force first and the widest jurisdiction first; each section's page lists every law.
| Area of law | Laws | Jurisdictions |
|---|---|---|
|
Cybersecurity law
Build software securely, handle reported flaws, and report incidents on a deadline. |
90 | 66 |
|
Communications law
Get consent before marketing, calling, recording or storing data on a device, and honor an opt-out.
|
68 | 46 |
|
Product and AI liability law
Answer in damages when defective software or an AI system causes harm.
|
23 | 22 |
|
Privacy law
Have a legal basis for personal data, honor people's rights over it, and report a breach. |
3 | 3 |
|
AI law
Tell people when they are dealing with an AI system or its output, and control the uses the law calls high-risk.
|
1 | 1 |
Counterparties that usually come with it
- a telephony or video-meeting platform
- a transcription vendor
A component that cannot run as documented without one of these names
it in its ACTIVITIES.md under talks_to, with
required: true. That party's jurisdiction then joins the
run of every product that uses the component, and the finding says
why it is there. A default the deployer can change is asked about,
never added. Talking to a party never makes a product that party.
In a declaration
A library or framework that makes this possible enables
it; an application whose shipped code does it performs it.
For a library
For an application
History
In the registry since version 1.0, . It replaces records_conversations, retired in version 1.0 together with Records text chat.
In the glossary: Records calls.
The activity registry is LexLint's open list; this page's text is licensed under Creative Commons Attribution 4.0.