Coinbase · Coinbase User Agreement · View original document ↗

TCPA Text Message Consent and User Indemnification

Medium severity Unique · 0 of 352 platforms
Get alerted the next time Coinbase changes these terms. Get same-day alerts →
Share 𝕏 Share in Share 🔒 PDF
Recent governance activity Coinbase recorded 2 documented changes in the last 30 days.
Get same-day alerts →
Monitor governance changes for Coinbase Monitor emails you the same day this changes. The archive stays free.
Get same-day alerts →

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.

Document Record

What it is

Users who opt in to text messages consent to recurring automated SMS, MMS, and successor technology messages from Coinbase. Users also indemnify Coinbase against all TCPA and state law equivalent claims, including claims arising from the user providing a telephone number they do not own.

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

ConductAtlas Analysis

Why it matters (compliance & governance perspective)

The indemnification provision shifts TCPA litigation risk to the user for claims arising from the user providing a telephone number belonging to another person, which is a common scenario in TCPA class action litigation. This provision may affect Coinbase's ability to be held liable in certain third-party TCPA claims and transfers that exposure to the user.

Recent Activity

This document changed recently

High Jul 23, 2026

The updated terms establish procedures for handling protocol upgrades and define Coinbase's role in migrating customer assets to new versions. Under the revised language, by maintaining a Coinbase account, customers are deemed to have instructed Coinbase to conduct Coinbase Supported Migrations on their behalf at times and in manner Coinbase solely determines appropriate. The agreement further states that Coinbase shall not be liable or responsible for any loss resulting from inability to transfer Digital Assets during a migration or from the Asset Transformation itself. This expands Coinbase's authority to act without advance notice while eliminating liability for migration-related losses.

View change record →
Medium Jul 7, 2026

The updated terms now explicitly disclose Coinbase's fee structure for California residents, establishing a $10 maximum fee for transactions under $200 and a 6% maximum for larger transactions, though actual fees displayed at checkout may be lower based on payment method, order size, market conditions, and location. The revised agreement also clarifies that virtual currency transactions may be irreversible and provides links to procedures for reporting unauthorized transactions, updating contact information, and accessing transaction receipts. Coinbase commits to providing California residents at least 14 days' prior notice of material changes to fees or terms affecting their accounts.

View change record →
Medium May 2, 2026

The updated terms eliminate language that previously allowed Coinbase to restrict your withdrawals if you designated USDC as Secured USDC and to comply with third-party secured party instructions without your consent. Under the revised agreement, Coinbase will not transfer, loan, or otherwise handle your Supported Digital Assets except as required by law or as you instruct. This means the One Card Secured USDC mechanism is no longer integrated into the core asset protection clause, and users no longer face withdrawal restrictions or loss of instruction authority tied to that designation. If you currently hold Secured USDC under a separate One Card cardholder agreement, that agreement remains in effect but is no longer cross-referenced in the main User Agreement's asset protection section.

View change record →

If You Do Nothing

Users who have opted in to text messages and do not opt out will continue to receive recurring automated messages from Coinbase as stated in Section 6.12

Cross-platform context

See how other platforms handle TCPA Text Message Consent and User Indemnification and similar clauses.

Compare across platforms →

Monitoring

Coinbase has changed this document before.

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

