From the journal

Data residency for AI and fintech: where data, backups and remote support may be located

Data residency requirements should be applied to each record and operation in a service. A provider may need a domestic master record, a lawful route for overseas inference, permission for foreign support and a separately controlled recovery environment. Those conditions can coexist within the same customer contract.

34 min read

For an AI or fintech product using cloud infrastructure and an external model API, the practical starting point is a five-part location map: storage, inference, human access, logs and recovery. Identify the legal entity performing each function, the countries involved, the data it receives and any further use it makes of that data. Then check the customer's licence, the provider's own role and the applicable legal connection. Citizenship, a cloud brand and the label “fintech” seldom answer those scope questions on their own.

The result is usually a choice among three structures: an international enterprise service with controlled recipients; domestic regulated records with separately permitted foreign functions; or a segregated deployment covering the protected data and operations. The comparison below explains the conditions that make each structure workable across North America, Europe, Asia, the Middle East, Africa, Latin America and Oceania.

What does a data residency requirement actually require?

Keep four categories distinct when choosing a service or negotiating its terms.

  • Legal localisation. Question to answer: Must specified records, processing or a serving copy remain within a defined territory? Evidence that makes the answer usable: The operative provision, regulated actor, covered data, geographic boundary and any permission or exception.
  • International-transfer compliance. Question to answer: May this recipient receive the data or obtain access from abroad? Evidence that makes the answer usable: The recipient's identity and role, destination, purposes, onward recipients and the applicable transfer mechanism.
  • Data sovereignty. Question to answer: Who controls the service, keys and access, and which authorities can compel action? Evidence that makes the answer usable: Ownership and legal-entity maps, governing laws, enforceability, administrative privileges and key custody.
  • Contractual residency. Question to answer: What precise location and access boundary has the provider promised? Evidence that makes the answer usable: The executed schedule, included services, exclusions and verified configuration and recovery behaviour.

The legal tests differ materially. The EU General Data Protection Regulation (GDPR) supplies conditional transfer routes. Germany adds an approval framework for keeping certain electronic tax records in third countries. India's payment-system rules regulate covered payment data and temporary foreign processing. Kenya specifies domestic processing or a serving local copy for listed strategic purposes. A provider must apply each relevant layer to the actual workload. GDPR Articles 44–49; German Tax Code, section 146; Reserve Bank of India (RBI) payment-data circular; RBI payment-data FAQ; Kenya General Regulations, regulation 26.

A voluntary “EU only” or “Canada only” promise can impose a narrower boundary than the relevant baseline law. Define whether the promise covers storage, processing, support, telemetry and restoration. The choice has contractual consequences even where legislation would permit a wider deployment.

Start with the five layers that can cross a border

  • Primary storage and authoritative records. What to inspect: Production databases, account records, object stores, replicated datasets and the system treated as the source of record. Legal consequence and architectural alternative: Covered Indian payment data requires the RBI storage treatment. Covered United Arab Emirates (UAE) licensed financial institutions have a continuously domestic master-system requirement, with a defined approved foreign-branch copy alternative. Canadian federal financial-record rules can require complete Canadian records. Mexican electronic payment fund institution (IFPE) arrangements within Articles 44/45(I) also require usable Mexican transaction and accounting records. Separate those records from ordinary enterprise analytics.
  • Inference and other processing. What to inspect: Where the model receives and decrypts the prompt; routing to another model; retention, abuse monitoring, training and output storage. Legal consequence and architectural alternative: A locally hosted application can send protected data to a foreign model company. India's narrow foreign-payment-processing route requires return and deletion within its specified clock. Saudi exports need a matching legal route for the actual recurring service. Local inference is an option where that route or required approval is unavailable.
  • Human and administrative access. What to inspect: Support employers, countries, privileged accounts, screenshots, downloads and key administration. Legal consequence and architectural alternative: Foreign access can create a transfer or confidential-data sharing event while the database remains local. US recipient restrictions can also apply to access to US-hosted data. Control recipients and privileges separately from disk location.
  • Logs, embeddings and derived outputs. What to inspect: Prompt traces, safety logs, support tickets, vectors, fraud features and records used to explain or reproduce a decision. Legal consequence and architectural alternative: Classification follows content and legal function. A numerical representation can still identify a person or expose a regulated record. Minimise diagnostic content and separate logs with different retention or location duties.
  • Backups, restore and failover. What to inspect: Snapshot and replica destinations, recovery processing sites, export copies and continuity during parent or supplier failure. Legal consequence and architectural alternative: Kenya's strategic-purpose rule can require a serving local copy. Chilean bank rules can require a domestic contingency processing capability. New Zealand's BS11 can permit an overseas backup system where its ownership/control and other conditions are met. Nigeria’s payment-data FAQ keeps covered backup/disaster recovery (DR) in Nigeria for full compliance by 1 January 2027. Test the actual recovery path.

