# What MSPs should say about de-identification | SourceX

Canonical: https://refer.sourcex.si/guides/what-technology-partners-should-say-about-de-identification
Last updated: 2026-11-04

Repeat only what SourceX itself publishes: SourceX de-identifies the data through approved processing routes before it is used or shared, and the supplier agreement records that re-identification may still be possible and that SourceX is not liable for it. Never promise anonymity, compliance, a method or a result, and never offer to scrub records yourself. Send method questions to SourceX, legal and regulatory questions to the client's counsel, and the decision to the CEO.

For an MSP or enterprise systems consultant, this is where expertise becomes a hazard. You know where the client's personal data sits, which fields carry free text and how a script could mask names. When the CEO asks whether customers will be identifiable, a confident technical answer sounds authoritative, and it commits SourceX to something SourceX has not said.

## Why the de-identification question lands on the technology partner

Because you are in the room when the client thinks about it. The question rarely arrives as a formal inquiry. It comes up in a quarterly review, during a migration planning call or in a hallway: "If we did this, would our customers' names be in it?" The people asking are the ones who will decide or advise. The CEO decides whether the company discusses licensing at all; a controller, privacy lead or general counsel advises; an internal IT owner knows the systems. Each of them deserves an answer that will still be true after SourceX's review.

Three moments produce most of these questions:

| Moment | What the client says | The temptation |
|---|---|---|
| A quarterly review where the idea first comes up | "Would our customers be identifiable?" | Answer from your own knowledge of the data |
| A migration or archive project | "Can you strip the names before anything goes?" | Offer the work, since you have the access and the skills |
| A security or compliance conversation | "What standard do they use, and are they certified?" | Fill the gap with something that sounds standard |

## The verified explanation and escalation card

The card has two sides. The front holds sentences you may repeat word for word, each traced to a page SourceX publishes. The back holds the claims you never make and the person who owns each question past the front.

**Front: four sentences you can repeat.**

| # | Sentence | Where SourceX says it |
|---|---|---|
| 1 | "SourceX de-identifies the data, through approved processing routes, before it is used or shared." | SourceX's insight on re-identification risk; its glossary also names the approved routes |
| 2 | "The supplier agreement records that re-identification may still be possible and that SourceX is not liable for it." | SourceX's glossary entry on re-identification |
| 3 | "The company decides whether to proceed and what scope to offer, and nothing is shared without its approval." | The referral program's how-it-works page |
| 4 | "The exact dataset and terms are fixed in a Dataset Deal Confirmation the company signs." | SourceX's insight on re-identification risk |

Sentences 1 and 2 keep SourceX's own wording; 3 and 4 condense what its pages say. If a client wants more than these four, the answer belongs to SourceX, not to you.

**Back, part one: six claims you never make.**

| Never say | Why not |
|---|---|
| "It will be anonymous" or "nobody can trace it back" | SourceX's own agreement records that re-identification may still be possible; NIST's survey of the field says some de-identified data can sometimes be re-identified |
| "The IDs are hashed, so it's anonymous" | The FTC's Office of Technology wrote in 2024 that hashing does not make data anonymous |
| "It meets the de-identification standard" or "it's compliant" | Where a legal standard applies, such as the HIPAA Privacy Rule for health information, whether it is met is for the client's counsel and SourceX, not the partner |
| "I'll scrub it before it goes" | The partner neither handles nor sends records; preparation happens in SourceX's process under the company's agreement |
| "Your customers' names won't be in it" | What is removed or masked is settled in the company's own deal, not promised in advance by an introducer |
| "SourceX is certified for this" | Never state a certification, audit or security standard for SourceX; send security questions to SourceX itself |

**Back, part two: who owns each question past the front.**

| Question | Owner | Your part |
|---|---|---|
| Which fields, which technique, who performs it, how the result is checked | SourceX, once the company applies | Put the CEO or privacy lead in touch; do not relay answers |
| Whether a legal standard applies, what contracts and privacy notices allow | The client's counsel or privacy lead | Name the question; give no view on it |
| Where personal data sits, in which systems and fields | The client's own system owner | Help only as a service the client orders, kept apart from the referral |
| What the re-identification clause means for the company | The client's counsel reading the agreement | Point to SourceX's advice to have counsel review the terms before signing |
| Whether to go ahead at all | The CEO | Ask once, and accept the answer |

**Method note.** The front comes from SourceX's glossary entry on re-identification, its insight on re-identification risk and the referral program's how-it-works page, all read on 2026-10-27. The back draws on NIST IR 8053, the FTC's 2024 post on hashing and HHS's de-identification guidance. The card limits what a partner says; it does not assess any client's data, legal position or the quality of anyone's de-identification. Re-read the front sentences on SourceX's pages before each use, because published wording can change.

## What the outside sources do and do not say

Each source on the card's back supports a narrow point, and none of it is advice about a particular client.

