Nobody licenses "the company's data" in one go. You agree a scope, and leaving things out is a normal part of that. Mode says you agree the systems and date ranges before anything is exported, and Mercor says nothing moves until you approve the scope.
01The test for each record type
Run this on each row of your data inventory, not on the company as a whole.
02Seven categories to exclude or clear first
- Client-confidential material. Anything under an NDA or a client contract's confidentiality clause. Clear it with the client or leave it out. See who owns the data?
- Legally privileged records. Advice from your lawyers, and for law firms the client files themselves. Take legal advice before going near these.
- Special category personal data. Health, ethnicity, religion, sexual orientation, biometrics and similar get extra protection under UK GDPR, so treat these as out by default.
- HR files. Performance reviews, disciplinary records, salaries and sickness notes. See employee emails and chats.
- Third-party content. Licensed reports, stock images, purchased datasets and software you don't own. Your licence to use them usually doesn't let you pass them on.
- Payment data. Card numbers and bank details. They add nothing a programme would want and a lot of risk.
- Secrets. Passwords, API keys and tokens in code, tickets and wikis. Rotate any you find, whether or not you go ahead.
03Things you may simply prefer to keep
Some records are yours to license, but you might decide against it:
- pricing models and margins;
- unannounced products and live deals;
- board papers and M&A material;
- anything from the last few months that's still commercially sensitive. A cut-off date often solves this.
04How to make exclusions stick
- Write them into the agreement. Name the systems, date ranges and record types, for both what's in and what's out.
- Exclude at source where you can. It's safer to leave a folder out than to rely on a filter later.
- Ask for a sample. Check it for excluded material before the full transfer goes ahead.
- Agree what happens if something slips through, including how quickly it's removed and confirmed deleted.
De-identification helps with personal data, but it doesn't fix a confidentiality problem. See how de-identification works. This isn't legal advice.
05Questions people ask
Can I choose which data to license?
Yes. Programmes agree the scope with you first. Mode, for example, says you agree the systems and date ranges before anything is exported, and Mercor says nothing moves until you approve the scope.
Does the programme remove sensitive data for me?
All three describe de-identifying data, but that doesn't replace your own decision. Removing a name doesn't make client-confidential material yours to license.
Will excluding data lower the price?
It may, because programmes price on what they receive. No programme publishes a discount. A smaller clean dataset is still better than a larger one you had no right to license.
Sources
- data.mode.inc, checked 31 October 2026 · Apply to Mode →
- mercor.com/data, checked 31 October 2026 · Apply to Mercor →
- ICO: special category data, checked 4 November 2026
Our links to these programmes carry our referral code, so the programme can see the introduction came from us. The programme may pay us a referral fee, and you pay nothing.
