Privacy Policy
Privacy Policy
Last updated: November 14, 2026
Information you provide
ScamSpot checks the message, email, chat text, or URL you paste into the tool. Remove personal details, passwords, codes, account numbers, or payment information when possible.
How the tool works
This section describes the remote checker at /api/check, not the local invoice or email-header checkers. When you submit the remote checker, the page sends the full text you entered (after trimming outer spaces), your selected language and, on some pages, a business or trucking context to /api/check on ScamSpot. It does not automatically remove personal details. Remove passwords, codes and other sensitive information before submitting.
Depending on configuration, usage limits and service availability, the server uses local rules or sends that text to Anthropic at https://api.anthropic.com/v1/messages for model analysis. This is not processing exclusively on your device. The checker code does not write the submitted text to a database, file, localStorage or sessionStorage. The text and result remain in the page while you use it; copying or sharing a result requires your action.
These statements describe the checker code, not the retention or logging practices of the hosting infrastructure or Anthropic. We do not establish those providers' retention periods here. The free checker does not require an account.
Local browser storage
The homepage stores the analysis counter and language preference in localStorage on your device. They persist across visits until cleared through your browser settings. The checker does not save the pasted text or its result in this storage. The separate test-only Family Brief page stores a test-session identifier in sessionStorage for that tab, not the pasted checker text.
Usage-limit counters
The server reads an IP address from the forwarded request header or connection. Minute and daily counter keys include that unhashed IP, and a separate daily counter tracks total site use. With KV storage configured and working, the code requests expiry after 70 seconds for minute counters and 90,000 seconds (25 hours) for daily counters. These are configured counter expirations, not guarantees about provider logs or backups.
The fallback keeps counters in process memory. Minute limits use clock-minute buckets: a new bucket applies at the next minute boundary. Each memory minute bucket has a resetAt timestamp 70 seconds after creation; that is not a 70-second wait before requests can resume. Daily limits reset at the next UTC midnight; a logical reset does not immediately delete every old entry from memory. Counter keys and values do not contain the submitted message. Explicit KV-failure logs in this handler record a stage and error code, not the message.
Analytics
The page loads Google Analytics. The checker events defined in the page code include input length, language and result classification or an uncalibrated indicator; they do not send the pasted-message field. Result fields can include free-form model text that could repeat part of your input. Page and interaction events are also defined. This description does not verify the remote analytics configuration or its retention settings.
Contact
Questions about this policy can be sent to the site owner through the contact method published for ScamSpot.