Skip to content
Staq
HomeiPhoneMacAndroidPrivacy PolicyTerms of Use
◎EN
EnglishEnglish (UK)ItalianoFrançaisDeutschEspañolTürkçeNederlandsPortuguês (Brasil)Polski

Staq · iOS + Android + macOS

Privacy Policy

Privacy information for Staq Route Personal and Team on Android and iOS, and Staq Office on macOS. Android storage, Google services, subscriptions, sharing and deletion are described separately.

15/11/2026

Android data deletion requestsTerms of Use

Staq Route on Android · Personal and local storage

Personal Free and Pro do not require a Staq account. Drafts, routes, stop names and addresses, imported text and document metadata, notes, favorites, history, settings and Personal delivery proofs are stored in the app's private storage on your Android device. The app does not routinely upload this Personal archive to the Team Firebase database. Local storage is protected by Android's application sandbox; this is not a claim that the app separately encrypts its database.

Personal is not entirely offline: enabled address verification and road calculations, Google Play purchase checks, SDK technical traffic, external navigation and exports can transmit information as described below. Availability of online services depends on the distributed version and its configuration.

Android · Documents, camera, photos and ML Kit OCR

Document parsing and recognition of text in selected or captured images take place on the device. Google ML Kit does not send the OCR input image, recognized text or recognition output to Google servers for this on-device recognition. Recognized addresses and text can become stored stops and can subsequently be sent through a separate online feature you use.

ML Kit sends technical metrics to Google for diagnostics, usage analysis, maintenance and abuse prevention. These can include app and device versions, per-installation identifiers, API configuration, input/output sizes, latency, event types and error codes. This technical collection is separate from the content recognized by OCR; on-device recognition does not mean an absence of SDK network traffic. Camera access and selected-photo access are used for OCR, QR pairing or delivery proof as applicable.

Personal proof photos remain in the Personal archive unless you export or share them. A newly captured Personal proof can be resized and marked with date/time and available coordinates; an imported existing photo is not presented as a new capture. Photos may contain personal information visible in the image, regardless of resizing or metadata handling.

Android · Google Geocoding, Routes and external navigation

Where enabled, verifying addresses or optimizing a route can send the stop's address components, such as street, postcode, city, region and country, to Google Geocoding over HTTPS. Do not put unrelated confidential information in address fields. The app's geocoding request does not separately add stop names, notes or photos. Google Routes requests send selected stop coordinates, travel mode and relevant routing options to calculate distance and duration; these requests do not upload the entire Personal archive or a continuous driver location trail.

Some provider results are held briefly in local memory or a local cache. A short local cache lifetime does not guarantee immediate deletion by Google or other providers. When you open Google Maps or Waze, the app passes the selected destination, as coordinates or an address, to that service. Google and the selected navigation provider process requests, connection information and navigation data under their applicable terms and privacy notices.

Android · Location and delivery records

With your permission, Staq Route Android uses location while the app is visible for the current starting point, arrival checks when returning from Google Maps or Waze, and available completion or proof coordinates. This applies to Personal and Team. An arrival check may suggest recording an outcome; completing a stop always requires your explicit confirmation. In-progress location requests are cancelled when Staq moves to the background. Current Android builds do not monitor location or arrival in the background and do not register new geofences.

At manual Team confirmation, available foreground coordinates can be added to the receipt and synchronized with the associated Office. A receipt can be saved without coordinates when no acceptable fix is available. Previously granted permission can be reused; there is not a separate location opt-out on every receipt. You can revoke location permissions in Android Settings. Location data contained in a synchronized receipt or photo remains part of that record.

Android Team · Technical identity, Firebase and synchronization

Team uses Firebase Authentication, Cloud Firestore and Cloud Storage for Firebase. QR pairing or connection recovery creates or reuses an anonymous Firebase authentication UID and associates the device with an Office, driver and pairing session. This is a technical authenticated identity without a separate driver email/password registration; it is not anonymized data, because the Office can associate it with its driver. Personal does not require this pairing. Firebase services also process service and connection metadata needed to authenticate, operate and protect the service.

Assigned routes and stops are downloaded to the paired device. Team sends delivery outcomes, progress, timestamps, notes, available completion coordinates and optional proof photos/thumbnails to Firebase for the associated Office and its authorized devices. Only attach content you are entitled to share with that organization. Team has local cached records and a queue for pending updates, so cloud and device copies can differ while offline. The Office administers its operational records and access; the developer provides the app and its technical services.

Android · Google Play subscriptions

Google Play processes Personal Pro monthly or annual subscriptions. Staq Route queries product/price and existing purchase information, checks purchase status and entitlement, and acknowledges purchases using purchase tokens. Purchase checks can run at startup and during use, even when you do not make a new purchase. The Android purchase flow does not upload purchase tokens to the Team Firebase database. The app does not receive full payment-card details. Google Play processes related payment, transaction and technical information under its own policies.

Android Personal Pro is separate from Office-managed Team access. Manage or cancel Google Play renewals in Google Play; uninstalling the app, unpairing or requesting data deletion does not cancel a subscription. Apple purchases and Office subscriptions are described separately below.

Android · Retention, exports, backups and deletion limits

Local drafts, saved routes, favorites, history and proofs are retained until changed, removed or replaced using the relevant controls, or until Android removes the app's local data. Deleting a history entry or removing proof from a record can retain the underlying photo for separate cleanup; the available cleanup of unreferenced proofs removes eligible files. Temporary-file cleanup runs through specific app actions, so an age threshold is not a guaranteed scheduled deletion deadline.

