1. Who this policy covers
This Privacy Policy describes how Joe Lumi LLC, doing business as Book More Leadz, handles personal information in connection with its website, lead-generation services, business accounts, and related communications. Our mailing address is 123 Main Street PA. For privacy questions or rights requests, contact [email protected]. This policy covers site visitors, contractor users, homeowner/requester inquiries, and people communicating with us.
A contractor receiving a lead may independently determine how to use it to respond to the service request and is responsible for its own privacy practices. We do not control third-party sites simply because we link to them. Some disclosures below describe a feature only when it is enabled and used; they do not claim that an inactive payment, advertising, recording, or analytics integration is operating.
2. Information we collect
Depending on your interaction, we may collect contact details (such as name, business name, phone, email, and service/project location); requested trade, project descriptions, photos you choose to submit, preferences and timing; self-reported homeowner or property-authority information; source/consent and verification records; account identifiers, user roles, territories, lead IDs, delivery records, dispute correspondence, and support requests.
Payment-related records may include the selected payment method, processor customer/token references, limited masked payment details, authorized amounts, invoices, credits, and refunds when a payment service is enabled. Do not send full payment credentials to us by chat or email. Processor-hosted collection, when configured, is governed by the processor's own notices as well.
Technical information can include IP address, user agent, request timestamps, referring pages, limited attribution parameters, service error logs, session/security identifiers, and necessary cookies or browser storage. The actual collection depends on enabled site components and hosting. Communications may include SMS/email content and call metadata; recordings or transcripts are collected only when the feature is active and the legally required notices/consents have been obtained.
We do not need Social Security numbers, government ID scans, precise continuous device location, health records, financial account credentials, or other unnecessary sensitive data to evaluate an ordinary service inquiry. Please avoid including such information in descriptions, photos, chat, or attachments.
When you use the contractor workspace, we also keep application drafts and review decisions, service-area and capacity requests, support and lead-credit correspondence, notification preferences, and an activity history linked to your account. Agreement records include the policy version, document fingerprint, accepted program rules, user and acceptance time. If the operator enables additional acceptance evidence, a salted IP fingerprint and user-agent information are recorded. Authorized support administrators can open an account in read-only support preview; the access is recorded. These account records are different from the public automated chat, which does not itself retain a server-side conversation transcript.
The territory page initially shows an illustrative location graphic. Choosing to load its optional OpenStreetMap view sends a normal browser request to that external map provider, including the requested map area and standard connection information. The marker is geographic context, not continuous device tracking or an official protected-territory boundary. External fonts and other installed website components can make their own requests as explained elsewhere in this policy.
When you use the guided contractor application in Emma, verified account information and structured application drafts are saved in the same contractor workspace used by the application form. Ordinary public chat messages are not retained as a transcript by this feature. Account actions, authentication events, record access, changes and integration outcomes may be recorded in a restricted activity log. The operator configures retention; secrets such as passwords and verification codes are not included in that log. Location maps may load automatically after a lookup according to the published map setting, sending the selected location and normal browser request data to OpenStreetMap. County directories and county-to-zip relationships may be processed from configured geographic sources. These features do not make a map or zip centroid proof of a particular service address.
3. Where information comes from
Information comes from you, the person making a service request, authorized company users, our website and communication systems, contractors responding to that inquiry, and advertising/referral partners or other service providers where disclosure is lawful. A referral partner's assertion that data can be shared is not, by itself, proof of unlimited contact permission.
We may combine records for the same account, contact, project, or delivery to verify an inquiry, avoid duplicates, maintain suppression preferences, investigate fraud, and reconcile billing. We should retain source and permission records appropriate to the contact method and intended recipients.
4. How information is used
We use information to evaluate and route requested services; check service-area availability and eligibility; provide account access; verify lead quality and contact permission; deliver leads and authorized communications; operate requested features; reconcile payments and credits; respond to disputes and rights requests; prevent misuse; maintain security; and comply with legal obligations.
We may measure the performance of our own services using appropriately limited information. Promotional email, texts, advertising attribution, targeted advertising, or other secondary uses require their own applicable legal basis, settings, notices, and opt-out mechanisms. Submitting a request does not mean consent to unrelated marketing by everyone who receives the information. We do not use this policy itself as a marketing-consent form.
5. Who receives information
A matched or participating contractor may receive the contact and project information reasonably needed to respond to the homeowner's requested service. We charge businesses for eligible delivered inquiries. Depending on the applicable law and the particular disclosure, compensated lead delivery may be considered a "sale," "sharing," or another regulated disclosure of personal information. We do not make a blanket promise that no personal information is sold when the business model includes compensated lead delivery.
We may disclose necessary information to hosting/security providers, communications providers (such as Twilio when configured), account/CRM services, customer-support providers, and payment processors when enabled. Provider access must be limited to legitimate contracted purposes with appropriate safeguards. Enabling a new recipient or use may require an updated inventory, contract, notice, or consent.
Information may also be disclosed to comply with valid legal process or law; protect safety, security, or legal rights; investigate suspected fraud; advisors under appropriate confidentiality; or in a proposed or completed business transfer with applicable protections and notices. We may disclose information at your direction or with valid consent.
Mobile opt-in/consent records are not furnished to unrelated third parties or affiliates for their independent marketing campaigns. Providing a requested lead to an identified or properly disclosed contractor is a separate processing activity that still requires a valid basis and appropriate notice. No statement here creates permission to sell mobile-marketing permission or evade an opt-out.
6. Website chat and external fonts
The landing-page Emma assistant in this release uses local, rule-based responses. Its conversation is held in page memory and is not saved by this widget as a server-side transcript or sent to an external language-model service. Closing/reloading the page can clear it; a session-storage preference can remember whether the widget was dismissed. A zip entered for an availability check is transmitted to the site's availability endpoint. The server may query Zippopotam.us to validate the U.S. zip; that lookup supplies the zip, not the page chat transcript. The browser and server may still produce ordinary request/security logs. When an operator chooses an embedded Gravity Form or an external form handler instead, submitted form data is processed and retained according to that configured system, its notices and the operator’s practices.
Clicking an email, phone, external contact, or account link opens a separate channel whose messages may be retained under that channel's practices. Existing homeowner SMS conversations and buyer portal messages are separate from this landing-page widget and can be stored by the platform and the configured messaging provider.
When remote Google Fonts are enabled, your browser requests the selected fonts from Google's font services and exposes connection information such as your IP address and browser request details to that provider. Administrators can select system fonts or disable remote fonts. No font files are packaged with this release. If chat recording, a language-model provider, a live-chat system, or additional third-party widgets are later enabled, the notice and consent controls must be reassessed before that processing starts.
8. Messages, contact permission, and recordings
We and contractors must distinguish a response to a specific requested service from unrelated promotional outreach. Permission must match the named/disclosed recipients, channel, purpose, and method as required by applicable law. For marketing calls/texts that require express or written consent, a separate clear consent mechanism must be used; consent is not a condition of an ordinary purchase where law prohibits such conditioning.
Use STOP or another legally effective method to revoke texting consent, and use HELP or the contact information provided for assistance. Marketing email must include an effective unsubscribe method and applicable sender information. Necessary account/security notices may continue when law permits and are not promotional. We retain minimal suppression information when reasonably necessary to honor a request rather than simply deleting the opt-out.
A call-recording notice and all required permissions must precede recording. Call duration, a connected status, or inclusion in a lead record does not automatically establish legally sufficient recording consent. Notify us if a contact permission or opt-out appears incorrect so it can be investigated and corrected.
9. Retention and deletion
We retain personal information only for as long as reasonably necessary for the purposes described in this policy, subject to applicable legal requirements and documented exceptions. Retention should reflect the purpose of collection, delivery/credit review, account history, consent and suppression evidence, tax/accounting requirements, security, and an actual legal hold. We should periodically review whether information is still needed and delete, deidentify, or restrict it when it is not.
This policy does not assert that a scheduled automatic purge is enabled. Platform, backup, and provider retention must be configured and documented separately. Deletion from an active application may not instantly erase a secured backup; retained copies should not be restored for unrelated use and should expire under the documented backup cycle. A valid legal obligation, fraud-prevention need, or legal claim may justify retaining limited information after a request.
10. Security and incident response
We use reasonable administrative, technical, and organizational safeguards appropriate to the information and services, which may include role-based access, authentication, encrypted transport, provider controls, and review of security events. No site, communication method, or storage system is guaranteed completely secure.
Authorized users must protect credentials, limit access, and report suspected unauthorized activity to [email protected]. We assess incidents and provide notifications where legally required. Do not send passwords, full payment credentials, or unnecessary sensitive documents to ordinary support channels.
11. Privacy rights and how to request them
Depending on your location, the law's applicability, and the information involved, you may have rights to access/know, obtain a portable copy, correct, delete, or restrict certain personal information; opt out of covered sale/sharing, targeted advertising, or certain profiling; withdraw applicable consent; limit certain uses of sensitive information; or appeal a decision. Some rights have exemptions and verification requirements.
Send a request to [email protected] with the action requested and enough ordinary contact information to locate the relevant record. A plain request such as "Do not sell or share my information" is sufficient to start an opt-out request; you do not need to create an account. Do not send a Social Security number or full ID document. We may ask for proportionate verification for access/deletion/correction or proof of an authorized agent's authority, without imposing verification where it is prohibited.
We respond within the period required by applicable law and explain a permitted extension or denial. To appeal an eligible denial, reply to the same privacy contact with "Privacy appeal" and the original request reference. Where applicable, we provide the required further complaint channel. We do not unlawfully discriminate for exercising privacy rights, although a requested deletion or restriction may affect our ability to provide a feature that genuinely requires the information.
For residents protected by California law, the categories in Sections 2 and 5 explain the kinds of information collected and recipient types; you may have rights to know, delete, correct, and opt out of covered sale/sharing, subject to the statute's scope and exemptions. This statement does not claim the business meets any particular legal coverage threshold. Before offering covered processing, we must verify the applicable requirements and implement any required prominent opt-out links and mechanisms.
12. Minors and geographic scope
The contractor program and website are directed to adults and businesses, not children. We do not knowingly solicit personal information from children under 13, and the paid contractor program requires an adult authorized representative. Report a suspected child-submitted record to [email protected] so we can investigate and take appropriate action.
The service is intended primarily for United States service areas. Hosting and providers may process information in other locations according to their operations and agreements. Where cross-border transfer safeguards or additional legal bases are required, they must be established before the affected processing; this notice does not create them.
13. Changes and contact
We publish an effective date and version. We will provide additional notice or obtain consent for a material new use when required by law, and will not retroactively expand a consent merely by changing this text. Contact [email protected] for privacy matters or [email protected] for account support. Mailing address: 123 Main Street PA.
Published snapshot: 61baa1dff737cfa9 · Complete retained version available on request.