Skip to content

Privacy Policy

Last updated: 29 October 2026

ScamPing is a free online safety project operated by an individual based in Ukraine. ScamPing is the public name of the service, not a separately incorporated company.

For privacy inquiries or requests for information about the operator's legal identity and legally required contact or location details, please email privacy@scam-ping.com.

We provide legally required information in accordance with applicable law.

When you visit the website, our hosting and security providers may receive ordinary technical information, such as your IP address, browser details, requested pages, timestamps and security signals needed to deliver and protect the site.

When you choose Check, we process the message, link or screenshot you provide, any optional context, and a generated assessment so we can identify possible warning signs, explain what was checked and suggest next steps. This material can include personal information about you or someone else. A screenshot may contain visible names, messages, account information or other private details. Please remove information that is not necessary for the check before sending it.

The Scanner does not create a user account or a saved history of your checks. We do not intentionally store scan contents, screenshots, extracted text or results in our product database, file storage, analytics, research datasets or training data. This is not a promise that service providers never retain operational records.

Your browser sends the submitted material directly to the Scanner service hosted on Supabase Edge. ScamPing uses OpenAI’s API to help interpret signs of risk and produce an explanation. The submitted content and generated result may therefore be processed by both providers. We use server-side API access; your browser does not receive our OpenAI API key. We do not open submitted links or visit their destination pages as part of this MVP.

ScamPing uses the information you provide for the check you request and to prevent abuse or technical failures. We do not sell submitted content, publish it, use it for advertising, or intentionally use it to train models. OpenAI states that API inputs and outputs are not used to train its models by default unless an account has opted in. ScamPing has not independently confirmed the account-level sharing settings and does not promise that provider processing is free of retention or reuse under provider settings and policies.

Although ScamPing does not maintain a scan history, Supabase platform operational records may contain request bodies and generated responses. The Scanner project uses Supabase’s Free plan. Log availability depends on the plan and usage limits; we have not verified a fixed project-specific retention period or deletion deadline for every internal copy. Dashboard visibility is not proof of complete deletion.

Under standard OpenAI API handling, OpenAI may retain prompts and responses in abuse-monitoring logs, typically for up to 30 days, with exceptions under its policies or legal obligations. ScamPing sets store=false, but this does not remove abuse-monitoring retention. We have not verified a special Modified Abuse Monitoring or Zero Data Retention arrangement and do not promise zero retention. Provider prompt caching may retain encrypted intermediate data for up to 24 hours. Image safety checks may require manual review and retention of flagged images, including under special retention arrangements.

Any information you email us about privacy or corrections may be retained as needed to address your request, document the outcome and meet applicable legal duties. We do not promise immediate deletion of independent provider logs following a request.

Messages sent to hello@scam-ping.com, privacy@scam-ping.com or corrections@scam-ping.com may be forwarded through Cloudflare Email Routing and handled in Google/Gmail. These providers may process email contents, attachments, sender details and other email metadata to deliver and handle our correspondence.

This email route is separate from Scanner. Checks submitted through the Scanner form are not sent to Cloudflare Email Routing or Google/Gmail. If you choose to email us scan material yourself, it becomes part of that correspondence. Do not email passwords, codes or unnecessary personal information.

Our website is delivered through Vercel and Cloudflare. Scanner requests are routed to Supabase Edge, with Frankfurt execution requested and verified as part of our technical launch checks. OpenAI and other service-provider operations may involve processing outside Ukraine or the European Economic Area. We use OpenAI’s global API endpoint and have not verified an EU-only processing arrangement or project-specific contractual transfer safeguards. We cannot guarantee a particular country for all provider processing. A requested European execution region does not guarantee that every support, safety or logging operation remains there.

We use technical controls to limit access, prevent abuse and handle errors. Cloudflare Turnstile may process browser and device signals to verify a request before a Scanner check. ScamPing application logs are designed not to include raw scan text, full submitted links, screenshots or results, but the separate provider-log limits described above still apply.

When enabled, ScamPing uses Plausible Analytics to measure visits and limited engagement on approved public pages, selected navigation actions, and whether a Scanner or Guided Check was started or completed. Individual article and guide detail pages are not measured in this version. We do not use Plausible for advertising tracking, session replay, or automatic form, file download or outbound-link capture. Analytics is optional and does not affect your ability to use Scanner or Guided Check.

