Help / Troubleshooting
Safety warnings and disabled codes
3 min read · updated
If you scanned a code and saw a Dotwick warning: the page it leads to was reported by other people or matched a list of known threats, and our safety team is reviewing it. You haven't been taken there. Only continue if you trust whoever put the code up — and never enter card details, passwords or ID on a page you reached from a code you don't trust.
If you scanned a code and saw "This code was disabled for safety": a person on our team looked at the page it led to and turned the code off, usually because it imitated another company to collect personal or payment details, spread harmful software or ran a scam. If you already entered card details there, call your bank and ask them to block the card. Use the number on your card, not one from the page you scanned.
How we check: every destination is looked up with Google Web Risk when a code is created or changed and again regularly after that, and against our own list of blocked domains and phrases. Anyone who scans a code can report it from the link at the bottom of a hosted page, or from dotwick.com/report. Reports from several different people put a new code behind the warning page; one person can't do that alone.
If it's your code: you get an email and a notice in the app with a reference like SAFE-882. A warning page lets people continue; a disabled code shows the Dotwick safety page instead of your destination. Nothing is disabled automatically — a person always makes that call. If we got it wrong, appeal from the link in the email or from the code's page within 30 days, and tell us what the code is for. A person reviews every appeal and emails you the decision.