privacy

Loom and Cloud Screen Recorders: Who Can See Your Recordings

Screen recording tools upload video to third-party servers by default, capturing sensitive content. Here's what to know before you hit record.

You record a quick walkthrough to send a colleague, paste in the Loom link, and move on. What you may not have considered: that recording is now on Loom’s servers, accessible via a link, potentially indexed by Loom’s internal systems, and subject to the terms of an agreement you accepted during signup and which has likely been updated several times since.

Screen recording tools — Loom, Screencastify, CloudApp (now Zight), Vidyard, and their many competitors — have become a category of ambient workplace and personal communication infrastructure. They are quick to use, the recordings are easy to share, and the cloud upload is seamless. The cloud upload is also always happening, always storing, and the terms governing that storage deserve more attention than most users give them.


What Cloud Screen Recorders Actually Capture

The obvious content: what is on your screen while recording. The less obvious content is substantial.

Full-frame screen content. When you record your screen, every pixel visible during the recording is captured. That includes: other tabs open in the browser (visible if you switch during recording), notification pop-ups that appear while you record, accidentally visible emails or messages, documents open in the background, file names in directory bars, and any personally identifiable information on screen at the moment of capture.

Audio. Most screen recording sessions include microphone audio or system audio or both. Audio captures background conversations, household sounds, and any verbal information spoken during recording — including information about topics unrelated to the recording’s intended subject.

Webcam video. Many screen recorders include an optional picture-in-picture webcam overlay. When enabled, your face is recorded and uploaded alongside the screen content. Face data in a cloud video is biometric data in practical terms, even if no active facial recognition analysis is run on it.

Metadata. The recording’s timestamp, duration, operating system, device type, screen resolution, and the URL of any web page visible during recording are all captured and stored as metadata alongside the video.

Transcript. Loom and several competitors offer automatic transcription of recordings. This means a text version of everything said during the recording is generated, stored, and made searchable — a machine-readable, indexable version of content you may have considered a one-time video.


Loom’s Policies and Its Acquisition

Loom was acquired by Atlassian in 2023 for approximately 975 million dollars. The acquisition integrated Loom’s recording capabilities with Atlassian’s Confluence and Jira product suite.

Post-acquisition, Loom operates under Atlassian’s privacy policy framework. Atlassian’s privacy policy is a comprehensive document that covers the collection of user content, usage data, and the conditions under which data is shared with third parties. Atlassian is a publicly traded company with enterprise customers worldwide, and its privacy practices are subject to enterprise security review processes — which is a different privacy model than an independent startup, in both directions.

The relevant question for personal and small-team use of Loom is: what does Atlassian’s consolidated infrastructure and data model mean for recordings made before the acquisition, and what data flows exist between Loom recordings and Atlassian’s broader product suite?

Atlassian has confirmed that Loom data may be used to improve Atlassian AI features, including Atlassian Intelligence. The specific terms governing what “improve” means in practice — whether recordings are processed by model training pipelines, what anonymization applies, and what the retention schedule looks like — are detailed in Atlassian’s terms of service rather than surfaced during Loom’s product flow.


The Transcript Problem

Automatic transcription converts your audio content into structured, searchable text. This makes recordings discoverable in ways that raw video is not.

A Loom recording you send to a colleague about a project update contains audio that, once transcribed, can be searched across your workspace. If the recording mentioned a client name, a salary figure, a business strategy, or a health issue in passing, that mention is now indexed.

Transcripts also create legal and discovery exposure that video alone does not. A written transcript of a recorded conversation is treated differently by courts, compliance programs, and regulatory bodies than a video — it is more directly usable as documentary evidence and more clearly readable as a record.

Many users who use screen recording for workplace communication are operating in environments with compliance obligations — financial services, healthcare, legal, government contracting — where the data handling requirements for written communications apply to transcripts in ways they do not apply (or apply differently) to informal video messages.

If you are using a cloud screen recorder in any of these contexts without knowing your organization’s specific guidance on it, the transcript feature in particular warrants verification.