These examples rest on the RBI payment-data FAQ, Central Bank of the UAE (CBUAE) Operational Risk Management Regulation, Article 8.9, bank outsourcing regulation, Article 6, Office of the Superintendent of Financial Institutions (OSFI) B-10, Saudi transfer regulation, US Data Security Program, Kenya General Regulations, Chile's banking outsourcing chapter 20-7 and New Zealand BS11. The Mexican IFPE record example follows Article 49(IV); the Nigerian backup example follows CBN FAQ questions 7 and 13. The requirements apply to the actors and records described in those instruments.

Model weights need a separate assessment. They are different artefacts from prompts, embeddings and training records. The European Data Protection Board (EDPB)'s AI opinion explains that personal information may remain represented in parameters and be extractable through reasonably likely means. The assessment should examine the actual model and exposure paths. A claim of anonymity needs technical evidence. The underlying account or payment record can retain its separate legal status even where a particular derivative passes a personal-data test. EDPB Opinion 28/2024, paragraphs 27–34.

Where a controlled international service can work

Many general privacy frameworks support international processing under defined conditions. The conditions determine the recipient, contract, assessment and access design.

EU and UK: two transfer assessments

For the EU, first establish GDPR scope through the relevant establishment, offering or monitoring connection. The EDPB then identifies a Chapter V transfer where a GDPR-subject exporter makes personal data available to another controller or processor in a third country or international organisation. An overseas affiliate is a separate recipient. Remote support can therefore need a transfer mechanism even when primary storage stays in the EU. GDPR Articles 3–4 and 44; EDPB Guidelines 05/2021.

The EDPB treats an employee travelling abroad within the same legal entity differently from a separate foreign recipient. Security and other processing duties continue. It also treats an EU processor returning data to a foreign controller as a transfer. The Information Commissioner's Office (ICO)'s UK guidance takes a different approach to a UK processor returning the same information to its overseas controller: the processor does not initiate a restricted transfer in that situation. Establish the sender, recipient and roles before selecting clauses for an EU and UK service. EDPB examples 6–8; ICO restricted-transfer guidance.

An EU exporter can rely on an adequacy decision covering the actual destination and recipient, or an applicable Article 46 safeguard such as the appropriate standard contractual clauses (SCC) module or approved binding corporate rules. The SCC assessment must address destination laws and practices, onward transfers and necessary technical measures. If effective safeguards cannot be ensured, the clauses require suspension. A recurring cloud service needs a sustainable route; Article 49 exceptions have their own specific conditions. Brazil received an EU adequacy decision in January 2026, so older comparisons that assume every EU-to-Brazil transfer requires SCCs need updating. GDPR Articles 45–49; 2021 transfer SCCs, clauses 14–16; Decision (EU) 2026/179.

The UK transfer provisions changed on 5 February 2026. Article 44A provides the general routes, and Article 46 requires the exporter, acting reasonably and proportionately, to consider that the applicable protection test is met. Protection after transfer, taken as a whole, must not be materially lower. The ICO continues to call for a transfer risk assessment and identifies the International Data Transfer Agreement (IDTA) or the UK Addendum to EU SCCs as contractual instruments. Select the instrument for the relevant legal regime and complete its recipient, data and security details. UK GDPR Chapter V; ICO IDTA and Addendum guidance.

