Policy

PRIVACY POLICY – PARCEL ROUTES
Effective Date: May 15, 2026
Developer: Jorge Oviedo
Application: Parcel Routes (Mobile Application)

This Privacy Policy (“Policy”) governs the data collection, processing, and privacy practices of Parcel Routes (“the Application”), a mobile software application designed and developed by Jorge Oviedo (“the Developer”) to assist delivery professionals in route optimization and distribution logistics. By downloading, installing, or utilizing the Application, you explicitly consent to the data practices described in this Policy.

1. INTRODUCTION & CORE PRINCIPLE
The Developer is highly committed to maintaining the privacy and security of your personal and professional data. The Application is architecture-optimized to run primarily as a client-side utility. This means that the vast majority of data operations, processing, and storage occur locally on your mobile device. We do not operate server-side databases to harvest, aggregate, or sell user distribution telemetry, addresses, or captured images.

2. INFORMATION WE COLLECT AND PROCESS
To deliver core logistic functionalities—such as barcode/QR scanning, geographic route sorting, navigation integration, and delivery validation—the Application requires and processes specific data inputs:

A. Precise Location Data
The Application requires real-time, high-accuracy geographic coordinates (GPS latitude and longitude) to determine your starting position and compute optimal path-routing matrix vectors.
– How it is used: Location data is handled via the Android FusedLocationProviderClient to center the interactive map, show the localized vehicle marker, and sequence your addresses effectively.
– Storage: This spatial telemetry is transiently processed on-device and is not transmitted to external developer servers.

B. Delivery Addresses and Delivery Stop Inputs
Users input text addresses via direct manual keyboard entry or utilizing the device camera through the ScannerActivity to parse barcode or QR code logistics labels.
– How it is used: Addresses are processed into geographic coordinates using local mapping intents and standard Android Geocoding system services.
– Storage: Up to 25 stops are stored temporarily within the mobile client’s execution runtime memory to perform routing sequencing and order-rendering updates.

C. Camera and Media Storage Access
The Application triggers a custom validation dialog allowing delivery drivers to capture a photographic image at the delivery drop point as absolute physical proof of delivery.
– How it is used: The camera framework takes high-resolution images. The Application locally overlays text data watermarks (address details, timestamp) onto the graphic canvas via localized bitmap drawing routines.
– Storage: The finalized watermarked image file is inserted straight into your native device physical storage under the Pictures/ParcelRoutes MediaStore public directory path. The Developer cannot view, access, or intercept these images.

3. PERMISSIONS REQUESTED FROM YOUR ANDROID DEVICE
To run the features listed above, the Application dynamically requests the following system-level hardware and software permissions:
– Manifest.permission.ACCESS_FINE_LOCATION & ACCESS_COARSE_LOCATION: Grants access to precise satellite and cellular positioning to configure mapping features.
– MediaStore.ACTION_IMAGE_CAPTURE (Camera Access): Grants the software interface the right to engage hardware camera shutters during delivery confirmations.
– Storage Write/Insert Privileges: Required to securely store high-resolution delivery evidence directly into your device’s persistent gallery storage.

4. THIRD-PARTY SERVICES AND DATA TRANSFER
The Application integrates industry-standard third-party Android components to execute enterprise-grade map displays, structural text lookups, and step-by-step navigation. These third parties handle data under their own respective policies:

A. Google Maps SDK & Geocoder API
The Application embeds Google Maps software blocks to visualize your courier distribution markers and convert raw textual addresses into structured coordinates. Google may gather hardware identity metrics, network status, and operational location data in accordance with the Google Privacy Policy.

B. Google Maps Navigation Intent
When clicking navigation actions, the Application forwards geographic destination inputs directly to the official Google Maps application installed on the user device via a secured system Intent string (google.navigation:q=). This navigation occurs external to the Application framework.

*Data Selling Prohibition Notice:* The Developer does not engage in broker trading, behavioral tracking, commercial sale, or monetization of location history, address datasets, or delivery metrics compiled during your professional shifts.

5. DATA RETENTION AND DELETION
Because your logistics files and route lists are managed strictly inside local device environments, you retain full ownership and control over data deletion cycles:
– Route Deletion: Clearing your routing lists or finalizing an integrated delivery cycle purges active geographic addresses from volatile memory.
– Evidence Photos: Delivery confirmation images reside inside your device’s Pictures/ParcelRoutes directory. You may delete them manually at any moment using native system file managers.
– Full App Reset: Uninstalling the Application or wiping its application storage data via Android System Settings instantly and permanently eliminates all local application settings, cached locations, and navigation records.

6. CHILDREN’S PRIVACY
The Application is strictly intended for professional distribution personnel, delivery drivers, and adult commercial couriers. It is not designed for or targeted toward children under the age of 13. We do not knowingly collect, analyze, or accept information from children.

7. CHANGES TO THIS PRIVACY POLICY
The Developer may update this operational Policy from time to time to align with legal mandates, framework version changes, or feature updates. Any modification will be made visible by updating the “Effective Date” at the top of this document. We advise you to review this Policy periodically.

8. CONTACT INFORMATION
For any inquiries, clarifications, or technical concerns regarding this Privacy Policy or your data practices within the Application, you may directly contact the Developer:

Developer: Jorge Oviedo
Support Email: manichov@gmail.com