Independent public-evidence reviewNo personal financial advice
Candid LedgerPut the evidence on the record.

Operator & custody investigation

Coinbase

The Coinbase file separates hosted custody from Coinbase Wallet, then tests whether prominent protection and pricing language survives product, entity and jurisdiction boundaries.

Editorial assessment: Coinbase supplies unusually extensive corporate, contractual and regulatory records for a consumer platform, but those records also expose why the brand cannot be treated as one globally uniform service. The clearest conclusion is documentary: users must identify the product, entity and asset type before interpreting protection or fee claims.

Editorial statusPublished review
Evidence reviewPublic evidence reviewed
Scenario testingScenarios published
ComparisonCategory matrix eligible
Reviewed
Evidence confidencemedium
Suitable for

Who may find this file useful

Readers who value a comparatively deep public record and are prepared to verify the agreement, fee surface and protections for their exact country and transaction route.

Primary trade-off

The decision tension

Disclosure depth makes scrutiny possible, while the number of products, entities and conditional protections makes a one-line safety or cost verdict unreliable.

Research boundary

Documentary, not experiential

Public evidence has been reviewed; account, funding, trading, withdrawal and support scenarios are specified as controlled routes with defined inputs and records.

Evidence-backed strengths

What the record supports

  • Detailed public terms and listed-company filings
  • Clear distinction between hosted custody and the separate self-custody wallet
  • Advanced order-book surface with an independently described fee model

Material limitations

What must stay qualified

  • No universal regulatory or insurance statement is supportable
  • Simple transactions can combine a fee with spread
  • Hands-on funding, execution, withdrawal and support scenarios are specified as controlled routes
Operator evidence file4 recorded fields
E1

Exact product

Coinbase.com is custodial; Coinbase Wallet is a separate self-custody product.

documented
E2

Operating entity

The US individual agreement names Coinbase, Inc.; other markets require separate entity checks.

documented
E3

Custody and protection

Coinbase controls hosted-wallet keys. Crypto is not FDIC- or SIPC-insured; eligible cash may qualify for conditional pass-through cover.

documented
E4

Costs and exit

Simple trading may include fee and spread; Advanced uses maker/taker pricing. Route-specific scenarios are specified as controlled routes.

documented

Investigative analysis

Claims, records and the gaps between them.

Each conclusion is tied to the primary records immediately below it. Links open the publisher’s original material.

01

The product boundary comes before the brand

Coinbase says it controls the private keys for assets in hosted wallets, making Coinbase.com a custodial relationship. Coinbase Wallet assigns key control differently and cannot inherit conclusions about the exchange account. Any review that merges the two would conceal the most important responsibility change.

Sources: Coinbase Help · Coinbase
02

Protection language is asset-specific

The US agreement says supported digital assets are held for the customer’s benefit, but it also says crypto assets are not insured by the FDIC or SIPC. Separate language describes conditional pass-through deposit insurance for eligible cash. The defensible statement is therefore narrower than ‘Coinbase funds are insured’.

Sources: Coinbase · Coinbase Help
03

The cheapest-looking screen is not a complete cost record

Coinbase documents that simple Buy, Sell and Convert orders can contain both a Coinbase fee and a spread. Advanced uses an order book and maker/taker fees without an embedded spread, with exact tiers tied to changing account conditions. A fair comparison needs a fixed route, amount, market and timestamp rather than one headline percentage.

Sources: Coinbase Help · Coinbase Help
04

The 2025 incident changes the support-risk ledger

In May 2025 Coinbase disclosed theft of customer data through paid overseas support personnel. The company said passwords and private keys were not compromised, yet later public-company reporting records material reimbursement and legal expense exposure. That combination supports a targeted warning about social-engineering and support-chain risk, not a claim that the custody system itself was breached.

Sources: US SEC · US SEC
05

Permissions stop at jurisdictional borders

US state records and UK enforcement history show why a licence badge cannot be expanded into ‘regulated everywhere’. Permissions attach to a named entity, activity and location; restrictions can also be product-specific. Readers should match their contract to the relevant register before relying on a regulatory description.

Sources: New York State Department of Financial Services · Financial Conduct Authority · Coinbase
06

What remains to be tested