Different countries use different recipient and processing tests

  • Canada. Practical route for ordinary enterprise data: Accountability under the Personal Information Protection and Electronic Documents Act (PIPEDA) can support processing abroad through contractual or other comparable protection, together with relevant transparency and security measures. Quebec requires the section 17 assessment and written agreement for covered activity outside the province. Fact that changes the decision: An Ontario processor can be outside Quebec for this purpose. Classify the provincial connection and any financial-record obligations separately. PIPEDA; OPC processing guidance; Quebec private-sector Act.
  • Singapore. Practical route for ordinary enterprise data: The responsible organisation must ensure comparable protection under section 26 and the transfer regulations. A contract can identify the countries and bind the recipient; qualifying law, group rules and certification routes also exist. Fact that changes the decision: A data intermediary under a written processing contract has the section 4 allocation of duties. Its own-purpose training requires a fresh role analysis. The regulations include qualifying Global Cross-Border Privacy Rules (CBPR) and Privacy Recognition for Processors (PRP) certifications from March 2026. Personal Data Protection Act (PDPA), sections 4 and 26; Regulations 9–12.
  • South Africa. Practical route for ordinary enterprise data: The Protection of Personal Information Act (POPIA), section 72, permits routes based on sufficiently protective law, binding corporate rules or an agreement, and specified consent or necessity grounds. Fact that changes the decision: Personal information can include juristic persons. Special personal information or children's information sent to a third party in an inadequately protected country can require prior authorisation under sections 57–58. POPIA sections 1, 57–58 and 72.
  • Kenya. Practical route for ordinary enterprise data: Apply sections 48–49 and the regulations to the actual transfer. Document safeguards, an applicable adequacy route, necessity or properly informed consent as relevant. Fact that changes the decision: Sensitive personal-data processing outside Kenya requires consent and confirmation of appropriate safeguards under section 49. Strategic-purpose processing adds the local-server or serving-copy condition. Kenya Data Protection Act; General Regulations 26 and 40–48.
  • Brazil. Practical route for ordinary enterprise data: The General Data Protection Law (LGPD), Article 33, and National Data Protection Authority (ANPD) Resolution 19 provide the transfer framework, including the Brazilian standard clauses and other specified mechanisms. Check whether an adequacy decision covers the exact direction and scope. Fact that changes the decision: EU and Brazilian adequacy measures adopted in 2026 affect qualifying flows. Other destinations and onward transfers retain their own analysis; bank cloud rules remain additional. LGPD; ANPD Resolution 19; ANPD Resolution 32/2026, Brazil-to-EU/EEA adequacy; ANPD international-transfer mechanisms.
  • Mexico. Practical route for ordinary enterprise data: Distinguish a genuine controller-to-processor remisión from a transfer to a third party. Processing on instructions requires suitable terms and authorised subprocessing. Third-party transfers require the applicable notice, recipient obligations and consent or statutory exception. Fact that changes the decision: Independent model training or other provider purposes can change the classification. Use the 2025 private-sector Act and compatible regulations, including the cloud provisions, when assessing the arrangement. Private-sector data law; Regulations, Articles 49–55 and 67–76.
  • Australia. Practical route for ordinary enterprise data: Determine coverage under the Australian Privacy Principles (APPs), then apply APP 8's foreign-disclosure rules and APP 11 security. Reasonable steps, recipient obligations and potential accountability for overseas breaches must be assessed. Fact that changes the decision: The Office of the Australian Information Commissioner (OAIC) distinguishes disclosure from narrowly controlled storage/retrieval that can remain a use. Ordinary foreign-contractor or overseas-parent access often needs the disclosure analysis. Privacy Act; OAIC APP 8 guidance.
  • New Zealand. Practical route for ordinary enterprise data: A controlled overseas agent can fall within section 11, while disclosure to an independent recipient requires an information privacy principle (IPP) 12 route. Comparable safeguards, including contractual safeguards, are among the statutory options. Fact that changes the decision: Section 11 covers return of derived information, but the agent's independent use changes the premise. Model retention and training terms therefore matter directly. Privacy Act, section 4; section 11; section 22, IPP 12; Privacy Commissioner guidance.

The documentation should explain why the chosen route fits the actual recipient. An adequacy decision may have sector or recipient limits. Consent must satisfy its own legal conditions and can be unsuitable for the planned continuous service. An agreement must also be supported by operational controls and enforceable rights.

Where local records, access restrictions or approval change the architecture

India: keep the payment-data rule attached to the payment function

The RBI payment-data regime applies to its covered payment-system actors and records. The official FAQ permits overseas processing subject to returning the data to India and deleting it abroad within the earlier of one business day or 24 hours after processing. It also addresses specific cross-border-transaction treatment. Use those precise branches when designing inference, logging and restoration. Indefinite foreign model retention or chargeback copies require another supported basis; the temporary-processing exception does not provide it. RBI circular of 6 April 2018; RBI FAQ, questions 3–5.

For commercial-bank outsourcing, use the RBI's 28 November 2025 consolidated directions and classify the outsourced function. The information technology (IT) chapter's India-storage wording is qualified by applicable existing regulatory requirements. The financial-services offshoring chapter separately addresses original records in India. The classification matters because the direction contains exclusions from its IT-service-provider definition. A vendor's role in statement analysis, validation or data retrieval must be checked against that text. Commercial Banks: Managing Risks in Outsourcing Directions 2025, paragraphs 47, 53, 69 and 95.

Digital lending adds a separate data-storage branch. The commercial-bank Credit Facilities Directions, updated 1 October 2026, require covered data to be stored on Indian servers. Their defined commercial-bank scope excludes Small Finance Banks, Payment Banks and Local Area Banks; those customers require their own instrument. Data processed abroad must be deleted abroad and returned within 24 hours of processing. A lending service provider (LSP) may retain only the basic minimal borrower personal information needed within its bank agreement, and third-party disclosure requires the applicable explicit borrower consent or statutory/regulatory exception. Map these conditions to prompts, logs, vectors and recovery copies. Credit Facilities Directions, paragraph 3 and Chapter III, paragraphs 13–14.

Ordinary enterprise datasets require the applicable general privacy and cybersecurity analysis. The Digital Personal Data Protection (DPDP) Act and final 2025 Rules have staged commencement; their later-commencing substantive provisions belong in the change timetable. The Indian Computer Emergency Response Team (CERT-In) direction (iv) requires covered entities to keep information and communications technology (ICT) system logs securely for a rolling 180 days in India. FAQ 35 permits logs to be stored abroad also if they can be produced within a reasonable time; FAQ 36 addresses India logs and financial-transaction records for providers serving users in India. Apply overlapping payment and other sector rules to every additional foreign copy. CERT-In directions, paragraph (iv); CERT-In FAQs 35–36; DPDP commencement instrument; Final DPDP Rules.

Canada and Germany: a domestic record function can coexist with separate foreign processing

