Team, accounts and cloud data

When you use Team, Firebase provides authentication, account management, QR pairing and synchronization. Data can include account email and profile, technical user, driver and device identifiers, pairing records, routes, stop addresses, assignments, notes, timestamps, progress and delivery proof data, including photos and available completion coordinates when submitted in Team. These operational records are shared with the relevant office and authorized paired devices to deliver the service; personal routes are separate from Team workflows.

Staq Office uses Firebase Authentication for the Office account. A paired driver device has a technical identity and association with that Office; pairing does not create a separate Office account. Cloud Firestore stores Team operational records and file references, while Cloud Storage for Firebase holds proof images actually uploaded. A stored file path or metadata is distinct from the image itself. A QR pairing session links an authorised driver phone to a driver and Office; that link can expire, be revoked or disconnected.

Team may share routes, stops, assignments, status, delivery outcomes such as delivered, not delivered, unavailable, refused or retry, notes, times and completion coordinates when recorded. The relevant Office and its authorised paired devices can access these records. Synchronisation can be delayed offline; a local cache may temporarily differ from the server and reconcile when connectivity returns. Personal routes remain separate and primarily on the device.

StaqRoute Android · Team location and proof

StaqRoute Android pairs a driver with Staq Office via QR and syncs assigned Team routes, delivery outcomes, notes and optional proof through Firebase. For the current stop selected for navigation, optional background location can detect arrival while Google Maps or Waze is in front and provide a reminder; it needs suitable destination coordinates, location permission and Google Play services. It does not automatically complete a delivery or upload a continuous GPS trail. Without background location, external navigation and manual outcome entry remain available. Android notifications may show an arrival reminder when enabled; they can be delayed or unavailable. At manual delivery confirmation, foreground location may attach available coordinates to the receipt; the outcome can be saved without coordinates. Photos chosen from the camera or gallery for proof are uploaded to Cloud Storage for Firebase when synchronized and made available to the associated Office. Local pending data may remain while offline; unpairing does not delete already synchronized Office records or proof. The Android arrival and delivery features do not use location for advertising. Google Maps, Waze and Google Play services process information under their own privacy terms.

Team iOS · Location during navigation

With location permission, active Team navigation may continue using location in the background or with the screen locked. Tracking pauses or ends when navigation pauses or ends, on arrival, unpairing or final route closure as applicable. Current location guides navigation; it is distinct from any completion coordinates saved with a delivery outcome. Team does not store a continuous GPS trail for this purpose.

Account, retention and support

Team data is retained to provide the service until deleted through the available controls or following an applicable deletion request, subject to necessary security and legal retention. Removing the app or unpairing a device does not itself erase cloud records. Contact staq.route@gmail.com for account or data requests; for employer-managed operational records, also contact your organization. Support processes your email and information you choose to send. Firebase may process technical connection data and transfer data internationally under its applicable data-processing safeguards. This website uses Firebase Hosting, which processes connection data to serve and protect the site.

In Staq Office for Mac, the account holder can start in-app account deletion. Unpairing a phone, uninstalling the app, or archiving or deleting a route has a different effect from deleting the Office account. Account deletion removes the account and associated Team cloud data through the implemented deletion process. Previously downloaded offline copies, independently saved exports, backups and necessary technical or legal records may remain where applicable; no fixed retention period is promised here.

Provider and contact

The data controller and application provider is the developer identified on the Staq Route App Store product page. For privacy requests or questions, contact staq.route@gmail.com.

Personal use of Staq Route on iOS · Information stored on your device

Addresses, route names, notes, priorities, time windows, favorites, templates, route history, stop outcomes and proof-of-delivery content are stored locally. Staq does not require an account and the developer does not receive this content merely because you use the app.

Personal use of Staq Route on iOS · Location

With permission, Staq uses location to calculate and update directions, show distance and ETA, detect arrival, record completion coordinates and, when requested, add available coordinates and accuracy to a proof photo. Background location is used only while Staq navigation is active and stops when navigation ends.

Personal use of Staq Route on iOS · Camera, photos and text recognition

Camera and selected photo access may be used to recognize addresses or add a proof-of-delivery photo. Address recognition and image preparation are performed on the device. Only capture people, property or documents when you have authority to do so.

Personal use of Staq Route on iOS · Proof photos, watermark and compression

A photo taken for proof of delivery can be resized and compressed, then marked with the capture date and time plus recent GPS coordinates and accuracy when available. If reliable location is unavailable, the image says so. Selected existing photos are not presented as newly captured evidence.

Personal use of Staq Route on iOS · Sharing and external services

Sharing is always initiated by you. The selected photo, message, route or export is passed to the iOS share sheet and then to the app or recipient you choose. Apple Maps, Google Maps, Waze, email, Messages and other selected services process the information under their own privacy terms.

Purchases

Apple / StoreKit: Apple processes payments; Staq uses purchase and entitlement information to enable the subscribed Pro or Team features. Staq does not receive your full payment card details.

Team subscriptions are purchased and managed in Staq Office for Mac through the App Store; there is no Team paywall on iOS. Deleting a Staq Office account does not automatically cancel the Apple subscription. Manage or cancel it separately in your Apple Account.

Personal use of Staq Route on iOS · Retention, backups and deletion

Local data remains until you edit or delete it, delete an associated route or proof photo, restore or replace a backup, or remove the app and its data. A backup you create can contain routes, settings and proof photos and remains wherever you save it until you delete it. You can revoke camera, photo and location permissions in iOS Settings.

Legal bases and your rights

Processing requested by you is necessary to provide the app’s functions; permission-based access relies on your choice, and limited technical processing may be based on legitimate interests in reliability and support. Depending on your location, you may have rights of access, correction, deletion, restriction, objection, portability, withdrawal of consent and complaint to a data-protection authority.

Children and changes

Staq Route is not directed to children. This policy may be updated when features or legal requirements change; the date above identifies the current version.