Your data stays in region, and a named person signs off every decision.
Actura was built around the two questions a chief risk officer and a head of underwriting ask first: where the data lives, and who stays accountable when a decision is wrong. This page answers both.
Regional data residency
Each organisation works in its own private space on the platform. Data is hosted in region, in Singapore, China and Australia as those deployments open, and nothing is installed on your premises.
Encrypted and permissioned
Data is encrypted in transit and at rest, with access permissioned to your organisation and its staff. Actura does not sell, share, or train public models on your submission or claims data.
A person signs off, always
Actura assembles the decision. It does not make it. An underwriter, a claims officer or a delegated authority team reviews and signs off before anything binds, pays or reports.
A source-linked audit trail
Every extraction, check and flag is logged and linked back to the source document. Evidence for a regulator, an auditor or the board comes out of the process, rather than being reconstructed afterwards.
Deterministic, checked steps
Actura runs the same validated pipeline on every submission, bordereau and claim, rather than improvising a fresh answer each time. The output stays consistent because the process is.
A proven engine underneath
Actura runs on Telligro Ubix, the execution engine already in live production with specialty carriers, MGAs and syndicates across Singapore, ASEAN and China.
Regulators and markets are tightening scrutiny of AI-generated documents and delegated authority oversight.
Industry studies report that 98 percent of insurers see AI editing tools fuelling a rise in digital fraud, and that 99 percent have already met manipulated documentation: convincing invoices, medical certificates and reports that pass a standard visual check.1
Delegated authority now represents around 40 percent of volumes in the London market and more than five billion pounds in premiums, and late or low-quality bordereaux remain the most cited operational drag.2
In Australia, the APRA CPS 230 operational risk standard commences on 1 July 2026 for regulated general insurers, sharpening focus on document-heavy, service-dependent processes of exactly this type.3
A note on compliance
Actura is built to support the way underwriters, claims officers and delegated authority teams already meet their obligations under local prudential standards and their own compliance programmes. It does not replace professional judgement, binding authority, or a compliance programme. We would encourage every organisation to review our data handling against its own requirements before onboarding.
What happens to a submission, end to end
Ingest
A submission, bordereau or claim arrives, by direct feed, email, secure transfer or broker portal, into a private space on the platform, over an encrypted connection.
Process and verify
The platform extracts, cross-checks and verifies inside your own workspace, in region. Nothing is used to train shared or public models.
Review and retain
An underwriter or a claims officer reviews and signs off. The file, and its source-linked audit trail, stay under your own access controls and retention policy.
1. Verisk, State of Insurance Fraud study, 2026. 2. Market commentary on delegated authority volumes and bordereaux data quality, 2026. 3. APRA, Prudential Standard CPS 230 Operational Risk Management, commencing 1 July 2026.
Give us one underwriting or claims workflow. We will run it on your own documents.
No integration work to start. We reply personally and put you in front of a working result.