The public file supports conclusions about contract language, disclosed fee mechanics and incident reporting. It does not establish real-time solvency, execution quality, support resolution or withdrawal reliability. Those questions require controlled, region-specific scenarios with recorded parameters.

Sources: US SEC · Coinbase Help

Claim → evidence → gap

Ten claims placed under an accountable burden of proof.

Each module keeps the decision consequence beside the evidence and the unresolved gap. Primary material was retrieved on .

Fit

A traceable US custodial contract and public-company reporting are priorities.

The agreement and SEC filings expose entity, custody and incident language that can be challenged.

Fit

The user will compare Simple and Advanced receipts before recurring purchases.

Coinbase publishes distinct pricing mechanics that support a matched route test.

Not fit

Direct control of private keys is mandatory.

Coinbase.com hosted balances use platform-controlled keys; Coinbase Wallet is a different product.

Not fit

One protection or fee statement must apply in every country.

Entity, permission, cash protection and product pricing vary by market and surface.

01

01 / Product claim

Claim under review
‘Coinbase’ can be assessed as one service.
Evidence on record
The US agreement distinguishes hosted services and additional products; provider documents separately describe Coinbase Wallet.
Unresolved gap
Non-US and wallet contracts are outside this record.
Decision impact
Name Coinbase.com, Advanced or Wallet before any safety or cost conclusion.

Adjacent sources: Coinbase · Coinbase Help

02

02 / Operator claim

Claim under review
A global brand identifies the responsible company.
Evidence on record
The reviewed US agreement names Coinbase, Inc.
Unresolved gap
The operator and permissions for other countries are not established by the US contract.
Decision impact
A reader must save the applicable agreement and match it to an authoritative register.

Adjacent sources: Coinbase · New York State Department of Financial Services · Financial Conduct Authority

03

03 / Custody claim

Claim under review
Customer ownership means customer key control.
Evidence on record
The agreement says title remains with customers while Coinbase retains control of hosted-wallet private keys.
Unresolved gap
Runtime segregation and withdrawal handling are not observed.
Decision impact
Hosted custody creates counterparty and access risk even where contractual title remains with the user.

Adjacent sources: Coinbase · Coinbase Help

04

04 / Security claim

Claim under review
No private-key breach means the 2025 event is irrelevant to asset safety.
Evidence on record
SEC filings say support personnel enabled data theft and social-engineering attempts; Coinbase said passwords and private keys were not compromised.
Unresolved gap
Current recovery hardening is not tested.
Decision impact
Identity and support-chain controls belong in the security verdict, not only wallet infrastructure.

Adjacent sources: US SEC · US SEC

05

05 / Protection claim

Claim under review
Funds at Coinbase are insured.
Evidence on record
The US agreement separates conditional pass-through treatment for qualifying cash from crypto, which is not FDIC- or SIPC-protected.
Unresolved gap
Eligibility and actual cash placement are account-specific.
Decision impact
Do not use an unqualified insurance label for a mixed cash-and-crypto account.

Adjacent sources: Coinbase · Coinbase Help

06

06 / Cost claim

Claim under review
The visible fee is the cost.
Evidence on record
Simple transactions may include a fee and spread; Advanced uses maker/taker pricing.
Unresolved gap
Matched quotes, fills and exit costs are not captured.
Decision impact
Recurring users should compare same-time receipts rather than a marketing rate.

Adjacent sources: Coinbase Help · Coinbase Help

07

07 / Funding and exit claim

Claim under review
Easy funding implies a predictable exit.
Evidence on record
The agreement allows limits, holds and operational conditions around transfers.
Unresolved gap
No named rail and external withdrawal have been completed.
Decision impact
The full deposit-to-self-custody route is the decision unit.

Adjacent sources: Coinbase

08

08 / Execution and API claim

Claim under review
Advanced availability proves professional execution quality.
Evidence on record
Advanced documentation establishes an order book and fee model.
Unresolved gap
Depth, slippage, partial fills, cancellation and API permission behaviour remain unobserved.
Decision impact
Feature presence earns no execution conclusion without a fixed market run.

Adjacent sources: Coinbase Help

09

09 / Privacy and support claim