Cloud screen recorders generate shareable links. The default access model for these links is more permissive than most users assume.

Loom links default to “anyone with the link can view.” This is appropriate for quick team communication and is the behavior most users want. It also means: anyone who receives the link can share it further, there is no expiration by default, and any system that processes the URL (email clients, Slack previews, corporate URL scanners) has accessed the recording.

Corporate URL scanners. Enterprise email systems routinely fetch URLs to generate previews and scan for malicious content. A Loom link sent over corporate email may be accessed by security infrastructure at the recipient’s organization — infrastructure that logs what URLs were fetched and potentially caches content.

Archival systems. Some organizations use email or Slack archiving systems that capture shared URLs and their associated content for compliance retention. A recording you thought was a quick team update may be retained by the recipient organization’s archival infrastructure indefinitely.

Search engine indexing. Loom recordings with public-facing settings can be indexed by search engines. A recording set to “public” on Loom and linked in a public Slack community, blog post, or social media message may appear in search results.

Reviewing access settings on existing recordings — and changing defaults for new ones — is an accessible privacy improvement for most users.


Sensitive Content That Appears in Recordings

The most common privacy risk in screen recording is not deliberate disclosure of sensitive information — it is incidental capture of content you did not intend to include.

Common examples:

Notification previews. A message preview appears in the top right corner during a recording. The message is from someone who did not consent to being recorded, about a topic unrelated to the recording’s subject.

Browser tab contents. You switch to a browser tab to show a web resource and a previous tab is briefly visible — one containing personal email, financial information, or medical records.

File path metadata. The path in a file dialog or address bar shows your file organization, which can reveal personal information — document names, project names, or directory structures that carry meaning.

Calendar widgets. A calendar preview visible in a corner of the screen shows upcoming appointments, their titles, and who is invited.

Password manager autofill. A password manager’s autofill animation triggers during a recording, revealing the domains of accounts you hold.

None of these require carelessness — they are the natural background of a typical computing environment. Capturing all of it in a cloud-uploaded video and sending a link means all of it travels.


What You Can Control

Review recordings before sending. Watch the full recording before sharing. Check for incidental captures visible in the frame. Many screen recording tools allow cropping the start and end of a recording — use this to trim captures of your setup process.

Use a dedicated browser profile for recording. Record from a browser profile with no personal bookmarks, no notification extensions, and no logged-in accounts beyond what the recording requires. This eliminates most incidental content capture.

Disable notifications during recording. On macOS: Focus mode before recording. On Windows: Notification pause in action center. On both platforms: closing communication apps before recording prevents notification-related captures.

Set explicit expiration on shared links. Some screen recording tools allow link expiration — the recording becomes inaccessible after a specified time. This is worth using for any recording with time-sensitive content.

Store sensitive recordings privately. For recordings that contain sensitive information and need to be preserved — training walkthroughs, client-facing demos, performance reviews — storing the recording file locally or in a private storage service rather than leaving it on the screen recorder’s cloud gives you control over who can access it and when access ends.

daftei supports video file storage alongside other file types. Video files stored in daftei are encrypted in transit and at rest, accessible only through your account, and not processed for content analysis or AI training. For recordings that need to be preserved but should not live on a third-party screen recorder platform indefinitely, uploading the exported file to a private storage service provides an alternative.


The Recording You Sent Six Months Ago

Most users have sent dozens of screen recordings through cloud tools without reviewing the access settings on those specific recordings. Those recordings are still there, still accessible via the same links, still subject to the same retention policies.

Loom’s interface shows all recordings in your account. A periodic review — checking what still exists, what the access settings are, and whether recordings containing sensitive content should be deleted or access-restricted — is a routine practice worth adding to a personal data hygiene schedule.

Screen recording tools are useful. Cloud storage of recordings adds friction-free sharing. Understanding what that storage means — and what controls you actually have — makes the tool safer to use in the ways you actually need it.

Your memories deserve better than an ad platform.

Try daftei free →
← All posts