This Privacy Policy explains how StopSorted (“we”, “us”, “our”) collects, uses, stores, and shares personal information when you use stopsorted.com, the Fleet portal, the Admin console, and the StopSorted Android app on Google Play (package com.stopsorted.delivery) (together, the “Services”).
The developer / company named for the Google Play listing is StopSorted (ABN 13 022 918 973). Contact for privacy: privacy@stopsorted.com.
We operate primarily for customers in Australia, with coverage expanding over time. Where the Australian Privacy Principles (APPs) under the Privacy Act 1988 (Cth) apply to us, we aim to handle personal information consistently with those principles.
1. Who this policy covers
Fleet controllers (business account owners and authorised users of the Fleet portal).
Drivers and device users on fleet-managed handsets, and solo / Play Store users of the Android app.
Website visitors who browse marketing pages, submit contact or country-coverage requests, or create an account.
If you are a driver employed or contracted by a fleet, your company is typically the primary controller of operational data about your work. Contact your fleet controller for day-to-day access or deletion requests about run history tied to their business account.
2. Information we collect
Account & contact: name, email, phone (optional), company name, password (stored hashed), role (fleet admin / super admin), and support messages you send us.
Billing metadata: for fleet subscriptions we receive limited payment metadata from Square (for example subscription status, amounts, timestamps, and truncated card descriptors if Square provides them). We do not store full card numbers, CVVs, or PINs. Consumer purchases through Google Play are processed by Google; we receive subscription / entitlement signals needed to unlock the app.
Device & licence data: device identifiers and signatures used to bind seats to phones you approve, device name / model labels, status (pending / approved / blocked / revoked), last-seen times, and access-request history.
Location: the Android app requests precise location (and may run a foreground location service while a run is active) so maps, next-stop guidance, arrival times, and — for fleet phones — live office tracking work. GPS points may be uploaded during an active run and briefly buffered on the phone if the network is offline, then synced when connectivity returns. Solo / free / Play personal use does not stream continuous background GPS to StopSorted for a fleet live map. You can deny or revoke location in Android settings; map and tracking features that need it will stop working.
Delivery operations: stop addresses and coordinates, customer or stop notes you enter, run codes, completion / skip / failure status, service times, priorities, VIP zones you draw, and related timestamps. Leave-list labels and customer tracking links work as described below.
Proof of delivery (when a fleet turns it on): the Android app may require a camera photo at Done, optionally with an on-screen signature. Photos are geotagged with the location at capture when location is available. Images and signatures are uploaded to our servers and shown to that fleet’s authorised users (and may be included in freight / POD exports or webhooks the fleet configures). Skip does not require a photo.
Notifications & overlay (Android): we may request notification permission so Done / Skip and route updates stay visible while Google Maps or Waze is open. If you choose the floating chip and your phone blocks bubbles, the app may ask for “display over other apps” permission so that chip can appear.
Customer tracking links: when a fleet turns on customer tracking emails and creates a tracking share, we store a random token, the related run/stop ids, optional recipient email, and an expiry (typically 7 days). Anyone with the link can see a minimal public page: company name, a masked stop address, status, a rough arrival estimate when available, and stop coordinates only when the stop is on the way or completed. Tokens can be revoked or expire; we do not publish full fleet dumps on these pages.
Usage & diagnostics: approximate product usage (for example free-route and stop counts for free-try limits), API and auth audit logs, IP address, user agent, and basic server logs needed to secure and operate the Services.
Website traffic (first-party): when you browse our public pages we record a pageview for the Admin console: page path, referrer, browser and OS, device type, language, timezone, screen size, and time on page. Country is taken from a CDN header when one is present, otherwise inferred from timezone or language. We store a random first-party cookie so we can count unique visitors. We do not store visitor IP addresses for this purpose, and we do not collect sex, gender, or age — browsers do not send those, and we do not buy advertising-network demographics.
Geocoding & maps: address search text you submit so we can return suggestions (processed against our address / road stack for enabled countries). Map tiles and styles may be loaded from map providers we configure (for example OpenFreeMap / open map tile hosts) so the in-app map can render.
3. How we use information
We use personal information to: provide and improve the Services; authenticate users and bind seats to approved phones; sort and display routes; show live fleet location to authorised fleet controllers; capture and store proof of delivery when enabled; send optional customer tracking emails and public tracking pages when a fleet enables them; bill seats for phones that run; send transactional email (verification, password reset, billing notices, dunning / grace / suspension notices); respond to support; prevent abuse and fraud; meet legal and tax record-keeping duties; understand product reliability (aggregated where practical); and count first-party website traffic in the Admin console.
We do not sell personal information. We do not use your delivery addresses, photos, or location history to build advertising profiles for third-party ad networks.
4. Payments
Fleet billing is processed by Square (Block, Inc. / Square AU). Card details are entered in Square’s payment form and handled under Square’s systems and policies, including their Privacy Policy, Payment Terms, and General Terms.
Google Play purchases are governed by Google’s terms and privacy practices. Manage or cancel Play subscriptions in Google Play.
5. Sharing
We share information only as needed with: Square (fleet payments); Google (Play billing / entitlement checks where applicable); email delivery providers you or we configure for transactional mail; map / tile providers that receive standard map tile requests from the device when the map is shown; infrastructure providers that host compute, databases, and logs under our direction; and professional advisers or authorities when required by law or to protect rights and safety.
Fleet controllers can see device, location (when on a run), stop data, and proof-of-delivery media for their own fleet. If a fleet configures a freight / POD webhook or export, completion data (and photo / signature fields when present) leave our system to that fleet’s chosen destination under the fleet’s responsibility. Customer tracking pages expose only the minimal fields described above to people who hold a valid tracking link. We do not publish your full operational data publicly.
6. International & hosting
Services are operated from infrastructure we control. Sub-processors (for example email, payment, or map providers) may process data in Australia or other countries. Where data leaves Australia, we take steps appropriate to the sensitivity of the data and the provider’s role.
7. Retention
We keep account and operational data while your account is active and for a limited period afterward as needed for backups, dispute handling, security, and legal obligations. Proof-of-delivery photos and signatures are kept with the related stop / run records for the fleet’s operational retention, then removed when those records are purged. Detailed website pageviews are kept about 400 days; daily totals and unique-visitor cookies are kept so lifetime counts still work. Tax and invoice records related to fleet billing may be retained longer in our tax ledger (including after a fleet is deleted) so we can meet Australian record-keeping expectations. Automated jobs may purge expired access requests, stale operational data, and accounts that remain unpaid after our published notice periods.
8. Security
We use industry-standard controls appropriate to a SaaS product of this scale (TLS in transit via our reverse proxy, hashed passwords, API keys and device tokens, access-controlled admin tools). No method of transmission or storage is perfectly secure. Please use a strong unique password and protect fleet admin access.
9. Your rights & choices
Subject to applicable law, you may request access, correction, or deletion of personal information we hold about you. Free / Play Store users can delete their account in the app (deletion is automated and removes associated operational data we hold for that personal account, subject to backups and legal retention). Step-by-step instructions: Delete your StopSorted account. Fleet business accounts and devices are deleted by the fleet controller from Fleet Settings (instant wipe for that fleet’s operational scope, with drivers signed out). Some billing / tax records may remain as noted above.
You can withdraw location, camera, notification, or overlay permission in Android settings. You can unsubscribe from non-essential marketing email if we send any; transactional billing and security messages will still be sent when required to operate your account.
Contact: privacy@stopsorted.com. Fleet drivers should also contact their company support email for operational data held by the fleet.
10. Children
The Services are directed to businesses and adult drivers. We do not knowingly collect personal information from children under 16.
11. Cookies & local storage
The marketing site and portals use essential cookies / local storage for session authentication and basic preferences. A first-party visitor cookie (ss_vid, about 13 months) and a short session cookie (ss_sid, 30 minutes idle) count unique visitors in Admin → Web Traffic. The Android app stores session tokens and offline buffers on the device as needed to operate. We do not run third-party advertising trackers on the core product.
12. Google Play Store listing
This Policy is the publicly accessible privacy policy for the StopSorted Android app on Google Play. Paste this URL into Play Console → App content → Privacy policy:
https://stopsorted.com/privacy
The same link is offered in the app (login and the driver menu). Complete Play’s Data safety form so it matches this Policy (location, photos, device IDs, and account data as described above).
13. Changes
We may update this Policy from time to time. The “Last updated” date will change when we do. Material changes that affect how we handle personal information will be highlighted on the site or by email where appropriate. Continued use of the Services after an update means you acknowledge the revised Policy.
14. Contact
Privacy questions: privacy@stopsorted.com
Legal: legal@stopsorted.com
Support: info@stopsorted.com
Postal: 110 Creamery Rd, Yinnar VIC 3869, Australia
ABN: 13 022 918 973
Website: https://stopsorted.com · Contact