Article

Does licensing records affect your customers?

By TrustPast

Updated October 28, 2026

Your customers let you into their attics, their crawl spaces and their basements. They gave you a gate code and a spare key. When an owner first hears that a company can license its old records, the next thought is about those people. This page settles that question for a contractor or a repair shop: what happens to your customers, what a buyer actually wants from your files, and what to check on your own side before you apply.

We, TrustPast, quote micro1’s public pages for everything micro1 does. Where we add our own advice, we say so. And where the answer turns on your contracts or the law, we say to ask counsel. We are not lawyers, and nothing here is legal advice.

The short answer

Licensing your records doesn’t put your customers in front of the companies that use them. micro1 handles the raw records under access limits and removes or transforms identifying information before sharing. Here is why, in micro1’s words first and ours second.

micro1’s data partnerships page says: “Protecting customer data is a core principle of the program.” It says “Personally identifiable information (PII) is removed when relevant.” Under “Before any participation, together we confirm,” one of the four items is “De-identified before sharing”: “Personal and identifying information is removed or transformed before your data is shared with third parties.”

Its 9 October 2026 announcement says micro1 “uses de-identified company data.”

And its contracting step includes “a commitment not to resell or distribute your data until personal and identifying information has been anonymized.”

So, in our own words. Your customers are not who the buyer is interested in. Personal and identifying information is removed or transformed before records are shared with third parties, and you agree the terms before anything moves.

One limit, plainly. micro1 writes “when relevant” and “removed or transformed.” It doesn’t publish a fixed list of what it removes for a given company. That is a question for your first call with micro1, and the rest of this page helps you ask it well.

Apply & License Your Data

Nothing in micro1’s process involves your customers

The first worry is the most concrete one. Will someone call the homeowner whose water heater you replaced in 2019?

Nothing on micro1’s pages describes a step that involves your customers. The process it publishes runs between micro1 and your company. On its referral page: someone at your company sets up the company’s profile and “completes data manifest.” Then “Our team reviews the company and determines whether it’s a fit for a data partnership.” Then “Qualified companies are invited to connect with a Data Partnership Manager to discuss their data, licensing terms, and next steps.” Then “the company moves through contracting, data transfer, and data approval.”

micro1’s published process has no step that reaches your customers: no survey, no consent form, no call. Whether you need to tell them or ask them is a separate question for your contracts and your counsel.

Our advice: ask micro1 to confirm in writing that it won’t contact anyone named in your records. One sentence in the agreement costs nothing and ends the question. We come back to your contracts below.

What a buyer wants from a contractor’s files

This is the part that settles most of the worry. A buyer is not after your customer list. It is after how your company works. micro1 does name “CRM records” among the records a company’s data can include, but what it values is the work, and personal and identifying information is what its de-identification removes or transforms.

micro1 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.” Its announcement puts it another way: “Real business operations involve incomplete information, competing priorities and exceptions that require judgment.”

Put plainly: records are de-identified before use. 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.

Here is what that looks like in four shops, as our own examples.

A roofing contractor. The estimate went out at one price. The tear-off found two layers and soft decking over the back bedroom. The change order added sheets of plywood and a day of labour. The email thread shows how the homeowner was walked through it and what was agreed. A buyer wants that sequence. It doesn’t need the homeowner’s name or the street.

An HVAC contractor. A no-heat call in January. The tech checked the igniter, then the flame sensor, then found a cracked pressure switch hose. The notes show the order of the checks and why the first guess was wrong. The customer’s card number on the invoice teaches nothing about any of that.

A plumbing contractor. A slab leak quoted three ways: a spot repair, a reroute through the attic, a full repipe. The file shows which option the customer chose, why, and how the price changed when the crew found galvanized pipe at the meter. The judgment sits in the options and the revision, not in the bill-to block.

A repair shop. A car came back twice with the same check-engine light. The first repair order replaced a sensor. The second found a vacuum leak, with a note on how the tech found it. The owner’s name and phone number add nothing to that story.

Our cornerstone page on what data buyers want from a trade business goes through this split for four trades, file by file.

A customer’s name has never once told anyone why a furnace short-cycles.

Where your customers sit in your records

