Hi community,
We are currently assessing the privacy implications of using Loom within our internal workflows — particularly for cross-functional collaboration (e.g., onboarding, product updates, training) involving team members across different jurisdictions (EU, US, APAC) and Clients.
Given that:
Loom captures video, audio, and transcriptions, which can include images and voices of individuals.
In some EU member states and under certain data protection authorities’ interpretations, biometric identifiers such as facial images and voice recordings may qualify as special categories of data under Article 9(1) GDPR;
And considering transparency obligations (Articles 12–14 GDPR) and requirements for data protection by design;
We are seeking community insights on the following:
What would be the appropriate legal basis under Article 6 GDPR for the processing of video/audio/transcription data using Loom in a workplace setting (e.g., legitimate interest vs. consent vs. contractual necessity)?
In what circumstances could such processing be deemed to fall under Article 9 GDPR (special categories)? Have any EU data protection authorities (e.g., CNIL, AEPD, DSK) issued guidance confirming this interpretation?
If Article 9 applies, what would be a compliant exception under Article 9(2) — and would this effectively require explicit consent from data subjects (employees or collaborators)?
Are there recommended best practices for ensuring GDPR compliance when implementing asynchronous video tools like Loom (e.g., DPIA, internal policies, opt-in mechanisms)? How are companies managing Consent if that is the case?
Any experience, DPIA templates, or regulatory references would be greatly appreciated. Our goal is to maintain compliance while promoting transparent and efficient internal communication.
Thanks in advance for your insights!
Hi Julie! Please open a ticket here so that we can route this to our legal team: https://support.atlassian.com/loom/
I just did. I hope this is routed correctly; if not, you can just direct it to them. Thank you.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Side note: I am particularly interested in the consent management control aspect, in case someone has implemented a solution for that or an alternative approach.
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.