A route someone follows at speed turns a software error into a crash.Founded by a software developer who runs an AI app.
We place technology E&O with contingent bodily injury and property damage for navigation, fleet routing, driver-assist and mobility apps, so a crash that follows your route or alert does not fall between the driver’s auto policy, product liability and your software policy.
Tell us the situation.
One licensed human replies the same business day — not five agents, not an auto-responder. If the policy you have is already the right one, we will tell you.
We use this to quote and service your insurance, and we do not sell it or pass it to lead networks. Privacy policy.
The person placing your tech E&O runs an app with an AI coach of his own.
Kevin Kelsey
Founder | Principal Agent
Boring’s founder, Kevin Kelsey, owns and runs TrainRec, a fitness app with a built-in AI coach, and has placed insurance for AI apps. Insuring his own taught him how an underwriter reads a model. Personal guidance from an AI reads more like the work of a professional than like software, technology E&O forms commonly exclude bodily injury, and not every form will add it back. So whether your app answers money, health, hiring or farming questions, the gap between what it says and what the policy covers gets read by someone who has had to close it for his own product.
Send us what you have. We’ll tell you if it’s right.
Your current policy paperwork, a renewal notice, or nothing at all. A licensed agent reads it and replies the same business day.
What navigation or mobility app businesses actually need.
Technology E&O with contingent bodily injury and property damage
Claims that your routing, map data or alert was wrong and someone was hurt or something was damaged after following it. Contingent means the harm is blamed on relying on your output, not on anything your company physically did.
Without it — The tech E&O form usually excludes both bodily injury and property damage, which are the two losses a crash produces. Ask for the contingent grant by name and check that it names property damage as well as injury.
Product liability
Injury or damage caused by a physical device you make or sell, such as a dash unit, a telematics box or a sensor.
Without it — Software coverage does not follow your software onto hardware you ship, and a product policy may not read on the part of the claim that is about the map or the route.
Cyber & tech E&O
Breach response, ransomware and the notification costs that follow. Technology errors and omissions sits on the same policy and covers the software or service itself failing a client, which is the half most tech companies find out about too late.
Without it — Location history shows where a person lives, works and sleeps, and a leak or an unauthorized share of it is a privacy claim and a safety claim at once.
Commercial auto
Vehicles the business owns and the people who drive them for work.
Without it — If you run vehicles yourself, such as a delivery or mobility service with its own cars, the auto policy answers the crash and your tech E&O does not.
Hired & non-owned auto
Covers vehicles the business does not own but its people drive on the job: rentals, and employees running errands in their own cars. Their personal auto policy will not cover a business trip, and the claim lands on the business. Pricing depends entirely on HOW it is bought: as an endorsement on a general liability policy we write, HNOA often costs a few hundred dollars; as a stand-alone (monoline) policy it runs $2,500 to $5,000, and association practitioner programs (CPH, CM&F and similar) generally cannot take the endorsement, so "add HNOA to my existing policy for $300-$800" is usually not a real option. A package carrying GL, professional liability and HNOA together is typically cheaper than the monoline.
Without it — A ride or delivery app whose drivers use their own cars can be pulled into the claim when one of them crashes while following your routing.
General liability
Third-party bodily injury and property damage. It is the line nearly every contract names by default.
Without it — The certificate a fleet customer asks for first. Read it for a professional services or technology exclusion, which is where a crash claim tied to your software usually gets pushed off it.
What the regulators actually wrote down.
A wrongful-death complaint filed September 19, 2023 in Wake County, North Carolina Superior Court (case 23CV026335-910) alleges that Philip Paxson died on September 30, 2022 when he drove off an unmarked, unbarricaded collapsed bridge in Hickory, North Carolina while following GPS directions, and names Google LLC and Alphabet, Inc. among the defendants along with the bridge owners. These are allegations; we have not verified any ruling or outcome.
Complaint, Paxson v. Google LLC et al., Wake County Clerk of Superior Court, e-filed 9/19/2023 (copy published by plaintiff’s counsel) · checked 2026-11-01
NHTSA’s Standing General Order requires the manufacturers and operators it names to report crashes involving automated driving systems or Level 2 driver-assistance systems, and NHTSA states it imposes no reporting obligation on any other company or on individual consumers.
NHTSA, Agency Information Collection Activities; Notice and Request for Comment; Incident Reporting for ADS and Level 2 ADAS, Federal Register (March 4, 2026), document 2026-04240 · checked 2026-11-01
Under the Standing General Order as described in NHTSA’s March 2026 notice, a Level 2 driver-assistance crash must be reported within five days when the system was engaged within 30 seconds of the crash and the crash sent someone to a hospital, killed someone, deployed an air bag or struck a vulnerable road user.
NHTSA, Incident Reporting for ADS and Level 2 ADAS, Federal Register notice of March 4, 2026 · checked 2026-11-01
A motor carrier hauling hazardous materials that must be placarded, and not subject to a state or tribal routing designation, must use routes that do not go through or near heavily populated areas, places where crowds assemble, tunnels, narrow streets or alleys, unless there is no practicable alternative, a reasonable deviation is needed, or an emergency requires one; operating convenience is not a basis for finding a route impracticable.
49 CFR 397.67(b) and (c), Motor carrier responsibility for routing · checked 2026-11-01
A motor carrier carrying non-radioactive hazardous materials must comply with the routing designations a state or Indian tribe has made under the federal standards.
49 CFR 397.67(a), Motor carrier responsibility for routing · checked 2026-11-01
In a real placement an underwriter read an AI product giving personal guidance as closer to a professional service than to software; technology E&O forms commonly exclude bodily injury, and at least one major technology E&O form does not offer contingent bodily injury at all, so the market has to be chosen for it.
Kevin Kelsey, agency placement experience (underwriter correspondence and forms, insurers not named) · checked 2026-10-29
The claims we actually see.
Ordered by how often we see them, not by how dramatic they are. Each one names the coverage that answers it — and the policy people wrongly assume already does.
Less common, severe
A driver follows your route into a hazard and is injured or killed
Covered by Technology E&O with contingent bodily injury and property damage
The driver’s auto policy pays the driver’s own damage and defends the driver, and neither pays for your software. Tech E&O often excludes bodily injury, so without the contingent grant nothing in your program is built to answer the family’s claim.
Common
A truck routed over a low bridge or a restricted road damages the bridge, the load or other vehicles
Covered by Technology E&O with contingent property damage, plus the carrier’s own auto and cargo coverage
Property damage to a bridge or to somebody else’s truck is the loss tech E&O excludes. The carrier will turn to your contract and your policy to see whether you promised to stand behind the route.
Rare, catastrophic
A driver-assist or alert feature fails and another road user is hurt
Covered by Product liability for the device, plus technology E&O with contingent bodily injury
The injured person never used your app and never saw your terms, so no disclaimer reaches them. Who made the sensor, who wrote the alert and who installed it all matter, and each of those parties has a policy that can point at another.
Common
A rider or delivery driver is hurt while following your dispatch or routing
Covered by Hired and non-owned auto, plus technology E&O with contingent bodily injury
Your drivers may use their own cars on your instructions. The claim then reaches the app that dispatched them, and your own auto program may not respond to a car you do not own.
What our navigation or mobility app clients ask us.
Does tech E&O cover a crash that followed my app’s route?
Often not, unless the policy says so. Technology E&O is written for financial loss, and most forms exclude bodily injury and property damage in plain words, which are the two things a crash produces. The grant that closes the gap is contingent bodily injury and property damage on the tech E&O. Ask for it by name, check that it covers both words, and read whether it has its own smaller limit.
What are contingent bodily injury and contingent property damage?
Contingent bodily injury is an injury someone says came from relying on your app’s output, rather than from anything your company physically did to them. Contingent property damage is the same idea for things: the bridge the truck hit, the car that was struck, the cargo that was lost. For a navigation app the driver followed the route, so the harm is contingent on the software being wrong. It is usually added to a tech E&O policy as an endorsement.
The driver has auto insurance. Why isn’t that the end of it?
The driver’s auto policy answers for the driver’s driving. A claim that says the app sent the driver there is aimed at the app, and the auto insurer will not defend your software company. The injured party can sue the driver, the app maker and the maker of any device the software ran on, and each of those has a different policy that may exclude the claim. The place where three policies each point at another is where a founder finds out what was never bought.
How is this different from the fitness app page?
The fitness page is about contingent bodily injury: a user follows a plan and hurts their own body. Navigation adds two things. The harm is often property damage as well as injury, and tech E&O forms commonly exclude both. And the person hurt is often not your user at all, such as the other driver or a pedestrian, so no screen of terms they accepted stands between them and your company. The same grant applies and the claimant is further away.
Fitness and health app insurance, where contingent bodily injury starts
What was alleged in the Hickory, North Carolina bridge case?
A complaint filed on September 19, 2023 in Wake County Superior Court alleges that Philip Paxson died on September 30, 2022 when he drove off an unmarked, unbarricaded collapsed bridge in Hickory while following GPS directions. It names Google, its parent Alphabet and the owners of the bridge as defendants. These are the plaintiff’s allegations, not findings, and we have not confirmed a ruling or an outcome. For an app maker the useful part is the shape of the claim: a death at a physical place, blamed in part on what a map said.
We route trucks. Is that a bigger exposure than routing cars?
Usually, because the failures are physical and the rules are written down. Federal rules tell a motor carrier hauling placarded hazardous materials to avoid heavily populated areas, places where crowds gather, tunnels, narrow streets and alleys unless there is no practicable alternative, and to follow state routing designations for non-radioactive hazardous materials (49 CFR 397.67). A routing product that sends a loaded truck down a road those rules or a bridge height forbid has made the carrier’s problem its own. A carrier customer will want your contract to say who is responsible for the route.
Is a navigation app a product or a service for insurance purposes?
It depends on the claim, and the answer is contested, so do not build your program on winning that argument. A plaintiff can describe your software as a product, which brings product liability thinking, or as a service, which brings professional liability thinking. Either way your tech E&O needs to answer the contingent injury and property damage claim, and any device you ship needs a product policy of its own.
We sell driver-assist or fleet safety software. Does the NHTSA crash reporting order apply to us?
Probably not directly. NHTSA’s Standing General Order requires the manufacturers and operators it names to report certain crashes involving automated driving or Level 2 driver-assistance systems, and NHTSA says it imposes no reporting duty on any other company or on individual consumers. It still matters to you: a vehicle maker that must report a crash will ask its software suppliers for logs and for contract promises. Your insurance and your data retention should be ready for that request.
Our drivers use their own cars and follow our routing. Who is covered?
Not automatically you. A ride or delivery app often does not own the cars, so the claim reaches it through hired and non-owned auto coverage and through your tech E&O. Add the question of how drivers are classified and whether your app dictates the route, because an app that directs the trip looks more responsible for the result than one that only shows a map.
What will the underwriter ask a navigation or mobility app?
Whether the app suggests a route or decides one and a vehicle follows it without a human, which vehicles and which users (consumers, commercial fleets, trucks, hazmat), how map and traffic data is sourced and refreshed, how a reported closure or hazard reaches the map and how fast, what warnings and disclaimers the driver sees, whether it runs on hardware you sell, which AI model or vendor produces the route, whether you keep logs of what the app said at the time of a crash, how many users and how much revenue, which states and countries, and any contract that makes you indemnify a customer. Prior claims and near misses are asked too. An app that gives a person directions can read to an underwriter more like a professional than like software, so say plainly what yours does.
Our routes come from an AI model. Is AI-generated output covered?
Only if the wording says so. A model that invents a road or misreads a height limit is giving the driver wrong output, and some 2026 forms exclude or limit generative AI claims outright. Ask whether the policy covers claims arising from AI output and whether the contingent injury and property damage grant reaches it. Check too for a generative AI exclusion on the general liability policy your customers see.
Does the generative AI exclusion on general liability change this?
It can. Some general liability forms now carry endorsements that remove claims arising from generative AI, which adds to the professional services exclusions already there. A navigation company relying on a general liability certificate for a crash claim should read the exclusions list before trusting it.
Do we need cyber insurance too?
Probably. A navigation app holds location history, which shows where a person lives, works and travels. A leak, a sale of that data or an unauthorized share is a privacy claim that cyber coverage is built for, and tech E&O is not. Cyber can also pay for the response to an attack on a connected fleet.
Our app was built fast with AI coding tools. Does that matter to an underwriter?
It changes the questions, not the answer. A route feature written quickly and tested thinly is the kind an underwriter wants to hear is reviewed by an engineer, tested against real closures and logged. Say who reviews the code and how a bad route would be caught before a driver sees it.
We are launching in other countries. Does our insurance follow the app?
Not automatically. Many tech E&O policies only promise to defend claims brought in the US or Canada. A crash abroad involving a visiting driver can be brought where the crash happened, and map data in another country raises its own privacy rules. Check where claims may be brought before you launch.
Which NAICS codes does this page cover?
Navigation and mobility software usually files under 513210 Software Publishers, 541511 Custom Computer Programming Services, 541512 Computer Systems Design Services or 518210 Computing Infrastructure Providers, Data Processing, Web Hosting, and Related Services. Businesses around it use 334511 Search, Detection, Navigation, Guidance, Aeronautical, and Nautical System and Instrument Manufacturing for devices, 485310 Taxi and Ridesharing Services, 492110 Couriers and Express Delivery Services, 488490 Other Support Activities for Road Transportation and 541614 Process, Physical Distribution, and Logistics Consulting Services. Tell us the code on your paperwork and what the app does, because the code alone does not say whether anything physical moves.
Where does this sit among insurance for AI apps?
Navigation is one of the industries where an app’s output moves something physical. Others handle money, health, hiring or children, and each has its own exposure and its own gap between policies. The hub lists every industry we have written up.
Also in this family
Guides on navigation or mobility app.
- Bodily Injury vs Contingent Bodily InjuryGeneral liability pays for injuries you cause by accident, and E&O pays for money lost to your mistakes. An injury caused by a mistake in your app, software or advice falls between them, and contingent bodily injury on the E&O is how that gap is closed.
- Insurance for an App Launching WorldwideAn app store launch puts your app in front of users in dozens of countries on the first day. Your tech E&O may only defend claims filed in the US or Canada, and your cyber policy has to handle European privacy rules, where health and fitness readings are a special category of data.
- Vibe-Coded App InsuranceA vibe-coded app carries the same liability as any other, and the documented failures are security ones: open databases, exposed keys and an agent that deleted data. Here is which policy answers which failure, what the AI tool providers say about who is responsible, and what to check before you buy.
Commercial insurance is 96% of what we do — it is not a department here, it is the whole business. Not ready to talk? The guides answer the questions this page raises in more depth. Already insured with us and need a certificate or a policy change? Ask the service team rather than starting a quote — it is faster and it goes to the people whose job it is. We also write home and auto, which is usually cheaper alongside the business policy than apart from it.
Handed a lease, a vendor packet or a client contract with insurance requirements? Paste it into the COI Requirements Decoder to see what each one means for your business, or read what the requirements mean.