Get Monitor Or create a free account →
▸ View Original Clause Language DOCUMENT RECORD
"
By voluntarily providing your telephone number(s) and opting in to receiving text messages from Coinbase, you expressly agree to receive recurring automated text messages (such as SMS, MMS, or successor protocols or technologies) from Coinbase and understand that consent is not required to make any purchase. Message and data rates may apply and the frequency of messages varies. You agree to indemnify, defend, and hold harmless Coinbase for any claims, losses, liability, costs and expenses (including reasonable attorneys' fees) arising from any privacy, tort or other claims, including claims under the Federal Telephone Consumer Protection Act or any state law equivalents, including claims relating to your voluntary provision of a telephone number that is not owned by you.

Excerpt from Coinbase's User Agreement

ConductAtlas Analysis

Institutional analysis (regulatory & governance intelligence)

1. REGULATORY LANDSCAPE: The Telephone Consumer Protection Act prohibits automated calls and texts to numbers without prior express consent from the called party. The FCC enforces the TCPA, and private plaintiffs may bring statutory damages claims of $500 to $1,500 per violation. State law equivalents may impose additional requirements. The indemnification provision attempts to shift TCPA litigation exposure to the user in the specific scenario where a user provides a number they do not own. 2. GOVERNANCE EXPOSURE: Medium. The user indemnification for TCPA claims is an unusual provision in a consumer financial services agreement and may face enforceability challenges depending on jurisdiction and the specific circumstances of a claim, particularly where the user is also the plaintiff. The provision does not affect Coinbase's direct TCPA obligations with respect to the user's own claims. 3. JURISDICTION FLAGS: Several states have enacted their own automated calling and texting statutes with varying requirements. The indemnification provision is broadest in its potential application in jurisdictions where TCPA class actions are common, including California, New York, Illinois, and Florida. 4. CONTRACT AND VENDOR IMPLICATIONS: The note that opt-in consent for text messages is not shared with third parties except telecommunication technology providers is a meaningful limitation on the text consent data use. 5. COMPLIANCE CONSIDERATIONS: Legal teams should evaluate whether the user indemnification provision for TCPA claims is enforceable in the context of a consumer financial services agreement, and whether it creates any tension with applicable consumer protection law in states with robust TCPA enforcement histories.

Full institutional analysis

Regulatory citations, enforcement risk, and due diligence action items.

Get same-day alerts when this changes → Get Analyst

Monitor: same-day alerts on the platforms you choose. Analyst: full institutional analysis.

Applicable agencies

  • FTC
    The FTC has jurisdiction over unfair or deceptive consumer practices; the FCC is the primary TCPA enforcement authority but is not listed among the available agency options
    File a complaint →

Applicable regulations

ePrivacy Directive
European Union

Provision details

Document information
Document
Coinbase User Agreement
Entity
Coinbase
Document last updated
May 5, 2026
Tracking information
First tracked
July 12, 2026
Last verified
July 12, 2026
Record ID
CA-P-00047008
Document ID
CA-D-00047
Evidence Provenance
Source URL
Wayback Machine
Content hash (SHA-256)
a9f500133b028586c3ef699c5845c93a81e3d2523e0ad6b93c23e63feb318580
Analysis generated
July 12, 2026 02:00 UTC
Methodology
Evidence
✓ Snapshot stored   ✓ Hash verified
Citation Record
Entity: Coinbase
Document: Coinbase User Agreement
Record ID: CA-P-00047008
Captured: 2026-07-12 02:00:01 UTC
SHA-256: a9f500133b028586…
URL: https://conductatlas.com/platform/coinbase/coinbase-user-agreement/tcpa-text-message-consent-and-user-indemnification/
Accessed: July 23, 2026
Permanent archival reference. Stable identifier suitable for legal filings, compliance documentation, and research citation.
Classification
Severity
Medium
Categories

Other risks in this policy

Compliance Governance Intelligence

Need to monitor specific governance provisions?

Compliance includes provision-level monitoring, governance timelines, regulatory mapping, and audit-ready analysis.

Arbitration clauses AI governance Data rights Indemnification Retention policies
Get Compliance

Or start with Monitor →

Built from archived source documents, structured governance mappings, and historical version tracking.

Frequently Asked Questions

What does Coinbase's TCPA Text Message Consent and User Indemnification clause do?

The indemnification provision shifts TCPA litigation risk to the user for claims arising from the user providing a telephone number belonging to another person, which is a common scenario in TCPA class action litigation. This provision may affect Coinbase's ability to be held liable in certain third-party TCPA claims and transfers that exposure to the user.

Is ConductAtlas affiliated with Coinbase?

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