Personal backups and exports are explicit actions. A backup can include routes, notes, settings and proof photos, including retained photos. The app does not encrypt its backup ZIP; an integrity checksum is not encryption. Files you save, copy or send to another app, storage provider or recipient remain there until removed separately. Deleting local app data cannot recall those copies. Android automatic app backup/device-transfer rules are disabled for app data; this does not disable your explicit exports.

Team cloud records and proof images are separate from local copies. Unpairing removes or revokes the device association and clears relevant local scope when that process completes; network failures can defer parts of it. Unpairing does not itself delete the Firebase Auth identity, pairing history, Office routes, delivery records, uploaded proof images, independent Office copies or exports. Uninstalling does not erase these cloud records.

Team operational records are retained for the associated organization's service and recordkeeping needs until removed through an applicable deletion process. Requests must distinguish operational records, technical identities, proof files and local/offline copies. Security, fraud-prevention or legal obligations may require limited retention; provider logs, caches and backups can follow separate retention cycles. No universal immediate deletion or fixed automatic expiry is promised. The response to a request should identify the data removed, any data retained, the reason and the applicable period or criterion.

Android · Reviewer access and Play Integrity

Reviewer demo access uses a separate Firebase environment with an anonymous authentication UID. To verify and protect this access, the app and backend process an installation public-key hash, access grants and timestamps, and Google Play Integrity tokens and verdicts about app and device integrity. Security controls also use hashed IP addresses for rate limiting. Demo routes, outcomes and any proof photos used in this mode are processed in the reviewer environment.

To request deletion of a reviewer identity or associated data, use the Android data request contact below and specify reviewer access. Do not send reviewer access credentials or Integrity tokens. This is a request subject to verification, not a promise of automatic deletion or a fixed deletion deadline.

Android Personal · Maps Production and technical identity

Personal does not require a traditional Staq account or email/password registration. In Release builds, enabled Maps functions use a dedicated anonymous Firebase Authentication identity, separate from Team and reviewer sessions. This technical UID authenticates service requests; it is not a conventional user account registration and does not mean that technical data is anonymised. Address and route-calculation requests pass through the Staq Production proxy to Google Geocoding or Routes.

The flow can process the UID and other technical identifiers, authentication tokens, Google Play Integrity tokens and app/device attestations, request hashes, security counters, addresses to geocode and coordinates needed to calculate a route. The purposes are providing requested functions, preventing abuse and fraud, security, rate limiting, replay protection and technical compliance. It does not upload the entire local Personal archive.

The proxy stores security counters and hashed replay references separately from the requested address or route. Replay records have an expiry set to 24 hours and an active asynchronous cleanup policy; this is not a guarantee that every copy or other category of data is deleted within 24 hours. Technical identities, counters and necessary provider or security records follow their applicable deletion processes and service, security or legal retention needs. There is no single fixed automatic retention period for all these data.

Staq Route Android · Request data or identity deletion

For a privacy or deletion request, email staq.route@gmail.com with the subject “Staq Route Android data deletion”. Say whether the request concerns Personal data on your device, a Team device identity, Team operational records or an Office account. For Team, name your organization and provide the driver/session reference if available; also contact your Office administrator. Do not send passwords, purchase tokens or unrelated identity documents.

This is a support request, not an automatic deletion button or a guarantee that every Office record can be erased immediately. Identity, authority and scope must be verified before relevant changes are made. The Android app has no standalone account-deletion function; unpairing is a different operation. The developer cannot retrieve or remotely erase a Personal archive that exists only on your device, or recall files independently exported or copied elsewhere. Subscription cancellation remains a separate store action.

The data-request procedure also covers the Personal Maps technical identity and related server-side data. Contact staq.route@gmail.com with the subject “Staq Route Android data deletion”, specify “Personal Maps Production” and the app version and approximate usage period; provide a technical UID only if available. Never send passwords, authentication or Integrity tokens. Following verification of identity, authority and scope, the request covers deletion of the relevant technical identity and associated data that can be identified; any retained security or legal records and the applicable reason and period or criterion are explained in the response. Uninstalling or deleting local routes does not itself delete this server-side identity; deleting it does not recall exports or cancel subscriptions.

Android · Necessary third-party services and security

Depending on the feature used, necessary providers include Google ML Kit, Google Play Billing and Google Play services, Google Geocoding/Routes, Firebase Authentication/Firestore/Storage, and the navigation, file-storage or sharing provider you choose. Online app endpoints described here use HTTPS/TLS. This is encryption in transit, not a claim of end-to-end encryption or immediate removal from all provider systems. No advertising use of Android location is implemented in these flows.

Google Privacy Policy · ML Kit privacy · Firebase privacy · Waze privacy. The general rights, support and website sections below also apply. The iOS-specific sections remain limited to iOS.

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, outcomes, notes and optional proof through Firebase. Google Maps or Waze handle navigation to the selected destination under their own terms and privacy policies. When you return to Staq, with the app visible and your permission, location may enable an arrival check; every outcome requires your confirmation. Staq does not monitor location in the background. An optional route notification displays progress and opens Staq; it does not use background GPS. You can decline location or notification permissions and record outcomes manually.

At manual confirmation, available foreground location may attach coordinates to the receipt; the outcome can be saved without coordinates. Photos selected 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.

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.

Firebase · Privacy

Provider and contact

Staq Route is the application covered by this policy, including Android package com.nicolavisentini.staqroute. The application provider is Nicola Visentini. For Team operational records, contact the organization administering your Office as well as the developer where relevant. 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.

Staq Routestaq.route@gmail.comApp Store
Staq

© 2026 Staq

HomeiPhoneMacAndroidPrivacy PolicyTerms of Usestaq.route@gmail.com