United Kingdom · Private AI

Private AI API in the United Kingdom: UK GDPR, ICO transfers and public-sector procurement

A UK buyer has to keep personal data inside UK GDPR, justify any transfer to Frankfurt or Virginia, and answer ICO and public-sector procurement questions. Plugsky has no UK region. The honest offer is the nearest live EU region plus contract-led private deployment.

Short answer. There is no UK data region. The nearest live Plugsky region is EU Frankfurt (eu-central-1); US Virginia and Singapore APAC are alternatives, not UK locations. Private VPC, on-premises, air-gapped deployment and Riyadh Enterprise are contract-only. Frankfurt is outside the UK, so transfer rules still apply; review the DPA, the transfer mechanism and a transfer risk assessment with counsel.

2027 planning guide — evidence checked 20 November 2026.

Availability at a glance

“Not claimed” is a deliberate answer. Plugsky does not have a UK data centre to sell, and a contract-led deployment does not create one.

Plugsky availability for UK buyers, November 2026
OptionStatusWhat it means in the UK
Live regionnot claimedNo UK region is live. Do not plan around a local data centre.
Nearest regionnearestEU Frankfurt, eu-central-1. US Virginia and Singapore APAC are farther alternatives.
Private VPCcontractDedicated scope in a live region; network, keys and support access are confirmed in writing.
On-premisescontractCustomer-operated deployment; hardware and support scope sit in the contract.
Air-gappedcontractOffline deployment; model bundle and update path are agreed in writing.
Riyadh EnterprisecontractEnterprise option in Riyadh; not a UK default and not a self-serve region.

What a UK buyer is actually buying

UK buyers usually start with a transfer question, not a model question. Where is personal data processed? Who can access it? Which subprocessors are involved? What happens on deletion? Can the supplier support a DPIA and an ICO inquiry without improvising?

Plugsky's UK offer is an OpenAI-compatible API in Frankfurt, or a contract-led private deployment for teams that cannot use a shared region. No UK office, local entity, customer reference or UK data centre is claimed. The contracting entity is Plugsky Inc. in Delaware; that matters to procurement and to your conflict-of-laws review.

The practical job is to document the data path end to end: inference, logs, backups, support sessions, evaluation data and any human review. A “data never leaves the UK” claim would be false here, so the page does not make one.

The UK framework: UK GDPR, ICO transfers and the Procurement Act

Three frameworks shape a UK purchase: data protection, international transfers and public procurement. They ask different questions and need different evidence.

UK GDPR and the ICO

The UK GDPR and the Data Protection Act 2018 set the core obligations, as amended by the Data (Use and Access) Act 2025. The ICO's guidance is being updated in places, so check the current version rather than a cached summary. Controllers need a lawful basis, transparency, a processor contract and appropriate security; a DPIA is likely for a new AI use case. Verify with counsel how the amendments apply to your processing.

International transfers

Frankfurt is outside the UK, so the transfer rules apply. A restricted transfer needs a UK adequacy regulation, an appropriate safeguard such as the IDTA or the UK Addendum, or an exception. A transfer risk assessment is part of the safeguard route. The UK's adequacy position for the EEA can simplify the mechanism, but check the scope and document the analysis; do not treat “EU” as automatically UK-equivalent. A US path needs its own transfer analysis, and the EU-US framework is not a blanket UK solution.

Procurement Act and cloud security

The Procurement Act 2023 came into force on 24 February 2025 for most England, Wales and Northern Ireland public procurement. It changes the commercial pathway, notices and the central digital platform; framework routes and social value still matter. Most devolved Scottish public bodies procure under the Procurement Reform (Scotland) Act 2014, so confirm the route. Security teams commonly use the NCSC Cloud Security Principles, and Cyber Essentials is often requested; Plugsky does not claim Cyber Essentials, ISO 27001 or a Crown Commercial Service framework place.

How Plugsky maps to a UK review

Treat these links as evidence requests. The contract, not the marketing page, decides the obligation.

  • Data location: confirm Frankfurt processing, backups, logs and support paths. Start with data residency questions.
  • Transfer file: DPA, IDTA or Addendum where relevant, and a transfer risk assessment. Verify with counsel.
  • Network isolation: private VPC or a dedicated endpoint is contract-led. See private VPC AI.
  • No outbound path: air-gapped deployment is contract-led. See air-gapped AI.
  • Key control: bring-your-own-key scope must be written into the order. See BYOK.
  • Procurement evidence: request the security pack and current SOC 2 report under NDA through security procurement.
  • Commercial path: compare pricing, read the docs, or review the sovereign AI model.

London: finance, legal and public-sector review

