Privacy and Confidentiality

What is useful to paste

• The text of the message, the URL, or the number as observed.
• The minimum context needed to understand the request.

What you should never paste

• An OTP code, a reader code, a seed phrase, a password, or a full card.
• Full identity documents if they are not strictly necessary.

Simple public promise

• The site is not meant to resell submitted cases.
• Public pages and testimonials must remain anonymised and moderated.

Visit tracking

• The site measures the pages viewed, calls to the detector, technical errors, the type of device, and the country passed on by Cloudflare to monitor how it works.
• The raw IP address is not kept in this tracking. It is turned into a pseudonymous identifier that changes every day; events are deleted after 30 days.

Data not to send

• Never paste a password, PIN, itsme code, reader code, full card number, seed phrase, identity document, or detailed medical data.
• Mask names, addresses, customer references and account numbers when these items are not needed to analyse the mechanism.

Separation between public promise and operations

• Retention periods, backups, deletion and incident handling must match the processing actually used by the service.
• The project states that it does not resell submitted content. Any change in processing must be documented before being presented as a public promise.

What to do now

• If you have not acted, do not click further and open the named service's official channel yourself.
• If you clicked, close the page, enter nothing else and note what information was shown or requested.
• If you shared a code, card, password or payment, contact your bank or the relevant official service immediately.
• Keep the message, time, link used and any useful screenshots. Share them only with an official reporting channel or a trusted helper.

Limits of this page

• This page does not prove that a message is safe and does not replace your bank, the police, Safeonweb, a platform or a public service.
• A scam may be new, very well written or described with too little context. Use the result as decision support, not as absolute certainty.
• Before taking a final action, checking through the official channel matters more than the appearance of the received message.

Check through an official channel

• Type the service address yourself or open the official app. Do not use a phone number, link or QR code from the suspicious message to verify the situation.
• When money, card details, a code or account access are involved, the safety action comes first. The analysis can then help organise the evidence.

How to read the result

• A low number of signals does not mean that everything is safe. It only means that this page or analysis did not find decisive evidence with the information available.
• Focus on the requested action: paying, sharing a code, installing an app, approving a bank action or leaving an official platform. That action matters more than a logo, sender name or polished wording.
• If the situation feels urgent, step away from the received message first. Then check calmly through a channel you already trusted before the message arrived.

Belgian reading of this situation

• For this this privacy and confidentiality situation situation, focus on the relevant Belgian next step: open the official channel yourself, contact the bank, use Safeonweb or preserve evidence.
• The right decision for this this privacy and confidentiality situation situation depends on what has already happened. Reading a message is not the same as clicking, paying, sharing a code or granting remote access.

How to use this page

• Use this page about this privacy and confidentiality situation to understand what StopArnaques can show, what still needs verification and which information is still missing before a public launch.
• This is not marketing proof. It helps assess trust, method, data protection and contact options honestly.

What to do with this page

• If you have a suspicious message, use the detector or a practical fraud page. If you want to assess the project, focus here on method, limits and correction channels.
• When legal or organisational information is missing, that gap remains visible instead of being hidden.

Evidence still needed

• A nationally credible project page shows sources, corrections, responsible parties, data use and limits without promising more than the system can actually prove.
• Missing legal, organisational or operational details remain visible as open points until they are completed by a real decision.

Limits of this project page

• This page does not replace a legal notice, privacy audit, official recognition or partnership. It only explains how the project works and where users should remain cautious.
• If someone already shared money, codes, card data or account access, they should not stay on this project page: use the action guides and contact the relevant service.

What the reader can verify

• Check whether the page clearly states who is speaking, which sources are used, what data may be processed and which promise is not being made.
• A public project page is strong only when a non-technical reader understands how an error can be reported, how information is updated and why the analysis remains cautious.

Frequently asked questions

Useful official sources

• SPF Économie - Victime d'une arnaque ? Que faire ? - link checked on 2026-09-17
• Centre pour la Cybersécurité Belgique - Collaboration avec la Police Judiciaire Fédérale contre le phishing - link checked on 2026-09-17
• ConsumerConnect - Message suspect concernant votre compte ou carte bancaire - link checked on 2026-09-17
• Safeonweb - Au secours, j'ai cliqué sur un faux lien - link checked on 2026-09-17
• Safeonweb - Un appel de Card Stop ? Attention, arnaque - link checked on 2026-09-17