Video conferencingLoom and the GDPR: agreement, role and data location.
Loom is a video conferencing tool. Most customers use it as a processor, it publishes its data processing agreement, and the data location depends on your account. Below: what to check and how to declare it.
Prefilled for you · Free to set up · No credit card
In short
- Category
- Video conferencing
- Usual role
- Usually a processor
- Data location
- Set per account or project
- Agreement
- Published by the vendor
What does Loom do with personal data?
Conduct remote meetings and customer or team calls. That is how Privacyboard describes a typical use of Loom, as a starting point you can edit.
The data usually involved: participant names, email addresses, meeting metadata, audio, video and recordings when enabled.
Is Loom a processor or a controller?
Most customers use Loom as a processor: it handles personal data on their instructions, for the purposes they set. That is the common reading for video conferencing tools and it is what Privacyboard suggests.
As a processor, it needs a written agreement with you under Article 28, and you should know which subprocessors it uses. Confirm the role against your own agreement, because the way you use a tool can change it.
Where does Loom store personal data?
Loom does not have one fixed location for every customer. The location depends on the plan, the account and the services you enable.
How to find yours: Check your account settings, the address you log in to, or the provider’s data processing terms. Support can tell you if you cannot find it.
Even when the main location is in the EU, ask whether subprocessors or support access involve a transfer outside the EEA, and record it if so.
Which legal basis usually applies to Loom?
For the usual use of Loom, companies most often rely on legitimate interests (GDPR Article 6(1)). Remote meetings are a normal way to work with customers and colleagues.
The interest you would state: “Holding meetings and calls with customers, prospects and our team.” The GDPR asks you to say which interest you pursue (Article 13(1)(d)).
Recording a meeting needs its own justification and clear information to participants. The balancing test is yours to do: the interest must be real, the processing necessary for it, and people’s rights must not outweigh it.
This is a starting point, not legal advice: the basis belongs to your activity, and you confirm it in your register.
Sources: GDPR Article 6, lawfulness of processing, EDPB Guidelines 1/2024 on legitimate interest
Does Loom have a data processing agreement?
Checked on 5 November 2026. Vendors change their pages, so check the date.
Yes. Loom publishes the text of its data processing agreement on its own website. Article 28 of the GDPR requires a written contract with every processor, so this is the document to read and keep.
What we noted when we opened the page: Loom Data Processing Addendum (undated) hosted by Atlassian, supplementing the agreement between Customer and Loom. DPF is the primary mechanism for US transfers, with SCCs and UK Addendum as fallback; no hosting location stated.
A page that exists does not mean you are covered. Whether the agreement applies to you depends on your plan and on what you accepted, so record the decision yourself in your vendor list.
Read the Loom agreementHow to declare Loom
- 1
In your privacy policy
Name Loom as a recipient, say what it is used for (conduct remote meetings and customer or team calls) and mention any transfer outside the EEA. Articles 13 and 14 ask you to tell people who receives their data.
- 2
In your vendor list
Add Loom with its purpose, the data involved, its role, its region and a link to the agreement. Privacyboard prefills all of this, you confirm or correct it.
- 3
In your processing register
Link Loom to the activities that use it, so each record shows its recipients. Article 30 asks the register to list the categories of recipients.
What to check before relying on Loom
- Tell participants when a meeting is recorded, and why.
- Set a retention period for recordings and transcripts.
- Review who can record and share meetings.
- Record the region and any transfer outside the EEA.
Go online for free. Grow when you need to.
Free puts you online. Pro adds requests, domains and your team; Business, your brand only.
Free
$0 forever
No card, no time limit
For getting compliant and going online on your own.
Start for freeKey features:
- Privacy and cookie policies
- Vendor and processing registers
- Requests and breaches tracked
- Impact assessment screening
- Privacy center on privacyboard.io
- Cookie banner on 1 domain
- 1 person
No card needed
ProRecommended
$32 per month
Billed $384 a year Save $84
For taking requests, covering all your sites and working as a team.
Start with ProEverything in Free, plus:
- DPA for your clients
- PDF and Excel exports
- Email reminders
- Request form and replies
- Your own domain
- Banner on 3 domains, every choice logged
- Weekly site scan
- Complete DPIAs and TIAs
- AI assistant connector
- Up to 5 people, with roles
Cancel any time
Business
$109 per month
Billed $1,308 a year Save $240
For proving it to customers and auditors, under your brand only.
Start with BusinessEverything in Pro, plus:
- No Privacyboard mention
- Security section and vendor alerts
- Evidence pack in one click
- Banner on 10 domains, daily scan
- Up to 50 people
- Two-step verification required
- Activity log kept 3 years
Bank transfer on request
Questions, answered.
Is Loom GDPR compliant?
Privacyboard does not certify vendors. Compliance depends on how Loom is configured and used, on the agreement you have with it and on your own practices. What can be checked is documented here: it publishes a data processing agreement, the usual role and the data location. Read the agreement itself before relying on it.
Does Loom have a DPA?
Yes. Loom publishes the text of its data processing agreement on its own website. Article 28 of the GDPR requires a written contract with every processor, so this is the document to read and keep. You can read it at https://www.atlassian.com/legal/loom/dpa.
Is Loom a data processor?
Usually, yes. Most customers use Loom as a processor that acts on their instructions. Check your own agreement and how you use the tool, because the role can differ.
Which legal basis applies when I use Loom?
For the usual use of Loom, companies most often rely on legitimate interests (GDPR Article 6(1)). Remote meetings are a normal way to work with customers and colleagues. The interest you would state: “Holding meetings and calls with customers, prospects and our team.” The GDPR asks you to say which interest you pursue (Article 13(1)(d)).
Where does Loom store data?
Loom does not have one fixed location for every customer. The location depends on the plan, the account and the services you enable. How to find yours: Check your account settings, the address you log in to, or the provider’s data processing terms. Support can tell you if you cannot find it.
Do I need to mention Loom in my privacy policy?
Yes, if Loom handles personal data for you. The GDPR asks you to tell people who receives their data (Articles 13 and 14). Name the vendor or its category, say what it is used for and mention any transfer outside the EEA.
How do I add Loom to my vendor list?
In Privacyboard, pick Loom from the catalog. The purpose, the data, the suggested role and a link to its agreement are prefilled, and you confirm each one. Creating a workspace is free.
Similar tools
ZoomVideo conferencing
WherebyVideo conferencing
GoTo MeetingVideo conferencing
WebinarJamVideo conferencing
Compare all video conferencing tools
Privacyboard is not affiliated with Loom. Names and logos belong to their owners and are used only to identify the tool. This page summarises public documents as checked on 1 November 2026; it is guidance, not legal advice, and it does not certify any vendor.