Provision record
Loom · Loom Terms of Service · View original document ↗

Customer settlement requires Atlassian written consent

Medium severity Explicitdocumentlanguage Common · 233 of 352 platforms
Get alerted the next time Loom changes these terms. Follow Loom →
Share 𝕏 Share in Share 🔒 PDF
Monitor governance changes for Loom Monitor emails you the same day this changes. The archive stays free.
Follow Loom →

Get the weekly research letter

Companies change their terms quietly. We read every version and catch what actually changed. One email a week on the changes that matter and what they mean. No account.

This analysis describes what Loom's agreement states, permits, or reserves. It does not constitute a legal determination about enforceability. Regulatory applicability and practical outcomes may vary by jurisdiction, enforcement context, and individual circumstances. Read our methodology

How other platforms handle this

Google Cloud Medium

Any settlement requiring the indemnified party to admit liability, pay money, or take (or refrain from taking) any action, will require the indemnified party's prior written consent, not to be unreasonably withheld...

Lyft Medium

You will not, without Lyft's prior written consent, agree to any settlement on behalf of any Indemnified Party which includes either the obligation to pay any monetary amounts, or any admissions of liability...

DeepL Medium

DeepL shall not settle or recognise claims of third parties without Customer's consent which shall not be unreasonably withheld or delayed.

See all platforms with this clause type →

Monitoring

Loom has changed this document before.

Receive same-day alerts, structured change summaries, and monitoring for up to 20 platforms.

Follow Loom → Or create a free account →
▸ View Original Clause Language DOCUMENT RECORD
"
Customer may not settle an Infringement Claim without Atlassian's prior written consent.

Excerpt from Loom's Terms of Service

Applicable regulations

FTC Act Section 5
United States Federal

Provision details

Document information
Document
Loom Terms of Service
Entity
Loom
Document last updated
May 5, 2026
Tracking information
First tracked
July 12, 2026
Last verified
July 12, 2026
Record ID
CA-P-071935
Document ID
CA-D-00564
Evidence Provenance
Source URL
Wayback Machine
Content hash (SHA-256)
f441c251830514f5a83e3398d892d775169e50249827f7ae34338762e14fe90c
Analysis generated
July 12, 2026 15:04 UTC
Methodology
Evidence
✓ Snapshot stored   ✓ Hash verified
Citation Record
Entity: Loom
Document: Loom Terms of Service
Record ID: CA-P-071935
Captured: 2026-07-12 15:04:00 UTC
SHA-256: f441c251830514f5…
URL: https://conductatlas.com/platform/loom/loom-terms-of-service/provision/CA-P-071935/customer-settlement-requires-atlassian-written-consent/
Accessed: July 25, 2026
Permanent archival reference. Stable identifier suitable for legal filings, compliance documentation, and research citation.
Classification
Severity
Medium
Categories

Other risks in this policy

Governance intelligence across arbitration, AI governance, data rights, indemnification, and retention

Provision-level monitoring, governance timelines, and regulatory mapping built from archived source documents and historical version tracking.

Frequently Asked Questions

What does Loom's Customer settlement requires Atlassian written consent clause do?

The clause states: “Customer may not settle an Infringement Claim without Atlassian's prior written consent.”

How many platforms have this type of clause?

ConductAtlas has identified this type of provision across 233 platforms. See the full comparison.

Is ConductAtlas affiliated with Loom?

No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Loom.