London concentrates finance, insurance, legal, media and government buyers. Regulated firms bring model-risk, outsourcing and records-retention questions that sit beside the GDPR analysis. Public-sector buyers add the Procurement Act route and a security questionnaire. Frankfurt is a short European hop, but the transfer file and the DPA do the real work. A public-sector buyer may also ask for a DPIA template and a data-processing schedule before the demo. Next step: complete a DPIA and document the transfer position before a pilot, then test the API from your own network.

Manchester: digital, health and public services

Manchester's mix spans technology, media, healthcare, ecommerce and public services. Buyers often want a practical pilot, not a platform programme: a small team, a defined use case and a clear data flow. Test latency to Frankfurt from your own network; it is a cross-border path, not a local one. The public-sector route and information-governance sign-off can take longer than the technical setup. Next step: ask for the DPA and security pack, then run a two-week pilot with your own evaluation set and an agreed deletion test.

Cambridge: life sciences, deep tech and research

Cambridge buyers cluster around life sciences, deep tech, university spinouts and research-intensive software. The data is often sensitive, the IP is valuable and the review group includes research governance as well as IT. A shared region may be acceptable for non-personal research data, but patient, participant or staff data needs a stronger transfer and security file. Next step: request an architecture review under NDA and map every dataset to Frankfurt, private VPC, on-premises or air-gapped before the pilot.

Edinburgh: financial services and Scottish procurement

Edinburgh combines financial services, asset management, software, public sector and data science. Scottish public bodies mostly follow the Procurement Reform (Scotland) Act 2014 rather than the 2023 Act, so a bid that assumes the Westminster route can miss the actual process. Latency to Frankfurt is a short European path, but resilience and exit terms deserve equal attention. Next step: confirm the procurement route with your commercial team, then ask for the transfer file and an exit plan.

Local search phrases to validate

These are research prompts, not published keyword targets. Validate with a native reviewer; not published as localized copy. No volume, difficulty or ranking data is claimed.

UK phrases for local validation, not published copy
PhraseLikely intentValidation note
private AI API UKVendor discoverySeparate UK-only vendors from EU-region vendors.
UK data residency AIResidencyCheck whether the searcher needs a UK region or accepts an EU region.
UK GDPR AI APIComplianceLook for DPA, transfer and DPIA language.
ICO AI guidance APIRegulatorValidate whether the intent is guidance or enforcement.
sovereign AI UKSovereigntyCheck for public-sector and defence-adjacent intent.
public sector LLM APIProcurementCheck framework names and security questionnaires.
AI API for London financeVerticalWatch for outsourcing and model-risk wording.
on-prem LLM UKDeploymentSeparate on-premises from private VPC and from a UK region.

What we did not verify

We did not verify a UK region, office, local entity, customer or data centre; none is claimed. We did not verify Cyber Essentials, ISO 27001, SOC 2 certification, NHS DSPT, a Crown Commercial Service framework place or any ICO approval. We did not measure latency from London, Manchester, Cambridge or Edinburgh, and we did not review your DPA, DPIA or transfer risk assessment. We cannot confirm that Frankfurt satisfies UK adequacy for your specific transfer; the law and the signed terms govern. Verify with counsel and your procurement team.

FAQ

Does Plugsky have a UK data region?

No. There is no UK region. The nearest live region is EU Frankfurt, with US Virginia and Singapore APAC as farther alternatives.

Is EU Frankfurt good enough for UK data?

It can be an option, but Frankfurt is outside the UK. Check the transfer mechanism, the DPA and any transfer risk assessment with counsel before relying on it.

Is Plugsky UK GDPR compliant?

Compliance depends on your role, data flows and contract. Plugsky offers Article 28 DPA terms, but no blanket certification or ICO approval is claimed. Verify with counsel.

Can we keep all data in the UK?

Not in a Plugsky UK region, because none is live. On-premises or air-gapped deployment is contract-led and can run in your facility, but that is not a Plugsky UK data centre.

Is Plugsky Cyber Essentials certified?

No Cyber Essentials claim is made. Ask for the current security pack and verify any scheme status directly before relying on it in a bid.

Does the Procurement Act 2023 apply to our purchase?

It applies to most England, Wales and Northern Ireland public procurement from 24 February 2025. Most devolved Scottish bodies use a different route. Confirm with your commercial team.

Can we get a private VPC in the UK?

Private VPC is contract-led, but it would sit in a live region such as Frankfurt, not in a new UK region. Scope the location and network in writing.

How do we start a UK pilot?

Pilot against Frankfurt with your own prompts and data-flow map. For a private deployment, request an architecture review with security, legal and procurement present.

Sources

Last checked 20 November 2026. Official pages were reviewed on that date; legal and procurement summaries are for orientation, not advice.