Editorial policy

Sources come first

• We base account, recovery, eligibility and policy guidance on the platforms’ own help centres, newsrooms and policies.
• Device steps come from Apple’s and Google’s official support pages.
• Each guide lists its sources and shows how each was checked: checked (we read the page), title checked (only the page title could be read) or linked for reference (the official page exists but couldn’t be read automatically — for example, some platform help centres block automated reading). We never treat a link on its own as proof of a claim.
• We don’t invent statistics, timelines, error meanings, policies or test results. If something isn’t confirmed, we say so or leave it out.

Safety rules every guide follows

• We never ask for, or tell you to share, passwords, login codes, recovery codes or session data.
• We never promise account recovery, reinstatement or a guaranteed fix.
• We never explain how to get around security checks, age or location rules, restrictions or enforcement.
• Account-specific recovery, identity checks and appeals are always routed to the platform’s official channels.
• Causes are labelled as possible unless an official source confirms them.
• We warn readers about recovery scams and fake support wherever accounts are at risk.

How we use AI tools

We use AI tools to help research, organise and draft guides. Every guide is checked against the sources it lists before publication, follows the safety rules above, and is reviewed again on a fixed schedule. Our publishing system blocks guides that don’t pass these checks.

Review dates and how often we re-check

• "Last reviewed" shows the date someone re-checked the guide against its sources. Cosmetic edits don’t change it.
• Guides about accounts, security or platform policies are re-checked at least every 90 days; general troubleshooting guides at least every 180 days.
• We re-check sooner when readers report a change or a platform redesigns a feature.
• Menu names change often and differ between devices, app versions and countries. Our guides say so where it matters.

One page per problem

We don’t publish near-duplicate pages for slightly different wording. Each guide owns one problem; related problems are linked, not copied.

Corrections

If you find an error or an outdated step, email [email protected]. We’ll check it against the official source and, if we were wrong, fix the guide and note the change in its "What changed" section.

Independence and money

We are not paid by any platform. We have no ads, affiliate links or sponsors today. If that changes, we will disclose it clearly and never place ads inside troubleshooting steps or in ways that could be mistaken for buttons.