| Quick facts | |
|---|---|
| The misconception | Removing names is not de-identification |
| EU standard | Anonymous only if re-identification is not reasonably likely (GDPR Recital 26) |
| California standard | "Deidentified" is a statutory definition, not a description of effort |
| Home services problem | The service address is the customer — geography is the identifier |
| The real trade-off | Safe enough to release vs. still carrying the labels that made it valuable |
| When it happens | Before a buyer sees any sample — never after |
Section 1
Removing names is not de-identification
The standard assurance in this market is that a specialist will review the data and remove identifying details before a buyer sees it. That describes an activity, not a standard, and it is the reason a lot of datasets fail diligence.
The legal tests are not about effort. Under the GDPR, information is outside scope only where re-identification is not reasonably likely taking account of all means reasonably available — and pseudonymised data, where a re-identification key exists anywhere, remains personal data.[1] California defines “deidentified” in statute, with ongoing obligations attached to maintaining that state, and defines “sale” of personal information broadly enough to capture transfers an operator would never describe as a sale.[2]
Reference treatments of the problem have made the same point for a decade: the difficulty is not the obvious fields, it is the combinations and the re-identification risk they carry.[3] Strip every name from a field services file and you have done perhaps a fifth of the work.
Section 2
Six kinds of identifier, and only one of them is easy
It helps to stop thinking about “PII” as one category. In an operational file there are six, and they need different treatment.
| Category | Examples in an operational file | Usual treatment | Why it is hard |
|---|---|---|---|
| Direct identifiers | Name, phone, email, account number, card number | Removal or tokenisation | Straightforward. This is the part most people mean by "de-identification" — and it is the easy 20%. |
| Quasi-identifiers | Service address, parcel, ZIP, install date, equipment serial | Generalisation or suppression | Where home services files actually break. A street address plus an install date is frequently unique. |
| Structural identifiers | Route sequence, crew assignment, visit cadence | Aggregation or re-indexing | A weekly route is a map of a neighbourhood. Order alone can reconstruct geography. |
| Free-text identifiers | Technician notes, call transcripts, scope descriptions | Detection and redaction | The hardest category. Identifiers appear unpredictably, in narrative, misspelled. |
| Employee identifiers | Technician name, licence number, performance score | Pseudonymisation or exclusion | Workforce data with its own legal basis. Licensing files describe work, not workers. |
| Commercial identifiers | Client name on a commercial contract, negotiated pricing | Exclusion | Usually contractual rather than privacy exposure, and usually non-negotiable. |
Section 3
In home services, the address is the customer
This is the structural difficulty that makes field services harder than most industries, and it has no clean solution.
In many sectors a record can describe a transaction without anchoring it to a physical place. Field services work cannot. You attended a specific building, on a specific date, and did something to a specific piece of equipment installed there. A street address combined with an install date is frequently unique to one household — which means location behaves as an identifier even after every name is gone.
You also cannot simply delete it, because geography is often part of what a buyer wanted: climate affects equipment behaviour, local code affects electrical outcomes, route density is a function of where properties sit. Dropping location entirely can remove the covariate that made the dataset interesting.
Section 4
Techniques, and what each one costs you
Every technique trades privacy protection against model utility. Anyone who presents de-identification as free is not describing the same process.
| Technique | What it does | Protection | Cost to model utility | Where it fits |
|---|---|---|---|---|
| Suppression | Delete the field entirely | Total for that field | High — the signal goes with it | Direct identifiers, and anything that cannot be cleaned |
| Pseudonymisation | Replace with a stable token | Partial — still personal data under GDPR | Low — joins survive | Linking a customer across visits without naming them |
| Generalisation | Street → ZIP3; exact date → month | Good, if coarse enough | Moderate — precision is lost | Quasi-identifiers like address and install date |
| Aggregation | Report groups, not rows | Strong | Severe — row-level training data disappears | Benchmarks and summaries, not training sets |
| k-anonymity | Ensure each combination appears k times | Measurable rather than asserted | Moderate, and uneven across the set | Structured operational records with repeated patterns |
| Differential privacy | Add calibrated noise | Strongest formal guarantee | High for small datasets | Rarely appropriate at single-operator scale |
Note the fourth row. Aggregation is the technique that most often destroys the asset. An operator advised to “just send summary data” has been advised to send something no one will train on. Benchmarks are not training sets. If a process pushes you toward aggregation, the honest conclusion is usually that this particular file is not licensable — not that a summary will do.
Section 5
Preserving the label is a design requirement
Here is the failure mode we see most often, and it is worth stating bluntly because it wastes real money.
An operator engages someone to clean the data. That person is measured on whether any identifiers remain, so they are appropriately conservative: anything touching a date, a location, a dollar figure or a free-text note gets suppressed. The result passes a privacy review and is commercially worthless, because the outcome — did the repair hold, did the quote close, did the pest return, did the inspection pass — went out with everything else.
This is also why the pass runs on the seller side, before any buyer sees a sample, with the methodology documented. A buyer subject to Article 53 of the EU AI Act has to describe its training content and maintain a copyright-compliance policy, which means a documented methodology is part of the value you are delivering.[4] A buyer offering to do the cleaning for you is asking for the identified version first.
Section 6
What cannot be cleaned into safety
Some records are excluded by category rather than treated, and a credible process names them at the start rather than discovering them late:
- Safety incidents, injuries and anything adjacent to them
- Records covered by third-party confidentiality — carrier, owner, general contractor, franchisor
- Documents describing a client facility, its systems or its security arrangements
- Property access information: codes, keys, alarm details, occupancy patterns
- Employment records — I-9s, SSNs, medical notes, immigration documentation, disciplinary files
- Anything held under a regulatory custody obligation rather than owned outright
Excluding these is not a concession that weakens the file. It is what makes the rest of it defensible, and it is one of the clearest signals to a buyer that they are dealing with a process rather than an opportunist.
Frequently asked questions
Is removing names and phone numbers enough?
Why is home services harder than other industries than most?
What does "deidentified" mean legally?
Does de-identification ruin the dataset?
Can every record be de-identified into a licensable state?
Who should do the work?
Why does the buyer care how we did it?
References
Sourced from primary industry reports, government data, SEC filings, and peer-reviewed valuation research. Retrieved at time of publication.
- 1.European Union — Regulation (EU) 2016/679 (GDPR), Recital 26 — Not applicable to anonymous data — The "reasonably likely to be used to identify" test that governs whether a de-identified record is still personal data (2016)
- 2.State of California — California Consumer Privacy Act, Civil Code § 1798.140 — definitions of "deidentified" and "sale" — Statutory standard a de-identified operational record must meet, and the breadth of "sale"
- 3.U.S. National Institute of Standards and Technology — NISTIR 8053 — De-Identification of Personal Information — Reference treatment of de-identification techniques and re-identification risk (2015)
- 4.European Union — Regulation (EU) 2024/1689 (Artificial Intelligence Act), Article 53 — Obligations for providers of general-purpose AI models — Copyright-compliance policy and public training-content summary; in force 2 August 2025 under Article 113(b) (2024)