Customer GPS for support: legal, useful, without permanent tracking
Updated: 2026-05-22
Locating a customer during a breakdown is lawful when you obtain explicit consent, capture a single point at session connection, and perform no continuous tracking. Assistance Leagora applies this model: one GPS position when the customer joins, shown on the agent map, with no hardware tracker on the asset and no movement history. Customers can decline GPS while keeping remote video support.
"Are we allowed to locate the customer?" — the question stalls GPS map projects at rental operators, fleet managers, and field service teams. Legal teams fear permanent tracking; operations need accurate dispatch. Both concerns are valid — and the answer hinges on one distinction: a proportionate snapshot when help is requested, not continuous surveillance.
Why Legal worries — and why location still matters
GDPR does not ban geolocation for support. It requires proportionality, clear purpose, and data-subject rights. What triggers audits is the embedded tracker model: pings every few seconds, trip history, geofencing without a customer action — hard to justify for a simple repair dispatch.
For rentals or field breakdowns, one position at call time is often enough: where is the customer who scanned the QR code on the bike, van, or internet box? That is a legitimate operational need — provided you do not slide into fleet surveillance.
Explicit consent — separate from video, declinable
Camera and GPS are separate browser permissions. Assistance Leagora shows a dedicated consent screen before any coordinates are read: no pre-ticked boxes, purpose explained ("to send help or a technician").
If the customer declines GPS, the remote video support session still works — only the map pin stays empty. Declining location does not block troubleshooting; it limits automatic dispatch. For the broader video and data framework, see our GDPR guide for end customers.
One capture at connection — not a tracker
Assistance Leagora records one GPS point at the instant the customer joins the session. No periodic updates, no movement history, no background tracking after the session ends.
No GPS hardware is installed on rented equipment. Location comes from the smartphone the customer already uses to scan the QR code or open the link — with explicit consent at that moment.
Real scenarios: rentals, fleets, multiservice field teams
An e-bike rental operator can locate a downtown breakdown to route a technician — without a tracker on every frame or per-unit IoT subscriptions. A camper van hire validates a return: the customer opens support, accepts GPS, the agent confirms condition and area on video.
A multiservice contractor sends a technician after video qualification: location confirms the exact address (underground parking, industrial zone) the customer struggles to describe by phone. In each case, purpose ties to a help request the customer initiated — not permanent fleet monitoring.
- Short-term rental: bikes, scooters, vans, camper vans
- Field service with tight routes and vague addresses
- Equipment fleets without embedded trackers (boxes, chargers, mobile assets)
Records of processing, end-user terms, and processor role
Document in your register: purpose (support / field dispatch), lawful basis (consent or contract performance depending on your setup), retention (linked to the support ticket), and processor Assistance Leagora (France/EU hosting).
Inform end customers via your terms and privacy notice. Assistance Leagora provides end-user term templates; your legal pages complete the picture. Platform cookies are strictly necessary — no third-party advertising tracking.
How Assistance Leagora helps
Assistance Leagora bakes GDPR GPS principles into the product — available from the Business plan.
- Explicit consent screen before any GPS capture
- Single position at connection — no continuous tracking
- Interactive agent map with SMS, email, or WhatsApp sharing
- EU hosting, no default video recording
- Combinable with equipment QR code to identify the asset in breakdown
Expected results
- Cost : Avoid fines, blocked audits, and per-unit embedded tracker costs — compliance built in from day one.
- Field trips : Reliable position at breakdown time: technician arrives first time without endless "where exactly are you?" calls.
- Customer satisfaction : Customers informed and in control of consent — transparency that builds trust, especially in B2C rental.
Frequently asked questions
Can the customer refuse GPS and still get support?
Yes. Declining only blocks location capture; remote video support remains available to attempt a fix without a site visit.
Do you keep a history of positions?
No. It is a single capture at connection, not tracking over time. Coordinates are tied to the support session context.
Do we need a GPS tracker on rented equipment?
No. Location comes from the customer's smartphone, with explicit consent, when they request help via link or QR code.
What lawful basis for a rental operator locating a breakdown?
Depending on your legal setup: explicit consent at capture time, and/or contract performance (repairing rented equipment). Your DPO decides based on your notice and terms; Assistance Leagora provides the technical consent UI.
Which plan includes GPS?
Customer geolocation is included from the Business plan at €40 excl. VAT/month. The free trial lets you test video and QR codes without a credit card.
How does this relate to the operational GPS guide?
This guide covers the legal framework. For agent workflows (map, dispatch, technician sharing), see "Where is my customer stuck?" on smartphone GPS.
Locate customers during breakdowns with full compliance — explicit consent, one capture, no tracking. Try Assistance Leagora free: one group + three devices, no credit card.
Start free trial30-second signup — 1 group and 3 devices included, no credit card required.