How this temporary ScamRadar service handles information. This explains how the current test version handles information. It is not yet a legally approved privacy policy. Before a full public launch, we still need to publish who is responsible for your data, how to contact us, why the data is used, how long it is kept and which service providers handle it.
Information handled by a scan
When you submit a domain, link, email address, phone number, message or company name, the checker analyzes the input against threat feeds and technical signals. The service may retain normalized indicators, risk scores, results, timestamps, source references and security events. A report or dispute may add the incident category, statement, moderation status and an account association if you are signed in. Do not submit secrets, documents or financial credentials.
Accounts, notices and personal records
WordPress accounts can hold login/profile details. ScamRadar can associate saved checks, watchlists, brand alerts, community reports, disputes and some shared information with a signed-in user. New account registration is currently unavailable in this test version. Email alerts are not yet available as a verified service. Do not rely on receiving an email notification here.
Cookies and information kept on your device
WordPress may use session or login cookies for authentication, settings and security. When you create a dispute, the browser may store its case reference and secret lookup token locally to help you check the status later. A person who obtains that token could access the private case status. Do not share it, and clear browser data on shared devices.
Sources and other technical services
Risk signals may use public third-party threat lists and technical network services. Each publisher has its own terms. Review the active source list and coverage. ScamRadar does not assert that a publisher entry establishes criminal wrongdoing. The complete service-provider and processor disclosures require an owner review before public launch.
Access, correction and erasure
The current software registers WordPress-native personal-data export and erasure handlers, including ScamRadar records. Confirmation and fulfillment involve identity checks and, in some cases, manual review. Historic threat evidence and moderation audit records may need to be retained after separating personal identifiers. The underlying WordPress login is not necessarily removed by a ScamRadar-specific data request.
Important limitation: email delivery and a dedicated ScamRadar support mailbox have not yet been activated. Do not rely on receiving a confirmation email here. Before the public launch, we will provide a verified way to contact the operator about privacy and data requests.
Security and retention
Technical anti-abuse and rate-limit safeguards apply to checks and submissions. Some reports may be held for editorial review; precise retention periods and legal bases still require formal site-owner validation. There is no automatic guarantee that submitting an appeal deletes public data or proves an accusation false or true.
For a suspected incorrect public warning, follow the report and dispute guide. For a financial incident, open the Recovery Center.
Operational disclosure as at 15 October 2026 - staging. It does not replace the final approved privacy policy.