Privacy and preparation
Homeowner names and addresses in field service records
By SourceX Editorial · Reviewed by Noah Loul ·
Short answer
Homeowner names and addresses in field service records should be replaced or generalized before any license, because a service address points to a household. Swap names for codes, cut street addresses back to city or ZIP code, drop phone numbers and emails, and keep equipment models, symptoms, diagnoses, parts and outcomes, which is where the value sits.
Key takeaways
- The service address is the most sensitive field in a job record because it identifies a household, not just a person.
- Generalize addresses to city or ZIP code, and go broader in rural areas where a ZIP code covers few homes.
- Keep equipment type, model, age band, symptom, diagnosis, parts, labor and callback outcome.
- Serial numbers, photos and call recordings can reveal the address even when the address field is gone.
- Franchise agreements may decide who controls customer records before any privacy question arises.
Why is the service address the most sensitive field?#
The service address is the most sensitive field because it identifies a household, and a household's job history says a lot about the people inside. A run of furnace calls, a water heater replaced in a hurry, a wheelchair ramp, a medical equipment circuit or a note that the owner travels in winter all attach to the address, not to the name on the invoice.
Removing the customer name while keeping the street address therefore protects very little. Anyone with a property lookup can turn an address back into an owner, and neighbors, former technicians and other contractors can do it from memory.
Repeat visits make the problem sharper. A coded customer with many visits over several years, each tied to the same street address, builds a detailed profile of one home: what is installed, when it fails and when nobody answers the door. Generalizing the address once, at the customer level, breaks that profile for every visit at the same time.
California's definition of deidentified data reflects the same idea: data must not reasonably be linkable to a consumer or a household, and the business holding it must take reasonable measures to keep it that way. Which privacy laws apply to your customers is assessed deal by deal with counsel.
Treatment table: name, address, phone and notes#
The treatment table sets a default for each homeowner field in a typical ServiceTitan, Housecall Pro, Jobber or FieldEdge account. Defaults can be tightened for a specific buyer, but they should rarely be loosened.
| Field | Default treatment | Why |
|---|---|---|
| Customer name | Replace with a stable customer code | Keeps repeat-service history linked without naming anyone |
| Service address | Generalize to city or ZIP code | Keeps climate and regional patterns; removes the household |
| Billing address, if different | Remove | Adds no service value and can point to a second property |
| Phone numbers and email | Remove | Direct identifiers with no analytical use |
| Property and location notes | Review and clean | Often hold access codes, pet names, occupant details |
| Technician job notes | Keep after cleaning | Hold the diagnosis and repair reasoning |
| Equipment model and age | Keep | Core value for diagnosis and parts prediction |
| Equipment serial number | Remove or replace with a code | Can be traced to the owner through warranty registration |
| Job date | Keep month or week | Preserves seasonality without pinning a visit to a day |
| Photos | Exclude or review one by one | House numbers, faces, vehicles and street views |
- 01Your work records
- 02Personal details removed
- 03You approve the release
- 04Licensed to AI developers
City, ZIP or county: how far should addresses be generalized?#
Addresses should be generalized until each area contains enough households that a single job cannot be pinned to one home. In a dense metro, a five-digit ZIP code often meets that bar; in a rural service area, a ZIP code may cover a handful of farms, and county or region is safer.
A widely cited benchmark comes from health privacy. The HIPAA Safe Harbor method, which does not govern home services but is often used as a reference point, treats every geographic unit smaller than a state as an identifier, except that the first three ZIP digits may be kept where the combined area holds more than 20,000 people.
Choose one rule for the whole package and apply it consistently. Mixing street-level detail for some jobs with ZIP-level detail for others invites linkage, because the precise records become anchors for the rest.
| Service area in the package | Location level for every job | Reason |
|---|---|---|
| Dense metro only | Five-digit ZIP code | Each ZIP holds many households |
| Metro plus suburbs | ZIP code or city, applied to all jobs | Suburban ZIPs can be small; one level avoids anchors |
| Includes rural routes | County or region for all jobs | Rural ZIPs and towns may hold only a few homes |
| Single small town | Region or climate zone only | The town itself narrows the customer base |
What should stay in the job record?#
The job record should keep everything that explains what was wrong, what the technician did and whether it worked. Those details are what make residential service history useful for diagnostic, dispatch and parts tools, and none of them needs a homeowner's identity.
Clean the free text inside these fields rather than dropping them. A symptom line such as no heat since the tenant in the back unit called often carries an occupant detail inside a useful complaint; removing the occupant phrase keeps the complaint. Technician reasoning is the most valuable text in the record and usually the least personal, so it deserves careful cleaning, not deletion.
- Equipment type, brand, model and an age band.
- Symptom as the customer reported it, cleaned of names.
- Diagnosis, test readings and the technician's reasoning.
- Parts used, labor time and whether a second visit was needed.
- Callback and warranty outcomes linked by customer code.
- Maintenance agreement status and visit sequence.
- Season and climate region from the generalized location.
Where else do homeowner details hide?#
Homeowner details hide in attachments, recordings and side systems that rarely show up in a job export. Estimates and invoices saved as PDFs repeat the full name and address. Call recordings and CSR booking notes capture names, phone numbers and sometimes the reason the homeowner is home during the day.
Marketing lists, review request logs and financing applications sit next to the field service platform and often connect to it. Financing records in particular can carry income and credit details and should stay out of scope entirely.
Technician photos are the easiest leak to miss. A shot of an outdoor unit can show the house number, the car in the driveway and the street, so photos are excluded by default and only reviewed individually when they carry real diagnostic value.
Illustrative: a plumbing and HVAC company prepares its job history#
Illustrative: a fictional plumbing and HVAC company runs ServiceTitan, with years of residential jobs, maintenance agreements and call recordings. The owner wants to license repair history and is worried about what customers would think.
The team replaces customer names with codes, generalizes addresses to ZIP code in the metro and to county in the outlying service area, removes phones, emails and billing addresses, and replaces equipment serials with codes. Call recordings, financing records and photos are excluded. Location notes are cleaned, which removes gate codes, pet names and remarks about elderly occupants.
The result keeps every diagnosis, part, callback and maintenance visit, linked by customer code. A sampled review by a long-tenured dispatcher finds no job that could be tied to a specific home, and the owner signs off on the field list with that review attached.
How SourceX approaches homeowner data#
SourceX applies these field rules in the Preparation step of the SourceX five-step transaction, after the Rights step checks who controls the customer records. For franchise businesses, that check comes first, because the franchise agreement may give the franchisor rights over customer data.
The field treatments, the address generalization rule and the excluded attachments are recorded in the privacy record of the SourceX Evidence Packet, and the owner approves them before Delivery.
Frequently asked questions
Do we need homeowner consent to license job history?
It depends on your privacy notice, the laws that apply to your customers and how thoroughly the records are de-identified. Properly coded and generalized records reduce the question considerably, but counsel should review your notice and the specific package before anything is licensed.
Are commercial customers treated differently?
Commercial service sites carry less household privacy risk, but names of property managers and facility contacts are still personal details, and the business may have a contract that treats its information as confidential. Replace commercial customers with codes too, and keep only the property type.
Can we keep street names for multi-unit buildings?
Generally no. A street and a building type can still point to one property, and unit numbers identify households directly. Keep a property type such as multi-family and the generalized location instead, which preserves the pattern without the address.
What if a franchisor owns the customer list?
Then the franchisor may need to approve or join the license, and some customer records may not be yours to license at all. Read the franchise agreement's data and confidentiality clauses first, before spending time on preparation.
Should we keep the original data after preparing a copy?
Yes, keep your operating records as they are. Preparation creates a separate, cleaned copy for the license; your ServiceTitan or Housecall Pro account stays unchanged, and the code map that links coded records back to customers stays inside the company.
Do renters and landlords change the treatment?
The treatment stays the same, but the notes change. Rental jobs often name both the tenant who reported the problem and the owner who approved the work, plus a property manager. Remove all three, keep a property type such as rental or owner-occupied if it matters for the job, and code the paying account.
Sources
- Under Cal. Civ. Code 1798.140(m), deidentified information cannot reasonably be linked to a particular consumer, and the business must take reasonable measures to ensure it cannot be associated with a consumer or household. Source
- The HIPAA Safe Harbor identifiers include all geographic subdivisions smaller than a state, except that the initial three ZIP-code digits may be kept if the combined area contains more than 20,000 people. Source
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.