Skip to content

Privacy and preparation

How to build a multinational data source jurisdiction map for one archive

By SourceX Editorial · Reviewed by Noah Loul ·

9 sections

Short answer

Document each slice of the archive separately: record the collecting entity, where the people were, where the data is hosted and read, the notice and contract in force, and the language, locale, currency and units. A multinational data source jurisdiction map puts those facts in one row per segment, marks each fact confirmed, inferred or unknown, and leaves the decision column for counsel.

System export

Multinational data source

This page covers how to build a multinational data source jurisdiction map for one archive.Illustrative

Key takeaways

  • Jurisdiction follows the facts behind each record segment, not the server or the parent company's country.
  • Eight facts per segment let counsel start: collecting entity, subject region, targeting, hosting, access, notice, contract and content conventions.
  • Each movement of the archive is a separate transfer question, judged under the rules of the jurisdiction it leaves.
  • Keep originals and standard codes for language, currency and dates, because silent conversions can move a record into the wrong jurisdiction.
  • Mark unknown facts as unknown and keep those segments out of scope until counsel decides.

Why can one company archive answer to several jurisdictions at once?

Because jurisdiction attaches to the facts behind each record, not to the server or the company name on the archive. A single CRM can hold customers in Ontario, Bavaria and Texas, entered by staff of three different subsidiaries, stored in one cloud region and read by support teams on two continents. Each of those facts can pull a different law onto the same table.

The EU General Data Protection Regulation shows why the server location settles little. Article 3(1) applies the regulation to processing in the context of an EU establishment of a controller or processor whether or not the processing itself happens in the Union, and Article 3(2) reaches organizations outside the Union when they offer goods or services to people in the Union or monitor their behavior there. A U.S.-hosted archive can therefore carry EU obligations on some rows and none on others.

Four questions get mixed up here and must stay separate. Access is whether your team can technically export the rows. Privacy permission is whether the law and the notices given to people allow a new use. Ownership is which entity holds the records. Contractual licensing rights are what your customer contracts, vendor terms and any later agreement let you do. A jurisdiction map feeds the second and fourth questions; it does not answer them, and de-identification alone does not create a right to license.

Which facts place a record segment in a jurisdiction?

Eight facts, recorded per segment, are enough for counsel to start: who collected the record, where the people were, where the record lives, who can read it from where, which notice and contract governed it, and how the content is written. A segment is any slice of records that shares all eight facts, so one system usually breaks into several segments.

Pull each fact from a system field or a dated document rather than from memory. Where the only evidence is a habit (the Paris office always used that pipeline), record it as inferred, not confirmed.

Which facts place a record segment in a jurisdiction?
FactQuestion it answersWhere it usually livesIllustrative value
Collecting entityWhich legal entity created or received the record?Owner or business unit field, company code in the ERP, invoice letterheadExample GmbH (DE)
Subject regionWhere were the people the record is about?Billing or shipping country, account country, phone country codeDE, AT
Targeting or monitoringWas the service offered to, or behavior tracked in, that region?Localized storefront, country-specific price list, analytics tagsGerman-language storefront with EU shipping
Hosting regionWhere are the bytes stored now and at collection?Cloud tenant settings, data residency page in the admin consoleUS East, migrated from EU Central in an illustrative year
Access locationsFrom which countries do people or vendors read it?Support rota, vendor contracts, SSO login country reportsUS, DE, outsourced support in a third country
Notice versionWhat were people told at collection?Privacy notice archive with effective dates, sign-up form copyNotice v3, effective date on file
Governing contractWhich customer or vendor terms cover the record?MSA governing-law clause, order form, platform termsCustomer MSA under German law
Content conventionsWhich language, locale, currency and units is it written in?Record language, locale setting, currency field, unit fieldsde-DE, EUR, metric

What should the source jurisdiction and rights matrix include?

The matrix is one row per segment and one column per field below, plus a decision column that only counsel fills in. It is built to be counsel-reviewed: the supplier fills the facts, a qualified lawyer for each jurisdiction records the decision, and nothing is offered until that decision exists. Treat the field list as the input dictionary; keep codes standard so a buyer or reviewer can read the matrix without a glossary.

At a glance

What should the source jurisdiction and rights matrix include

Standard codes matter more than they look. Language tags under BCP 47 (RFC 5646) combine a language subtag with an optional region subtag, usually an ISO 3166-1 alpha-2 country code, so fr-CA and fr-FR stay distinct. Currency belongs in ISO 4217 three-letter alphabetic codes, which tell CAD, USD and AUD apart where a bare dollar sign cannot.

  • segment_id: stable identifier, never reused after a segment is split or retired.
  • source_system and object: for example the CRM instance and the Case or Contact object, with the export query used.
  • record_count and date_range: counts and first and last created dates for the segment.
  • collecting_entity: legal name plus ISO 3166-1 alpha-2 country of establishment.
  • subject_regions: ISO 3166-1 codes with a status of confirmed, inferred or unknown.
  • targeting_evidence: what shows goods or services were offered to, or behavior monitored in, each region.
  • hosting_region_now and hosting_region_at_collection: provider region names, with migration dates.
  • access_locations: countries from which staff, affiliates or vendors read the records, and whether each reader is a separate legal entity.
  • notice_version and contract_reference: the notice text and the governing terms in force when the records were collected.
  • transfer_position: none identified, transfer with named mechanism, or open question for counsel.
  • language_tag, locale_conventions, currency_code and units: BCP 47 tag, date and number format, ISO 4217 code, unit system.
  • original_or_translation and translation_of: whether the text is the source language and, if not, the segment_id it was translated from.
  • counsel_decision, reviewer, jurisdiction_reviewed and review_date: filled only by the reviewing lawyer; blank means not cleared.