Scanner analytics is limited to a pageview of the public /check page and events indicating that a check request was sent or a validated, non-failed server response was received. These events do not measure whether an assessment was correct. We do not send Plausible submitted message text, inspected links, screenshots, extracted text, optional context, authentication codes, assessment details, check results, Guided Check answers, contact details or identifiers for individual checks or users. Scanner events have no custom properties.

For Scanner analytics, the reported page URL is the canonical public /check URL without query parameters, fragments or referrer information. On other approved public pages, pageviews may include only a predefined set of approved campaign values for utm_source, utm_medium, utm_campaign and utm_content. Other analytics events do not carry campaign parameters. Referrer information is limited to the origin of an approved HTTPS website or omitted. Referrer paths, queries and fragments are not transmitted, and Plausible analytics requests do not send an HTTP Referer header.

When an analytics request reaches Plausible, Plausible receives ordinary network information, including the visitor's IP address and browser User-Agent. According to Plausible, it uses these details to derive approximate location and device characteristics and to calculate a daily visitor identifier specific to this website. Plausible states that it does not store raw IP addresses or User-Agent strings, rotates and deletes the identifier salt every 24 hours, and does not use analytics cookies, browser storage or persistent visitor identifiers. Plausible stores event and session records to produce aggregated statistics. Aggregated reports do not mean that only aggregated data is processed or stored.

Plausible states that its website visitor analytics data is processed and stored within the European Union. Its visitor-data subprocessors include Hetzner, Bunny and UpCloud. Analytics records are retained for the period needed to provide website statistics, subject to the retention limits of the subscription in use and applicable deletion arrangements. Site statistics or the account may be deleted earlier, while backup copies may remain temporarily under Plausible's terms. We do not guarantee immediate deletion of every provider copy. These analytics arrangements are separate from the processing and retention of Scanner submissions by Supabase and OpenAI.

We use this limited analytics processing for our legitimate interest in understanding and improving ScamPing, subject to applicable data protection requirements and the rights of visitors. You may contact privacy@scam-ping.com with privacy questions or objections to this processing. We handle such requests in accordance with applicable law. For details of the provider's practices, see https://plausible.io/data-policy and https://plausible.io/dpa. Essential hosting and security services may separately use temporary identifiers or tokens.

You can stop future optional analytics requests from this browser using Analytics preferences below. We store your choice in this browser solely to honor it; this preference is not a visitor tracking identifier and is not sent to Plausible. Your choice applies only to this browser. Turning analytics off does not retroactively remove records previously received by Plausible. You can turn analytics back on whenever you choose.

Please avoid submitting material about other people unless you are entitled to share it for this purpose. Remove names, phone numbers, email addresses, account details and unrelated parts of conversations where possible. Do not enter passwords, one-time codes, card credentials, recovery phrases, identity documents or sensitive private records. Automated safeguards cannot reliably identify every secret or every type of personal information. Screenshot metadata is removed by our browser before upload and checked again at the Scanner boundary, but visible pixels are not automatically anonymized. Direct requests can reach provider infrastructure before being rejected. If you cannot safely redact the material, use Guided Check without sending its contents.

Subject to applicable law, you may contact us to ask about personal information we control, request correction or deletion, object to certain processing or raise a privacy concern. The rules and available remedies depend on the law applicable to the request. Because checks are anonymous and ScamPing does not keep a scan history, we may be unable to identify an individual past check in our own systems. Provider operational records may be subject to different access, retention and deletion processes. We will explain what we can and cannot do.

Privacy contact: privacy@scam-ping.com. You may also raise a complaint with the competent data-protection authority where applicable.

ScamPing articles may link to third-party websites with their own terms and privacy practices. We may update this Policy as our website changes. Material changes to how Scanner data is handled will be reflected here before the changed processing becomes available to users.

ScamPing is operated by an individual based in Ukraine, as described above. General enquiries: hello@scam-ping.com. Corrections: corrections@scam-ping.com.

Analytics preferences

We use privacy-minimized Plausible statistics to improve ScamPing. There are no analytics cookies or advertising profiles. You can stop future analytics requests from this browser at any time without affecting Scanner or Guided Check.

Checking your preference…