- **NIST IR 8053**, a 2015 survey of de-identification research, says in its abstract that de-identification can reduce the privacy risk of handling and sharing information, and that some de-identified data can sometimes be re-identified (our paraphrase). "Reduces risk" is a fair summary; "removes risk" is not.
- **The FTC's Office of Technology** said in July 2024 that hashing does not make data anonymous, describing hashing as turning a value such as an email address into a consistent number, and saying data is anonymous only when it can never be associated back to a person (our paraphrase of the excerpt).
- **HHS's guidance** under the HIPAA Privacy Rule explains two methods that can satisfy that rule's de-identification standard: Expert Determination and Safe Harbor. A partner cannot tell from outside whether either applies to a client's records, which is exactly why the question goes to counsel.

The [comparison of pseudonymisation and anonymisation](/compare/pseudonymisation-vs-anonymisation-gdpr) covers the European vocabulary, and [whether a company can be identified from anonymized data](/questions/can-a-company-be-identified-from-anonymized-data) covers the separate worry that the business itself might be recognizable.

## Custodian, client and SourceX: who touches the data

The technical custodian, the customer owner and SourceX have different jobs here, and the access you hold changes none of them.

| Party | Holds | Decides | Does not do in a referral |
|---|---|---|---|
| The MSP or systems consultant | Admin access and system knowledge under a service agreement | How to carry out work the client orders for its own purposes | Export, sample, mask or send records; promise any de-identification result |
| The client | The records, the systems and the CEO's authority | Whether to proceed, what scope to offer, which advisers to involve | Hand privacy decisions to its IT provider |
| SourceX | Nothing until the company applies and signs | Its review, and, under the signed agreement, the preparation it performs through approved routes | Need the partner to export, upload or describe confidential records |

SourceX's program page states the partner's position directly: you make the introduction, and you do not need to export, upload or describe confidential records. Any redaction a client asks you to run on its own systems is a separate service decision, billed or not under your agreement, and it does not stand in for anything in SourceX's process. The wider security conversation an MSP may face is covered in [client data security questions for MSPs](/guides/msp-client-data-licensing-security), and the difference between privacy processing and the right to license is set out in [de-identification versus permission to license](/guides/how-to-distinguish-de-identification-from-permission-to-license).

## Describing personal data in the introduction without a promise

If the CEO wants the conversation, the introduction can describe personal data at metadata level, because that helps SourceX plan: which record families contain names, contact details or free-text notes, and roughly how much. It carries no sample, no screenshot and no promise about what will be removed.

Fit decides before privacy does. A company needs a full-time headcount that reached 50 at its peak, contractors excluded, years of records it created itself, rights to license them and a CEO who wants to talk. SourceX's screening page lists personal consumer data, scraped data and material belonging to clients as usually not a fit, so a business whose main records are consumer data may not be a candidate however well it could be de-identified. Business records that mention people in passing, such as work orders naming a site contact, are a different matter for SourceX's review to judge.

One partner is credited per company once it submits a verified application inside the 90-day window, and that partner signs the SourceX Channel Partner Agreement before submitting.

## One client, three questions (Illustrative)

Illustrative. The company and conversation are invented.

A 260-person commercial facilities maintenance company keeps fifteen years of work orders and service emails that name tenants, building managers and technicians. During a quarterly review, three people ask three questions.

- **The CEO: "Will our tenants be identifiable?"** The partner gives front sentences 1 and 2, says plainly that SourceX itself does not claim re-identification is impossible, and offers to connect the CEO with SourceX for the method if the company applies.
- **The controller: "Can you strip the names before anything is sent?"** The partner says the referral sends nothing, so there is nothing to strip for it. If the company wants a cleanup of its own systems for its own reasons, that is a normal service request, separate from any introduction.
- **The IT lead: "We already hash tenant IDs. Doesn't that count?"** The partner does not argue the point either way, notes that the FTC has said hashing alone does not make data anonymous, and lists the question for SourceX and the company's counsel.

A week later the CEO asks to hear about licensing. The introduction names the company, its peak full-time headcount, the record families and the fact that work orders and emails contain names and contact details. It says nothing about what will happen to them.

## Next step

> **Refer a company. No cap on rewards.** Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

Keep the card's front for the client and its back for yourself. When a CEO asks to hear more, [open a partner account](/register), test the company against the [screening profile SourceX publishes](/who-qualifies) and confirm in the [program terms](/terms) how credit and payment work before you write a word to SourceX. MSP-specific context is in the [managed service provider overview](/for/managed-service-providers) and the [guides library](/guides).

## Sources

- https://sourcex.si/glossary/re-identification
- https://sourcex.si/insights/re-identification-risk-in-business-data
- https://refer.sourcex.si/how-it-works
- https://refer.sourcex.si/who-qualifies
- https://refer.sourcex.si/terms
- https://csrc.nist.gov/pubs/ir/8053/final
- https://www.ftc.gov/policy/advocacy-research/tech-at-ftc/2024/07/no-hashing-still-doesnt-make-your-data-anonymous
- https://www.hhs.gov/hipaa/for-professionals/special-topics/de-identification/index.html