Every trade record has two layers. One says who the job was for. The other says what was done and why. Customers live in the first layer. The value lives in the second.

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.” The words “linked or linkable” matter in a trade company. A service address points to one household as well as a name does.

Here is our own list of where customers sit, record by record.

Estimates and quotes. Name, address and phone in the header. A signature at the foot. Sometimes a note like “per the owner, keep the old vanity.” Between them sit the scope, the options, the measurements and the revisions. Our page on estimates and quotes explains why the revisions matter.

Job files and work orders. The address, the gate code, the lockbox number, the callback number, a note about the dog. Then the complaint, the checks, the finding and the fix. Photos may show a house number. Our page on job files and work orders covers the whole folder.

Invoices and payments. Mostly identity and money. The bill-to name, the amount, the payment method, sometimes the last digits of a card. The line items repeat what the work order already says.

The CRM, email and dispatch chat. Contact cards, signatures, a surname typed so a tech can find the job. The reasoning sits in the body of the note or the thread.

The pattern is the same everywhere. Customers cluster in headers, contact fields, signatures and stray mentions in notes. The work sits in between. That is why taking customers out doesn’t empty the file. Our page on whether the buyer sees your customers’ names follows a name through each system in more detail.

What micro1 says about anonymisation, redaction and approvals

micro1 doesn’t ask you to clean your records first. Its answer to whether a company must anonymize its records before transferring them is one line: “No, micro1 has processes for de-identifying and transforming sensitive information.”

Here is what it publishes about each stage, in its own words.

Before anything moves. “We protect sensitive information through data anonymization and secure handling. Before any participation, together we confirm” four things. U.S. and allied buyers only. Data segregation: “Your data is kept separate from other companies’ data, with access restricted to authorized personnel.” De-identified before sharing. Defined retention periods: “Raw data is deleted according to an agreed schedule.”

At contracting. micro1 says it establishes “clear licensing terms, including a commitment not to resell or distribute your data until personal and identifying information has been anonymized.”

At transfer. “You securely transfer your data through our APIs or other approved methods. We review the data for completeness.” Its referral page says that if there is a fit, “the company transfers approved data.”

After transfer. “Depending on the nature of the data, personally identifiable information may be removed and certain datasets may undergo synthetic rewrites that preserve workflow structure while reducing direct ties to original records.” A synthetic rewrite, in our own words, keeps the steps of a job and loosens the tie to the actual household.

Before use. “Companies are given the opportunity to review representative samples before prepared data is used.”

At the end. “Upon request or at the end of an engagement, data is deleted according to the agreed retention and deletion terms.”

Our page on how de-identification works shows what this looks like on a real estimate and a real work order. Our page on reviewing the records before use covers who should read the samples.

Two limits, as our own reading. micro1 doesn’t publish a fixed redaction list, and it doesn’t publish what happens when a sample shows a name. Both are questions for your first call. Ask them before you sign, not after.

What to check in your own contracts and privacy notice

This is the part only you can do. micro1 can promise what it will do with the records. It can’t tell you what you promised your customers. Here is our own checklist. It is a list of things to find, not a legal reading of them.

Your standard customer terms. Find the terms on the back of your estimate or in your service agreement. Look for a confidentiality clause, a clause on who owns drawings, photos or reports, and any line on how you use customer information.

Your larger commercial contracts. A property manager, a school district, a general contractor or a fleet customer may have signed its own paper with you. Those contracts often carry confidentiality terms that the homeowner’s estimate doesn’t. Our advice: read the ten biggest accounts one by one, since some may say they own the site records. Our page on client-owned work and NDAs shows how to sort the files those contracts reach.

Maintenance agreements. A service plan with an HVAC or plumbing customer may carry its own terms on records and notice. Find the template and read it.

Your privacy notice. If your website, your booking form or your financing paperwork carries a privacy notice, it says what you collect and who you share it with. Read it as the customer would. Does it say you never share customer information? Does it say nothing either way?

The law where your customers are. Privacy law depends on the state, the size of the company and what the records hold. One example, as the Texas Attorney General summarises that state’s privacy act: “personal data” means information “linked or reasonably linkable to an identified or identifiable individual,” and “Publicly available information and deidentified data are not ‘personal data.’” The same page says small businesses, as the federal Small Business Administration defines them, “are generally exempt from the Act,” with an exception for selling sensitive data. It also lists what a covered company’s privacy notice must disclose, including “the categories of personal data that the controller shares with third parties.” Whether any of that reaches your company is exactly what counsel is for. Other states have their own rules.