Canada's Bank Act record rules and OSFI B-10 require attention to the specified corporate, accounting and customer records, the applicable statutory exceptions and any supervisory direction. B-10 discusses complete Canadian electronic copies, day-end accuracy and regulatory access. Design a verifiable Canadian record store where that branch applies, then assess foreign inference and support under the separate privacy and outsourcing rules. OSFI B-10; Bank Act, section 239; Bank Act, section 245.

A targeted B-10 amendment took effect on 19 November 2026. Within the federal consumer-driven-banking framework, institutions should rely on participating entities’ government accreditation in place of duplicative risk assessment and contracting. They retain responsibility for residual operational, data-integrity and cyber risks. This qualified treatment does not establish a general cloud or model-provider exemption. B-10, section 2.2.1.2; OSFI amendment backgrounder.

Germany's Tax Code permits required electronic books and records in another EU Member State when full prescribed tax access remains available. Keeping them in third countries requires the competent tax authority's permission and the cumulative section 146 conditions. The taxpayer must preserve the required location/provider information, usable records and access. Changes to the notified data-processing-system location or the engaged third party’s name and address must be reported immediately. If taxation becomes impaired, the authority must revoke the permission and order prompt return to an EU Member State. A segregated tax-record service can preserve that function while other product data follows its own lawful route. AO section 146(2a)–(2b); AO section 147. If the taxpayer informs the authority that the relevant data is held by a third party, section 147(6) also places specified inspection, evaluation or transmission duties directly on that holder. Include that access process in the provider’s operational schedule.

United States: screen recipients and transactions as well as geography

The US Department of Justice (DOJ) Data Security Program regulates covered access to specified US sensitive personal data and government-related data by countries of concern or covered persons. Government-related data can qualify without a bulk threshold; personal financial data has its own threshold and aggregation rules. Covered-person status involves the detailed entity, ownership, employment, residence or designation tests. The relevant connection requires more than an assumption about citizenship. 28 CFR Part 202, definitions and prohibited/restricted transactions.

Prohibited transactions cannot be made lawful through ordinary privacy consent or transfer clauses. Restricted vendor, employment and investment transactions require the applicable Cybersecurity and Infrastructure Security Agency (CISA) security measures and other compliance duties. The financial-services and intragroup exemptions are defined by their actual activities; a new AI product or general cloud arrangement needs its own examination. A local US database can remain subject to these rules when a covered foreign recipient can access it. 28 CFR 202.301–305, 202.401 and 202.505–506; CISA security requirements.

Separately, determine whether the provider or customer falls within the Federal Trade Commission (FTC) Safeguards Rule, the banking guidance or California's service-provider and contractor regime. The California Gramm–Leach–Bliley Act (GLBA) exclusion is tied to the regulated information. Contract limits on purpose, disclosure and subprocessing need to match actual model use. These selected federal and California layers should be supplemented when another state, regulated activity or public contract creates a material connection. FTC Safeguards Rule; Interagency third-party guidance; California privacy statute.

Saudi Arabia: qualify the transfer route before relying on clauses

Saudi Arabia's 2024 transfer regulation requires a permitted purpose and the applicable safeguards and conditions. Its Article 4 mechanisms operate within defined circumstances. Those include limited non-recurring or time-limited transfers under their conditions, necessary central operations within a multinational group, and specified direct-benefit or research cases. Their sensitivity, certification, contract and risk-assessment requirements differ. A recurring external model API must fit the actual branch relied on; having a document called SCCs is insufficient to establish that fit. Personal Data Protection Law (PDPL), Article 29; 2024 Transfer Regulation, Articles 2, 4–5 and 7.

For institutions within the Saudi Central Bank (SAMA) cloud framework, the public/hybrid-cloud approval requirements are additional. The framework's default location principle and explicit approval requirement for use outside Saudi Arabia must be applied to the customer's scope and planned service. It also constrains secondary use. A local data and inference environment is a practical design where the necessary foreign permissions have not been obtained. SAMA Cyber Security Framework, section 3.4.3. Banks must separately obtain written SAMA non-objection for material outsourcing and for any proposed outsourcing to an overseas third-party provider, including nonmaterial arrangements. The overseas request includes the function/provider details, data treatment and legal opinions on compliance and supervisory access. Apply this bank rule even where an arrangement falls outside the public/hybrid-cloud subdomain. SAMA Rules on Outsourcing, paragraphs 10 and 41–42.

Government and critical-national-infrastructure customers require another classification step. The National Cybersecurity Authority (NCA)'s Cloud Cybersecurity Controls (CCC-2:2024) deleted the earlier local storage/processing and local support/monitoring controls and directed location questions to the National Data Management Office (NDMO). Determine the NDMO requirements for the actual data and entity before committing that branch. The 2026 PDPL implementing-regulation proposal is a separate legislative watch item. NCA CCC-2:2024, scope and Annex D; Official 2026 consultation.

