Is Loom – Screen Recorder & Screen Capture safe?

Low risk

Loom is low risk.

Loom sends analytics events including your Segment identity and loom.com cookies to api.segment.io.

When you use the extension, it reads your loom.com anonymous ID cookie and transmits it alongside event names and context (app version, extension client type) to Segment at api.segment.io in batches every two seconds. The extension also accepts programmatic commands from the loom.com website to start recordings, and reads additional loom.com cookies for UI state.

Loomv5.5.217Extension ID liecbddmkiiihnedobmlmillhodjkdmbChrome Web Store
22Risk
Who publishes it

Atlassian - 4 other listings from the same operator, none carrying a finding

Publisher
Loom
Declared legal entity
Atlassian
Registered address
350 Bush Street, Floor 13, San Francisco, CA 94104, US
Registered contact
Vinay Hiremath

Same operator - 4 listings

Published under a different store account, but sharing the registered address, contact or declared legal entity this one gave the store.

Shared hosts - 4 hostnames

Hostnames hardcoded in this extension that few other listings call. That can mean one operator behind both, and it can equally mean a small shared vendor, so it is context rather than a conclusion. Hosts that many listings call are left out: they are services, not connections.

app.outreach.io
Also called by 2 other listings, including CallCloud - Dialer for Salesloft, Outreach, HubSpot & Salesforge
loomlocal.com
Also called by 6 other listings, including Draft by Slite, FYI
stage.loom.com
Also called by 6 other listings, including Draft by Slite, FYI
support.loom.com
Also called by 6 other listings, including Draft by Slite, FYI
AI-assisted analysis.

Loom findings

Extension sends operational metrics to Datadog via Loom GraphQL proxy

LowunwantedCWE-200Dynamic sandbox

Loom's service worker posts batched performance/error counters to www.loom.com/metrics/graphql every 60s (mutation EmitDatadogEvents), tagged with OS, Chrome and extension versions.

What actually happens

You did this

The service worker records an operational event (e.g. a recording error or credential fetch failure).

Events are queued in memory and flushed as a batch every 60 seconds.

The extension did this

A POST request is sent to www.loom.com/metrics/graphql carrying the queued counters.

Each counter is tagged with OS, Chrome version, extension version, and environment before transmission.

The code that does this

GraphQL mutation call in the service worker

Readable version

Effective metric names (G6 constants, sw.js:308280)

