Privacy Policy for Courier Route Planner

Last Updated: May 12, 2026

Courier Route Planner ("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).

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 request foreground location permission when you use the app. Location is accessed only when the app is active (not in background tracking), to set your starting point, optimize routes, display your position on the map, bias address search results, and preload map tiles.

Permission required: iOS: "Location When In Use"; Android: ACCESS_FINE_LOCATION and ACCESS_COARSE_LOCATION.

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.

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, search queries and address selections. 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.

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 (no email or password), subscription tier, usage limits (stops per route, optimizations per month, address search per month), account creation date. We use Firebase Anonymous Authentication.

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: POD entries follow the same retention as their parent route (30 days free / 60 days premium from last modification). Deleting a route auto-deletes all its POD entries (Firestore subcollection and Storage files via a server-side function).

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 image is sent to our backend Cloud Function for text recognition and address extraction, then discarded after processing (not stored).

On-device pre-check: Before sending to the cloud, we run an on-device text recognition pass (Google ML Kit). If no text is detected, the image is not uploaded. ML Kit runs entirely on your device and does not transmit images.

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 location in the background, sell your data, use data for advertising, or share data with other users.

Third-Party Services

1. Firebase (Google)

Authentication (anonymous), Firestore, Analytics, Crashlytics. Data shared: user ID, device info, route data, usage events, crash reports. Privacy policy.

2. Mapbox

Route optimization and directions API. Data shared: stop coordinates. Privacy policy.

3. HERE

Address search and geocoding. Data shared: search queries, user location (for bias when permitted). Privacy policy.

4. Google Cloud (Route Optimization API)

Route optimization (when Mapbox or HERE limits are reached). Data shared: stop coordinates. Privacy policy.

5. RevenueCat

Subscription and entitlement management. Data shared: anonymous user ID, subscription status, store transaction identifiers. Privacy policy.

6. Mapbox (map tiles)

Map tiles (Mapbox Maps SDK). Data shared: tile coordinates from visible map area. Privacy policy.

7. Google Gemini (Address Scan OCR)

Optical character recognition and address extraction for the "Scan address" feature. Data shared: a single captured image of the address (sent from our backend, discarded after processing). Privacy policy.

8. Google ML Kit (on-device OCR)

On-device text-presence pre-check before any cloud OCR call. Runs locally on your device, no images or text transmitted. Bundled via the standard Android/iOS ML Kit SDK.

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.

Data Retention

Routes: 30 days (free) or 60 days (premium) from last modification, then auto-deleted; you can delete manually from "My Routes". User profile: deleted after 30 days of inactivity. Recent searches: last 5 only. Analytics and crash reports follow Firebase policies. Local cache cleared on uninstall.

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, or contact us to request Firebase data deletion. You can revoke location permission in device settings; the app works with limited features without it. No background location tracking. Notifications can be disabled; we use them only for route navigation reminders.

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.

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

Uninstall the app (removes local data) and email us to request Firebase data deletion (provide device ID or approximate account creation date).

Contact Information

Email: e.tekhov@gmail.com

Developer: Yevhen Tekhov

Legal Compliance

This Privacy Policy complies with Google Play Developer Policy, GDPR (EU), CCPA (California), and other applicable data protection laws.

By using Courier Route Planner, you agree to this Privacy Policy.