Version 2026-09-28-contact-v5
Privacy notice
Operator: Asahi Management LLC
Questions or data requests: use our contact form
Guest searches
You can search without an account. A temporary secret token identifies your browser session; the server stores its hash. Submitted contact details and results are held for request recovery. Guest access expires 24 hours after session creation. Expiry ends access; it does not immediately erase stored content. Expired guest content becomes eligible for cleanup, while minimal usage and retry records remain. Guest searches are not automatically added to account history. When available, Save or Export lets you sign in to a free account and save that exact report without rerunning the search. Saving creates a separate account-owned copy and does not move the guest record. Saving and exports require an account; save a report before the guest session expires if you need to keep it.
What we process
We process account information, submitted contact identifiers, optional context, report evidence, private notes and decisions, and any historical blocklist, purchase and credit records. Submit only information needed for a legitimate research purpose. Do not submit payment-card data, passwords, government IDs, sensitive personal information, or unrelated personal details.
How information is used
We use information to provide and secure the service, prepare requested reports, manage free usage and historical payment records, respond to support, and maintain necessary operational records. Private context and reference fields are stored with the account record and excluded from the AI/public-web research request. Submitted name, email, phone and address fields may be processed by the hosting platform and the AI or search services used to prepare the report. On the scam text checker, the pasted message text is also sent to the AI for analysis, after anything that looks like a one-time code, password or card number is removed in your browser and again on the server. Links found in the message are searched on the public web. The message text itself is not stored; only the extracted contact details, the links found and the report are kept, under the same rules as other searches.
Service providers
The app uses Base44 for hosting, authentication and app records, together with configured AI and web-search services. New paid checkout is disabled. Historical payment records are retained for review; they do not fund new searches. Each provider processes information needed for its service.
Retention and controls
Account report content becomes eligible for cleanup after 90 days. Account provides export and deletion controls for report content, saved batches, notes and historical blocklist entries. Minimal usage, payment, credit and operational records may remain for usage enforcement, reconciliation and retry safety. Deleting a saved guest report removes the account copy, not the original guest record. Deleting report data does not delete your sign-in account or the original public sources; contact support about closing your account.
Abuse prevention
New searches are limited to one every 30 seconds per browser identifier, across guest and account use. There is no per-account or per-session search-count limit. Service-wide capacity controls also apply. We use a randomly generated first-party browser identifier for this control; it is not a hardware identifier or a fingerprint. It is stored in browser local storage and can be reset by clearing site data. The limiter processes the browser identifier, and stores keyed hashes with a cooldown deadline in protected operational records, rather than the raw identifiers. Expired limit entries are removed during subsequent successful search admission; backup copies follow the hosting provider’s retention. These identifiers are not added to reports, exports, usage analytics or advertising. Hosting providers separately process request metadata under their own retention practices. Do not reset identifiers or change sessions to evade security controls.
Browser storage and downloads
Authentication/session settings and operation identifiers support access and interrupted-request recovery. Guest tokens and the latest request identifier are stored in the current tab’s session storage; keep this capability private. Search inputs are not persisted by the search workflow in browser local or session storage. Downloaded PDF, CSV and JSON files are under your control.
Opening source websites
Opening a source link takes you to an independent website with its own privacy practices. That site receives the request from your browser, and its URL may include contact information. Review the destination before opening or sharing a link.
Aggregate usage counters
When enabled, the app counts visits, return visits, source-link opens, PDF exports and CSV exports using fixed event names. These counters do not include search details, report content, source URLs, session tokens or a unique visitor identifier. A UTC date in local browser storage records the last visit day to distinguish a later-day return. Clearing that date resets this browser’s visit comparison. These totals describe actions, not unique people.
Advertising
Public pages on contactcheckup.com, including the homepage and reviewed guide articles, are prepared for Google AdSense. Ads remain disabled while Google approval and deployment checks are pending. When activated, ads may appear on the homepage introduction and guide articles. Ads are never shown on the scam check form or on check results, because those pages show what you typed or pasted. Ads are also not shown on sign-in, sign-up, password, account settings, history, error or loading screens. Page addresses and titles never contain searched names, emails, phone numbers or addresses, and this information is not sent to Google. When activated, Google and its advertising partners may process the public page, IP address, browser information and cookies or similar identifiers to serve, measure and protect ads, according to your privacy choices and their policies. Searched contact details, report content, session tokens and account data are not advertising targeting inputs. Public pages provide advertising privacy choices and a way to change consent. Declining advertising consent does not prevent reading the website or using free searches.
Partner links
Some results and guides include optional links to paid services, such as identity theft protection, data removal or password managers. These are plain links: no partner code runs on our pages, nothing you typed or pasted is added to the link, and the partner is not told which ContactCheckup page you came from. If you choose to open one, you leave ContactCheckup and the partner’s own privacy policy applies. ContactCheckup may earn a commission if you sign up. Partner links never change a scam check result.
Public FTC complaint data
Phone number pages and check results may show how many complaints a number received in the FTC’s public Do Not Call complaint data, when they were made and what callers said the calls were about. We import only the calling number, the complaint date, the call subject and whether it was a robocall. We never import or show the names, locations or phone numbers of the people who complained. The FTC does not verify these complaints and caller ID can be faked. If a number is yours and you want its page reviewed, contact us through Help and we will review it for removal.
Affiliate links
Some tiles marked "Featured" link to partner services, such as identity protection. If you sign up through one, we may earn a commission. These links carry no tracking script from us, and we never share your searches or contact details with partners.
Scam reports
Reporting a scam number or text is separate from searching: a search never creates a report. When you send a report, we store the phone number, the scam type, any text message you paste (after removing codes, card numbers, email addresses and link paths), the links found in it, your optional note, and a hash of your random browser identifier used only to limit repeat submissions. If you are signed in, the report is linked to your account. Reports stay private until an administrator approves them. Approved reports are published on public pages that show the number or the redacted message, the scam type, how many people reported it and when; they never show who reported it, and your optional note is never published. Rejected reports are kept privately for abuse review. If a public page is about your number or contains your information, use the Support page to ask us to review it for removal.
Requests and corrections
Use the contact form on the Support page for access, correction, deletion or data-handling questions. Do not send full personal records or session tokens in an initial message. A correction in ContactCheckup does not change the source website; contact that publisher separately to request a source correction.