Editorial policy

A practical editorial policy

DontClickYet is an educational resource for people who want to pause before clicking, replying, paying, downloading, or sharing information. We explain recognizable patterns and safer verification routes; we do not decide that a particular person, phone number, account, or business is fraudulent.

Our guides are written for ordinary readers who may be under pressure. They use plain language, name the action a suspicious contact is trying to trigger, and put the safest next step near the top. We update pages when official reporting routes, platform workflows, or common tactics change.

How safety wording works

We use careful phrases such as “commonly associated with scams” because a familiar pattern is a reason to pause, not proof about an individual sender. We avoid fake testimonials, invented credentials, unverifiable success claims, and instructions that could expose private information.

We review guide wording for accidental accusations, unsafe requests to investigate or confront someone, and advice that could be mistaken for legal, financial, or cybersecurity professional advice. If you need urgent help, use the official app, website, bank, provider, or government channel involved.

What readers can expect

• A specific explanation of the pressure, request, or impersonation pattern.
• Verification steps that start outside the suspicious contact path.
• Evidence-preservation advice that does not require clicking deeper.
• Links to official reporting and recovery resources when relevant.

Questions about corrections or safety wording can be sent to [email protected]. For help with a site issue, contact [email protected].

Using this resource responsibly

This page is part of DontClickYet, an educational library maintained for people who want a calm way to evaluate an unexpected contact. The wording is intentionally practical: pause, avoid the supplied contact path, and check the relevant account or service through a website or app you opened independently.

Online patterns change quickly. A familiar name, logo, message style, or caller ID can appear in both legitimate and deceptive contexts, so readers should treat the page as a starting point for questions rather than a verdict. If the situation involves money, account access, identity information, a device, or a safety concern, contact the responsible provider or official agency promptly.

DontClickYet does not ask readers to publish private details, confront a sender, pay for investigation, or trust an unverified recovery service. Keep sensitive information out of search fields and email unless an official channel genuinely requires it. Corrections and accessibility feedback are welcome at [email protected]; site issues can go to [email protected].

A simple reader checklist

Before trusting the claim described on this /editorial-policy.html page, identify the channel, the claimed organization, the requested action, and the consequence the contact predicts if you wait. Then separate those facts from the sender’s interpretation. A real-looking message can still use a misleading link, an unfamiliar payment route, or a request that the legitimate organization would not make.

Use a clean verification path: open a saved official app, type a known domain, review a statement or account dashboard, or call a number printed on a card or bill. If the official source shows no matching alert, do not continue through the original message. If it does show an issue, follow the official workflow rather than the instructions supplied by the unexpected contact.

When preserving evidence, save only what is safe and necessary. Redact private numbers before sharing a screenshot, do not forward malicious links to friends, and do not keep interacting just to collect proof. After payment or account exposure, speed matters: contact the provider, secure access, monitor activity, and use the official reporting route.

A useful review also includes the possibility of an innocent explanation. An unexpected message can be mistyped, outdated, or sent through a compromised account without proving who caused it. That uncertainty is another reason to avoid accusations and use independent verification. If a provider’s official help page gives different instructions, follow that current official process and treat this educational page as background context.