It does not make a scan anonymous or stop the scanning service from receiving the identifier. Ordinary page requests, analytics, and provider processing can still occur.
01. Scope and purpose
This policy applies to spiderfoot.app, operated as SpiderFoot.app (the “Service”). References to “we,” “us,” and “our” mean the operator of this website. It covers the public website, username and email scans, optional Google account connection, search history, blog interactions, and support correspondence.
We use information to perform the scans you request, associate saved results with your browser or account, manage support requests, measure website usage, maintain and protect the service, and respond to applicable legal requirements. The explanations below describe the current application and its configured integrations. External providers have their own data-handling practices.
02. Data at a glance
| Activity | Information involved | Where it goes or stays |
|---|---|---|
| Visit a page | Connection IP, requested page, browser headers, and browser identifier | Website infrastructure, loaded resource hosts, and Google Analytics |
| Run a standard scan | Username or email query, scan type, task status, positive matches, IP, and timestamps | The configured scanning service and our user/search-history records |
| Run a private scan | Query and the request information needed for source checks | The configured scanning service; no first-party search task or saved matches for that scan |
| Connect Google | Google account ID, name, email, and profile-image URL | Google's authorization service and our user record |
| Display source icons | The origin of a result's source site and ordinary connection information | Google's favicon service, requested by your browser |
| Contact support | Optional name, reply email, category, and message | Our support-request database or support mailbox, depending on the channel you use |
03. Scans and privacy mode
Standard scans
Privacy mode is off by default. A standard scan sends the query to this website to create a history task, then requests source checks from the configured scanning service. The browser receives source statuses, links, reasons, and any extra information returned. Positive matches can be normalized and saved as the scan progresses.
All returned rows are available in the live category log. Negative, unknown, skipped, and failed checks are not saved as positive matches. The saved history is therefore not a permanent copy of the entire live response log.
Private scans
When enabled before scanning, privacy mode skips history-task creation, result saving, and completion updates for that run. The submitted username or email address is still sent to the scanning service with the category, page, and request information needed to perform the checks.
This setting does not disable the browser identifier, website analytics, infrastructure logging, or external-service processing. Scanning requests can include the identifier in the request URL, which the receiving service and its infrastructure may process. It also does not delete older scans saved in standard mode.
Understanding the output
Username checks and email registration signals are described in our search methodology. A registration signal does not provide access to a mailbox or establish who owns an account. Submit only an identifier you have an appropriate basis to investigate.
05. Accounts and saved history
A standard scan can create a browser-linked user record without Google login. That record may include the browser identifier, language, country information where supplied by the infrastructure, a shortened browser-language header, and timestamps. Search tasks store the query, scan type, task identifier, completion state, normalized positive results, simplified source information, visitor IP, and timestamps.
If you choose to connect Google, the authorization request uses basic identity, email, and profile scopes. Returned account ID, display name, email, and profile-image URL can be stored with the user record. The Google password you enter is handled by Google, not received by this application.
The current browser/account identifier determines which history is available. You can delete one search from its list or details page, or delete the current account and all search history linked to it through the user workspace. These actions remove active application records and cannot be reversed through the website.
Opening or liking a blog article can send its article ID to update aggregate counters. The blog controller does not create a separate per-reader action record, although normal request information and cookies still accompany the request.
06. Support requests
The contact form stores your optional name, reply email, selected category, and message with a public reference number, review status, and timestamps. These records allow us to review the issue and identify follow-up correspondence. Email sent directly to support is handled in the support mailbox.
To limit repeated form submissions, the application combines the connection IP and reply email into a one-way hashed cache key, retained for 60 seconds after a successful submission. The form does not write the raw IP or that key into the support-request table.
Support requests are separate from browser/account and search-history records. Deleting your account does not automatically remove a previous contact message or email conversation. To ask about that correspondence, contact us and include its reference number if available. Do not send credentials or unrelated sensitive information.
07. Services, analytics, and sharing
Scanning services and public sources
The configured scanning service receives the query and request information needed to run the supported source checks, including in privacy mode. Its processing and retention, and those of the checked services, are separate from first-party search history. Opening a result sends a new request from your browser to the external site.
Website infrastructure and page resources
The web server and Cloudflare, where used, process connection and request information. Available headers can supply the visitor IP and country; standard scan history stores the connection IP. Google Fonts, Tailwind's resource host, cdnjs/Font Awesome, and code.jquery.com receive ordinary connection information when their resources load.
Google services
The shared page layout loads Google Analytics for usage measurement. Google also provides optional account authorization, fonts, and source-site icons. The favicon request contains a source site's origin and is sent without a referrer; Google still receives the requested origin and ordinary connection information such as IP and browser headers. The current shared layout does not include an advertising-network script.
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.
Providers may process information in countries different from yours. Their policies and settings govern their own records. Information may also be disclosed where necessary to handle a request, comply with applicable law, or protect the service and the rights of others.
08. Retention and security
User and search-history database records currently have no automatic expiry in this application; they remain unless deleted. Contact messages are retained for support handling and have no fixed automatic deletion schedule. The cookie, session-storage, and rate-limit periods above describe those specific mechanisms, not every copy of related information.
Infrastructure logs, backups, analytics records, scanning-service records, and support email have separate retention arrangements. Removing an active account or task does not establish when a log, provider record, or backup outside the active database is erased. We do not promise a deletion deadline for systems we do not control.
Input validation and restrictions on browser/account history access help reduce risk, but no online service can guarantee absolute security. Protect your browser profile, connected Google account, and any results you save or share. Send support only the information needed for the request.
09. Your controls and rights
- Enable privacy mode before starting a scan to avoid saving that scan to first-party history.
- Use the user workspace to review or permanently delete individual tasks, or delete the current account and its linked history.
- Use browser settings to manage local cookies and session storage. Signing out removes the current browser identifier cookie, rather than deleting database records.
- Manage Google permissions through Google. Revoking permission does not automatically erase profile fields already stored here.
- Use available browser and provider settings to manage analytics storage.
Depending on the law that applies to you, you may have rights to request access, correction, deletion, portability, restriction, objection, or withdrawal of consent where relevant, and to raise a concern with an appropriate authority. Contact [email protected]. We may need enough information to locate the records and verify your authority to make the request; do not send a password or authentication secret.
10. Age requirements
The service is intended for adults aged 18 or over. We do not invite children to use its research workflows or submit personal information. Contact us if you believe a child has provided information through the service.
11. Updates and contact
We may revise this policy as the service, providers, or information flows change. The date above identifies this published revision. External pages linked from results have their own privacy practices; public availability does not remove limits on how information may be used.
For privacy questions, requests about your records, or a correction to this policy, use the contact page or email [email protected]. Include only the information needed to identify the issue.