How we check every step

Every step comes from the platform's own help center, read on the date shown at the bottom of the page. Every official link must sit on a domain the platform owns, and our build fails if one does not. Forum posts, news articles and “recovery service” blogs are never sources.

Button and menu names appear in this styleand are copied from the platform's help page, never paraphrased. When a help page does not print the label, we describe the action in plain words instead.

A step gets this tag when the official page supports it but does not spell it out word for word, or when it varies by account type or region. These steps are next in line for testing on a real iPhone and Android device. A page whose main official link we cannot confirm is not published.

We only give a wait time when the platform publishes one, and we label it as published. When a platform publishes nothing, we say so. We never quote odds of getting an account back.

• Weekly: an automated check opens every official link.
• Monthly: recovery flows re-read against each platform's help pages; changes ship with a changelog entry.
• A page not re-checked in 60 days shows a “Needs retest” banner and is hidden from search until it is.

We are not affiliated with any platform, we use no logos, and we cannot get into any account. We never ask for passwords, codes or ID, and never charge. Screenshots, when added, come from our own test accounts with personal data removed.

An account is only as strong as its recovery path. Account recovery design is the security ceiling and the help desk is the new perimeter explain why attackers target it. Where this is heading: passwordless everything.