Article

Does the buyer see your customers’ names?

By TrustPast

Updated October 23, 2026

You’ve spent fifteen years earning the trust of the people in your files. Some of them have called you at midnight with water coming through a ceiling. The idea that a buyer might read their names next to that call is where most owners stop listening. This page settles that one question, using micro1’s own words: does the buyer see your customers’ names, where do those names sit in the records you keep, and what can you ask to come out before anything leaves your systems.

It is a narrow page on purpose. Our page on how de-identification works shows the process on a sample of each record. Our page on whether it’s safe to license company records covers access, retention and deletion. Here we stay with the customer: the person or the business that paid you, and every place your systems wrote them down.

The plain answer, in micro1’s words

micro1 doesn’t publish a one-line promise that no name is ever seen. It publishes a method, and the method puts you at the table.

Start with removal. On its data partnerships page, under how company data is protected, micro1 says: “Personally identifiable information (PII) is removed when relevant.” Under what happens after records are shared, it adds that “personally identifiable information may be removed and certain datasets may undergo synthetic rewrites that preserve workflow structure while reducing direct ties to original records.”

Then the rules. micro1 says: “Before any participation, together we define” four things. One of them is “Anonymization and redaction requirements.” Another is “Approved data scope and clear boundaries.” Together means you and micro1. Before any participation means before anything moves.

Then the check. micro1 says “companies are given the opportunity to review representative samples before prepared data is used.”

Then the purpose. micro1’s 9 October 2026 announcement says it “uses de-identified company data.”

And ownership stays put. micro1’s answer to “Who owns the data?” is short: “Companies retain ownership of their underlying data.”

So here is the plain answer, in our own words. Customer names are what the redaction rules exist to remove. You help write those rules before anything is shared. You see samples of the prepared records before they’re used. If a name on your list turns up in a sample, you see it before the records are used, and can raise it.

Note the limit. micro1’s words are “when relevant” and “may be removed.” It doesn’t publish what counts as relevant for your company. That is what the discovery call is for. Our advice: don’t leave “relevant” undefined. Ask, in writing, that customer names and contact details come out of everything in scope.

Apply & License Your Data

What counts as a customer’s name

Owners picture the name field. The real list is longer, and it matters for what you ask.

The US National Institute of Standards and Technology defines personally identifiable information as “Information that can be used to distinguish or trace an individual’s identity, either alone or when combined with other information that is linked or linkable to a specific individual.”

Read the second half again. “Linked or linkable.” A name is the obvious one. But in a trade company, plenty of other things point to one customer just as well. Here is our own list of what to treat as a name:

the customer’s name, and the names of anyone else on the account, such as a spouse or a tenant;
the service address, and any description of the place that gives it away;
phone numbers, email addresses and the account number in your software;
gate codes, lockbox numbers and alarm codes typed into notes;
the business name of a commercial client, and its staff names;
anything a customer signed, photographed or sent you.

A commercial client is a different case from a homeowner. A business isn’t a person under the NIST wording. But its name can still be confidential under your contract with it, and its facilities manager is a person. Our advice: treat commercial client names the same way as homeowners’ names, unless your counsel says otherwise.

Where customer names sit in your records

Every record a trade or service company keeps has two layers. One layer says who the job was for. The other says what was done and why. The names live almost entirely in the first layer, and the value lives almost entirely in the second. Here is where the first layer sits, record by record, as our own description.

The CRM. This is the system built around the customer, so the names are its spine. The contact card holds the name, address, phones and email. The lead source may be a person who referred you. The notes field picks up names in passing: “spoke to his wife,” “tenant in unit 3 called.” What sits under the card is different. The lead, the follow-ups, the quote history, the reason a job was won or lost. micro1’s referral page lists “CRM metadata” among the records a good fit has, and its data partnerships page lists “CRM data.” Our page on CRM records goes through what those notes show.

Estimates and quotes. The name and address sit in the header. The signature sits at the foot. In between is the scope, the options, the measurements, the revisions. A name may also appear in the notes, as in “per the owner, keep the old fixtures.” Our page on estimates and quotes explains why the versions matter.

Job files and work orders. These were written so a technician could find a house and get in. So they carry the address, the gate code, the callback number and sometimes a note about who’ll be home. The technician’s own notes may name the customer, and the photos may show a house number. The rest is the complaint, the checks, the finding and the fix. Our page on job files and work orders covers the whole folder.

Invoices. An invoice is mostly identity and money: the bill-to name, the address, the amount, the payment method, sometimes the last digits of a card. The line items repeat what the work order already says. That makes the invoice the record with the most names and the least reasoning. Our advice: leave the invoicing system out of scope. The work order tells the story better.

