Counsel-review draft
Privacy notice
This preview does not transmit form information. The sections below define the policy that must be finalized against the actual live forms, vendors, routing, analytics, retention, and operating states.
Scope
This draft covers the parent business website and contractor availability inquiries. Each consumer-facing lead source must use a notice that accurately reflects its own operator, forms, calls, vendors, disclosures, and routing.
Information we expect to collect
Business contact details, service and territory information, website and company details, the contents of a request, communication preferences, and technical records needed to operate and secure the service. Consumer lead sources may also collect project, contact, source, consent, delivery, and call information as disclosed on those sources.
How information is expected to be used
To respond to requests, evaluate market and service fit, provide and improve services, route authorized opportunities, communicate about an account, invoice and collect, prevent abuse, maintain records, and comply with law. Information should not be used for a materially different purpose without an appropriate notice or permission.
Contractors and service providers
Information may be disclosed to an eligible contractor when needed to respond to the consumer’s request, and to vendors that support hosting, communications, CRM, analytics, payment processing, security, professional services, and business operations. Final language must identify categories and any legally required details accurately.
Calls, text messages, and email
The live forms must present channel-specific consent language and retain the version and timestamp submitted. Consent to marketing texts must remain optional where required. Opt-outs and do-not-contact requests must be honored, and transactional communications must remain distinguishable from marketing.
Cookies and analytics
The final notice must describe the analytics, cookies, pixels, call tracking, and similar technologies actually enabled. No tool should be described as active until it is configured and verified.
Retention and security
Records should be retained only for legitimate operational, contractual, dispute, compliance, and legal purposes under an adopted retention schedule. Reasonable safeguards will be used, but no system can be promised to be perfectly secure.
Choices and requests
The final notice must provide a working method for access, correction, deletion, opt-out, or other requests that apply under relevant law, along with identity-verification and appeal details where required.
Children and geographic scope
The services are intended for business users and adults requesting local services, not children. State-specific disclosures and rights must be added before operating where they apply.
Contact and changes
The final version must contain a monitored privacy contact, legal mailing address, effective date, change-notice method, and any required regulator or representative information.