IntelliBooks — AI in Insurance

A customer emails and asks you to delete everything you hold about them. Under GDPR, the UK Data Protection Act, or CCPA, you have a legal obligation and a clock ticking. Simple request. Then you go looking for "everything," and you discover the uncomfortable truth about your own company: you have no idea where all of it is. The right-to-erasure request isn't really a privacy problem. It's a data-architecture problem wearing a privacy costume, and it exposes exactly how fragmented an insurer's data really is. One customer, twelve systems, zero map A single policyholder's footprint inside a mid-sized insurer typically spans: the policy admin system, the claims system, the billing platform, the CRM, the document store full of scanned PDFs, the data warehouse, three or four analytics marts, the email archive, the contact-centre call recordings, the fraud database, a couple of vendor platforms, and — the one everyone forgets — the backups. To them it's o...

Insurers are collecting more personal data than ever, and more intimate data than ever. Telematics knows where you drive and how hard you brake. Connected-home sensors know when you're home. Wearables know your heart rate. Behavioural models infer things you never disclosed. Most insurers are sleepwalking into a privacy problem with all of it — not through malice, but through a data architecture that was never built to track consent, and a growing gap between what they can collect and what they're actually permitted to use . The gap that's opening There's a widening space between two things: the data an insurer can technically gather, and the data it has clear, specific, current permission to use for a given purpose. A customer consented to telematics for a usage-based discount. Does that consent cover using the same data to validate a claim? To decline renewal? To feed a model that affects their premium in ways they never anticipated? These are different purpo...