The UAE has several different operating routes

  • Federal/onshore PDPL. Location and transfer decision: Check Article 2's territorial scope and exclusions, including qualifying sector data and free zones with their own data laws. Articles 22–23 provide export routes. Article 23's contractual limb is specifically framed for a destination without a data-protection law and includes enforcement conditions. Contracting consequence: Establish the exact applicable route and implementing conditions. The statute's Article 29 adjustment period is tied to Executive Regulations. Federal Decree-Law 45/2021, Arabic operative text.
  • CBUAE licensed financial institutions and banks. Location and transfer decision: C 1/2026, effective 14 September 2026, requires covered juridical-person licensed financial institutions (LFIs) to keep the master system in the UAE, with an approved foreign-branch up-to-date-copy alternative. Outsourcing that could significantly affect Critical Operations needs prior non-objection. Banks retain the 2021 daily-copy minimum where applicable, foreign-confidential-sharing approval/consent and material-outsourcing gates. Contracting consequence: Identify the actual licence, master records, branch approval and Critical Operations; apply the cumulative bank conditions where relevant. C 1/2026 scope; Article 8.9; Article 13; Bank outsourcing regulation.
  • Dubai International Financial Centre (DIFC) and Dubai Financial Services Authority (DFSA). Location and transfer decision: DIFC's transfer boundary includes the rest of the UAE. Use a qualifying adequacy determination, safeguards or a specific derogation. DFSA material outsourcing and technology controls add their own duties. Authorised Market Institutions additionally need prior approval for material outsourcing under AMI 5.5.3. Contracting consequence: Identify DIFC exports even where the cloud region is in Dubai. Keep processor terms, appropriate transfer instruments, regulator access and required notifications. The data protection officer (DPO) residency rule has its own conditions and group exception. DIFC Data Protection Law, Articles 6, 16 and 26–28; DFSA technology controls; GEN outsourcing controls; AMI 5.5.3.
  • Abu Dhabi Global Market (ADGM) and Financial Services Regulatory Authority (FSRA). Location and transfer decision: ADGM also treats mainland UAE as outside its territory. Its adequacy list and safeguards have recipient-specific conditions; bespoke safeguards can require Commissioner authorisation. Financial firms separately apply FSRA outsourcing and cyber rules. Contracting consequence: Map the exact destination, legal recipient and safeguard. Preserve material-outsourcing notification, written contracts, regulator access and controls for technology services and subcontractors. ADGM Data Protection Regulations, sections 26 and 40–46; ADGM adequacy list; FSRA outsourcing framework. Check additional prudential modules for the customer’s licence; preserve the rule/guidance distinction for subcontractor and deletion expectations.
  • Dubai Virtual Assets Regulatory Authority (VARA). Location and transfer decision: The Company Rulebook requires prior notification for cross-border outsourcing and effective supervision. Applicable personal-data law remains a separate layer. Contracting consequence: Preserve country-risk assessment, virtual asset service provider (VASP) control over client-data access, audit and regulator rights, continuity and exit. Match the actual licence conditions. VARA Company Rulebook, Part IV; VARA Technology and Information Rulebook. Company IV.A.4(a) also refers to CBUAE Circular 14/2021 to the extent applicable.

The phrase “UAE hosted” should identify a verified geographic property of the service. The governing privacy law and financial supervisor require the additional entity, licence and legal-zone analysis above. Mixed bank, VASP, DIFC and ADGM customers need distinct permissions and contract profiles even where infrastructure is shared.

Financial outsourcing adds oversight, continuity and change controls

A financial customer often remains responsible for a function delivered through several suppliers. The resulting contract requirements can reach the SaaS provider, its cloud host, its model company and its support affiliates. The provider should distinguish its direct legal duties from the commitments required to let its customer comply.

EU financial entities. The Digital Operational Resilience Act (DORA), Article 30(2), requires the contracted and subcontracted service locations and data processing/storage locations, with advance notice of changes. Critical or important functions have additional access, audit, contingency, testing and exit requirements. Regulation 2025/532 adds the relevant subcontracting assessment and change procedure: sufficient notice, a reasonable approval or objection period, and implementation only after approval or expiry without objection. A global subprocessor list should be linked to an effective contractual and operational change process. DORA Articles 28–30; Regulation 2025/532, Articles 3–6.

UK and Singapore financial customers. Prudential Regulation Authority (PRA) rules and SS2/21 require risk-based control over relevant outsourcing and data locations. The November 2024 statement recognises the resilience benefits of geographically distributed infrastructure. The Monetary Authority of Singapore (MAS)'s Notice 658 has separate branches for material ongoing services and services involving customer information, alongside relevant secrecy and supervisory-access controls. Determine the applicable branch and customer conditions before fixing the provider's approval, audit and notice schedule. PRA SS2/21, November 2024, sections 6–10; PRA Outsourcing rules; MAS Notice 658. For a Singapore bank’s material ongoing outsourced relevant service, subcontracting that requires disclosure of customer information also needs the bank’s written customer-consent basis under Notice 658 para 6.1, subject to para 6.2’s limited banking-company/designated-institution exceptions. Supplier engagement notice and the bank’s prior risk assessment are separate para 6.3 requirements.

