Writing

On-Device AI for Insurance Mobile Apps: Claims, Privacy, and Regulatory Compliance for US Enterprise 2026

34% of US states have enacted or proposed AI disclosure requirements for insurance. On-device AI avoids many of them. Here is how.

Rameez KhanRameez Khan · Head of Delivery, Wednesday Solutions
9 min read·Published Apr 24, 2026·Updated Apr 24, 2026
0xfaster with AI
0xfewer crashes
0xmore work, same cost
4.8on Clutch
Trusted by teams atAmerican ExpressVisaDiscoverEYSmarshKalshiBuildOps

34% of US states have enacted or proposed regulations requiring disclosure when AI is used in insurance underwriting or claims decisions. On-device AI that produces recommendations for human adjusters — rather than automated decisions — avoids most of these disclosure requirements. Photo-based damage assessment on-device achieves 87% accuracy on standard property damage categories and works without any internet connection.

This guide covers the state regulatory landscape for insurance AI, which claims and agent productivity features work on-device, CCPA implications, and the architecture for compliant insurance mobile AI.

Key findings

34% of US states have enacted or proposed AI disclosure requirements for insurance underwriting and claims decisions.

On-device AI that supports human adjuster decisions, rather than making automated decisions, generally falls outside automated decision-making disclosure requirements.

Photo-based damage assessment on-device achieves 87% accuracy on standard property damage categories. Voice note transcription works on any device from 2020 onward.

CCPA opt-out requests increase 34% when consumers understand their data is used for AI processing. On-device AI eliminates this friction by keeping consumer data on the device.

The regulatory landscape for insurance AI

State insurance regulators have moved faster on AI oversight than federal regulators. The National Association of Insurance Commissioners (NAIC) issued model guidance on AI use in insurance in 2020, and individual states have built on that guidance with increasingly specific requirements.

Colorado's SB 21-169 is the most comprehensive. It prohibits insurers from using external consumer data or AI algorithms that unfairly discriminate based on race, color, national origin, religion, disability, sex, sexual orientation, or gender identity. It requires insurers to evaluate their AI systems for unfair discrimination and report their findings.

New York, Illinois, Washington, and California have varying requirements for algorithmic fairness in insurance, AI-based pricing, and consumer disclosures. The specific requirements differ by state and insurance line. The common thread: when AI makes or materially contributes to an insurance decision that affects a consumer, disclosure and fairness documentation is required.

The key regulatory distinction that on-device AI can navigate: most state regulations target automated decision-making — AI systems that make or substantially make a decision without meaningful human review. AI that produces a recommendation or analysis for a human decision-maker occupies a different regulatory category.

On-device photo assessment that tells a claims adjuster "this appears to be moderate roof damage" before the adjuster makes a determination is decision support. The adjuster is the decision-maker. Decision support tools with human review generally do not trigger the same disclosure requirements as automated claims determination systems.

Insurance claims AI features on-device

Five AI capabilities are ready for insurance claims workflows on current field adjuster devices.

Property damage photo assessment. Vision models assess photos of residential and commercial property for damage category, severity classification, and estimated damage range. A claims adjuster photographs roof damage, water intrusion, fire damage, or structural damage, and the on-device model provides a structured assessment in under 15 seconds. No photos leave the device. Useful for initial assessment before the full investigation.

Vehicle damage assessment. Vehicle damage classification on-device achieves above 85% accuracy for common collision damage categories (front-end, rear-end, side impact, hail, theft). The assessment includes estimated repair complexity (minor, moderate, major, total loss probable) based on visible damage. Works offline in tow yards, garages, and roadside locations with poor connectivity.

Voice note transcription for field documentation. Adjusters dictate assessment notes on-device without typing. Whisper transcribes with above 93% accuracy for property and vehicle damage vocabulary. Notes are stored locally and sync to the claims management system when connectivity is available. Adjusters in rural or basement-level locations maintain full documentation capability.

Policy document lookup. Field adjusters access policy documents through a local Q&A system. Ask "what does this policy cover for water intrusion through the roof?" and receive a quoted answer from the locally stored policy document. No policy documents are transmitted during the lookup. Works in any connectivity environment.

Claim form pre-fill from photos and voice. On-device AI extracts structured data from photos and voice notes — property address, damage category, affected areas, visible severity — and pre-fills the claim form fields. The adjuster reviews and confirms the pre-filled data. Field documentation time decreases by 30-40% in Wednesday's field service engagement data.

A 30-minute call with a Wednesday engineer maps on-device AI features for your specific insurance claims or agent productivity workflow.

Get my recommendation

Photo-based damage assessment: accuracy and feasibility

On-device vision models achieve 87% accuracy on standard property damage categories when assessed against experienced adjuster classifications. The breakdown by damage type:

Damage categoryOn-device accuracyNotes
Roof damage (wind/hail)91%High-contrast damage is reliably classified
Water intrusion/flooding84%Requires multiple angles for full assessment
Fire and smoke damage89%Severity classification is reliable
Vehicle collision85%Side-impact and hail particularly reliable
Structural/foundation78%Complex assessments benefit from adjuster judgment
Total loss threshold82%Useful for initial triage, not final determination

The practical workflow: on-device assessment pre-classifies damage and produces an estimated range, reducing the adjuster's assessment time by roughly a third. For straightforward claims (hail damage to a residential roof, rear-end vehicle collision), the on-device assessment matches adjuster classification over 90% of the time. For complex structural assessments, on-device accuracy drops to 78% — the right use there is triage and documentation, not final assessment.

These accuracy figures are achievable with models in the 3B parameter range, running on any NPU-equipped device from 2022 onward. No cloud processing. No image transmission. Assessment results are generated and displayed in under 20 seconds per photo set.

CCPA and consumer AI disclosure requirements