Claim under review
A regulated hosted account removes privacy and remedy uncertainty.
Evidence on record
The contract establishes verification, support and dispute obligations; the incident records show support data can be targeted.
Unresolved gap
Consent controls, data requests and case escalation are not tested.
Decision impact
Treat identity exposure and remedy quality as separate evidence questions.

Adjacent sources: Coinbase · US SEC

10

10 / Change claim

Claim under review
A long disclosure trail makes the conclusion permanent.
Evidence on record
The agreement was updated in July 2026 and the 2025 incident continued into 2026 reporting.
Unresolved gap
Future terms, controls and remediation can change.
Decision impact
Every recommendation needs a retrieval date and change trigger.

Adjacent sources: Coinbase · US SEC

Accountable scenario file

What the next observation must record.

Each row specifies a fixed protocol with defined inputs and record.

P-1

Simple versus Advanced receipt

Fixed inputs: Same US account, USD 1,000, BTC/USD, five-minute window.

Record: Preview, spread reference, order type, fee, fill and withdrawal quote.

Published
P-2

Hosted-asset exit

Fixed inputs: One supported asset/network and a clean self-custody address.

Record: Hold, address control, fee, transaction ID and usable arrival time.

Published
P-3

Lost-device recovery

Fixed inputs: No-value account with documented security settings.

Record: Identity steps, lockouts, channel hand-offs and restoration time.

Published
P-4

Privacy and dispute request

Fixed inputs: Default consent state and one non-urgent written case.

Record: Data controls, case owner, final response and external escalation.

Published

Change timeline

Events that change the reading.

  1. Support-chain data theft disclosed.

    Social-engineering and recovery controls enter the core risk file.

  2. 2025 Form 10-K reported incident-related cash expense.

    The event remains a governance and reimbursement issue.

  3. US individual agreement updated.

    Custody, pricing and dispute language must be rebound to the account.

Alternatives

When another responsibility model fits better.

Kraken

Granular security controls and a professional interface matter more than a mainstream onboarding path.

MetaMask with hardware-backed keys

Direct signing authority is the objective and the user accepts irreversible recovery responsibility.

Conclusion control

Medium evidence confidence.

Supported
A current US contract, fee documents and SEC filings support the claim-to-record chain.
Gap
Live cost, exit, recovery, privacy and support evidence is absent.
What changes the conclusion
A new applicable contract, repeatable exit failure or strong controlled route evidence would change the assessment.

Method

How the burden of proof is applied.

  1. Atomise each brand statement into product, entity, asset and market claims.
  2. Use contracts and regulator/SEC records for legal and incident propositions.
  3. Keep documentary evidence and account observations in separate columns.
  4. Publish contradictions and missing evidence beside the conclusion they limit.

Change log

Material file revisions.

Added ten claim-evidence-gap modules, four fixed scenarios and an explicit conclusion-change gate; primary sources re-retrieved.

FAQ

Questions that survive the headline.

Who holds hosted-wallet keys?

Coinbase controls the relevant private keys under the reviewed US hosted service.

Is crypto FDIC insured?

No. Conditional pass-through language concerns qualifying cash, not crypto.

Is Advanced always cheaper?

Not proven. Compare the same-time fee, fill and exit receipt.

Why no rating?

The live route, withdrawal, recovery and support evidence gate is still open.

SR

Primary-source register

Reviewed on by Candid Ledger Editorial Team; independent editorial review by Candid Ledger Review Team.

  1. Coinbase User Agreement — United StatesCoinbase · retrieved 16 August 2026
  2. What does Coinbase do with my digital assets?Coinbase Help · retrieved 16 August 2026
  3. Coinbase pricing and fees disclosuresCoinbase Help · retrieved 16 August 2026
  4. Coinbase Advanced feesCoinbase Help · retrieved 16 August 2026
  5. Coinbase Global 2025 Form 10-KUS SEC · retrieved 16 August 2026
  6. Coinbase Form 8-K — 14 May 2025US SEC · retrieved 16 August 2026
  7. Virtual currency businessesNew York State Department of Financial Services · retrieved 16 August 2026
  8. FCA enforcement action concerning CB Payments LimitedFinancial Conduct Authority · retrieved 16 August 2026