Email. Names are everywhere in a mailbox. The From and To lines, the greeting, the sign-off, the footer with a mobile number, the subject line with a job address, the forwarded chain three replies down. The reasoning is in the body: why a price went up, how a dispute was settled. Our page on email archives covers what else a mailbox holds.

Slack and Teams. Chat names people constantly and casually. A dispatcher types a customer’s surname and street so a tech can find the job. A manager names the customer who complained. The display names of your own staff sit on every line. The useful part is the decision: who went where, what was tried, what changed. Our page on Slack and Teams chats explains why that matters.

The pattern is the same in all six. The names cluster in headers, contact fields, signatures and stray mentions in free text. The work sits in the body. That is why removal works on trade records, and it’s why a request to remove names doesn’t empty the file.

What you can ask to come out before anything leaves

micro1 says the scope and the redaction rules are set together, before any participation. It doesn’t publish a fixed menu of what you can ask for. What follows is our own advice on how to put the request, in three tiers.

Tier one: leave it out of scope entirely. Some systems are mostly names. Our advice is to ask that these stay home:

the CRM contact table itself, the list of who your customers are;
the invoicing and payments system;
any customer mailing list or marketing export;
the folder of signed contracts and authorisations.

None of these shows how a job was done. Leaving them out costs little, and it removes the biggest pile of names in one line. micro1 calls this the “Approved data scope and clear boundaries.” Name the systems you’re keeping home there.

Tier two: remove the fields. For records that are in scope, ask that the identifying fields come out. Name them by system: the contact fields on a job, the bill-to block on an estimate, the address on a work order, the email headers and signatures. A structured field is the easy case. It’s in the same place on every record.

Tier three: handle the free text. This is the hard part. Notes, comments, email bodies and chat messages hold names wherever someone typed one. Ask how free text will be handled under the “Anonymization and redaction requirements.” Ask whether a synthetic rewrite, which micro1 says can “preserve workflow structure while reducing direct ties to original records,” would replace people with roles in those notes. Ask who does it, and at what step.

You don’t need to scrub your own systems first. Your files stay as they are when you apply. What helps is a one-page map of where the names live: each system, its identifying fields, its free-text fields. Bring that to the discovery call. micro1 says the discovery call is there “to discuss your data and privacy requirements.”

Who in your office could draw that map in an afternoon?

Why names are not what is wanted

This is the part that settles most of the worry, so it’s worth putting plainly. micro1 says it uses de-identified company data. Customer names and payments are never what is wanted. What is wanted is how the work was done. How an estimate became a job. How a change order was settled. How a repair was diagnosed.

micro1’s own words point the same way. It says: “We are looking for data that reflects how work is actually performed within an organization.” It says “The most valuable datasets capture real operational expertise, decision-making processes, and repeatable workflows” and its sentence continues from there. One of its headings is “Decision-making patterns,” described as “How teams evaluate information and make operational decisions.”

Take a callback on a commercial walk-in cooler. The first visit replaced a fan motor. The second found the real fault, a failing defrost timer, and the tech wrote down how he ruled out the motor again. The customer’s name adds nothing to that. The restaurant’s address adds nothing. What teaches something is the order of the checks and the reason for the second answer.

A customer’s name has never once explained why a breaker kept tripping.

Our cornerstone page on what data buyers want from a trade business goes through this split for four trades. The short version: the buyer is paying for the judgment in your records. Names are the part of the record that the judgment never depended on.

That is also why asking for them to come out is an ordinary request, not a hard bargain. Our own reading of micro1’s compensation answer: it names “dataset size and volume, workflow complexity, data quality, domain expertise represented, and the uniqueness of the operational knowledge.” A customer’s name sits under none of those headings. Ask micro1 directly whether any removal you ask for changes the offer. It’s the only answer that counts.

Checking that the names came out

A rule on paper is only half the job. The other half is reading what came back.

micro1 says companies are “given the opportunity to review representative samples before prepared data is used.” That review is where your list meets your records. Here is our own advice on running it.

Pick the right reader. The person who answers your phones knows your customers’ names better than you do. They’ll spot a surname in a technician’s note on the first pass.

Bring a list. Write down your twenty largest accounts and your ten most frequent residential customers. Search the samples for each one. A name that shows up once is a sign it will show up again.

Ask for the messy records. Request samples from free-text notes, old systems and email threads, not only the tidy structured ones. Names hide where nobody filled in a form.

Look past the name. Check for street names, unusual job descriptions and photos. Under the NIST wording, information that is “linkable” to a person counts too. A job described as the only geothermal install on a named road is linkable.

Write it down. If a sample shows something that should have come out, say so in writing and ask what happens next. micro1 doesn’t publish what follows a failed sample. Ask at discovery.

