Privacy
What you share with Can It Scam?, what is saved, and what you can control.
Searches are not storage-free. Submitted text can be saved in private search logs and saved results. Remove passwords, OTPs, bank or card numbers, Aadhaar details and other personal information before checking.
Searches and saved results
Checks that reach our service can log up to 2,000 characters of the submitted text, the check type, time, result, risk score, whether the result was reused and whether you were signed in. Authorized administrators can view these logs to understand usage and investigate abuse. Repeat checks answered entirely on your device may not create a new server log.
Saved results and lookup keys allow repeat checks to reuse an earlier answer. Those records may contain information from the item you checked and are currently retained without a fixed automatic deletion period. Search logs also have no fixed automatic deletion period. Checking an item does not, by itself, publish a community report.
AI and other service providers
When a check needs AI, the submitted content and relevant evidence are processed through our AI service provider using OpenAI models. AI is also used to read screenshots and review contributions. Not every check requires AI. Links and QR-code addresses you check are also sent to Google Safe Browsing to see if Google lists them as dangerous.
AI requests ask the provider not to store the response, but this is not a promise that no processing or security logs exist. Provider retention and data handling are governed by their own terms. Hosting, account sign-in, email delivery, anti-bot protection and external lookups also involve service providers. Relevant URLs, domains or phone numbers may be sent to lookup services, such as malware-information services or Google Maps, when needed for a check.
Screenshots, QR codes and app files
- Checker screenshots: images are sent for AI text extraction. If you then check the extracted text, it is handled like any other submitted search.
- QR images: decoding happens in your browser. The decoded content is sent to our service when you check it.
- APK files: uploaded files are processed to inspect their contents, not executed. The checker does not save the APK file itself in its application storage; extracted information may be used in the result and external lookups.
- Report evidence: screenshots attached to a contribution are kept in private storage and processed for review. Editing or deleting the contribution removes its attached screenshot from that storage.
Accounts, reports and stories
Signing in involves account information, such as your email address and information supplied by your sign-in provider. Contributions, review status and feedback can be associated with your account. Anonymous contributions use claim tokens so the original submitter can claim them after signing in.
Reports and stories submitted for publication may become public after review, including their text and any display name shown with them. Do not include private information about yourself or other people. Your private review details and attached evidence screenshots are not part of the public report display.
Email alerts
Alert subscriptions save your email address, verification information and subscription status. You must verify your address before alerts are activated. Use the unsubscribe link in an alert to stop further alerts; unsubscribing changes your subscription status and does not automatically erase the subscription record.
Browser storage, traffic and security
Your browser stores a visitor identifier, sign-in session information and some recent checks. Saved checks can include the original input in their lookup key. The local result cache is used for up to seven days, although expired entries may remain in browser storage until replaced or cleared. Report and contribution preferences may also be saved on your device.
We use hashed identifiers derived from account, browser or network information to count usage and limit abuse. A hash is a pseudonymous identifier, not a guarantee of anonymity. Public page arrivals record the UTC day, source category, landing page path and a keyed hash of the browser identifier to estimate distinct visitors over a selected period. Campaign tags can also be saved. The visitor counter does not store raw IP addresses, full referrer URLs, search terms or page query strings. Google arrivals are inferred from a referring hostname, not confirmed organic clicks. One person on different devices may count more than once, and a shared browser may count as one visitor. Preview measurements are kept separate from live-site counts. This visitor measurement is separate from the saved search logs described above. We also record the source guide path and destination checker path for internal guide-to-checker arrivals, using the same keyed browser identifier. These records estimate which guides lead visitors to a checker, not whether they complete a check. Hosting and anti-bot services may also process IP addresses, request information and device signals for analytics and security.
Shortcut and shared links containing your search text can leave that text in browser history or URL logs. Avoid putting personal information in those links.
Your choices and questions
Clear this site’s browser data to remove locally saved checks and sign-in information. This does not delete server records. You can manage your own contributions from Report a scam after signing in. There is currently no self-service control for deleting search logs or all account data.
For privacy questions or a request to review or delete data, contact privacy@canitscam.com. Describe your request without sending passwords, OTPs or sensitive documents. We may need enough information to identify the relevant record and verify the request.