South African and Kenyan banks. South Africa's banking guidance requires written approval for specified internal-audit, core-banking IT and financial-reporting IT outsourcing; other material outsourcing has an advance-notice route. Its cloud/offshoring directive preserves effective authority access and resilience. Kenya's operative banking outsourcing guidelines require prior approval for material outsourcing, including relevant information-system support, processing and recovery functions. Apply the banking rules in force while keeping proposed revisions separate. South Africa Directive 3/2018; Guidance 5/2014, paragraph 5.1; 2026 guidance-status record; CBK Prudential Guidelines, outsourcing. Kenyan payment service providers use a separate rule: National Payment System Regulations 2014, regulation 23 requires notification at least 30 days before operational outsourcing and preserves internal controls and Central Bank of Kenya (CBK) monitoring for material functions. NPS Regulations, regulation 23.

Brazil and Mexico. Brazil's banking and other Central Bank of Brazil (BCB) outsourcing rules require appropriate country, access, contract and notification arrangements. Where the required supervisory information-exchange arrangement is absent, the specified advance authorisation route matters. BCB Resolution 85 also requires attention to its updated institutional scope. In Mexico, bank and IFPE rules have different triggers. The Mexican bank text reaches services performed abroad and foreign-resident providers. A Mexican data centre alone therefore leaves the provider-residence question open. An IFPE must assess privileged access and critical providers separately. For arrangements within Articles 44 or 45(I), Article 49(IV) requires usable Mexican records of all operations and accounting records under the IFPE’s custody, available even when the contracted provider fails. Article 50 adds a separate two-hour continuity mechanism only where its specified primary-cloud interruption risk and activity/account/balance thresholds apply; its independent-provider, own-infrastructure or jointly approved alternatives are not a universal Mexico-only backup rule. National Monetary Council (CMN) Resolution 4.893; BCB Resolution 85; Mexican banking provisions, Articles 326–328; IFPE provisions, Articles 44–50.

For a Mexican bank transaction, a contract schedule should record provider residence, physical service countries, approvals and usable regulator access separately.

Australia and New Zealand. The Australian Prudential Regulation Authority (APRA)'s CPS 230, effective 1 July 2026, distinguishes notification after certain material agreements from prior notification of material offshoring or significant proposed changes. Its narrow standard-contract exemptions for listed infrastructure providers and written APRA relief should be checked against the actual supplier. Ordinary cloud and model services require their own applicable contract analysis. Australia also has a distinct section 20Q(3) storage provision for credit-reporting bodies. Australian or external-territory storage is the supported branch here. As at 21 November 2026, the regulations contain no overseas-storage security prescription. The official explanatory memorandum distinguishes routine correspondence and application-based viewing or editing from storage; this distinction does not authorise persistent foreign copies or provider retention. APRA CPS 230; CPS 234; Privacy Act, section 20Q(3); Privacy Regulations. Official explanatory memorandum, paragraphs 2.55–2.57.

New Zealand BS11 focuses on applicable large-bank outsourcing arrangements, continuity and separation. The definition and the bank's actual registration conditions determine coverage. Its robust-backup requirements differ across direct and related-party structures, and the guidance permits an overseas backup system where the prescribed ownership/control conditions are met. The 2026 ANZ breach finding demonstrates why real backup capability and oversight need evidence. BS11, sections A2 and B2–B3; Reserve Bank of New Zealand (RBNZ)'s ANZ finding.

Apply transition dates to the deployment timetable

Three scheduled changes deserve explicit release and renewal checkpoints.

Nigeria's payment-data requirement has a full-compliance deadline of 1 January 2027. The Central Bank of Nigeria (CBN) circular requires covered payment-transaction data generated within Nigeria to be stored and managed in Nigeria. The official FAQ includes processing, related supporting datasets, relevant logs, backups and disaster recovery; Q6–7 reject offshore processing and backup/DR. Q8 permits overseas technical support with governance, monitoring, restricted access, audit and security that prevent unauthorised offshore copies, migration, synchronisation, retention or transmission. Check additional customer licence and approval conditions. Q16 permits limited necessary disclosures for legitimate cross-border payments and does not clear a general overseas model service. CBN circular of 15 June 2026, paragraph 2; CBN FAQ, questions 1–9, 13 and 16–20.

Ordinary personal-data transfers remain subject to the Nigeria Data Protection Act (NDPA) and General Application and Implementation Directive (GAID). GAID Article 28(3)(o) requires filing a data protection impact assessment (DPIA) with the Nigeria Data Protection Commission (NDPC) for cross-border transfers, and Article 28(9) requires assessment and filing before processing. A certified, Commission-accredited DPO must vet and sign the submitted assessment; its outcome belongs in the compliance audit return under Article 28(4), (5) and (12). Article 18(1)(e)’s consent wording for destinations without an NDPC adequacy decision must be read with Article 45, Schedule 5 and the NDPA’s statutory routes. A proposed non-consent route must resolve that interaction for its actual corridor; a transfer contract alone does not settle it. Nigeria Data Protection Act, sections 28 and 41–43; GAID 2025, Articles 18, 28 and 45 and Schedule 5.

