Provision record
Threads · Threads Privacy Policy · View original document ↗

User like or reply shared to third-party service

Common · 280 of 343 platforms
Stay ahead of the changes
Track Threads and hear on the next check after its terms change. We check daily where we can, and show you where we can't.
Share 𝕏 Share in Share 🔒 PDF
ⓘ

This analysis describes what Threads'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

Indeed

By using our Sites, you acknowledge Indeed's use of such third-parties, including, but not limited to, for the purpose of collecting, processing, analyzing, and recording your activity on, interaction with, and communications with, or through our Sites.

Harvey AI

These third parties have limited access to your information, may use your information only to perform agreed tasks, and are prohibited from disclosing or using your information for other purposes.

Kling AI

We may share your personal data with a third party for purposes other than processing on our behalf. We will obtain your consent to such disclosure as required by applicable laws.

See all platforms with this clause type →
▸ View Original Clause Language DOCUMENT RECORD
"
when you like or reply to a post from a Third Party Service, you are asking us to share a copy of that like or reply to the Third Party Service so that it can be stored, processed, and delivered

Excerpt from Threads's Privacy Policy

Provision details

Document information
Document
Threads Privacy Policy
Entity
Threads
Date stated by the document
June 3, 2025
As printed in Threads’s text (version CA-V-007374), not a ConductAtlas date.
Tracking information
First captured by ConductAtlas
April 19, 2026
Text quoted from version
CA-V-007291, captured Oct. 2, 2026
Record ID
CA-P-033028
Document ID
CA-D-000248
Evidence Provenance
Source URL
Wayback Machine
Archived bytes SHA-256 (version CA-V-007291)
316c3e9485819b3c3a6eac9e183437cd99cbd252ae46aaa87d0fed183f68b541
Analysis generated
July 9, 2026 14:43 UTC
Methodology
Evidence
✓ Excerpt found in version CA-V-007291, captured Oct. 2, 2026 (checked Oct. 5, 2026)
Not the current version. The document's current version is CA-V-007374, captured Oct. 7, 2026; this clause has not been re-checked against it.
Citation Record
Entity: Threads
Document: Threads Privacy Policy
Record ID: CA-P-033028
Version: CA-V-007291
Captured: 2026-10-02 00:45:04 UTC
SHA-256: 316c3e9485819b3c…
URL: https://conductatlas.com/platform/threads/threads-privacy-policy/provision/CA-P-033028/user-like-or-reply-shared-to-third-party-service/
Accessed: Oct. 17, 2026
Permanent archival reference. Stable identifier suitable for legal filings, compliance documentation, and research citation.
Classification
Categories

Other risks in this policy

Related Analysis

Get the weekly coverage letter

Companies change their terms without announcing it. We capture governance documents, compare each new version with the last, and publish what changed, with the source text behind it. One email a week on what we found and what we could not reach.

Frequently Asked Questions

What does Threads's User like or reply shared to third-party service clause do?

The clause states: “when you like or reply to a post from a Third Party Service, you are asking us to share a copy of that like or reply to the Third Party Service so that it can be stored, processed, and delivered”

How many platforms have this type of clause?

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

Is ConductAtlas affiliated with Threads?

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