Our page on whether licensing company records is legal lists whose rights to check first: customers, vendors, staff and regulated records.

When to ask counsel

Our advice: ask counsel before your first call with micro1 if any of these is true.

A customer contract has a confidentiality clause, or says the customer owns the reports or drawings.
Your privacy notice says you don’t share customer information, or you can’t find one.
You serve customers in a state with its own consumer privacy law and you don’t know whether it covers you.
Your records hold anything about health, such as a note that a customer is on home oxygen, or card and bank details.
You do work for a government body, a hospital or a school.

A short read before the call costs less than a long one after. micro1’s referral page says timelines vary with, among other things, “legal requirements.” Bringing counsel’s answer to the first call keeps those requirements from surprising anyone.

Who in your office keeps the signed contracts, and could pull the ten biggest by Friday?

What this means for a contractor with 30 or more staff

Here is one company, as our own hypothetical. Say an HVAC and plumbing contractor with 45 people. Residential service and replacement, some light commercial, eleven years in its field-service software. micro1’s referral page lists “30+ employees” among the requirements, so it is in range. Our page on companies with 30 or more staff covers that lane.

Where its customers sit. About twelve thousand contact cards. A bill-to block on every estimate. Gate codes and callback numbers on every work order. Card details in the payments system. Surnames in the dispatch channel. Two property management contracts with confidentiality clauses.

What it checks first. The terms on the back of its estimate. The two property management contracts. The service agreement template. The privacy notice on its booking page. Counsel reads all four and writes a page of answers.

What it asks to keep out. The contact table, the payments system and the marketing list stay home. Names, addresses, codes and phone numbers come out of everything in scope. The two property managers’ sites are handled however counsel says.

What it still has to offer. Eleven years of how an estimate became a job. How a replacement quote changed after a duct inspection. How a callback on a heat pump was settled with a credit and a second visit. How a slab leak was traced with a pressure test before anyone broke concrete. That is what a buyer licenses to train AI models on real work.

What it asks micro1. Confirmation that no customer will be contacted. What exactly gets removed from free-text notes. How many samples it will see, and from which years. What happens if a sample shows a name.

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

What is never included

micro1’s own words are short. It says “We protect sensitive information through data anonymization and secure handling,” and that shared records are processed “according to the agreed use case and handling requirements.” It doesn’t publish a fixed list of what is never included.

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 page about customers, two more belong on the list: the customer list itself, and anything a customer 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 TrustPast a referral fee when a company that applied through our link completes a deal. Your company pays us nothing.

We never see your files, and we never see your customers. Your records go from your systems to micro1. Your customers stay your customers; their details are handled on the terms you agree with micro1.

TrustPast

Questions and answers

Will micro1 contact our customers?

micro1 publishes no step that involves a company’s customers. The process on its pages runs between micro1 and the company: a company profile and a data manifest, a conversation with a Data Partnership Manager, contracting, the transfer and the review. As our own advice, ask micro1 to confirm in writing that it won’t contact anyone in your records.

Will our customers’ names reach the companies that use the records?

micro1 says that before any participation it confirms with the company that “Personal and identifying information is removed or transformed before your data is shared with third parties.” At contracting it commits “not to resell or distribute your data until personal and identifying information has been anonymized.” You can also review representative samples before prepared records are used.

What does the buyer want from a contractor’s files, if not the customers?

micro1 says it is looking for “data that reflects how work is actually performed within an organization.” In a trade company that is how an estimate became a job, how a change order was settled and how a repair was diagnosed. A customer’s name and payment explain none of those.

Do we have to strip out customer details before we send anything?

No. micro1’s answer to whether a company must anonymize its records before transferring them is: “No, micro1 has processes for de-identifying and transforming sensitive information.” What helps, as our own advice, is a short map of where customer details sit in each system.

Do we need to tell our customers?

That depends on your customer contracts, your privacy notice and the law where you and your customers are. We can’t answer it for your company, and we don’t give legal advice. Have counsel read your contracts and your notice before your first call with micro1.

Do we keep ownership of the records?

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