Privacy Policy

This notice covers the public SpiderFoot.tools pages, username, email, and IP workflows, optional Google connection, browser- or account-linked search history, blog interactions, and the contact route.

Statements about storage and data flow are based on the current ThinkPHP controllers and services, browser JavaScript, routes, shared page template, feature flags, database columns, and local response headers. Provider-side retention and production infrastructure outside this codebase are identified as unknown rather than estimated.

For a supported username parameter on the home page or email parameter on the email page, an early page script tries to place the value in sessionStorage under spiderfoot_pending_search. It then removes that parameter from the visible URL before the shared external page scripts load. The scanner consumes and removes the stored value.

If session storage is unavailable, the script leaves the URL fallback in place. Even when cleanup succeeds, it cannot undo the initial HTTP request, an earlier browser-history entry, network or extension access, or infrastructure logging that occurred before the script ran.

Every page request receives the first-party browser identifier described above. A database user is created when that browser starts its first valid username or email task. The user record stores the cookie identifier, site language, Cloudflare country value, Accept-Language value, and created/updated timestamps.

A history task stores the raw query, scan type, task identifier, completion state, normalized result records, simplified site names, visitor IP, created/updated timestamps, and—when those paths run—public-web results and AI status, errors, duration, search output, and summary output.

History is available to the current browser identifier; Google login is not required. Anyone with access to the same browser profile may therefore be able to view its username and email history. IP lookups are not displayed in this history interface.

If you connect Google, the OAuth request asks for openid, email, and profile. The returned Google subject identifier, name, email address, and profile-image URL are stored with the user record. The Google password is entered with Google, not SpiderFoot.tools, and the access token used to request profile data is not written to the user table by this code.

The shared layout loads Google Analytics property G-WMG0MQ892B on page load. Google describes its default implementation as collecting user counts, session statistics, approximate geolocation, browser/device information, a first-party _ga client identifier, and interaction data.

The site’s Analytics configuration supplies a page location and referrer with query strings removed. For supported username/email deep links, the earlier URL-cleanup script runs before the Analytics script. This reduces the chance of a query appearing in the configured Analytics page-view fields, but it is not a promise that no infrastructure, browser component, or provider ever sees the original URL.

No application-level consent banner or Google Consent Mode call was found before Analytics initialization. The Analytics dashboard’s retention, regional, Signals, or advertising-link settings are not stored in this repository and therefore are not described as configured.

Pages also request Google Fonts, Tailwind’s CDN script, Font Awesome through cdnjs, and jQuery from code.jquery.com. Those hosts receive ordinary browser request information such as IP address, user agent, and referrer data. The shared template uses a strict-origin-when-cross-origin referrer policy.

Advertising status: no Google AdSense, Ezoic, or other advertising-network script was found in the current application layout. This notice therefore does not describe advertising as an active application feature.

• Use the history pages to review username and email tasks linked to the current browser identifier.
• Clear spiderfoot_pending_search by closing the browser session or clearing this site’s session storage. Browser controls can also clear the site identifier and Analytics cookies.
• Logout deletes the current site identifier cookie. A later page request creates a new identifier; logout does not delete the existing database user or history rows.
• Google-account authorization can be managed through Google, but revoking it does not automatically erase the profile fields or history already stored by SpiderFoot.tools.

No working self-service history-delete, account-delete, or Google-unbind backend was found in the current application. For an access, correction, or deletion request, email [email protected]. We may need enough information to locate the relevant record and verify that the requester is entitled to control it; do not send a password or authentication secret.

Depending on the law that applies to your circumstances, you may have rights concerning personal data, such as requesting access, correction, deletion, restriction, or objection. Those rights and any exceptions depend on the applicable law; this notice does not state that every right applies identically to every visitor.

The application validates email and IP formats, checks task ownership against the current browser/account identifier, and uses timestamped signed-request validation on public-web and AI endpoints. These are implementation controls, not a guarantee that the service or any provider is risk-free.

File-based application logging is enabled. The reviewed code explicitly logs provider errors, Google OAuth binding errors, Radar errors, and AI provider responses when the AI worker runs. Web servers, reverse proxies, and Cloudflare may separately process or record visitor IP, timestamps, paths, referrers, user agent, routing data, and other request metadata for delivery, debugging, reliability, or abuse response.

No production log-retention schedule, backup policy, encryption-at-rest configuration, security-audit schedule, or complete access-control policy was found in the repository. This policy therefore does not claim any of those practices.