Fast Home Help privacy framework

Fast Home Help is operated by Brutal Honesty Solutions LLC through BHS Home Solutions. The property uses request information to classify a home-service need, preserve routing consent, and support an approved service-routing handoff when one is available.

Information used for routing

The current flow may process the consumer's problem description, service classification, ZIP code, consent version and text, acceptance timestamp, traffic-source evidence, landing/referrer information, user agent, and call-recording state. The current control surface is designed to keep commercial handoff fail-closed unless durable consent storage succeeds and an approved route exists.

Consent and transmission

No consumer request should be transmitted to a commercial provider or routing partner unless the required disclosure and affirmative consent for that request are recorded and the applicable route is approved. A general privacy page is not a substitute for request-specific consent.

Partner data controls before activation

Before activating a route that sends consumer information to a third party, the applicable commercial agreement and implementation should define the permitted purpose, data fields, recipient, retention, security requirements, onward-transfer or resale restrictions, deletion obligations, consumer-rights handling, incident responsibilities, and any legally required notices or authorizations.

Purpose limitation

BHS intends consumer request data to be used only for the disclosed home-service routing purpose and related operational, compliance, fraud-prevention, reconciliation, or recordkeeping needs. A partner relationship does not transfer ownership of BHS proprietary analytics, routing logic, source-provenance methods, consent architecture, or unrelated BHS data.

Traffic-source provenance

Traffic-source information may be retained to support partner compliance, campaign eligibility, fraud review, attribution, and dispute resolution. Sources that are prohibited or cannot be verified are not eligible for commercial transmission under the current control surface.

Call recording

The current control surface has call recording disabled. No representation that a call is recorded should be made unless recording is actually enabled for that flow and all required disclosures and permissions are implemented.

Changes

This framework should be updated if the data collected, partner route, call flow, storage architecture, or applicable legal requirements change.

Partner-activation control:

Do not activate a new data handoff merely because a partner account exists. The actual route, disclosure, consent, permitted data use, and operational responsibilities must be configured and verified for that relationship.

Updated for partner-readiness review: September 20, 2026.