PROFILE FINDER / DATA & PRIVACY

Privacy, in plain sight.

What happens to an identifier when you search, what the site remembers, and the choices you can make before you begin.

THE DATA FLOW

The distinction that matters: Privacy Mode keeps a scan out of this site’s search history. It does not stop the scan provider from receiving the query.

SEARCH INPUTUsername or email
EXTERNAL REQUESTScan service receives it
YOUR CHOICEHistory on or off

01. Who and what this covers

This notice covers Profile Finder at profilefinder.tools, including username search, email lookup, optional Google account connection, search history, the research blog and support requests. “We” refers to the operator of Profile Finder. You can reach us at [email protected].

A username or email address can relate to a real person even when it is publicly visible. Before submitting one, make sure you have an appropriate reason and any permission needed to assess it. Please do not enter passwords, private messages or other information the search does not require.

03. What Privacy Mode changes

Privacy Mode is off by default. Turn it on before starting the scan. For that scan, the browser skips this site's task-creation, result-saving and task-completion requests. The query and results are therefore not added to application search history through that workflow.

The scan service still receives the identifier and request metadata. Privacy Mode does not disable the browser identifier, statistics, ordinary infrastructure logs or requests to external asset hosts. It does not erase previous searches, change a provider's retention practices, or make the scan anonymous. Closing the tab removes the live view; it does not recall requests already sent.

04. Browser identity and Google connection

The site sets a first-party cookie named osinttools_user_id. Its legacy name remains in use so existing visitors can keep their linked history. It is assigned even if you do not connect Google. The configured lifetime is ten years and is renewed on visits; your browser can clear or limit it sooner.

If you choose to connect Google, Google handles its sign-in page. Profile Finder uses the returned Google identifier, basic profile information, email address and profile-image URL to associate a site account. We do not receive the password you enter on Google's page. See Google's sign-in documentation for how profile and email permissions work.

Signing out clears the current browser identifier cookie. It does not delete stored account or history records. Clearing cookies can also disconnect a browser from guest history; it is not a reliable substitute for deleting the records first. Other people using the same browser profile may be able to access its linked history.

05. Other browser storage and requests

A “Run again” action can place the selected search type and query in session storage while you return to the search page. The page reads and removes that pending-search value. Session storage belongs to that browser tab's browsing session and can also be cleared through browser controls.

Opening a result takes you to an independent site. Displaying a source icon can cause your browser to request that site's origin from Google's favicon service. These requests also convey ordinary network information, including the visitor IP address. An icon request is not a request for the full saved result.

Google Dorks builds optional search links from the username or full email address you submit. Opening one sends that identifier and the selected search operators to Google in a new tab, where Google handles the search under its own policies. Privacy Mode still allows these outgoing searches. Copying a generated query places it on your clipboard when you choose the copy action.

The site loads typography from Google Fonts, Tailwind from its CDN, jQuery from code.jquery.com and Font Awesome from cdnjs. Fetching these resources sends network request information to their hosts. Google explains its font delivery in the Google Fonts FAQ. Your browser's developer tools can show the requests made during a particular visit.

06. Analytics and blog activity

The shared page layout loads Google Analytics to understand use of the site, such as page visits and device or browser characteristics. It may use cookies or similar identifiers. It is loaded separately from the search-history setting, so enabling Privacy Mode does not turn it off.

Google describes its handling of information from partner sites, including page URLs and network information, in How Google uses information from sites or apps. Browser privacy settings, content controls and Google's own controls can affect what is collected. We do not promise that a search is invisible to infrastructure or analytics providers.

When you open an available blog article, the site can increment its view count. Choosing to mark an article as useful increments a feedback count. These counters do not create a separate application table of individual likes, though the HTTP requests can still appear in infrastructure logs.

07. Messages and support records

The contact form collects an optional name, reply email, category and message. We store these with a reference number, review status and timestamps so the request can be received and handled. A short rate-limit cache uses a hash derived from the request IP and reply email. Email sent directly to support is also handled through the email services used for that correspondence.

Keep a report limited to what is needed. If you are reporting a problem with someone else's information, a public source link and a description are usually a better starting point than a copy of the information itself. We may need to verify your relationship to a record before responding to a disclosure or deletion request.

08. Why information leaves this site

Running a scan requires sharing its query with the configured scanner. Optional sign-in involves Google; analytics and external assets involve their respective providers. Hosting, delivery, database, logging and email services can process information as part of operating and supporting the site. A provider may process it in a different country from yours under its own arrangements.

We may also need to handle or disclose records to respond to a valid legal requirement, address abuse or a security incident, or protect the rights of people affected by the service. This notice does not set the retention periods of independent providers, and turning off application history does not bind them.

09. Retention, deletion and your choices

Search and account records remain available until deleted; the application does not currently apply an automatic expiry schedule to them. Support records likewise have no fixed automatic deletion period configured here. Temporary application caches may expire independently. We cannot give a single retention period for hosting logs, provider records or backup copies.

You can delete an individual task in the history interface, or delete the current application account and its linked username and email history from the user workspace. These actions permanently remove the relevant active database records. They do not remove the original profiles, erase messages already sent to support, or establish when independent provider copies and backups are erased.

For an access, correction, deletion or other privacy request, email [email protected] with a limited description of the record and the action requested. The options and rights available can depend on your location and the circumstances. We may need to clarify the request or verify authority, and may need to retain information to resolve a dispute or meet a legal obligation.

10. Security and changes to this notice

No internet service can guarantee complete security. Use a device and browser profile you trust, limit the identifiers you submit, and avoid storing sensitive research on a shared device. Report a suspected exposure privately through the contact page.

Profile Finder is not designed as a service for children. Please contact us if you believe a child has submitted information that needs attention.

When the service or its data practices change, we will update this notice and its date. Read it together with the Terms of Service and search methodology, especially before relying on a new workflow.