Dropbox Watchdog

Search issues

Search the Dropbox Watchdog archive

All issues

Verification friction: a security code to an old phone or unreachable inbox can lock you out

Ongoing pattern

MediumStatus: OngoingProduct: AccountYear: 2023

Dropbox sends one-time verification codes for new-device or unusual logins, but when the code goes to an outdated phone number or an inbox the user can no longer reach, legitimate owners report being unable to sign in — and the questionnaire-based recovery often fails.

What happened

Beyond opt-in 2FA, Dropbox triggers extra verification — a six-digit code by email or SMS — when it detects a new device or unusual login. The mechanism protects accounts, but it strands legitimate users when the destination is stale: a code sent to a phone number the user no longer owns, or to an email account they have lost access to. Community threads describe users who never receive the code, click a verification link that does nothing, or cannot pass the fallback.

Dropbox's documented recourse is a recovery questionnaire in which a user answers as many account-specific questions as possible, or a manual identity check by a specific support department. Users widely report that this path is slow and frequently unsuccessful, especially for older accounts where they cannot recall enough detail. The result is a verification system that, by design, can refuse the real owner while having no fast, reliable way to tell them apart from an attacker.

This entry documents an aggregated pattern set against Dropbox's official verification guidance; it is a recurring friction point rather than a single dated event.

Impact

Identity-verification lockouts hit exactly the users least equipped to recover — those who changed phones or emails and didn't update Dropbox first — and route them into the same slow, hard-to-reach support documented across this category. When the questionnaire fails, the practical outcome is the same as a 2FA lockout: a legitimate owner permanently separated from their files.

Dropbox's Response / Official Position

Dropbox documents verification-code troubleshooting and an account-access recovery questionnaire, and says a specific support department can manually verify identity in some cases. It does not publish how often manual verification succeeds.

Sources

Related guides

Spot an error, or have a source to add?
Report an error / suggest update

Related issues

Across multiple years, attackers have built convincing fake Dropbox login pages — reached via PDF lures and redirect chains through trusted cloud storage — to harvest victims' real business email and Dropbox credentials.

Security Incidents & Data BreachesAccount Lockouts & Support Failures
Read documentation
2 sources
Medium1,180+ documented BBB complainants (3-year window)

Over 1,180 BBB complaints: the paper trail of Dropbox's billing and support grievances

The Better Business Bureau has logged more than 1,180 complaints against Dropbox over three years, dominated by surprise auto-renewal charges, denied refunds, and support tickets that vanish without resolution.

Pricing & Business PracticesAccount Lockouts & Support Failures
Read documentation

Because Dash can be downloaded and set up with 'no sales or IT required,' an individual employee can connect and index an organization's apps and browser history without administrator oversight — recreating the shadow-IT data-governance risk that earlier consumer Dropbox use posed to enterprises.

Privacy & Encryption ConcernsCurrent / Ongoing Issues (2024–2026)Account Lockouts & Support Failures
Read documentation
3 sources
HighHundreds of thousands (Sign-breach class, now in arbitration)

2025: Dropbox forces the Sign-breach class action into private arbitration

A federal judge compelled the users suing over the 2024 Dropbox Sign breach into individual arbitration — finding that by clicking 'I agree' to sign a document they had accepted Dropbox's terms — and then denied reconsideration, effectively shutting the class action out of court.

Legal Actions & LawsuitsCurrent / Ongoing Issues (2024–2026)Account Lockouts & Support Failures
Read documentation