A plumber, electrician, HVAC technician, or handyman running a website doesn't have the same data footprint as an online store, and a generic privacy policy template built for e-commerce checkout flows tends to skip the parts that are actually specific to a local service business. A quote-request form collects a home address before any sale happens. A scheduling or dispatch app shares that address, plus a customer's calendar availability, with a field technician's phone. A technician takes photos on someone's property as part of the job. And the review request that goes out after the job is done hands a customer's name and email to a third-party platform. None of that is exotic, it's just specific, and specific is exactly what a template written for a generic small business tends to leave out.
The data flow, start to finish
Before writing any policy language, it helps to see the whole path a customer's information takes, from the first form submission through to the review request that closes out the job. Four distinct handoffs happen along the way, and each one needs its own line in the policy rather than a single vague "we collect information you provide us" sentence.
Each of the four stops on that path, the quote form, the dispatch app, the on-site photos, and the review request, involves a different recipient and a different reason the data is being used, which is exactly why they need to be disclosed separately rather than folded into one generic paragraph.
Quote request forms: more than a typical contact form
A "get a free quote" form on a home services site usually asks for more than a name and email. It commonly collects a full street address (so the business can estimate travel time and scope the job), a phone number, a description of the problem, and sometimes photos the homeowner uploads themselves, a cracked pipe, a tripped breaker panel, storm damage on a roof. That address and problem description isn't incidental, it's the core input the business runs its scheduling and estimating on, and it typically gets stored in whatever CRM or dispatch tool the business uses, not just left sitting in an inbox.
Your privacy policy should name what happens to that quote request: which system it's stored in, who inside the business (or which third-party answering service, if the business uses one) can see it, and whether uploaded photos are treated as part of the job record or deleted once the quote is answered. A vague line like "we collect the information you submit" doesn't tell a homeowner that their address and a photo of the inside of their home are now sitting in a CRM the business may also use for marketing follow-up.
Scheduling and dispatch apps: name the platform
Most local service businesses run their day-to-day operations through a scheduling and dispatch platform. Jobber, Housecall Pro, ServiceTitan, and similar tools are common across trades, they hold the customer's address, contact information, service history, and appointment windows, and they push that information out to whichever technician is assigned to the job, often as a mobile app notification with the address and job notes attached. That's a meaningfully different data flow than a typical business's internal database, because the customer's home address is actively being transmitted to a field employee's personal or company device before anyone shows up.
A privacy policy for this kind of business should name the dispatch platform being used, state that a customer's address and contact details are shared with the assigned technician to complete the job, and note whether the platform sends automated appointment reminders (text or email) on the business's behalf, since those are usually generated by the dispatch tool itself rather than sent manually. If the dispatch platform also stores payment information for invoicing, that's worth its own sentence too, distinct from whatever payment processor handles the actual card transaction.
On-site photos: the piece most templates miss entirely
Taking photos on a customer's property is routine for contractors and repair technicians: before-and-after shots to document a completed job, photos attached to an invoice as proof of work, or images used for a warranty claim. None of that is unusual, but it's also personal data in a specific sense that a generic template doesn't anticipate, a photo taken inside someone's home can capture far more than the repair itself: family members, personal belongings, the general layout of the property.
The disclosure that actually matters here is the line between internal use and marketing use. Photos kept as part of the job file, for warranty documentation, insurance, or invoicing, are a reasonably expected part of doing the work and need only a short disclosure that photos may be taken as part of the service. Photos used on the business's website, social media, or in a portfolio are a different matter entirely, and using a customer's property image for marketing without a separate, specific opt-in is the kind of gap that turns into a real complaint if a customer later recognizes their own kitchen or driveway on the business's Instagram.
On-site job photos: two different uses
| Internal documentation | Marketing use | |
|---|---|---|
| Purpose | Invoice, warranty, proof of work | Website, social media, portfolio |
| Consent needed | Reasonably expected as part of service | Separate, specific opt-in |
| Retention | Kept with the job record | Kept until customer requests removal |
| Who might appear | Property/equipment only, ideally | Should exclude identifiable people |
A short, separate checkbox at job completion, "may we use before/after photos from your job on our website," does more to close this gap than any amount of policy language, but the policy still needs to describe both uses so a customer understands what happens to a photo either way.
Review-platform data sharing: name the platforms, not just "third parties"
Almost every local service business asks for reviews after a job, usually through an automated email or text sent from the dispatch or CRM tool a day or two after completion, pointing the customer to Google Business Profile, Yelp, Angi, or a similar platform. That review request typically works by handing the customer's name and email (and sometimes the completed job details) to the review platform or to a review-management tool that syncs with it, so the customer can be matched to a review invitation or the review can be tied back to a verified job.
- We may share your information with third parties to request feedback.
- No platform named, no way to know who receives the request.
- Your name and email may be shared with [review platform] to request a review.
- Declining the request stops future invitations for that job.
A policy that says "we may share your information with third parties for marketing purposes" without naming Google, Yelp, or whatever review-management tool sits in between is exactly the kind of line that reads as boilerplate rather than an actual account of what happens, and it leaves out the fact that the platform receiving the request is a company with its own separate privacy practices the customer might want to know about.
Put it together
None of this requires a longer policy than a typical local business needs, it requires a more specific one in the four places that are actually different about this kind of business: name the CRM or dispatch platform that holds a customer's address and routes it to a technician, separate internal job-documentation photos from any marketing use of those same photos, and name the review platform a completed job's contact details get shared with instead of hiding it behind "third parties." Those four disclosures cover the parts of a contractor, repair, or trade services business that a generic small-business template was never written for.
Our Privacy Policy Generator walks through a short questionnaire covering exactly these flows, the dispatch or scheduling tool a business uses, whether job photos are used for marketing, and which review platforms receive customer contact details, the same approach we covered for Shopify stores and mobile apps, pointed instead at the quote-to-job-to-review path a home services business actually runs.
The information in this article is for informational purposes only and should not be construed as legal advice on any matter, and does not create a lawyer-client relationship.