Worked scenario: one CRM, three entities, four customer regions

Here is how the matrix reads on an invented archive: a software company whose single CRM holds records created by its U.S. parent, a German subsidiary and a Canadian subsidiary, with customers in the United States, Germany, Austria and Quebec. All names, counts and outcomes below are illustrative, not drawn from any real company.

Two things stand out in the example. First, the German subsidiary's rows and the U.S. parent's EU-customer rows look identical in the CRM but reach the EU regulation by different routes, one through establishment and one through targeting. Second, the translated knowledge-base articles are their own segment because they repeat customer content in a new language and must point back to their originals.

Worked scenario: one CRM, three entities, four customer regions
Segment (illustrative)Jurisdiction factsContext to preserveOpen questions for counselStatus
S1: U.S. parent, U.S. customers, about 40,000 casesEntity US; subjects US; hosted US; read in USen-US, USD, imperial units, month-first datesState privacy notices in force at collectionFacts confirmed; awaiting review
S2: German subsidiary, DE and AT customers, about 9,000 casesEntity DE; subjects DE, AT; hosted US since an illustrative migration year; read in DE and USde-DE and de-AT, EUR, metric, day-first datesWas the migration a transfer, and which mechanism covered it?Transfer question open
S3: U.S. parent, EU customers via German-language storefront, about 3,000 casesEntity US; subjects DE; targeting evidence on file; hosted USde-DE, EURArticle 3(2) reach through offering services in the UnionAwaiting review
S4: Canadian subsidiary, Quebec customers, about 6,000 casesEntity CA; subjects CA-QC; hosted US; vendor support in a third countryfr-CA and en-CA, CAD, metricProvincial rules and the accountability for transfers for processingAwaiting review
S5: Translated help-center articles, about 1,200 itemsEntity US; derived from S2 and S4 contentTranslations tagged with source segment and languageDo customer details survive translation?Excluded until S2 and S4 clear
S6: Records with no reliable country field, about 700 casesEntity unknown; subjects unknownLanguage onlyNone until facts are foundExcluded

When does moving part of the archive become a cross-border transfer?

Under the European Data Protection Board's reading, a transfer exists only when three conditions meet: the exporter is subject to the GDPR for that processing, it discloses or makes the data available to a separate controller or processor, and that importer is in a third country or is an international organization. The Board also treats processing that is not disclosed to another controller or processor as outside the transfer rules, even when it happens outside the EU, though the rest of the regulation still applies.

The UK regulator frames the same test for UK GDPR. The ICO's brief guide says the restricted-transfer rules apply when UK GDPR covers the processing, you initiate the transfer and the recipient is a separate legal entity, and each such transfer needs adequacy regulations, appropriate safeguards or an exception.

Canada works differently. The Office of the Privacy Commissioner's 2009 guidelines say an organization remains accountable for personal information it transfers to a third party for processing and should use contractual or other means to provide comparable protection, while noting that no contract overrides the laws of the destination country. The OPC has since consulted on a stricter view of consent, so counsel should confirm the current position.

For the matrix, the practical decision is per hop. Record each movement the archive has already made (the migration in S2), and each movement a licensing deal would add (a delivery to a recipient abroad). Article 30(1)(e) of the GDPR already asks controllers to record transfers to third countries and identify those countries, so your processing records are the first place to look for the history.

How can a silent locale conversion put a record in the wrong jurisdiction?

Any assumption that silently converts one convention into another can move a record into the wrong jurisdiction or corrupt its meaning, so the matrix keeps originals and states every conversion. The four that most often flip a decision are below.

  • Language as a proxy for location: French text can come from Quebec, France, Belgium or a U.S. customer writing in French. Derive subject_regions from address or account fields, never from the language tag.
  • Day-first and month-first dates: 03/04 means two different days depending on locale. If a retention cutoff or a notice effective date decides whether a record is in scope, store ISO 8601 dates and the original string side by side.
  • Currency symbols: a dollar sign alone cannot tell a Canadian invoice from a U.S. or Australian one. Keep the ISO 4217 code with every amount, and never convert amounts in the licensed copy without a column stating the rate source and date.
  • Units and translated text: converting metric to imperial, or replacing an original with a translation, creates derived content. Keep the original, tag the derived version, and link it with translation_of so a reviewer can trace it back.

How do you record a jurisdiction fact nobody can confirm?

