Privacy Policy for Route Planner for Couriers
Last Updated: November 17, 2026
Route Planner for Couriers ("we", "our", or "the app/service") is committed to protecting your privacy. This Privacy Policy explains how we collect, use, and share information when you use our mobile application and related website pages (including landing and invite pages).
Who We Are
The controller of your personal data is Yevhen Tekhov, an individual (sole trader) based in the United Kingdom, trading as "Route Planner for Couriers". Address: Abbotsfield, The Den, Wiveliscombe, TA4 2SU, United Kingdom. Email: support@courierrouteplanner.com.
For data that a business adds to Route Planner Teams (for example, its stops, recipients and routes), that business is the controller and we act as its processor (see section 12, Route Planner Teams).
Information We Collect
1. Location Data
What we collect: Your current location (latitude and longitude), addresses you search for or add to routes, and location coordinates for route stops.
How we collect it: We ask for location permission only while you use the app (“When In Use”); we never ask for “Always” or background location access. Location is used while the app is open to set your starting point, optimize routes, display your position on the map, bias address search results, and preload map tiles. There are two exceptions, both limited to a route that you have started: a team route in Route Planner Teams, where the app keeps sending your position to your team (see section 12, Live position on team routes), and a delivery tracking link that you have chosen to send to a recipient with “Share ETA”, where the app sends your position to the page behind that link (see section 12a, Delivery tracking link) — in both cases including when the app is in the background.
Permission required: iOS: "Location When In Use"; Android: ACCESS_FINE_LOCATION and ACCESS_COARSE_LOCATION. During a running team route, the app also receives location updates in the background — on iOS this is shown by the location indicator, on Android by an ongoing notification of a location foreground service.
Saved delivery points: If address memory is turned on for your account, the location of your device at the moment you mark a stop as Done may be saved together with that stop's address (see section 11, Saved Delivery Addresses).
2. Route Information
We collect route names and start times, stop addresses and coordinates, optimization data (distances, travel times, ETAs), route progress, and timestamps. Stored in Firebase Firestore (cloud) and locally for drafts and recent searches.
File import troubleshooting: If the app cannot read a file you import (for example, it cannot find the address column), it may send the file's header row and its first few rows (at most three, each value shortened) to our servers so that we can fix the problem. This data is kept in our server logs for up to 30 days, is not shared with third parties and is not used for analytics.
3. Device Information
Automatically collected: device model and manufacturer, OS version, app version and build number, platform type, device identifier (Android: ANDROID_ID, iOS: IDFV). Purpose: analytics and app performance monitoring.
4. Crash Reports
Via Firebase Crashlytics: crash reports and stack traces, device state at crash time. Purpose: stability. Not collected in debug/development builds.
5. Usage Data
Analytics about features used, screens viewed, app launches and session duration, routes created/completed, stops optimized, and how address search is used (for example, the length of a search query, the position of the chosen result and which map provider answered — not the text you typed or the addresses you chose). We do not send recipients' addresses, names or phone numbers to analytics. Services: Firebase Analytics and, on web pages where configured, Google Analytics 4 (gtag).
6. Website Analytics and Cookies
On our website pages, we may use analytics technologies (such as Google Analytics 4) and event tracking to measure page performance and interactions (for example, download button clicks). These technologies may use cookies or similar browser storage. We use this data for product and website improvement, not for selling personal data.
Our website pages count visits with our own counter that uses no cookies and no browser storage: for each page view or button click we receive only the page address, the page language, the referring website (domain only), campaign tags from the link (utm) and whether the device is a phone or a computer, and we store them only as daily aggregated counters. No IP address, user agent or other identifier is stored with these counts.
7. User Preferences
Stored locally: preferred navigation app, distance unit, onboarding status, app review status, recent address searches (last 5).
8. Account Information
Anonymous user ID, subscription tier, usage limits (stops per route, optimizations per month, address search per month), account creation date. We use Firebase Anonymous Authentication, so you do not need an email address or a password. If you choose to sign in with Google or Apple, we also keep the details described in section 13.
9. Proof of Delivery (POD) Data
What we collect (Premium feature, optional): When you configure POD requirements and mark a stop as Done or Failed, the app may capture one or more of: delivery photos, recipient signature (as a vector path drawn on screen), barcode/QR values, ID-check confirmation flag, and a short text note. POD entries are linked to a stop in your own route.
How we store it: Photos are uploaded to Firebase Storage under a per-user path; metadata (signature strokes, barcode values, text notes, timestamps, ID-check flag) is stored in Firestore under your route's subcollection. Offline captures queue locally until network is available, then sync.
Visibility: POD entries are private to your account. We do not share them with recipients, other users, or third parties. They are not used for advertising or training.
Retention: on the Lite and Pro plans, POD entries follow the same retention as their parent route (60 days from last modification), and deleting a route auto-deletes all its POD entries (Firestore subcollection and Storage files via a server-side function). On the Business plan, POD entries (including photos and signatures) are kept in your Proof archive for 90 days from the moment they were captured, even if the route itself was deleted or expired earlier; after 90 days they are deleted automatically by a server-side job. Using “Delete my data” in Settings deletes all POD entries immediately, on every plan.
10. Address Scan (OCR) Image Data
What we collect: When you use the "Scan address" feature, we capture a single photo of the address label/list. The text recognized on your device or, if that is not available or not enough, the photo itself is sent to our backend Cloud Function for address extraction, then discarded after processing (not stored).
On-device recognition: Where available, text recognition first runs on your device (Google ML Kit on Android, Apple Vision on iOS). It runs entirely on your device and does not transmit images or text.
11. Saved Delivery Addresses (Address Memory)
What we collect: If address memory is turned on for your account, the app saves addresses you have confirmed yourself: when you mark a stop as Done while your device is within about 150 meters of the stop, the stop's address (as shown in the app) is saved together with your device's location at that moment; when you move a stop's pin by hand and save it, the address is saved with the location you chose. For each saved address we also keep how many times it was used and when it was last used. Search results from map providers are not stored as such — only the location you confirmed.
How we use it: To show your own saved addresses first when you type an address, and to recognize them when you scan a label or import a file, so the stop can be added at your saved location without sending the request to map and geocoding providers. Saved addresses are private to your account; they are not shared with other users or third parties and are not used for advertising.
How we store it: In Firebase Firestore under your anonymous user ID, with a copy on your device for fast search. Up to 3,000 most recently used addresses are kept; older ones are removed automatically. Using “Delete my data” in Settings deletes saved addresses on our servers and on your device immediately.
12. Route Planner Teams
Dispatchers (website): When you sign in to the dispatcher website with Google or Apple, we receive your name and email address and use them to identify you, run your team and contact you about it. We also keep your team's name, its members and their roles (owner, dispatcher, driver), invites, and the usage of the team's plan. We may email you occasional news about Route Planner Teams; you can unsubscribe at any time.
Drivers (app): When you join a team, the team's dispatchers see the name you choose and, on team routes, the time and location of your route events — starting a route, marking a stop as delivered or failed, capturing proof of delivery and finishing a route — together with the proof of delivery itself, and your live position while a team route that you have started is running (see below). Your personal routes outside the team are never visible to the team. If you leave or are removed from a team, the team keeps its routes, including routes you have driven. On team routes, these rules replace the statements in this policy that proof of delivery is private to your account.
Live position on team routes: While a team route that you have started is running, the app sends your current position (coordinates, accuracy, direction and speed) to your team about every 30–60 seconds while you are moving, and less often while you are standing still, including when the app is in the background. Only the team's owner and dispatchers can see it, on the map of the dispatcher website. We keep only your latest position, with no history of where you have been. Sharing lasts only until that team route is finished: it stops, and your position is deleted, when you finish the route, leave or are removed from the team, or use “Delete my data”; if none of this happens (for example, your phone is switched off), your position expires 12 hours after its last update and is then deleted automatically. You can revoke the app's location permission in your phone's settings at any time: the app then stops receiving your position, and routes work with limited features. Your position is never shared during personal routes or when no team route is running. The business that runs the team is the controller of this data (see Team data below); please send any questions about this monitoring to that business.
Team data: Stops, addresses, recipient names and phone numbers, notes and routes that a team adds belong to the business that runs the team. That business is the controller of this data, and we process it on its behalf under our Teams Terms of Service. Please send requests about this data to that business first; we will help it respond.
Payments: Teams subscriptions bought on our website are sold by Paddle.com, our Merchant of Record (see Third-Party Services).
12a. Delivery tracking link (Share ETA)
What it is: When you use “Share ETA” for a stop, the message you send to the recipient can include a link to a web page on our site (courierrouteplanner.com/e/…). The page shows the expected arrival time, the recipient's own delivery address on a map, your current position while you are on the way, and whether the stop has been delivered. The link is optional: you can turn it off in Settings (“Tracking link in ETA messages”), and the message is then sent without it.
What the page contains: only the delivery address of that one stop (the address the recipient gave for their delivery), the expected arrival time and delivery window, the stop's status, your latest position (coordinates, direction and accuracy) and the language and clock format of your app. It does not contain the recipient's name or phone number, any other stop, your other routes, or your identity.
Your position: While the route is started and the stop is not yet delivered or failed, the app sends your current position to the page about every 30–60 seconds while you are moving and less often while you are standing still, including when the app is in the background (on iOS this is shown by the location indicator, on Android by the ongoing notification of the route service). Only the latest position is kept, with no history. Your position is removed from the page when the stop is marked Delivered or Failed, when you finish or leave the route, when you turn the tracking link off, or when you revoke the app's location permission.
Who can see it: anyone who has the link. The link is a long random code that cannot be guessed and is not listed anywhere; please send it only to the recipient of that delivery. The page is not indexed by search engines.
Retention: each link expires 24 hours after it was sent and the page then shows that the link is no longer valid; the underlying record is deleted automatically after it expires. We count page views and clicks on the page without cookies and without storing identifiers (see section 6).
13. Sign in with Google or Apple (optional)
What we receive: Signing in is optional; the app works without it. If you choose to sign in with Google or Apple, the provider shares with us an identifier of your Google or Apple account, your email address (if you use Apple's Hide My Email, this is a private relay address created by Apple) and your name, if the provider shares it. Signing in links Google or Apple to your existing account in the app: your user ID, routes, subscription and team membership stay the same. If you later sign in with the same Google or Apple account on another phone where the app already has its own data, that phone's routes, proof of delivery, saved delivery addresses and files are not moved into your account: the app warns you first, and that phone's separate account is then deleted with all its data. Usage already counted on that phone still counts toward your account's monthly limits.
Why we use it: To let you restore your routes, subscription and team membership on another phone or after reinstalling the app, and to answer your support requests. We do not use your email address for advertising.
Retention and your choices: These details are kept while your account exists. You can unlink Google or Apple at any time in Settings. “Delete my data” erases your app data as described in Data Deletion Request and also unlinks Google or Apple from your account.
How We Use Your Information
We use data for: route optimization, navigation display and turn-by-turn via third-party map apps, service improvement, subscription/limit management, and local convenience (recent searches, preferences).
We DO NOT: track your location in the background outside a started route with live position sharing (a team route or a delivery tracking link you sent), sell your data, use data for advertising, or share data with other users.
Exception for teams: if you join or run a team in Route Planner Teams, team routes and their events are shared with the members of that team, and your live position during a team route that you have started is shared with the team's owner and dispatchers, as described in section 12.
Legal Bases (UK GDPR and EU GDPR)
- Contract: to provide the app, routes, optimization, subscriptions and Route Planner Teams that you ask for.
- Legitimate interests: to keep the service secure and stable, prevent abuse of free limits, fix problems, and improve the service using analytics and crash reports. We balance these interests against your rights.
- Consent: for access to your device's location, camera and photos. You can withdraw consent at any time in your device settings.
- Legal obligation: for example, to keep tax and accounting records.
Third-Party Services
1. Firebase (Google)
Authentication (anonymous, or Google or Apple sign-in if you choose it), Firestore, Analytics, Crashlytics. Data shared: user ID, email address and name if you sign in with Google or Apple, device info, route data, usage events, crash reports. Privacy policy.
2. Mapbox
Route optimization, directions, and address search and geocoding. Data shared: stop coordinates, search queries, user location (for bias when permitted). Privacy policy.
3. HERE
Address search and geocoding, route optimization and directions. Data shared: search queries, user location (for bias when permitted), stop coordinates. Privacy policy.
3a. LocationIQ
Address search and geocoding (fallback provider). Data shared: search queries, user location (for bias when permitted). Privacy policy.
3b. Photon (Komoot)
Address search and geocoding (fallback provider). Data shared: search queries, user location (for bias when permitted). Service info.
4. Google Cloud (Route Optimization, Routes, Geocoding and Places APIs)
Route optimization and directions, address search and geocoding. Data shared: stop coordinates, search queries, user location (for bias when permitted). Privacy policy.
5. RevenueCat
Subscription and entitlement management. Data shared: anonymous user ID, subscription status, store transaction identifiers. When you ask Apple or Google for a refund, RevenueCat may send the store, on our behalf, information about your purchases and use of the subscription (for example, account age, purchase and refund history and whether the subscription was used) to help the store decide on the refund (Terms, section 9). Privacy policy.
6. Google Maps SDK (map display)
In-app map rendering (Google Maps SDK for iOS/Android). Data shared: map tile requests for the visible map area (coordinates, zoom) and standard Google Maps SDK telemetry. Privacy policy.
7. Google Gemini (Address Scan and Import)
Address scan: When you scan an address label or list, the photo or the text recognized on your device is sent from our backend to Google Gemini (Google AI) to extract the delivery address. Images and text are processed only to return the address, are not used by us for any other purpose, and are discarded after processing.
File and list import: Address lines from files or lists you import that could not be matched to an address right away may be sent from our backend to Google Gemini to separate the address (street, house number, postcode, town) from other text such as names or notes. Only the address lines are sent (phone numbers and email addresses are removed first), together with the country, your working area (town and region names of the address in the same file closest to your device's location; no coordinates) and the town names of other addresses in the same file. To find the town of a line that names none, the other address lines of the same file or list may be sent together with it. Privacy policy.
8. Google ML Kit and Apple Vision (on-device OCR)
On-device text recognition for address scanning: Google ML Kit on Android, Apple Vision on iOS. Runs locally on your device; ML Kit and Vision do not transmit images or text. The recognized text may then be sent to our backend for address extraction (see Google Gemini above).
9. Paddle (Route Planner Teams payments)
Paddle.com is the Merchant of Record for Route Planner Teams subscriptions bought on our website. Paddle collects billing details (such as name, email address, billing address and payment method) as an independent controller to process payments, taxes and invoices. We receive the buyer's email address, subscription status and transaction details, but never full card numbers. Privacy policy.
10. Sign in with Google and Sign in with Apple (dispatcher website and app)
Dispatchers sign in to the Route Planner Teams website with a Google or Apple account, and app users can choose to sign in with one (see section 13), through Firebase Authentication. Google or Apple shares with us an account identifier, your email address (with Apple, possibly a private relay address) and, if available, your name. Google privacy policy, Apple privacy policy.
International Data Transfers
We are based in the United Kingdom. The service providers listed above may process data in the United States and other countries. Where UK or EU law requires it, these transfers are protected by adequacy decisions (including the UK–US data bridge and the EU–US Data Privacy Framework for certified providers) or by standard contractual clauses (the UK International Data Transfer Agreement or Addendum, or the EU Standard Contractual Clauses).
Data Storage and Security
Cloud (Firebase): encrypted in transit and at rest; users can only access their own data. Local: auth ID in SecureStore (encrypted); drafts and preferences in AsyncStorage (cleared on uninstall). We use HTTPS and Firebase Security Rules.
Team data in Route Planner Teams is isolated per team: only members of the team can access it, according to their role.
Data Retention
Saved delivery addresses: kept while the account exists, limited to the 3,000 most recently used; erased when you use “Delete my data”.
Routes: 30 days (free) or 60 days (premium) from last modification, then auto-deleted; you can delete manually from "My Routes". Account record: kept while the account exists. It holds your anonymous user ID, plan and subscription status, usage counters for monthly limits, and a device link used to prevent abuse of free limits; it does not contain your phone number or a password, and it contains your email address only if you sign in with Google or Apple (see section 13). The personal settings stored with it (display name, country, preferred navigation app) are erased when you use “Delete my data”. Recent searches: last 5 only. Analytics and crash reports follow Firebase policies. Local cache cleared on uninstall.
Live position on team routes: only the latest position is kept, with no history; it is deleted when the route is finished, when you leave or are removed from the team, or when you use “Delete my data”, and otherwise expires 12 hours after its last update.
Route Planner Teams: team routes are deleted automatically 60 days after their last change. When a team is deleted, or 45 days after its subscription ends unpaid, all its data, including proof of delivery, is deleted within 30 days. A dispatcher's name and email address are kept while they are a member of a team and deleted on request after they leave. Paddle keeps billing records as required by tax law.
Your Rights and Choices
You can: delete routes from "My Routes", rely on limited recent searches (5), change preferences in Settings, uninstall to remove local data, use “Delete my data” in Settings to erase your data from our servers at any time (see Data Deletion Request), or contact us. You can revoke location permission in device settings; the app works with limited features without it. No background location tracking, except your live position while a team route that you have started is running, which stops when that route is finished (see section 12); for questions about this monitoring, contact the business that runs the team. Notifications can be disabled; we use them only for route navigation reminders.
Your rights under UK GDPR and EU GDPR: you have the right to access, correct or delete your personal data, to restrict or object to its processing, to data portability, and to withdraw consent at any time. To exercise these rights, email us; we respond within one month. You also have the right to complain to the UK Information Commissioner's Office (ico.org.uk) or to the data protection authority where you live or work.
California and other US states: we do not sell or share personal information for cross-context behavioral advertising. You can ask to access or delete your personal information by emailing us, and we will not discriminate against you for exercising your rights.
Team data: for data a team has added, contact the business that runs the team; we will help it respond.
Children's Privacy
This app is not directed to children under 13. We do not knowingly collect personal information from children under 13. If you believe a child has provided us with information, please contact us.
In the United Kingdom, the European Union and the European Economic Area, the app is intended for users aged 16 and over.
Changes to This Policy
We may update this policy from time to time by updating the "Last Updated" date and, for significant changes, an in-app notice where applicable. Continued use after changes indicates acceptance.
Data Deletion Request
In the app: Settings → “Delete my data”. This immediately and permanently deletes from our servers all your routes and your route list, all proof-of-delivery records (photos, signatures, barcodes, ID-check flags, notes) and the personal settings in your account record. To keep monthly limits fair, the account record itself (anonymous user ID, plan and subscription status, usage counters, device link) is kept.
Team members: if you are a member of a team in Route Planner Teams, “Delete my data” also removes you from the team. Team routes and their proof of delivery stay with the business that runs the team, which is the controller of that data (see section 12); your name stays on the routes you drove, the locations of your route events on them are erased, and your live position is deleted.
Sign in with Google or Apple: if you signed in, “Delete my data” also unlinks Google or Apple from your account and removes your email address from it.
Account record: to request deletion of the remaining account record, email us at the address below and include your device ID or approximate account creation date. Uninstalling the app removes data stored on your device.
Contact Information
Email: support@courierrouteplanner.com
Developer: Yevhen Tekhov
Address: Abbotsfield, The Den, Wiveliscombe, TA4 2SU, United Kingdom
Legal Compliance
This Privacy Policy complies with Google Play Developer Policy, Apple App Store Review Guidelines, GDPR (EU), CCPA (California), and other applicable data protection laws.
Summary
What we collect: Location (while you use the app; during a team route you have started, also in the background), routes and addresses, device info, app and website usage analytics, crash reports, preferences, optional POD captures (Premium: photos, signatures, barcodes, notes), scan images or label text recognized on your device, sent to our backend for address extraction (not stored), and, if you choose to sign in with Google or Apple, your email address and name.
Why: Optimize routes, display maps, improve performance, track usage limits, provide proof of delivery, and recognize addresses from photos.
Who we share with: Firebase/Google (auth, Firestore, Storage, Analytics, Crashlytics), Mapbox (route optimization and address search), HERE / LocationIQ / Photon (address search), Google Maps SDK (map display), Google Cloud (route optimization and Places search when applicable), Google Gemini (address scan and cleanup of imported address lines), RevenueCat (subscriptions). ML Kit OCR runs on device only.
Teams: If you use Route Planner Teams, the dispatchers of your team see team routes and their events, and your live position while a team route that you have started is running; Teams payments are processed by Paddle (Merchant of Record).
We do NOT: Track location in background outside a running team route, sell data, share POD with anyone, share data with advertisers, or require email/name/phone (signing in with Google or Apple is optional).
By using Route Planner for Couriers, you agree to this Privacy Policy.