Customer contracts and privacy law

Two questions sit outside anything micro1 or we can settle for you.

The first is your contracts. Some commercial clients sign agreements that say who owns the drawings, the reports or the site records, and what you may share. A property manager’s tenant list may belong to the property manager. Only the contracts say which records are yours to license, and only your counsel can read them for you.

The second is privacy law. Which rules apply depends on where you work, who your customers are and what your records hold. We don’t give legal advice, and this page isn’t any. Our page on whether licensing company records is legal lists whose rights to check first.

Our advice: have counsel read your customer contracts and your privacy notice before the discovery call. Bring their answer with your map of where the names live. It turns a vague worry into two or three specific lines for the redaction rules.

What this means for a service company with 30 or more staff

Here is one company, as our own hypothetical and not a description from micro1. Say an electrical contractor with 50 people. Residential service, light commercial, twelve years in its field-service software. micro1’s referral page sets the line at “30+ employees,” so it’s in range. Our page on companies with 30 or more staff covers that lane.

Where its customer names sit. About nine thousand contact cards in the CRM. A bill-to block on every estimate. Addresses, gate codes and callback numbers on every work order. Customer surnames typed into the dispatch channel in Slack. Facilities managers’ names and signatures throughout the shared inbox. A commercial client list in the invoicing system.

What its request would say. Out of scope: the contact table, the invoicing system, the marketing list, the signed contracts folder. Fields removed: names, addresses, phones, emails, account numbers, codes and signatures across the CRM notes, estimates and work orders. Free text: names in notes, email and Slack replaced with roles. Commercial client names treated the same as homeowners’ names, pending counsel’s read of two maintenance contracts.

What stays. How a panel upgrade estimate was revised after the utility’s service check. How a tripping breaker was traced to a shared neutral. Why the service manager sent the senior electrician on a repeat call. How a lost commercial bid changed the next one. With the names removed, that is the record a buyer licenses to train AI models on real work.

What it asks micro1. Whether those systems can be named as out of scope. How free text is handled. How many samples it will see, and from which years. What happens if a sample shows a customer’s name.

Worth two minutes to see your range? Our estimate asks five questions.

What is never included

micro1’s own words are short. On its data partnerships page and its payout page, it says “We understand business data can contain sensitive information” and that every partnership is designed around your requirements, “with clear controls over what is shared, how it is handled, and what is never included.” It sets the scope and boundaries with each company, before any participation. It doesn’t publish a fixed list.

What follows is our own advice, not micro1’s. Keep these out unless micro1 agrees otherwise in writing: attorney-client privileged records, health information, payment-card and financial-account details, Social Security numbers, minors’ data, biometric data, and classified or export-controlled material. On a customer page, two more belong on the list. The customer list itself. And anything a client owns under its contract with you.

Where those records hide, folder by folder, is on what is never included in a records licence. Our How it’s safe page gives the short version.

Where we fit

We, TrustPast, explain how this works and give you a range with our estimate. The range is ours, not an offer. You apply to micro1 yourself, through the button below. micro1 pays us a referral fee. You pay us nothing.

We never see your files, and we never see your customers’ names. Your records go from your systems to micro1, on the scope and redaction rules you agree with micro1. The map on this page is only a way to arrive at that conversation knowing exactly where your customers sit in your records.

TrustPast

Questions and answers

Does micro1 see our customers’ names?

micro1 says “Personally identifiable information (PII) is removed when relevant,” and that the “Anonymization and redaction requirements” are defined together with the company before any participation. Its 9 October 2026 announcement says it “uses de-identified company data.” Asking that customer names come out of everything in scope is our own advice, and the place to ask is the discovery call.

Can we ask for whole systems to stay out, not just names?

micro1 says the “Approved data scope and clear boundaries” are defined together before any participation. As our own advice, ask that the customer contact table and the invoicing system stay out of scope entirely, and that names in the notes come out under the redaction requirements.

Will we see whether a name slipped through?

micro1 says “companies are given the opportunity to review representative samples before prepared data is used.” As our own advice, have the person who knows your customers best read those samples, with a list of your largest accounts beside them.

Why would a buyer not want the names?

micro1 says it is looking for “data that reflects how work is actually performed within an organization.” A name doesn’t show how a job was estimated, run or fixed. The steps do, and they read the same with the name taken out.

Do our customer contracts allow this?

Only your contracts and your counsel can say. Some commercial agreements say who owns the documents and what may be shared. Have counsel read them before the discovery call. We don’t give legal advice.

Do we still own the records?

Yes. micro1’s answer to “Who owns the data?” is one sentence: “Companies retain ownership of their underlying data.”