# Claims and underwriting data that stays in-country

> Insurers use DataNature to automate claims documents with DocuContext, detect fraud and leakage, build underwriting risk models and run customer 360, all on a sovereign lakehouse where policyholder data stays in their jurisdiction and every decision is explainable.

Source: https://datanature.ai/industries/insurance
Publisher: Dlytica Inc. (DataNature is a Dlytica company)
Updated: 2026-11-05

## Use cases

- **Claims automation**: DocuContext classifies and extracts claim documents.
- **Fraud and leakage**: Models flag suspicious claims for review.
- **Underwriting**: Risk models on governed, lineage-tracked data.
- **Customer 360**: One view of policyholders across lines.

## Regulations

- PIPEDA and Québec Law 25
- OSFI B-10 and B-13 for federally regulated insurers

## Where do insurers start?

Usually with claims. Claims are document-heavy, slow and costly. DocuContext cuts manual handling, and the extracted data feeds fraud models in the same lakehouse.

## How are models kept explainable?

Every feature and score is traceable to source data in Atlas. Underwriters and auditors can see why a score was produced.

## Can we keep policyholder data on-premises?

Yes. DataNature can run fully on-premises or in a private cloud.

## Which insurance guides and use cases should I read next?

- [The data and AI platform for insurance companies](/blog/data-ai-platform-for-insurance-companies), with six illustrative scenarios across P&C, life and health.
- [AI in insurance claims: from FNOL to settlement](/blog/ai-insurance-claims-automation-fnol-to-settlement) and [insurance claims fraud detection](/blog/insurance-claims-fraud-detection).
- [AI for insurance underwriting](/blog/insurance-underwriting-ai-submission-intake-risk-scoring).
- [Customer data platform for insurers](/blog/customer-data-platform-for-insurers-policyholder-360-retention).
- [Telematics and IoT data for insurers](/blog/insurance-telematics-iot-usage-based-insurance-streaming).
- Use cases: [lapse prevention](/use-cases/life-insurance-lapse-prevention), [proactive claim updates](/use-cases/proactive-claim-status-updates), [catastrophe outreach](/use-cases/catastrophe-event-customer-outreach), [SIU assistant](/use-cases/siu-fraud-investigation-assistant-insurance), [subrogation](/use-cases/subrogation-opportunity-agent-insurance), [reinsurance bordereaux](/use-cases/reinsurance-bordereaux-treaty-analyst-insurance), [complaints monitoring](/use-cases/insurance-complaints-conduct-monitoring), [reserving data assistant](/use-cases/actuarial-reserving-data-assistant-insurance) and [usage-based insurance](/use-cases/usage-based-insurance-telematics-pricing).

## Frequently asked questions

### Does my data ever leave my country?

Not unless you allow it. Data, metadata, query logs, embeddings and prompts stay in the deployment you choose. The only way out is an external model API that an administrator enables per workspace in the Atlas AI gateway. It is off by default. Air-gapped installs have no outbound connection.

### Is DataNature built in Canada?

Yes. DataNature is built by Dlytica Inc., a Canadian company founded in 2018 and headquartered in London, Ontario. Canadian deployments are hosted on Edwin, R2i's 100% Canadian sovereign cloud, and operated under Canadian law.
