Privacy and preparation
International data supplier fact sheet: what should it contain?
By SourceX Editorial · Reviewed by Noah Loul ·
10 sections
Short answer
An international data supplier fact sheet should state, for each record source, the collecting entity and country, the languages present as BCP 47 tags with a measured share, how dates, units and currencies are written, which rights and notices cover the records, and where they are stored and may be processed. Keep originals beside normalized values and mark unknowns.
Countries and languages
International data supplier
Key takeaways
- Fill the fact sheet per source system and collecting entity, never once for the whole company.
- Origin country, storage location and processing limits are separate fields, and each can change the answer.
- Record languages as BCP 47 tags with a variety description and a share measured on the records actually offered.
- Keep original dates, amounts and units beside normalized values, with the conversion rule and rate source.
- The sheet gathers facts for counsel and localization reviewers; it does not decide transfers or rights.
What should an international business data opportunity fact sheet contain?
An international data supplier fact sheet should state, for each record source, where the data was collected, which legal entity holds it, which languages and locales it contains and in what share, how dates, units and currencies are written, what rights and permissions cover it, and where it is stored and may be processed. It should keep original values next to any normalized or translated ones, and mark every unknown as unknown.
The fact sheet is a metadata document. Like a data profile one-pager, it describes records without sharing them. What makes the international version different is that several answers can change depending on the country of collection, the language of the text and the location of storage, and a buyer or reviewer cannot infer those from the company's headquarters address.
The template below has two parts. The country, language and source summary describes what the records are. The rights and custody summary describes who may decide about them and where they sit. Both are filled in per source, because a company with offices in three countries usually has three different answers.
Why the company's country is not the data's country
A company's country of incorporation answers only one question: which entity signs. The records themselves may have been collected in other countries, by subsidiaries, from customers abroad, and stored in a cloud region somewhere else again. Each of those facts can matter separately.
At a glance
Why the company's country is not the data's country
The Data & Trust Alliance's Data Provenance Standards model this distinction explicitly. The standard separates data origin geography, defined as where the data was originally collected, from data processing geography included or excluded and data storage geography allowed or forbidden, and it asks for country codes in ISO 3166 form. A fact sheet that records only one country collapses several fields into one and hides the questions a reviewer most needs to ask.
For a supplier, the practical rule is to write one line per source system and collecting entity, not one line per company. A Zendesk instance shared by a Dublin office and a Toronto office is two sources for this purpose if the two offices collected under different notices and laws.
- Collecting entity: the legal entity whose customers or staff produced the records.
- Origin geography: the country, and where relevant the state or province, where collection happened.
- Current storage location: the country or cloud region holding the system of record today.
- Processing limits: any country where a contract or law says the data may not be processed or stored.
Language fields: tags, varieties, translations and the English share
Record language with a standard tag, a short description of the variety and a measured share, not a single word like English. RFC 5646, the specification behind BCP 47 language tags, lets a tag carry a script and a region, so es-419 identifies Spanish as used across Latin America and the Caribbean and sr-Latn identifies Serbian written in Latin script. The region subtag is a two-letter ISO 3166-1 code or a three-digit UN M.49 area code.
Bender and Friedman's data statements for natural language processing recommend the same practice: give the language in BCP 47 form and add a prose description of the variety, because language varies by speaker, setting and region in ways that affect how models trained on it behave. For a business dataset that means noting, for example, that support tickets are written by customers in informal English while technician notes are terse and full of trade abbreviations.
Translation lineage needs its own fields. If any record was machine translated, human translated or written in one language and summarized in another, keep the original text with its identifier, the translated text with its own identifier, and a field that links them and names the method. A buyer evaluating English text needs to know which sentences a person actually wrote.
Measure the English share on the records you would actually offer, not on the system as a whole. Count by record and by characters, state the method, and report the share per source. A mixed-language source can often be split so that the offered subset is cleanly in one language.
Dates, units and currencies: keep the original and add the normalized value
Keep dates, quantities and amounts exactly as the source wrote them, and add a normalized field beside each one with the rule used to convert it. A date written 03/04/2025 means different days in different locales, and once it is rewritten without the original, the error cannot be found later.
At a glance
Dates, units and currencies: keep the original and add the normalized value
Electronic invoicing standards show what a disciplined approach looks like. The Peppol BIS Billing 3.0 specification requires dates in the ISO 8601 calendar date form YYYY-MM-DD, without time zone information, and requires every currency in an invoice to use the alphabetic ISO 4217 code. It also notes that the exchange rate used to convert VAT into the national currency is not specified in the invoice itself, so a dataset that converts amounts should record the rate source separately.
Units need the same care. Weights, volumes, temperatures and distances may appear in metric and imperial forms in the same archive, sometimes in free text. Record the unit system per source and per field, and flag free-text quantities that carry no unit at all.
- Dates: original string, source locale, normalized ISO 8601 value and the time zone of the source system.
- Amounts: original value, ISO 4217 currency code, and any converted value with its rate source and date.
- Units: original unit, normalized unit and the conversion rule.
- Names of places and entities: original spelling and script, plus any transliteration with its scheme.
The country, language and source summary
Fill this table once per source system and collecting entity. Every row needs an answer or the word unknown, plus the person who answered. It is the first half of the country, language, source, rights and custody summary.
| Field | What to record | Format | Who answers |
|---|---|---|---|
| Source system and entity | System of record and the legal entity that collected the records | System name, entity legal name | System owner |
| Origin geography | Country, and state or province where relevant, of collection | ISO 3166-1 and 3166-2 codes | Operations lead |
| Collection period | First and last dates of records offered | ISO 8601 dates | System owner |
| Languages and varieties | Every language present, with a variety description | BCP 47 tags plus prose | Localization reviewer |
| Language share | Share of offered records and characters in each language, with method | Percentages by source | Data preparer |
| Translation lineage | Which records are originals, translations or summaries, and how produced | Original ID, translation ID, method | Data preparer |
| Locale conventions | Date, number, unit and currency conventions in the source | Locale tag and field list | System owner |
| Source authority | Whether the system is the system of record or a copy, and who may change it | Short statement | System owner |
The rights and custody summary
The second half of the summary records who may decide about the records and where they physically sit. It does not answer legal questions; it collects the facts counsel needs to answer them quickly, and it separates technical access from privacy permission, ownership and contractual rights.
At a glance
The rights and custody summary
Two legal facts explain why the jurisdiction column matters. Under GDPR Article 44, any transfer of personal data to a third country or international organisation may take place only if the conditions of Chapter V are met, including for onward transfers. The United Kingdom runs its own regime: the ICO's guidance explains that a restricted transfer under the UK GDPR must be covered by UK adequacy regulations, appropriate safeguards or an exception, and that the UK's own standard clauses, the IDTA and the Addendum, are used instead of the EU clauses alone.
| Field | What to record | Evidence | Who answers |
|---|---|---|---|
| Rights holder | Entity that holds rights in the records and any third-party content inside them | Contracts, platform terms, IP assignments | Contract owner |
| Customer and vendor terms | Clauses that restrict sharing, by contract version and period | Clause references | Contract owner and counsel |
| Privacy notices | Notice versions in force during collection, per country | Notice text and dates | Privacy lead |
| Personal data present | Categories of people and fields, and whether de-identification is planned | Field list and sample review | Privacy lead |
| Database or similar rights | Whether a local right protects the compiled database itself | Counsel note | Counsel |
| Storage location | Country or cloud region of the system of record and backups | Admin settings | IT |
| Processing or storage limits | Countries where processing or storage is forbidden by contract or law | Clause or legal note | Counsel |
| Transfer path | Which entity would send the data, to which country, under which mechanism | Counsel note | Counsel |
| Custody plan | Whether records stay in place, move on encrypted media or are exported | Plan with named custodian | IT and project lead |
Which hidden assumption about language, dates or jurisdiction flips the verdict on a source?
The assumption most likely to reverse the answer is that the collecting entity and the storage location are in the same country. When they are not, a different privacy regime, a different transfer mechanism or a different database right may apply, and a source that looked straightforward becomes a counsel question.
In the European Union, the database directive gives a database maker who shows substantial investment in obtaining, verifying or presenting the contents a right to prevent extraction or re-use of all or a substantial part of them. That right protects the compiled database separately from copyright. A fact sheet should therefore ask, for each EU source, whether the database was compiled by the company itself or licensed in from someone who might hold that right.
Language assumptions reverse answers too. A source labelled English may be largely code-switched or contain attachments in another language, which lowers the measured share once someone samples it. A date field assumed to be month-first may be day-first for one office, which silently shifts every record from that office.
- Collecting entity differs from the signing entity or the storage country.
- A source labelled with one language turns out to be mixed once sampled.
- Date or decimal conventions differ between offices sharing one system.
- Records include content licensed in from a third party in another country.
- A customer contract in one country carries a data localization or confidentiality clause.
Worked example (illustrative): a Singapore freight forwarder with three offices
This example is illustrative and describes no real company. A freight forwarder headquartered in Singapore holds shipment and customer service records in one transport management system and one help desk, with offices in Singapore, Kuala Lumpur and Jakarta. The figures are counts and shares invented to show how the sheet behaves.
The fact sheet splits the help desk into three sources by office. The Singapore and Kuala Lumpur sources are mostly English, with some Malay and Chinese in customer messages. The Jakarta source is mostly Indonesian. Because the language share is measured per source, the company can see that offering only the first two sources gives a far cleaner English subset than offering the whole help desk.
- Exception: the Malaysian source falls short of a 90% English threshold as a whole, but splitting out messages tagged ms raises the offered subset above it; the sheet records the split rule so the figure can be reproduced.
- Limit: the shares come from a sample; the sheet states the sample size and method, and the figure is re-measured on the final offered records.
| Source (illustrative) | Languages (BCP 47) | English share of records | Storage location | Open question |
|---|---|---|---|---|
| Help desk, Singapore entity | en-SG, zh-Hans, ms | About 94% (illustrative) | Cloud region in Singapore | Customer contract confidentiality clauses |
| Help desk, Malaysia entity | en, ms | About 88% (illustrative) | Cloud region in Singapore | Transfer path from Malaysian entity |
| Help desk, Indonesia entity | id, en | About 20% (illustrative) | Cloud region in Singapore | Excluded from first offer |
| Shipment records, all offices | Structured fields, en | Not applicable to codes | On-premises server, Singapore | Free-text remarks need sampling |
Points where the sheet hands over to counsel or a localization specialist
The fact sheet collects facts; it does not decide legality, translation quality or eligibility. Hand it over rather than filling gaps with assumptions at the points below, and record each handover in the sheet so the next reader knows the question is open.
- Personal data would leave the country or bloc where it was collected; counsel decides the transfer mechanism.
- The records include content compiled or licensed from a third party, or an EU database the company did not build itself.
- Privacy notices differ by country or changed during the collection period.
- More than a small share of records are translations, summaries or mixed-language text; a localization reviewer confirms the lineage and the measured share.
- Any source would need to move physically to be reviewed, which raises custody and export control questions for IT and counsel.
How SourceX reads an international fact sheet
Read against the sheet, SourceX's eligibility rule is simple to apply: it works with U.S., Canadian and EU companies that had 50 or more full-time employees at their peak, contractors excluded, and it can consider companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when the offered data is at least 90% English, as confirmed on the actual dataset.
For those countries the measured English share of the offered records decides eligibility, not the headquarters address or the staff's working language, and every dataset still goes through rights, privacy, quality and buyer-fit review. Large datasets can remain in the company's storage or travel on encrypted drives, and the first step is a brief company questionnaire, so the fact sheet can stay internal at that stage.
Frequently asked questions
What is a data supplier fact sheet?
It is a metadata document that describes a set of records without sharing them: sources, collection countries, languages, date ranges, rights, storage and custody. Buyers and reviewers use it to judge fit and to find the questions that need specialist review before any data moves.
How do you record the language of a business dataset?
Use a BCP 47 language tag for each language present, add a short description of the variety and writing style, and measure the share of each language on the records you would actually offer. Keep originals and translations in separate, linked fields.
Does the company's country decide which privacy law applies to its data?
Not on its own. The country where records were collected, the entity that collected them and the location where they are stored can each matter. The fact sheet records all three so counsel can decide.
Should dates and currencies be converted before sharing a dataset?
Add normalized values, but keep the originals. Record the source locale, the conversion rule and, for currency, the exchange rate source and date, because the source document may not carry the rate used.
How is the English share of a dataset measured?
Sample or scan the records you intend to offer, count by record and by characters, state the method and report the share per source. Re-measure on the final offered set, since filtering and splitting change the figure.
Sources
- The Data Provenance Standards define separate fields for data origin geography, processing geography included and excluded, and storage geography allowed and forbidden, with country codes in ISO 3166 form. Source
- RFC 5646 defines language tags whose region subtag is an ISO 3166-1 code or a UN M.49 code, with es-419 for Latin American Spanish and sr-Latn for Serbian in Latin script. Source
- Bender and Friedman's data statements recommend giving each dataset's language in BCP 47 form with a prose description of the language variety. Source
- Peppol BIS Billing 3.0 requires dates in ISO 8601 calendar date form YYYY-MM-DD without time zone information. Source
- Peppol BIS Billing 3.0 requires every currency in an invoice or credit note to use the alphabetic ISO 4217 code. Source
- Peppol BIS Billing 3.0 notes that the exchange rate used to convert VAT into national currency is not specified in the invoice instance. Source
- GDPR Article 44 permits transfers of personal data to third countries or international organisations only when the conditions of Chapter V are met, including for onward transfers. Source
- The ICO explains that a UK restricted transfer needs UK adequacy regulations, appropriate safeguards or an exception, and that the IDTA and Addendum are the UK standard clauses. Source
- Directive 96/9/EC gives a database maker who shows substantial investment in obtaining, verifying or presenting the contents a right to prevent extraction or re-use of all or a substantial part. Source
See if your company qualifies
A short company assessment. No data uploads are needed.