Get in touch

Before you send a message

Most questions we receive have already been answered on one of our pages. If your question is in the list below, you'll usually find the answer faster than waiting for a reply.

"Is this email/text a scam?"

Run it through ScamSupport. The tool analyses the message in your browser in seconds and is much faster than emailing us. If the result is borderline, you can also search our community database to see if other people have already reported the same campaign.

"How do I report a scam I've received?"

Use the report form. It feeds straight into the detection model and the public database. For serious financial loss you should also report to the appropriate national agency (Action Fraud in the UK, the FTC in the US).

"Do I need an account to use ScamSupport?"

No. The detection tool works entirely in your browser without any sign-up. The newsletter is the only thing that requires an email address.

"How is my data handled?"

Detection happens client-side — the message you paste in never leaves your browser. The newsletter list is held by our mailing provider (Mailchimp) and used solely to send the digest. Full details in our privacy policy.

"I think I've been scammed — what do I do right now?"

If money has just left your account, contact your bank immediately and ask them to recall the payment. Change the password of any account you suspect was compromised. Then file a report with Action Fraud (UK) or the FTC (US). Time matters — banks have a much better chance of recovering funds within the first few hours.

"Can you help me get my money back?"

Unfortunately no — recovering funds is something only your bank, your payment provider, and the police can do. We are an analysis tool, not a recovery service. Be wary of anyone online who claims to recover scam losses for a fee; that itself is one of the most common follow-up scams.

Press, partnership, or security disclosure

For press enquiries, partnership proposals, or responsible-disclosure of a security issue, please use the form above with the appropriate category selected. Security reports get the fastest turnaround.

What we read carefully — and respond to

A few categories of message tend to produce the most useful conversations:

• A correction or clarification on a published guide. If we have a fact wrong, a contact number stale, or a step in the wrong order, please tell us — ideally with the URL of the page and the specific line. We re-date the page when we make the correction so readers can see when it was last reviewed.
• A scam pattern that is not yet covered on the site. If you have received something that doesn’t map cleanly to any of the existing guides, paste the message (with personal details redacted) and a brief note about how it arrived. New patterns shape the next batch of guides.
• A false positive or false negative from the scanner. If the scanner gave a result that was clearly wrong on a message you understand the context of, that is high-signal training data — we use those reports to refine the model. The dedicated report form on the training page is faster than email for this, but email works too.
• Press, partnership, or security-disclosure enquiries. For coordinated security disclosure on the site itself, please use email with “[SECURITY]” in the subject line; we will reply with a PGP key for sensitive follow-up if needed.

For everything else — general questions, feature suggestions, the “I really enjoyed the recent post on X” messages — we read them all and reply when we have something useful to add. Thank you in advance for the patience that requires when the inbox is busy.

What we can and can't help with

To set expectations honestly: SignalTools is run by a small team and we keep the scope intentionally narrow. Here's what falls inside and outside what we can do.

We can help with

• Bug reports about the ScamSupport tool — incorrect detections, layout issues, broken links, accessibility problems.
• Adding a new scam category, brand, or campaign to the detection model when you've seen something we don't yet cover.
• Press, partnership, and integration enquiries.
• Responsible-disclosure of any security issue you've found in our site or infrastructure.
• Removing your reported message from the public community database if it contains information you'd rather not have published.

We can't help with

• Recovering money lost to a scam — this is a job for your bank, your card issuer, and law enforcement. Be sceptical of anyone online (us included) who claims they can recover funds for a fee.
• Investigating individual fraudsters, hosting providers, or registrars — we don't have law-enforcement powers.
• Personalised legal or financial advice — we publish general guidance, but specific situations need a qualified professional.
• Whitelisting your domain so it stops triggering false positives — instead, please send a sample of the email and we'll add it to the training set.

Response times in plain numbers

For ordinary enquiries, replies typically go out within one working day. Security reports are handled the same day they arrive. Bug reports and detection-model additions are batched into a weekly review and may take up to seven days to land in production. If you haven't heard back after five working days, the message probably got caught in a spam filter — please resend or email us directly at info@signaltools.org.