How driving-based (usage-based) car insurance works

Two kinds: how much you drive, and how you drive

The US National Association of Insurance Commissioners (NAIC) describes two main forms. Pay-as-you-drive links the policy mainly to distance driven. Pay-how-you-drive also looks at driving behaviour. Some products combine both.

The idea behind both is the same: an insurer usually prices on proxies such as age, vehicle and address. Driving data adds a direct observation of the risk the policy actually covers.

What gets measured

According to the NAIC, telematics programmes can record miles driven, time of day, location, rapid acceleration, hard braking, hard cornering and airbag deployment. Each insurer chooses its own subset and how to weigh it.

Connected cars make a separate device unnecessary: the car already measures speed, acceleration and braking. In some US states, Tesla's own insurance sets a monthly premium using factors such as forward collision warnings, hard braking, aggressive turning, unsafe following distance and forced Autopilot disengagements, according to Tesla's support pages.

The Driving Index we are building in pilot follows the same logic and always shows its factors: hard braking, aggressive turning, speeding, late-night driving, excessive acceleration and trip context (length, city versus highway). The index describes driving; it does not set a price.

How data reaches an insurer

In a good design the driver decides. The data should flow only after explicit consent, for a stated purpose, and the driver should be able to see what is shared and withdraw consent. In Turkey, personal data processing falls under the Personal Data Protection Law (KVKK, Law No. 6698); in the EU, under the GDPR.

Less is often enough. An insurer pricing on behaviour needs aggregated factors per period, not a map of every trip. Ask any provider whether raw location leaves your account.

What stays the insurer's decision

A driving score is an input, not an offer. The insurer decides whether it uses the data at all, how it combines it with everything else it knows, and how that turns into a premium, a renewal decision or nothing. Regulators oversee that process: in Turkey, the Insurance and Private Pension Regulation and Supervision Agency (SEDDK).

Be wary of any site that promises a specific discount for a score before an insurer has priced your policy. In Turkey, trafik sigortası (compulsory motor liability) is mandatory and kasko (own-damage cover) is voluntary; driving-based pricing concerns the voluntary part.

Questions to ask before you share driving data

Before you join any usage-based programme, get clear answers to these:

• Which signals are collected, and is location among them?
• Who can see the raw data, and for how long is it kept?
• Can the data only lower the price, or can it also raise it?
• Can I see my own factors, and dispute an event I think is wrong?
• How do I withdraw consent, and what happens to data already shared?

Frequently asked questions

Does a good driving score guarantee a cheaper kasko?

No. The score is one input. Whether and how it affects the premium is the insurer's decision, together with everything else in the policy.

Do I need a device in the car?

Not with a connected car. Many modern EVs, Teslas included, already record speed, acceleration and braking, so the data can come from the car's own systems with your consent.

Is my location shared with the insurer?

It depends on the programme. The NAIC lists location among signals some programmes collect. Pricing on behaviour does not require raw trip maps; ask the provider what exactly is shared.

Can I stop sharing data later?

Under KVKK in Turkey and the GDPR in the EU, consent-based processing can be withdrawn. The policy terms decide what that means for your current contract.