Practical AI use cases for Insurance in Hong Kong, the Hong Kong regulators that matter, and how dgm integrates them with osFoundry.
dgm is an independent osFoundry integration partner — not affiliated with osFoundry’s maker (OS LLC), and dgm has no completed client integrations yet.
AI is moving from pilots to everyday tools across Hong Kong’s insurance sector — but the value comes from a scoped use case, not a generic rollout. This guide looks at where AI genuinely helps in insurance, the Hong Kong rules that apply, and how to start sensibly.
Where AI helps in insurance
AI claims triage and fraud detection, underwriting and risk analytics and policy and document automation are among the most common starting points. A practical at-a-glance view:
| Use case | What the AI does |
|---|---|
| AI claims triage and fraud detection | Assists or automates AI claims triage and fraud detection |
| Underwriting and risk analytics | Assists or automates underwriting and risk analytics |
| Policy and document automation | Assists or automates policy and document automation |
| Customer-service copilots | Assists or automates customer-service copilots |
| Distribution support | Assists or automates distribution support |
The pattern that works is to pick one high-volume, repeatable, text- or data-heavy task, prove value with a baseline, and expand from there.
What about compliance and Hong Kong regulators?
Insurers and intermediaries are supervised by the Insurance Authority (IA). As of 2026 the IA has not issued a standalone AI guideline — AI-relevant obligations sit inside existing corporate-governance and cybersecurity guidelines — and the IA participates in the cross-regulator GenA.I. Sandbox++ launched in March 2026. Hong Kong is a major Asian insurance centre, so AI in pricing and claims must respect conduct and consumer-protection expectations and the PDPO for sensitive health and financial data; an insurance-specific AI framework is reportedly in development.
There is also no standalone, binding AI Act in force in Hong Kong in 2026 — the approach relies on advisory frameworks (the PCPD’s Model Personal Data Protection Framework and the Digital Policy Office’s generative-AI guideline) plus sector circulars that bind only the firms they cover — so the binding constraints today are the PDPO and the relevant sector rules, rather than an AI-specific statute.
Keeping data in Hong Kong
Sensitive claims and health-related data favour in-region or self-hosted processing. osFoundry’s managed cloud pins data to the US, EU or Japan — it does not currently offer a Hong Kong managed region (its nearest managed region is Japan). To keep data in Hong Kong, the honest path is self-hosting osFoundry (BYO Cloud) inside a Hong Kong cloud region such as AWS Asia Pacific (Hong Kong) ap-east-1, Microsoft Azure East Asia (Hong Kong SAR) or Google Cloud asia-east2 (Hong Kong), or running models locally on-device.
A model-agnostic platform like osFoundry helps here: it runs your chosen AI model under one orchestration layer, on usage-based pricing with no per-seat fees, and can be self-hosted in a Hong Kong cloud region or run locally for sensitive data.
Where dgm fits
dgm is an independent integration partner that helps Hong Kong businesses adopt osFoundry — scoping a first use case, handling the build, and connecting AI to the systems you already run. For insurance, that usually means starting with one use case such as AI claims triage and fraud detection. dgm is independent of osFoundry’s maker (OS LLC) and has no completed client integrations yet, so everything described here is a service offered, not a past result. If you want to scope a practical first project, dgm can help you map it out.