CBN FAQ Q12 also tells financial institutions choosing data-centre, cloud or integration suppliers to check compliance with the National Digital Cloud Policy and its implementing framework. For the 2026 instruments, verify the applicable provider class, workload endorsement and transition. The three National Information Technology Development Agency (NITDA) instruments commence on 1 January 2027. Apply the additional policy sovereignty duties only after establishing the required Presidential approval and regulated-data designation for the workload. Supplier certification transitions do not extend the CBN payment deadline. 2026 Policy, sections 11.6–11.7 and 14.5; National Guideline for Cloud Computing in Nigeria (NCG), clause 5; National Cloud Technical Guideline (NCTG), clause 5; National Digital Infrastructure Assurance Framework (NDIAF), sections 5, 7, 18.9 and 21.3.

As at 21 November 2026, Chile's enacted data-protection reform is scheduled for 1 December 2026. Contracts spanning that date need a sustainable route under the new transfer provisions. The limited exception for specific, non-habitual transfers is poorly suited to a continuous cloud or model stream. Congress has also approved a bill proposing postponement to 15 October 2027, which the official tracker records at the presidential-approval stage as at 21 November 2026. No postponement had been enacted at that date. Law 21.719, new Articles 27–29 and first transitional provision; official bill 18.623-07 tracker. Chamber report of 20 November 2026.

Chile's existing bank outsourcing requirements already apply. Significant or strategic offshore processing requires the specified Chilean contingency centre unless the bank meets the express exemption conditions, including the required risk assessment and independent evidence. Banking-secret transmissions abroad also need the prescribed customer authorisation. Plan that existing banking architecture separately from the reform's commencement date. RAN chapter 20-7, sections III–V.

The published March 2026 UK SS2/21 update takes effect on 18 March 2027. Until that date, use the November 2024 statement for applicable expectations and prepare the contract and reporting transition for arrangements continuing beyond it. November 2024 SS2/21; March 2026 SS2/21 and its effective-date statement.

India's staged DPDP commencement and Saudi Arabia's proposed implementing changes should also appear in the change timetable. A consultation, enacted provision awaiting commencement and operative rule have different effects on the design.

Choose the deployment through a repeatable decision process

  • Identify actor, data and every operation. Next: domestic record or processing requirement?
  • Domestic record or processing requirement? Yes: build required domestic capability or obtain valid permission. No: map foreign recipients and access.
  • Build required domestic capability or obtain valid permission. Next: map foreign recipients and access.
  • Map foreign recipients and access. Next: available transfer and recipient route?
  • Available transfer and recipient route? No: change recipient, minimise data or keep function local. Yes: document transfer, purpose and security controls.
  • Document transfer, purpose and security controls. Next: financial outsourcing procedure applies?
  • Financial outsourcing procedure applies? Yes: complete approval or notice and enforce oversight rights. No: validate contract promises and recovery.
  • Complete approval or notice and enforce oversight rights. Next: validate contract promises and recovery.
  • Change recipient, minimise data or keep function local. Next: identify actor, data and every operation.
  • Validate contract promises and recovery. Next: release the assessed configuration.

The process produces three practical choices.

An international enterprise service is suitable where the actual data has no additional domestic-function requirement and every recipient and purpose has a supported route. Keep a country and legal-entity map, enforce processor instructions and independent-use restrictions, and apply the relevant local assessment. Quebec activity outside the province, Singapore comparable protection and New Zealand agency processing each require their own treatment.

Domestic regulated records with international functions can work where the local record requirement and separate foreign-processing route are both satisfied. Examples include a qualifying Canadian bank record store with separately assessed support, a German taxpayer's compliant EU record service, a Kenyan strategic-purpose tenant with a genuinely serving local copy, or an IFPE’s usable Mexican transaction/accounting records with separately compliant foreign functions. Indian payment inference must also meet its specific foreign-processing and deletion conditions.

A segregated deployment is appropriate where a mandatory condition remains unmet or the customer has accepted a stricter boundary. Include protected storage, inference, content logs, key access and recovery within the assessed environment. Restrict support to its permitted role. A shared control plane should receive only the data its own recipients and purposes are authorised to handle.

For mixed datasets, identify the specific fields, documents and operational dependencies that require separation. Keep technical controls aligned with contractual promises. An approved domestic database can still leak regulated content through a global tracing service, support export or model-retention feature.

Put the chosen route into a usable contract schedule

