Who this notice covers
This notice describes how [LeadWhistle legal entity or owner name] ("LeadWhistle," "we," "us," or "our") handles personal information through the LeadWhistle service and website.
LeadWhistle has two different roles. For workspace accounts, billing, security, support, and operation of our own service, LeadWhistle decides how information is used. When a customer connects a website and asks LeadWhistle to monitor lead activity or store permitted lead contact details, LeadWhistle processes that information for the customer under the customer's instructions. The connected business decides why the lead information is collected and is responsible for its own privacy notice and choices.
What LeadWhistle does
LeadWhistle helps agencies and business owners monitor public website and lead paths, understand observed incidents, and organize follow-up with leads a connected business has chosen to retain.
Information collected
- Account information: work email, workspace, sign-in records, subscription and plan status.
- Monitoring information: connected public URLs, check results, timestamps, response details, public-page fingerprints, incident history, and optional customer-approved browser evidence.
- Lead information: only the fields the connected business enables. These may include name, email, phone, and, for a completed submission, a message. Completed-submission capture must be enabled by the business after it confirms that a disclosure is live. Unfinished-form callback capture is limited to enabled contact fields and requires the visitor to accept the displayed follow-up choice.
- Lead activity: form starts, progress milestones, completions, abandonment points, source pages, and timestamps. Aggregate funnel events are designed not to contain names, email addresses, phone numbers, messages, or field values.
- Device and operational information: IP address and request logs where generated by the service or its infrastructure, browser and device information, alert delivery status, outreach activity and notes entered by workspace users, and bounded usage data for browser checks.
- Payment information: subscription, invoice, and payment-status information from our payment provider. LeadWhistle does not store full payment-card numbers.
Sources of information
We receive information directly from account users; from connected websites, forms, and integrations configured by a workspace; automatically when the service is used; and from service providers that support authentication, hosting, alerts, payments, and browser checks.
How information is used
We use information to provide and maintain monitoring; detect and explain observed failures; deliver alerts; measure lead-path performance; organize customer follow-up; generate client-safe reports; authenticate and secure accounts; process subscriptions; enforce plan and usage limits; provide support; comply with law; and improve the reliability of the service.
LeadWhistle does not use lead contact details collected for a connected business to market unrelated LeadWhistle services to that lead, train general-purpose AI models, or build advertising profiles.
Legal grounds where required
Depending on the activity and applicable law, processing may be necessary to perform a contract, comply with law, protect the service and users, pursue legitimate operational interests, or act on consent. When LeadWhistle processes lead information for a connected business, that business is responsible for identifying its lawful basis and giving any required notice or choice.
Sharing and service providers
We disclose information to infrastructure, database, authentication, email, SMS, payment, analytics, security, customer-support, and browser-execution providers that help operate LeadWhistle. These providers are selected by LeadWhistle or, where a workspace connects its own integration, by that workspace. We may also disclose information when required by law, to protect rights and safety, or as part of a merger, financing, acquisition, or sale of assets subject to appropriate safeguards.
Lead contact details are limited to authorized members of the connected workspace and are excluded from client-safe incident reports and signed report exports. LeadWhistle does not exchange lead contact details for money or use or disclose them for cross-context behavioral advertising.
A current subprocessor list and any applicable data-processing addendum will be made available at [subprocessor and DPA location] before launch.
Retention and deletion
Workspace owners choose a supported retention period for confirmed submissions and permitted unfinished-form callback details. The current product supports 30, 90, or 180 days. Contact records are scheduled for deletion from the active Lead Inbox after the selected period, and an authorized workspace user can delete a record sooner. Aggregate funnel and monitoring counts may remain after the identifying contact record is deleted. Account, billing, security, and legal records may be retained for as long as reasonably necessary for the purpose described or as required by law; the final schedule must be confirmed before launch.
Consent and client responsibility
The connected business is responsible for placing an accurate notice at or before collection, identifying the business and purpose, selecting only the fields it needs, linking to its privacy notice, providing any legally required choices, and obtaining any required approvals. Marketing consent must be separate from a service or callback request when the law requires it. LeadWhistle does not provide legal approval or automatically publish legal copy to a connected website.
Cookies and local storage
LeadWhistle may use cookies or browser storage that are necessary for sign-in, security, preferences, and core service operation. Any non-essential analytics or advertising technologies must be documented here and, where required, presented through an appropriate consent choice before they are enabled. [Confirm the production cookie and analytics inventory.]
Security
Lead contact payloads are encrypted before storage, workspace routes require authentication, and client-safe exports omit lead contact details. We use administrative, technical, and organizational safeguards intended to protect information, but no online system can guarantee absolute security. Report suspected unauthorized access to [privacy or security contact].
International processing
LeadWhistle and its providers may process information in countries other than the one where the user or visitor is located. Before serving people in jurisdictions that restrict international transfers, LeadWhistle must document the relevant transfer mechanism and make any required addendum available. [Confirm launch regions and transfer mechanism.]
Your privacy choices and requests
Depending on where you live, you may have rights to request access, correction, deletion, portability, restriction, or an appeal, and to object to or opt out of certain uses. For information collected through a connected business, contact that business first because it controls the lead relationship. You may also contact [LeadWhistle privacy contact]. We may verify the request, coordinate with the connected workspace, and respond within the period required by applicable law. Exercising a privacy right will not result in unlawful discrimination. See Data choices for the request path.
Children
LeadWhistle is a business service and is not directed to children. Customers must not knowingly use LeadWhistle to collect children's personal information without first confirming that the use and required parental or guardian permissions comply with applicable law. [Counsel to confirm the minimum age and launch-region wording.]
Changes
We may update this notice when the product, providers, or applicable requirements change. We will update the effective date and provide additional notice when required for a material change.
Contact
Privacy questions may be sent to [LeadWhistle privacy contact]. Legal notices may be sent to [business mailing address].