Voiceprint & biometric data policy
BIPA/GDPR framing for the opt-in voiceprint feature.
Voiceprint recognition (see What is voiceprint recognition?) is the one feature in Meetbook that processes biometric data — a voice signature used to recognize the same speaker across meetings. It's handled under stricter rules than ordinary meeting content.
Off by default, opt-in only
Every workspace starts with voiceprint recognition disabled. It has to be turned on deliberately by a workspace Admin — see Turning voiceprint recognition on or off — it's never silently active.
Why this matters legally
Biometric data (including voiceprints) is regulated more strictly than most personal data in a number of jurisdictions — Illinois' BIPA and the EU's GDPR both treat it as a special category requiring explicit, informed consent, not just a general privacy-policy acceptance. If your workspace enables this feature, especially for recurring external participants (clients, candidates) who never explicitly agreed to be voice-fingerprinted, you're responsible for meeting whatever consent requirements apply in your jurisdiction.
Deleting stored voiceprints
Disabling the feature stops new matching but doesn't automatically erase voiceprints already stored — contact support to request deletion of stored voiceprint data specifically, separate from deleting ordinary meeting recordings (see Deleting a meeting and its data).
This data is not used for anything else
Voiceprints are stored and used solely to power cross-meeting speaker matching — they aren't used for any other purpose, and are separate from the "no AI training" commitment covered in Is my data used to train AI models?.