The schedule should convert legal conditions into specific provider obligations. Mandatory transfer clauses, regulator approvals and customer notices remain separate instruments where required.

  • Parties, licence and roles. Content to agree: Legal entities, regulated-customer category, controller/processor roles and the services each entity performs. Evidence to retain: Entity chart, licence and actual service descriptions.
  • Covered data. Content to agree: Personal, payment, bank-confidential, tax and credit-reporting records; prompts, outputs, logs, vectors and backups. Classify weights separately. Evidence to retain: Field-level map and documented classification decisions.
  • Locations by function. Content to agree: Storage, inference, support, logging, backup, restoration and key-management countries and legal recipients. Evidence to retain: Service-specific region settings and architecture diagrams.
  • Domestic records. Content to agree: Required master, serving or complete copy; completeness, update cadence, access and retention. Evidence to retain: Reconciliation, availability, readable export and restore tests.
  • Model handling. Content to agree: Permitted endpoints and purposes; retention including abuse logs; training and onward-provider controls. Evidence to retain: Executed model terms, settings and deletion evidence.
  • Support access. Content to agree: Authorised employers, countries, roles, approval, permitted exports and emergency process. Evidence to retain: Privileged-access configuration and audit trails.
  • Transfer and supervisory instruments. Content to agree: Exact safeguards, assessments, consent/necessity records, regulator decisions and notifications, with versions and scope. Evidence to retain: Signed instruments and evidence that their conditions are met.
  • Subprocessors and changes. Content to agree: Legal name, function, data, location, access and equivalent obligations; required notice, objection or approval before activation. Evidence to retain: Current register, downstream terms and change history.
  • Recovery and exit. Content to agree: Permitted backup and restoration sites; continuation/control rights; exports, deletion and transition services. Evidence to retain: Tested recovery and exit plans with actual dependencies.
  • Regulatory access. Content to agree: Enforceable customer, auditor and authority access and cooperation; lawful foreign-request handling. Evidence to retain: Contract provisions, access demonstrations and request records.

Set notice periods around the actual legal procedure and customer decision process. A single arbitrary number can be too short for one arrangement and legally irrelevant to another. DORA's relevant subcontracting process, Brazil's specific regulator timetable, Mexican licence-specific procedures and Kenyan bank approvals should each be reflected in the affected schedule. Where the law requires a decision before a change, the deployment process should prevent activation until that decision exists.

Location assurances should describe an observable boundary. “Customer transaction records and their recovery copies are stored in the named country; inference and support occur only in the listed locations” can be tested against configurations and contracts. A broader “all data stays local” assurance requires evidence covering every included service, log and access path. Avoid promising immunity from lawful government access; specify the controls and request-handling obligations the provider can perform.

Documents to request before selecting a region

Ask for the following evidence together, so that legal and technical teams assess the same service:

  1. The customer and provider entity map: financial licence, regulator, contracting entity, affiliates, support employers and actual licence conditions or approvals.
  2. The data-flow map: origin, category, purpose, recipients and every storage, inference, logging and recovery location. Include prompts, outputs, embeddings and model artefacts separately.
  3. The supplier terms: cloud and model contracts, processing terms, training permissions, retention exceptions, subprocessors, regulator access and exit rights.
  4. The configuration baseline: region selections, fallback routing, key custody, privileged access, telemetry settings and deletion controls.
  5. The recovery evidence: complete records, functioning local copies where needed, restore destinations, direct control and continuity through group or supplier failure.
  6. The legal-route packet: transfer assessment and instruments, customer permissions, supervisory decisions/notifications and any public procurement or stricter residency commitment.
  7. The change timetable: launch, renewals, effective dates, pending legislation and the events that require reassessment before processing changes.

The decisive gaps are usually concrete: an unidentified support employer, an external model's retained abuse log, a recovery environment in an unassessed country, an absent regulator permission or an unenforceable audit right. Fix the missing fact or condition before making the corresponding location promise.

Questions product and commercial teams should resolve

Does GDPR require EU data residency?

GDPR provides conditional international-transfer routes. An EU-only arrangement can be a valid customer choice and can simplify particular transfer dependencies. The complete decision still includes any national record rule, financial requirement and the scope of the provider's contractual promise. GDPR Chapter V; DORA Article 30; German tax-record location rules.

Can overseas support access a local database?

Apply the actual privacy, confidentiality and recipient tests to the access. The support employer's legal identity, country, privileges and purpose matter. EU/UK own-employee and processor-return distinctions, CBUAE foreign confidential-sharing requirements and US covered-person restrictions can produce different answers for the same technical remote session. EDPB transfer guidance; ICO guidance; CBUAE Article 6; 28 CFR Part 202.

Are encrypted backups or embeddings outside residency rules?

Establish the data and legal classification before relying on that conclusion. Encryption is a security control; access to keys, restoration and identifiable content remain relevant. A serving-copy, master-record or operational contingency requirement may also apply to the function of the record. Document technical anonymity separately where it is relied on. GDPR Articles 4 and 32; EDPB AI opinion; Kenya regulation 26; US DSP definitions.

Can one global service support ordinary and regulated customers?

Yes, where its data routing, access controls, contract profiles and operational evidence can satisfy each customer's applicable requirements. Otherwise separate the protected records or customer deployment. The architecture should make the lawful boundary enforceable through support, inference, logs and recovery as well as production storage.

What should a scoped review produce?

A useful review produces a data and recipient map, a classification of the actual legal constraints, supported deployment options and a contract schedule tied to implementation evidence. Licentium's existing guides on personal data in AI models, AI cloud exit contracts and the UK critical third-parties regime cover related questions. For a scoped data-protection and AI review, start with the entity and licence map, proposed data flows, cloud/model terms, support locations and backup design.

Planning a launch somewhere new?

Prefer email? Write to hello@licentium.io. By sending, you accept our privacy policy.