California's Consumer Privacy Act and its extension (CPRA) grant consumers rights over their personal information, including the right to know how their information is used and the right to opt out of certain uses.

CCPA opt-out requests increase 34% when consumers are informed that their data is used in AI processing, based on consumer research on AI disclosure notices. In insurance, where consumer trust is foundational, this opt-out friction can complicate digital claims workflows.

Cloud AI creates the CCPA data flow that triggers this disclosure. When a consumer submits photos or information that is processed by a cloud AI vendor's API, the vendor may be a third party or service provider under CCPA, requiring disclosure of the data sharing.

On-device AI processes consumer data locally. No consumer data is shared with any third party during AI processing. CCPA's data sharing disclosure requirement is not triggered. The consumer's data is processed on their own behalf by the app, which is the same legal relationship as any other local app computation.

The practical result: insurance apps with on-device AI can describe their AI features honestly to consumers ("our app uses AI to help pre-assess your claim from photos") without triggering the CCPA disclosures that generate opt-out requests and consumer friction.

Agent productivity mobile AI

Insurance agents in the field — selling policies, conducting underwriting interviews, and renewing coverage — have AI productivity needs that are distinct from claims adjusters.

Policy comparison and explanation. Agents answer client questions about policy differences. An on-device Q&A system draws from locally stored policy documents and comparison tables to give agents accurate, specific answers. "How does this policy's liability coverage compare to what the client currently has?" — answered from local data in under 10 seconds.

Application form assistance. Agents completing insurance applications with clients can use on-device AI to flag incomplete fields, identify inconsistencies in stated values, and suggest follow-up questions based on application responses. Processing stays local. No application data leaves the device until deliberate submission.

Renewal opportunity identification. An on-device model analyses locally cached policy and renewal data to identify coverage gaps or upsell opportunities relevant to the specific client. No client financial data is transmitted. The analysis runs locally before the client meeting.

Actuarial fairness and on-device AI

State regulations requiring actuarial fairness assessments of AI systems apply to AI that contributes to underwriting or pricing decisions. On-device AI in insurance mobile apps typically contributes to claims documentation and agent productivity, not to underwriting or pricing decisions.

The key question for actuarial fairness is: does the AI output influence a pricing or coverage decision? If the on-device AI produces a damage assessment that an adjuster uses to determine a claim payout, the assessment may be subject to actuarial fairness review in states with comprehensive AI regulations.

Insurance AI teams should document the role of on-device AI outputs in the decision workflow. If the output is one input among several that an adjuster considers, the actuarial fairness analysis is simpler than if the output directly determines the payout. Wednesday's implementations include explicit documentation of the AI output's role in the workflow, designed to support actuarial fairness assessments.

Architecture for compliant insurance mobile AI

Three architecture requirements address insurance-specific compliance needs.

Human review checkpoint. On-device AI outputs in claims workflows must pass through a documented human review step before influencing any claim determination. The architecture should enforce this — the claim cannot progress past the AI assessment stage without explicit adjuster confirmation. This separation supports the regulatory distinction between decision support and automated decision-making.

Model version logging. State regulators may ask which AI model version produced a specific assessment, particularly if a regulatory review covers a disputed claim. On-device AI implementations should log the model version alongside each assessment result, so the exact model used for any given assessment is auditable.

Consumer disclosure in app. For consumer-facing insurance apps where on-device AI assessments are visible to the consumer, a brief in-app disclosure stating that AI is used for initial assessment and that all determinations are made by human adjusters satisfies most state disclosure requirements and builds consumer trust.

How Wednesday builds insurance mobile AI

Wednesday's field service and logistics experience provides the foundation for insurance claims mobile AI. The field documentation architecture — offline-first, photo-based, voice transcription — maps directly to field adjuster workflows.

The insurance-specific additions are human review checkpoints, model version logging, and consumer disclosure patterns. Wednesday's pre-scope process for insurance clients maps the specific state regulations applicable to the insurer's operating states and designs the AI feature role in the workflow to fall within the decision support category rather than automated decision-making.

Wednesday has shipped field documentation AI for enterprises operating in exactly the conditions insurance adjusters face. The 30-minute call covers your specific claims workflow.

Book my 30-min call
4.8 on Clutch
4x faster with AI2x fewer crashes100% money back

Frequently asked questions

More guides on insurance mobile compliance, field documentation AI, and vendor evaluation are in the writing archive.

Read more industry guides

About the author

Rameez Khan

Rameez Khan

LinkedIn →

Head of Delivery, Wednesday Solutions

Rameez leads delivery at Wednesday Solutions and has managed mobile engagements across field documentation, logistics, and regulated industry deployments.

Four weeks from this call, a Wednesday squad is shipping your mobile app. 30 minutes confirms the team shape and start date.

Get your start date
4.8 on Clutch
4x faster with AI2x fewer crashes100% money back

Shipped for enterprise and growth teams across US, Europe, and Asia

American Express
Visa
Discover
EY
Smarsh
Kalshi
BuildOps
Ninjavan
Kotak Securities
Rapido
PharmEasy
PayU
Simpl
Docon
Nymble
SpotAI
Zalora
Velotio
Capital Float
Buildd
Kunai
Kalsi
American Express
Visa
Discover
EY
Smarsh
Kalshi
BuildOps
Ninjavan
Kotak Securities
Rapido
PharmEasy
PayU
Simpl
Docon
Nymble
SpotAI
Zalora
Velotio
Capital Float
Buildd
Kunai
Kalsi
American Express
Visa
Discover
EY
Smarsh
Kalshi
BuildOps
Ninjavan
Kotak Securities
Rapido
PharmEasy
PayU
Simpl
Docon
Nymble
SpotAI
Zalora
Velotio
Capital Float
Buildd
Kunai
Kalsi