js/sw.js
const METRIC_PREFIX = "v2.developer_context";const G6 = {  COLLECTION_STARTED:            `${METRIC_PREFIX}.collection.started`,  COLLECTION_FINISHED:           `${METRIC_PREFIX}.collection.finished`,  COLLECTION_INCOMPLETE_DETECTED:`${METRIC_PREFIX}.collection.incomplete_detected`,  SERVICE_WORKER_RESTART_DETECTED:`${METRIC_PREFIX}.sw_restart_detected`,  TIME_TO_START_CONSOLE_CAPTURE: `${METRIC_PREFIX}.time_to_start_console_capture`,  ERROR: {    BROWSER_INFO_ERROR:             `${METRIC_PREFIX}.error.browser_info_error`,    CREDENTIALS_FETCH_FAILED:       `${METRIC_PREFIX}.error.credentials_fetch_failed`,    CREDENTIALS_MISSING:            `${METRIC_PREFIX}.error.credentials_missing`,    UPLOAD_FAILED:                  `${METRIC_PREFIX}.error.upload_failed`,    NETWORK_CAPTURE_START_ERROR:    `${METRIC_PREFIX}.error.network_capture_start_error`,    CONSOLE_CAPTURE_START_ERROR:    `${METRIC_PREFIX}.error.console_capture_start_error`,    SYSTEM_INFO_ERROR:              `${METRIC_PREFIX}.error.system_info_error`,    // ... additional error codes  }};

Tags appended to every Datadog metric

  • Operating system
    mac

    The OS platform reported by Chrome's system API, sent on every metric flush.

  • Chrome version
    124

    The major Chrome version extracted from the user-agent string.

  • Extension version
    5.5.193

    The installed version of the Loom extension, from the manifest.

  • Manifest version
    3

    Chrome extension manifest version (always 3 for MV3).

  • Environment
    production

    Deployment environment label (e.g. production, staging).

Where the metrics are sent

    • www.loom.com

    Vendor's own backend. Acts as a GraphQL proxy to forward batched Datadog metrics from the extension. Loom is owned by Atlassian.

    • browser-intake-datadoghq.com

    Datadog's intake endpoint (reached indirectly through the Loom proxy). Datadog is a US-based observability SaaS provider.

Loom reads loom.com cookies to fingerprint your install

LowunwantedCWE-200Dynamic sandbox

Loom's service worker pulls two cookies from loom.com: ajs_anonymous_id (Segment ID) and a UI flag.

What actually happens

You did this

The Loom service worker initialises its analytics path (during startup, when the popup opens, or before any tracked action).

The extension did this

It pulls the loom.com 'ajs_anonymous_id' cookie out of your browser cookie jar and reuses the value to identify you to Segment for the rest of the session.

It also queries the 'workspace-tooltip-limit-dismissed' cookie to decide whether to show certain in-extension tooltips, and (in a sibling code path) writes the cookie back with a 2-year expiry to keep the identifier alive.

Cookies the extension reaches into the loom.com cookie jar for

  • ajs_anonymous_id
    558eef83-b27a-45cf-a6ba-ec847df9aa6e

    Your Segment anonymous ID from loom.com, kept for years. Reused as 'anonymousId' on every analytics POST.

  • workspace-tooltip-limit-dismissed
    true

    Tracks whether you have already dismissed Loom's workspace-tooltip nudge, so the extension can decide whether to show it again.

Cookie value observed in the browser jar matches the value POSTed to Segment (verified live).

  1. +0-2s (within one flushInterval)

    You did

    Page-cookie hook records ajs_anonymous_id read from loom.com.

    Dynamic analysis session hook recorded ajs_anonymous_id read from loom.com: value '558eef83-b27a-45cf-a6ba-ec847df9aa6e'

    The extension did

    Same value appears as 'anonymousId' in every event of the next Segment batch.

    Observed during dynamic analysis: POST api.segment.io/v1/batch, anonymousId=558eef83-b27a-45cf-a6ba-ec847df9aa6e

The code that does this

The cookie reads, exactly as shipped.

Readable version

Resolve the loom.com anonymous ID

const COOKIE_NAME = 'ajs_anonymous_id';function getLoomAnonymousId() {  return new Promise(resolve => {    chrome.cookies.getAll({ domain: 'loom.com', name: COOKIE_NAME }, cookies => {      // Drop cookies on staging hosts (stage.loom.com); keep prod.      cookies = cookies.filter(c => !c.domain.includes('stage'));      if (cookies.length) {        // Cookie value is JSON-quoted (e.g. "abc-123"); strip quotes.        resolve(decodeURIComponent(cookies[0].value).replace(/"/g, ''));      } else {        resolve(null);      }    });  });}

Refresh the cookie with a 2-year expiry

function persistLoomAnonymousId(value) {  chrome.cookies.set({    domain: 'loom.com',    url:    'https://www.loom.com',    name:   'ajs_anonymous_id',    httpOnly: false,    secure:   true,    expirationDate: new Date(      new Date().setFullYear(new Date().getFullYear() + 2)    ).getTime(),    value: encodeURIComponent(`"${value}"`),  });}

UI dismissal cookie

// Read whether the user previously dismissed the workspace-tooltip nudge.const TOOLTIP_LIMIT_KEY = 'workspace-tooltip-limit-dismissed';chrome.cookies.get(  { url: 'https://www.loom.com', name: TOOLTIP_LIMIT_KEY },  cookie => { dismissed = cookie?.value === 'true'; });

Where the cookie value ends up

    • loom.com

    Source of the cookies. Originally set by Segment's analytics.js on the loom.com site; the extension is a second consumer of that same identifier.

    • api.segment.io

    Receives the cookie value as the 'anonymousId' on every analytics batch the extension POSTs (see claim 5871 for full payload).

Check if you're affected

Run on any loom.com tab. Reads the document.cookie 'ajs_anonymous_id' value and prints it, then asks you to compare it against the anonymousId field your network capture (or the loom-segment-tap.js artifact) shows reaching api.segment.io. Same value = the extension is using your loom.com identity to tag analytics.

Requires
  • Loom installed
  • A loom.com tab open
loom-cookie-link.js · js
// loom-cookie-link.js — run on any loom.com tab DevTools consoleconst m = document.cookie.match(/(?:^|;\s*)ajs_anonymous_id=([^;]+)/);if (!m) {  console.log('[LOOM-COOKIE] ajs_anonymous_id not present. Visit loom.com first.');} else {  const raw = decodeURIComponent(m[1]).replace(/"/g, '');  console.log('[LOOM-COOKIE] loom.com ajs_anonymous_id =', raw);  console.log('[LOOM-COOKIE] Compare against the anonymousId in any');  console.log('              POST https://api.segment.io/v1/batch from the');  console.log('              Loom service worker. They should match.');}
How to run it
  1. 1Open loom.com, DevTools Console.
  2. 2Paste snippet, note cookie value.
  3. 3Open Loom's service-worker DevTools, run loom-segment-tap.js.
  4. 4Trigger an event, confirm anonymousId in the Segment batch equals the cookie value.

Loom relays your loom.com identity to Segment analytics

LowunwantedCWE-200Dynamic sandbox

Loom's service worker reads the ajs_anonymous_id cookie from loom.com and sends it to Segment (api.segment.io) with every analytics event, letting Segment tie extension use to your loom.com identity even when signed out.

What actually happens

You did this

You click Loom in the toolbar, start a recording, or even just have the extension installed at startup.

The extension did this

The extension reads the loom.com 'ajs_anonymous_id' cookie from your browser and sends a Segment analytics event tagged with that ID and what you did.

Events ('Camera bubble was rendered', 'Extension Activated', etc.) are batched and POSTed to api.segment.io/v1/batch. Even visitors who never log in get tagged because the cookie is set on first loom.com page-view.

Captured request

POSThttps://api.segment.io/v1/batch

200 OK with {"success":true}, Segment confirms ingestion and forwards the events to every destination Loom has wired into the workspace (warehouses, marketing tools, etc.).

Headers
User-Agent
analytics-node-next/latest
Content-Type
application/json
Authorization
Basic <base64(writeKey:)>
Body
{  "batch": [    {      "type": "track",      "event": "Extension Activated",      "anonymousId": "558eef83-b27a-45cf-a6ba-ec847df9aa6e",      "properties": {        "source": "toolbar",        "extension_version": "5.5.166"      },      "context": {        "app_version": "5.5.166",        "client": "browser_extension",        "manifest": 3,        "library": {          "name": "analytics-node-next",          "version": "latest"        }      },      "messageId": "node-next-1744640329122-7c1f",      "timestamp": "2026-04-14T14:12:09.122Z"    },    {      "type": "track",      "event": "Camera bubble was rendered",      "anonymousId": "558eef83-b27a-45cf-a6ba-ec847df9aa6e",      "properties": {        "source": "recorder",        "variant": "default"      },      "context": {        "app_version": "5.5.166",        "client": "browser_extension",        "manifest": 3      },      "messageId": "node-next-1744640329214-1d2a",      "timestamp": "2026-04-14T14:12:09.214Z"    }  ],  "sentAt": "2026-04-14T14:12:09.300Z"}

What every Segment batch carries

  • Your loom.com anonymous ID
    558eef83-b27a-45cf-a6ba-ec847df9aa6e

    The ID loom.com assigns on first visit, in a cookie. Lets Segment join extension activity to your loom.com sessions, even before login.

  • Your Loom user ID (when signed in)
    auth0|6122a1f0e8b3c40070b4e7e2

    Once you sign in, every event also carries your account ID, directly identifies the human behind the events.

  • Event name
    Camera bubble was rendered

    What you did inside the extension. Reveals which Loom features you use and how often.

  • Client tag
    browser_extension

    Marks the event as coming from the browser extension (rather than the loom.com website or mobile app).

  • Extension version
    5.5.166

    Which version of Loom you have installed.

  • Timestamp
    2026-04-14T14:12:09.122Z

    When the event happened, to the millisecond.

The code that does this

The wiring that links your loom.com cookie to every Segment event.

Readable version

Singleton Segment client

// Lazily constructs one Segment analytics client for the whole service worker.let segmentClient = null;function getSegment() {  if (!segmentClient) {    segmentClient = analyticsClient({      env: ENV_TAG,                  // 'PROD' | 'STAGING' | ...      version: EXT_VERSION,          // '5.5.166'      product: 'loom',      errorHandler: () => {},      sendEventHook:  () => {},    });  }  return segmentClient;}

Pull the loom.com cookie and use it as the analytics anonymous ID

const COOKIE_NAME = 'ajs_anonymous_id';function getLoomAnonymousId() {  return new Promise(resolve => {    chrome.cookies.getAll({ domain: 'loom.com', name: COOKIE_NAME }, cookies => {      // Drop staging-host cookies, keep production loom.com.      cookies = cookies.filter(c => !c.domain.includes('stage'));      if (cookies.length) {        resolve(decodeURIComponent(cookies[0].value).replace(/"/g, ''));      } else {        resolve(null);      }    });  });}// And every event carries it:segmentClient.track({  userId: loggedInUserId,                          // present once signed in  anonymousId: loggedInUserId ? undefined : loomAnonId,  event: eventName,  properties: eventProps,  context: { app_version: '5.5.166', client: 'browser_extension', manifest: 3 },});

Where the data lands

    • api.segment.io

    Segment (Twilio) analytics ingestion. Events fan out to Loom's connected destinations, typically a data warehouse plus analytics tools (Mixpanel, Amplitude class).

    • loom.com

    Source of the ajs_anonymous_id cookie that ties extension activity to your loom.com sessions.

Reproduce it yourself

Run inside the Loom service-worker DevTools console. Wraps fetch() so any POST to api.segment.io/v1/batch is logged with its full body; you can see the anonymousId, event names, and context object Loom is shipping in real time.

Requires
  • Chrome with Developer mode enabled
  • Loom extension installed and enabled
loom-segment-tap.js · js
// loom-segment-tap.js — run in the Loom service-worker DevTools console// 1. Open chrome://extensions, enable Developer mode// 2. Find 'Loom – Screen Recorder' and click 'service worker'// 3. Paste this script into the console// 4. Use Loom normally; every Segment batch will be pretty-printed below(() => {  const origFetch = self.fetch.bind(self);  self.fetch = async (input, init = {}) => {    const url = typeof input === 'string' ? input : input.url;    if (url && url.includes('api.segment.io')) {      try {        const body = init.body || (typeof input !== 'string' ? await input.clone().text() : '');        const parsed = typeof body === 'string' ? JSON.parse(body) : body;        console.groupCollapsed('[LOOM→SEGMENT]', url, parsed.batch?.length ?? '?', 'events');        for (const ev of parsed.batch ?? []) {          console.log(ev.event, '\n  anonymousId =', ev.anonymousId, '\n  userId =', ev.userId, '\n  context.client =', ev.context?.client, '\n  properties =', ev.properties);        }        console.groupEnd();      } catch (e) { console.warn('[LOOM→SEGMENT] parse failed', e); }    }    return origFetch(input, init);  };  console.log('[LOOM→SEGMENT] tap installed. Trigger a recording or open the bubble.');})();
How to run it
  1. 1Visit chrome://extensions, enable Developer mode.
  2. 2Open 'Loom' service worker console.
  3. 3Paste this script.
  4. 4Open the popup or record.
  5. 5Each Segment batch logs with anonymousId and event name.

Loom version history

  1. 5.5.167

    Mar 4, 2026

  2. +27 more

  3. 5.5.215

    Nov 2, 2026

  4. 5.5.216

    Nov 10, 2026

  5. 5.5.217

    Nov 16, 2026

Where Loom sends data

  • cdn.loom.com/assets/camfort/…66 calls

    From its background script · only this extension

  • www.loom.com/v1/users/…20 calls

    From its background script · only this extension

  • www.loom.com/js/…10 calls

    From a script it injects into websites · only this extension

  • www.loom.com/api/util/…8 calls

    From its background script · only this extension

  • as.atlassian.com/api/v1/…6 calls

    From its background script · only this extension

  • id.atlassian.com/js/…5 calls

    From a script it injects into websites · only this extension

  • http-intake.logs.datadoghq.com/api/v2/…4 calls

    From its background script · 3 other extensions

  • www.loom.com/api/users2 calls

    From its background script · only this extension

  • www.loom.com/graphql2 calls

    From its background script · only this extension

  • api.segment.io

    Found in its code · 23 other extensions

Chrome Web Store listing

Versions
5.5.217 latest of 31 seen since March 4, 2026
Store rating
4.6 from 10,223 ratings
Last updated
May 28, 2026
Size
32.04 MiB
Privacy policy
www.loom.com
Updated November 20, 2026