Checking location-tracking policies
Delpack Logistics
October 26, 2026
10 min read
Determine which device supplies location data, whether collection continues after work, who can view history and how long records stay.
A delivery driver installs a route app on a personal phone. It requests location access “all the time,” even though the driver expects to use it only during assigned shifts. After clocking out, the app still appears in the phone's location-permission list. That setting does not prove the employer viewed an off-duty trip, but it raises a question the worker deserves to have answered. Checking location-tracking policies means finding out which device supplies location, when collection begins and ends, who can see the data, and how long it is kept.
Google's Android help distinguishes location access allowed all the time from access allowed only while an app is in use. The Federal Trade Commission recommends limiting app data access to what is needed and having a written retention policy for information kept by a business. Those sources establish useful questions, not Delpack's technology or privacy practice. A candidate should read the employer's current policy and ask for a demonstration of the route app's actual permissions and end-of-shift behavior.
Identify the location-data source
The location-data source may be a company-owned van, an employer-issued scanner, or a personal phone app. Ask which one the job uses and whether more than one system records movement. A vehicle tracker can continue operating after a driver leaves the van; a phone app may follow the device the worker carries home. The privacy question changes with the source, so “we track routes” is too broad an answer.
Ask what the system records. Does it keep a continuous path, periodic points, a location at each delivery scan, a last-known vehicle position, or only route events tied to an address? The answer affects how much can be inferred about a driver's movement. Do not assume that a map on a dispatcher screen represents the whole stored record, or that a scan location is the same as a live GPS feed.
Find out who owns and administers the device. A company phone may have managed settings that a worker cannot change; a personal phone may require the worker to grant specific app permissions. Ask whether an alternative device is available if the employee does not want a route app on a personal phone. This is separate from the cost and connectivity burden of using the device; here the focus is the location data it exposes.
Ask whether the app uses precise or approximate location and when precision is needed. Android's permission guidance explains that apps can request approximate or precise access and that users can inspect the permission setting. The employer should explain which level the work requires and which feature depends on it. A driver should not disable a required function mid-route without guidance, but the request should be understandable before the permission is granted.
Checking location-tracking policies begins by mapping the device to the data. “The van is tracked” and “the driver's personal phone is tracked” are different statements. If both are true, ask which record the employer uses for dispatch, safety, payroll, or investigation and whether the two streams are linked. Clear terms make it possible to judge the scope of tracking rather than react to a vague technology label.
Pin down the collection period
The collection period should have a start and an end. Ask whether location begins when the app opens, when the worker signs in, when a route is assigned, or when the shift starts. Then ask what stops collection: closing the route, signing out, clocking out, or turning off a permission. Those events may occur at different times. A worker needs the employer's actual rule, especially when a route app remains installed between shifts.
Android offers “allow all the time” and “allow only while using the app” permission choices. All-the-time access permits an app to use the phone's location even when it is not open; it does not by itself prove that the app continuously sends or stores positions. Conversely, an app's promise to stop tracking at sign-out is a policy and technical behavior that should be verified, not assumed from a phone icon. Ask how the employer tests that boundary.
Check breaks and personal trips. If the driver stops for an approved meal, does the system continue recording van location? If the worker uses a personal phone after clocking out, does the app retain permission but suspend collection? Ask whether those cases are described in the written policy. A route may involve both vehicle movement and personal time; the worker should know which period is treated as work tracking.
Find out what happens during a late return. The route may close in one system while the driver is still returning the vehicle, fueling, or completing a handoff. Ask whether location remains active through those assigned tasks and when it ends. A useful boundary follows the actual work process and is explained in terms the driver can observe, rather than relying on a hidden backend status.
Ask how to check the setting after a shift. A personal-phone user can inspect app permissions and the phone's location indicators, but those screens only show device-level access. The employer should also explain whether its service stores the last point, keeps a route history, or stops receiving data at sign-out. A screen that says “route complete” is not enough to answer all of those questions.
Ask about location-history access
The scope of location-history access can be broader than live dispatch. Ask which roles can view a driver or van's past positions, whether a manager needs a reason to open a record, and whether access is logged. A dispatcher may need a current van position to coordinate deliveries; a different team may review historical data after a complaint or crash. The policy should distinguish those uses and identify the person who approves access.
The FTC's business privacy guidance recommends limiting access to people who need the information for their jobs. That principle suggests useful questions: Can every supervisor see every driver's history? Can a customer or contractor see it? Does a third-party app provider process the data? The candidate should ask for the actual recipients and purposes rather than infer them from a generic statement that the data is “secure.”
Ask whether location is shared outside the employer. Route software, vehicle telematics, mapping services, insurers, and customers may have different roles, but their presence should not be guessed. A policy can identify categories of recipients and the conditions under which data is shared. If the employer uses a vendor, ask where to find that vendor's privacy terms and which terms apply to the driver as opposed to the employer's account.
Find out whether workers can inspect or correct records associated with them. GPS points can be missing or inaccurate because a phone loses signal, a van is reassigned, or a device is left behind. Ask how the employer handles a disputed location and whether the driver can add a factual explanation. A map point alone may not show who was holding the phone, who was driving, or what happened at the stop.
Checking location-tracking policies includes purpose limits. If location is collected to route vehicles, ask whether it is also used to evaluate break timing, attendance, customer complaints, or safety events. The worker should understand those uses before accepting an app permission or vehicle assignment. A broad statement such as “operational purposes” may be too vague to predict how a record will affect a real workplace decision.
Read the retention and deletion terms
The retention and deletion terms determine what happens after a shift ends. Ask how long live and historical location points remain available, whether the employer keeps aggregated route reports longer, and what happens when a driver leaves the job. A location map disappearing from the dispatch screen does not prove the underlying record has been deleted. The policy should distinguish display from storage.
The FTC advises businesses to keep sensitive information only as long as there is a business or legal reason and to write down what is retained, how it is secured, for how long, and how it is disposed of. That guidance does not set one universal retention period for a delivery fleet. It supports asking the employer for its schedule and the reason behind it. A candidate should avoid accepting “we delete it eventually” as a complete answer.
Ask whether records are copied into another system. A route platform may export location to a safety case, payroll review, customer dispute, or backup. A short retention period in the app may not cover those copies. The policy should explain when an incident hold extends retention and who decides that a record can be released. The worker does not need the server architecture, but should understand the practical fate of their data.
Check what the employee can do at separation. Does deleting the app from a personal phone stop future collection? Does the company deactivate the account and remove a managed profile? Are prior route records kept under the stated schedule? Ask for the offboarding steps in writing. Removing a phone permission does not automatically erase data already stored by the employer or its vendor.
Security deserves a concrete question. Who can export location histories, and how are exports protected? A policy may describe access controls, audit logs, or limits on downloads. The FTC's need-to-know and retention guidance makes those questions relevant. The article does not claim a particular employer has weak security; it helps the candidate ask whether stored movements receive appropriate care.
Work through the personal-phone example
Consider an illustrative driver who uses a personal phone for deliveries. The route app asks for all-the-time location access during setup. The driver signs in at 08:00, completes deliveries, and clocks out at 17:30. At 20:00, the phone's settings still list the app as allowed to use location all the time. The example does not show that Delpack uses such an app or that any off-duty location was stored.
The driver asks the employer what the permission enables, when the app sends positions to the fleet system, and whether sign-out stops that transmission. The employer shows the written policy and the app's route-end process. If all-the-time permission is technically necessary for an assigned feature, the employer explains why and how off-shift collection is limited. If it is not necessary, the worker asks whether a while-in-use setting or company device is approved.
Suppose the driver later sees a location event on the employer's account after clock-out. The next step is to ask what the event represents: a cached last position, a vehicle tracker, an app background update, or another source. The record needs a timestamp, device identity, and system explanation before anyone concludes that the employer followed the worker home. If collection exceeded the stated policy, the employer should investigate and correct the practice.
Change the example: the phone permission shows “while using,” but the van has its own tracker. Ending the app session may stop phone location while vehicle location continues until the van is parked or another driver takes it. The two records have different privacy implications. A candidate should ask about both rather than treating a phone setting as the complete location policy.
This case concerns location data. It does not decide whether the employer supplies a scanner, pays for data service, or supports an app outage; those are route-technology requirements. It also does not answer whether an inward-facing camera records the cab. A written policy should address each stream separately so the worker can understand the scope of each system.
Request the policy before installing the app
A candidate can ask: Is location gathered from the van, a company device, a personal phone, or several sources? What does each system record? When does collection start and stop? Who can view live and historical positions? Is data shared with vendors or customers? How long is it kept, and what happens after employment ends? Can the worker review a disputed record? Ask for the written policy and the current app-permission instructions.
Compare the policy with a demonstration of a normal shift end. The person explaining it should be able to show sign-out, the expected device permission, and the contact for a location-data concern. Checking location-tracking policies is complete when the worker understands the difference between a device's ability to access location and the employer's actual collection, use, and retention. The driver guide hub has related work guidance, and local openings are on the Fort Wayne driver careers page .
Continue with Delpack
Review the Fort Wayne career overview or contact Delpack with a question about the company.
Topics
Browse Topics
All Guides
346
Job Search, Applications & Offers
79
Role Types & Job Fit
83
Schedules, Policies & Work-Life
40
Route Operations & Performance
91
Logistics & Warehouse Operations
53
Delpack Logistics Delpack Logistics is an Amazon Delivery Service Partner and last-mile logistics company serving the Fort Wayne market. Explore Welcome Meet Delpack Fort Wayne Delivery Driver Careers Driver Resources Contact Delpack Delpack News Legal Terms of Service Privacy Policy SMS status Contact info@delpacklogistics.com 260-306-5806 View market and mailing address © 2026 Delpack Logistics . All rights reserved.