How to carve EU and UK records out of a US data license

How do you exclude EU and UK records from a US dataset?

Filter on several independent signals, apply them in a fixed order, then sample what remains. No single field identifies every European record, but mailbox domains, office location, CRM country, workspace membership and ticket locale together catch most of them. The result is a US-focused dataset that is simpler to license than one needing a full European data protection analysis.

This is general information, not legal, tax or financial advice. Which records must be excluded, and how thoroughly, is a decision for the company and its counsel. Many US companies take this route because licensing US records first keeps the dataset inside one legal frame.

What do you need before you start?

Have these in hand before anyone writes a filter.

• A list of systems in scope: email, chat, CRM, ticketing, shared drives, HR and finance exports.
• An owner for each system who can run exports and test queries.
• A list of EU and UK offices, remote staff, subsidiaries and known European customers.
• The counsel-approved rule on what "excluded" means: removed entirely, or kept after redaction.
• A written log where each filter, its date and its result are recorded.

The partner's role stops at the introduction. Partners never export, upload or describe confidential records; the company runs this work with SourceX once an inventory begins.

Which filters catch which records?

Use the table as a menu. Each row has a gap, which is why you stack them.

Step-by-step process

1. Define the exclusion scope. Agree with counsel whether the rule covers EU and UK residents, EU and UK offices, or both, and whether partners and contractors count.
2. Build the roster. List European staff, offices and subsidiaries from HR and finance. This drives the mailbox and workspace filters.
3. Apply structural filters first. Use country, locale and workspace fields because they are fast and auditable. Record counts removed per system.
4. Apply domain and keyword filters. Match email domains, European city names in signatures and European phone prefixes. Expect false positives; log the rule used.
5. Handle threads carefully. If one participant is European, decide whether to drop the whole thread or redact that participant. Whole-thread removal is simpler and safer.
6. Sample the remainder. Pull a random sample from each system and have a reviewer search for European indicators. If more than a handful appear, tighten the filters and run again.
7. Document and freeze. Save the filter definitions, counts, sample results and approver's name in the inventory file, then lock the dataset version.

The companion guide on keeping an introduction record without storing unnecessary personal data shows the same minimal-record habit on the partner side.

Common mistakes

Who does what on the company side?

Small teams often combine these roles, but someone must own each task. When a person leaves mid-project, the log lets a replacement continue without redoing the work.

Illustrative example

Illustrative and fictional: a 140-person US managed services firm has a Dublin sales office with six people and a handful of European clients. It excludes the six mailboxes, drops the Dublin channels from its chat export, removes CRM accounts with a European billing country, and filters tickets with a European locale. A sample of 200 tickets finds two that mention a European city, both from a multinational client with a US contract. The firm drops that client's tickets too and freezes the dataset with a one-page log. The license covers US records only.

How does this connect to the rest of the licensing process?

Exclusions are agreed with the company before any work begins and sit alongside redaction rules. A buyer will read the log. Contract terms such as a field-of-use restriction and a residuals clause govern what happens to delivered data. Other regimes can apply to specific records, such as the rules for student records held by education vendors.

Partners earn 25% of the eligible platform fees SourceX actually collects from the referred company's licensing deals, capped at $100,000 per referred company. The reward is paid only after the buyer pays and SourceX receives its fee; no reward is guaranteed.

When excluding is not enough

If the sample check keeps finding European records after two rounds of tightening, stop and ask whether the systems can be separated at all. Some tools mix regions in a single tenant without reliable location fields. In that case the company may need to exclude the whole system from the first license.

Consider pausing the opportunity if European records make up most of the data, if the company cannot tell which records are European, or if nobody can run the exports. Companies that fail today can sometimes qualify later once exports are preserved.

Next step

Run a preliminary screen with the company fit checker and read how the process works. If you know a US company with 50+ full-time employees at peak (contractors excluded) and years of records, register as a partner and make the introduction.