Activities / What code does
Processes voice recordings
processes_voice
Your app records, stores, or analyzes a person's spoken voice, whether a call, a voice memo, or a voice command.
- scope code
- in the registry since 1.0
- 672 laws in 183 jurisdictions name it
What triggers it
The lint's definition. It records, stores, transcribes or analyzes human voices, including call recordings and voice messages, with or without a model anywhere in the product.
This covers a call-recording feature, a voice-command assistant, and a voicemail transcription tool.
What does not
Text a user typed themselves does not count, even if your app later reads it aloud.
Often confused with Records calls and Processes biometric data.
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.
Counterparties that usually come with it
- a transcription or speech-recognition vendor
- a telephony provider
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, .
In the glossary: Processes voice recordings.
The activity registry is LexLint's open list; this page's text is licensed under Creative Commons Attribution 4.0.