Mark it unknown, say what evidence would settle it, and keep the segment out of scope until counsel decides how to treat it. A blank field reads as fine; an explicit unknown forces a decision.

Use three statuses for each fact. Confirmed means a system field or dated document supports it. Inferred means a reasonable signal supports it, such as a phone country code standing in for an address, and the signal is named. Unknown means nothing supports it yet. Show the share of records at each status per segment, because a segment that is 95 percent confirmed and 5 percent unknown can often be split, while one that is mostly inferred usually cannot.

Three working rules keep uncertainty from leaking into a delivery. Never resolve an unknown by choosing the most convenient jurisdiction. When a fact is inferred, list the alternative jurisdictions it could plausibly be, and let counsel decide whether to treat the segment under the strictest of them or exclude it. Re-run the counts after any split so the matrix and the export query always describe the same rows.

What does counsel sign before a segment leaves the map?

Counsel signs a decision per segment, per jurisdiction, with a date; the supplier's job is to make that decision possible in one reading. A matrix is ready for that review when every segment has all eight facts at a stated status, every transfer hop is listed, and every translated or converted field points to its original.

Expect three outcomes. Cleared means the segment can enter a licensing scope on stated conditions, such as removal of direct identifiers or exclusion of a field. Conditional means a step must happen first, such as documenting a transfer mechanism or reviewing a notice version. Excluded means the segment stays out, with the reason recorded so nobody re-adds it in a later export.

Keep the review honest about scope. A privacy clearance does not settle ownership between group entities, and it does not override a customer contract that limits reuse. If the German subsidiary owns its records, for example, the parent may need an intra-group agreement before the records can be offered at all. Refresh the matrix when a hosting region, notice, vendor or governing contract changes, since each of those changes a fact on which a decision rests.

How does a jurisdiction map feed a licensing review?

A segment-level map shortens the rights review that any licensing deal starts with, because it shows which slices of an archive are candidates and which are not. SourceX runs that review, along with the contract, data preparation and delivery, for businesses licensing selected records to AI developers.

For a multinational group, the entity offering the archive decides which eligibility tier applies. SourceX takes on U.S., Canadian and EU companies whose full-time headcount reached 50 or more at its peak, with contractors left out of that count; an entity in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE or Saudi Arabia can be considered if at least 90 percent of the records it offers are in English, a share confirmed on the actual dataset rather than assumed from where the entity operates. Whichever tier applies, the dataset itself is then reviewed for rights, privacy, quality and fit with buyers.

A group can test its eligibility through a brief questionnaire before exporting anything, and nothing is delivered until the company has approved the scope and terms and signed the agreement, so a map like the one above can be built and reviewed by your own counsel before any record leaves your systems.

Frequently asked questions

Does storing an archive in the United States mean only U.S. law applies?

No. Under Article 3 of the GDPR, the regulation can apply because of an EU establishment or because services were offered to people in the EU, regardless of where the processing happens. Hosting location is one fact in the map, not the deciding one.

Is an employee abroad reading the archive a cross-border transfer?

The EDPB's guidelines treat a transfer as requiring disclosure to a separate controller or processor in a third country, so access by the same organization's employee is generally not a transfer under Chapter V. The regulation's other obligations still apply, and a vendor or affiliate reading the data is a different case that counsel should assess.

Do translated records need their own rows in the matrix?

Yes. A translation is derived content that can carry the same personal details in a new language, so it gets its own segment, a language tag and a pointer to the original segment. If the original is excluded, the translation should be excluded too.

Does de-identifying the records remove the need for a jurisdiction map?

No. Whether data counts as de-identified is itself judged under each jurisdiction's standard, and de-identification does not create a right to license. The map is what tells counsel which standard to apply to which rows.

Who should fill in the counsel decision column?

Only a lawyer qualified for the jurisdiction in question, with the date of the decision. The supplier fills in the facts and their status; a blank decision column means the segment is not cleared.

Sources

  • GDPR Article 3 applies the regulation to processing in the context of an EU establishment regardless of where it takes place and to non-EU organizations offering goods or services to, or monitoring, people in the Union; Article 30(1)(e) requires records of transfers to third countries. Source
  • The EDPB's Guidelines 05/2021 (version 2.0) set three cumulative criteria for a transfer under Chapter V and treat processing not disclosed to another controller or processor as outside Chapter V. Source
  • The ICO's brief guide says restricted-transfer rules apply when UK GDPR covers the processing, you initiate the transfer and the recipient is a separate legal entity, and each transfer needs adequacy regulations, appropriate safeguards or an exception. Source
  • The Office of the Privacy Commissioner of Canada's guidelines say an organization remains accountable for personal information transferred to a third party for processing, and that contracts cannot override the laws of the destination country. Source
  • RFC 5646 (BCP 47) language tags combine a primary language subtag with optional script and region subtags, where regions are usually ISO 3166-1 alpha-2 codes, for example de-AT. Source
  • ISO 4217 defines three-letter alphabetic codes for currencies, such as USD. Source

See if your company qualifies

A short company assessment. No data uploads are needed.

See if your company qualifies