Privacy
PackSort Privacy Policy
Kunwarbir Singh Padda provides PackSort to help authorized warehouse sorting teams route packages using configurations supplied by their organization.
Data handled by PackSort
PackSort may process postal-code characters, street names, civic numbers, selected routes, speech-recognition results, corrections, scan history, and diagnostic flags. This operational information is used to route packages and help supervisors investigate routing results.
Most of it stays on the device. The exception is wrong-driver reports, which contain a delivery address and are uploaded to the employee’s own depot — see “Depot configuration and wrong-driver reports” below. Scan history stays on the device and is not uploaded.
Authorized users sign in with an administrator-created email and password. PackSort uses Google Firebase Authentication to process the account email, password, authentication identifier, user-agent information, and IP address for sign-in, account security, and access management. Public registration is not available.
Firebase Remote Config and Firebase Installations process an installation identifier and basic app/device context—including country and language codes, time zone, operating-system and app versions—to provide the global access status and minimum supported version. PackSort does not use Firebase Analytics, Crashlytics, advertising, or third-party marketing SDKs.
Depot configuration and wrong-driver reports
An employee’s account belongs to one depot and holds one role, manager or worker. PackSort stores that assignment on the sign-in token and, for administration, in Cloud Firestore. The administrative record holds the account email, the depot and the role, and nothing else. It is written only by the developer’s provisioning tool and never by the app, and it is readable by that account and by managers of the same depot.
Each depot has one published routing configuration. PackSort stores it in Cloud Firestore and Cloud Storage, and every phone in that depot downloads a copy. It contains routes, driver names, bays, street rules and postal-code mappings supplied by the organization. It does not contain package recipients.
When PackSort routes a package to the wrong driver, a worker can report it. A report contains the postal code, the street name and civic number the worker entered, the driver PackSort chose, the driver the worker chose, the configuration revision in use, the reporting account, and the time. A report therefore contains a delivery address. It does not contain a recipient name, a tracking number, or any image.
Reports exist so a manager can decide whether the depot’s routing needs changing. They are readable only by managers of the same depot, are written only by the depot’s own devices, and are not sent anywhere else. A manager reviewing a report sees the email of the account that filed it, because the same address reported five times by one person means something different from the same address reported by five people, and a decision to change a depot’s routing turns on that difference.
A report a manager has resolved is deleted after 90 days; the published revision that resolved it already records the outcome, so the address itself is not the part worth keeping. A worker’s device holds an unsent report until it can be uploaded, and discards it once it has been.
Civic address data
An employee may choose to download the Capital Regional District’s public civic-address dataset directly to their device. The CRD receives ordinary request information such as the device’s IP address and the PackSort user agent. The downloaded addresses are stored only in PackSort’s local app storage, are removable in the app, and are not hosted, proxied, exported or redistributed by PackSort.
Camera, microphone, and maps
The camera is used only when a user opens barcode scanning. Barcode images are processed on the device and are not retained or uploaded by PackSort.
The microphone is used only when a user activates voice input. Speech recognition is restricted to on-device engines, and PackSort does not retain or upload audio recordings.
The Android supervisor configuration map may request public map tiles over the internet. The map provider receives ordinary network request information such as the requesting IP address. The package-sorting workflow and bundled address database operate locally after access is validated.
Sharing and sale
PackSort does not sell personal information. Data processed by Firebase is handled by Google as a service provider to operate authentication and access controls. PackSort does not share user data for advertising or marketing.
Retention and deletion
Local scan history can be cleared in the app, and local app data can be removed by uninstalling PackSort or through device-management controls. Resolved wrong-driver reports are deleted after 90 days. Authentication records remain until the PackSort administrator deletes the Firebase user. Firebase installation records follow Google's published retention practices.
To request deletion of an account or associated authentication information, email kunwarpadda46@gmail.com. Include the email address used to sign in so the administrator can identify the correct account.
Security
Network data is encrypted in transit. PackSort uses reasonable safeguards appropriate for an internal operational application. Users should not include real customer package data in public screenshots or support messages.
Contact
Privacy and support enquiries can be sent to kunwarpadda46@gmail.com or support@packsort.ca.