Global delivery · US · UK · EU · Canada · Australia · Gulf
Collected in Pakistan. Delivered to your cloud region, under your law.
Most of our licensing goes to AI teams in the United States, the United Kingdom, Europe and Australia. This page sets out how that works in practice: contracts, compliance mapping, data residency, payment and time zones — so your legal, security and finance reviews have what they need before the first call.
By region
Who buys from each region, and what we map to
The compliance column is what our consent, DPA and datasheets are written to satisfy. It is not legal advice; your counsel decides what applies to your product.
| Region | Typical buyers | Compliance we map to | Delivery regions | Notes |
|---|---|---|---|---|
| United States | Frontier labs, voice AI, KYC/identity, call analytics, ADAS | CCPA/CPRA; state biometric laws such as Illinois BIPA for face and liveness data; NIST AI RMF documentation | AWS us-east-1 / us-west-2, GCP us-central1, Azure East US | US business hours overlap with our evening shift; same-day response every US working day |
| United Kingdom | NHS and public-sector language access, fintech, contact-centre AI, universities | UK GDPR and Data Protection Act 2018; ICO guidance; UK IDTA / Addendum for international transfers | AWS eu-west-2 (London), Azure UK South | Urdu and Punjabi are among the most spoken non-English languages in England and Wales, so UK demand is domestic, not export |
| European Union | LLM developers, speech companies, research consortia | GDPR with Standard Contractual Clauses; EU AI Act training-data documentation for general-purpose models | AWS eu-central-1 (Frankfurt), GCP europe-west, Azure West Europe | Datasheets are written to satisfy the AI Act summary-of-training-content obligation |
| Canada | Telecom IVR, healthcare interpreting, immigration services, universities | PIPEDA; Quebec Law 25 | AWS ca-central-1, Azure Canada Central | Punjabi and Urdu are top-ten non-official languages in Canada |
| Australia & New Zealand | Government language services, contact-centre AI, speech research | Privacy Act 1988 and the Australian Privacy Principles; NZ Privacy Act 2020 | AWS ap-southeast-2 (Sydney), Azure Australia East | Punjabi is one of the fastest-growing languages in Australia; morning-to-midday AEST overlaps our working day |
| Gulf & Singapore | Banks, telcos and government platforms serving South Asian workforces | UAE and Saudi PDPL; Singapore PDPA | AWS me-central-1, ap-southeast-1; Azure UAE North | Pakistani-language demand here is driven by a workforce of several million Urdu, Punjabi, Pashto and Sindhi speakers |
Why these markets need Pakistani-language data
Urdu, Punjabi and Pashto are domestic languages in the UK, Canada, the US and Australia
The 255 million speakers are in South Asia. The paying users are often in Bradford, Brampton, Houston and Sydney.
United Kingdom
Urdu and Punjabi are consistently among the top non-English languages in the England and Wales census. NHS trusts, councils, banks and utilities need speech recognition, interpreting and IVR that handle them.
Canada
Punjabi and Urdu are top-ten non-official languages. Telecoms, healthcare and immigration services are the buyers; Brampton and Surrey are the users.
United States
Hundreds of thousands of Urdu and Punjabi speakers, concentrated in New York, Texas, California and Illinois — plus every frontier lab that needs South Asian language coverage and evaluation data.
Australia
Punjabi was among the fastest-growing languages in the 2021 census; Urdu, Pashto and Hindko communities are established in Sydney and Melbourne. Government language-access programmes are the natural buyers.
Contracting
What the paperwork looks like
MSA, SOW, DPA, licence
Mutual NDA on day one. A master agreement with per-project statements of work, a data-processing agreement with SCCs or the UK Addendum where transfers require it, and a licence schedule that states training and derivative-model rights in plain terms. Your paper or ours.
Governing law and invoicing
Governing law is negotiated per agreement; England & Wales, Delaware and Singapore are all in use. Invoices in USD by default, GBP, EUR or AUD on request, paid by international wire. W-8BEN-E supplied to US payers.
Vendor review pack
Answers to SIG Lite and CAIQ questionnaires, network and access-control description, incident process, sub-processor list and insurance certificates, maintained and sent within one business day. Security detail.
Working together
How international teams run a programme with us
Weekly batches, a shared channel, and a kickoff in your time zone.
Scoping in your hours
Karachi is UTC+5. Our client team works a shifted day so US East mornings, the full UK afternoon and Australian mornings are all covered live; everything else gets a same-day written answer.
Spec sign-off and pilot
You approve the quota, transcription convention and acceptance test in writing. A 3–5 week paid pilot validates all three before headcount scales.
Weekly QA-passed batches
Delivered to your bucket with manifests and checksums, a QA report and the running datasheet. A shared Slack or Teams channel carries questions and decisions.
Acceptance and re-collection
Fourteen-day acceptance window per batch; anything outside signed tolerance is re-collected free. Rejected units are never invoiced.
Inside your perimeter if required
Work-in-your-VPC, on-prem annotation and secure-facility collection are available for regulated buyers; see Security.
Answers
Questions international buyers ask
Yes. US teams are our largest buyer group. Contracts are in English under a mutually agreed governing law, invoices are in USD, we supply a W-8BEN-E for your accounts-payable process, and data is delivered to the US cloud region you choose. Consent artefacts on every record are what make our face, liveness and voice data usable under state biometric laws such as Illinois BIPA.
Yes. We sign a DPA with Standard Contractual Clauses or the UK IDTA/Addendum as required, deliver to London or Frankfurt regions, and our datasheets document consent basis, composition and known limitations in the form the EU AI Act asks general-purpose model providers to summarise.
Yes. We deliver to Sydney regions, map our consent and handling to the Australian Privacy Principles, and our working day overlaps Australian mornings. Punjabi, Urdu and Pashto communities in Australia are growing quickly, so several Australian buyers use our data for domestic language-access products.
Raw collection happens in Pakistan on managed devices. Processing, QA and storage run on encrypted cloud infrastructure with access control and audit logs; you choose the delivery region. Retention after delivery follows your contract, including deletion on request. See Security for the technical detail.
USD by default; GBP, EUR and AUD invoicing on request. Pilots are billed on delivery; programmes are milestone-billed against QA-passed batches, typically net 30 by international wire. We are outside the UK and EU VAT area, so reverse-charge rules usually apply — confirm with your finance team.
Yes. We sign mutual NDAs the same day, work under your paper or ours, and answer standard security questionnaires (SIG Lite, CAIQ, custom) from a maintained vendor pack. Legal documents are sent within one business day of request.
Because the alternative is usually a reseller that subcontracts to Pakistan anyway. Buying at source gives you a direct consent chain you can audit, provenance labelled on every record, quota control over who is recorded, and a price that does not include a margin for a company that never met the speakers.
Start the vendor review today
Ask for the legal and security pack, or go straight to a free sample. Either way you hear back within six business hours.
Serving teams in 13 countries. Delivery to any AWS, GCP or Azure region.