What enters a BeeFind workspace, and why.
This page gives members and business contacts a practical view of the account, research, contact, and security information BeeFind processes to run the product.
Last updated: October 1, 2026
Account and workspace information
To create and secure a workspace, BeeFind processes the account identifier issued by Firebase Authentication, email address, display name when available, verification state, plan and search allowance, and account-review or notice status.
To make the workspace useful, we store the searches a member runs, including the category and locality supplied for the brief, source-backed records returned to that workspace, review choices, history timestamps, and export actions.
Business research records
BeeFind may collect public business information such as business name, location, category, public website, published phone number, published email address, registry identifier, and source or evidence URL. Availability varies by locality, category, and the public sources relevant to a search.
Contact extraction is limited to details explicitly published on a validated official business website or to records from approved data sources. The service stores the usable result and evidence context; it does not store raw copies of official web pages as a general page archive.
Search-result providers can be used only as temporary pointers to candidate official sites where their terms require that handling. The exported record should identify the applicable source context rather than presenting results as an unqualified database claim.
Outreach information you choose to add
If a member enables outreach, the workspace stores sender identity, SMTP host and port, campaign subject and body, selected recipient email addresses, delivery state, unsubscribe state, and limited provider message identifiers. The member chooses the recipients and controls each send.
SMTP login credentials are optional. When supplied, they are encrypted before server-side storage and are not displayed back to the browser. BeeFind keeps unsubscribe suppression information so a recipient who opts out is not sent another campaign by the same member workspace.
Security and service operation data
We process timestamps, error codes, rate-limit events, and privacy-reduced network fingerprints to maintain availability, prevent abuse, investigate security problems, and enforce search and send limits. The application is designed not to retain raw IP addresses in its application database.
Operational logs are used to diagnose failures and protect the service. They are not used to create advertising profiles or sold to third parties.
What BeeFind does not collect through research
The research workflow does not access login-only pages, private accounts, browser session cookies, CAPTCHA-protected content, or private network resources. It does not attempt to collect personal inbox content, social-platform messages, or private profile details.
BeeFind also does not treat a public business detail as permission to contact a person. Members must decide whether their own intended use and outreach meet applicable requirements.
How to ask about data
Members can request access, correction, or deletion assistance for their account and workspace information by contacting the BeeFind operator from the verified account email. Recipients can use an outreach-message unsubscribe link to stop future sends from that member’s workspace.
Read the full privacy notice for retention, provider, and request-handling information, and the responsible outreach page for the product standard.