> For the complete documentation index, see [llms.txt](https://docs.drivequant.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.drivequant.com/stolen-vehicle-locator/how-it-works.md).

# How it works

The Stolen Vehicle Locator component uses Bluetooth Low Energy beacons embedded in vehicles and your users' smartphones to form a collaborative detection mesh, enabling rapid localisation of any stolen vehicle.

The feature relies on a Bluetooth beacon emitting an iBeacon signal — the same hardware used by the Trip Analysis component for trip detection and vehicle identification. A single beacon serves both purposes.

Here's how it works:

* **Vehicle identification:** An iBeacon beacon is placed in each user's vehicle. It continuously broadcasts a unique identifier (UUID + Major + Minor) detectable by both Android and iOS smartphones.
* **Theft reporting:** You report the theft via the API by providing the iBeacon identifiers associated with the stolen vehicle.
* **Collaborative search:** Every smartphone in your user base that has opted in passively scans for iBeacon signals matching vehicles in the community fleet. Scanning runs in background, is energy-efficient, and requires no action from the user.
* **Detection:** When a smartphone detects a beacon matching a vehicle under search, it automatically transmits to the server: the smartphone's GPS location, the beacon signal strength (RSSI), and a timestamp.
* **Vehicle location alerts:** Each detection event — including position and timestamp — can be shared to your platform via a push service. A separate endpoint allows you to request a refined position calculated by cross-referencing detections from multiple users, with increasing accuracy as more detections are collected.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.drivequant.com/stolen-vehicle-locator/how-it-works.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.