QuickPass helps drivers estimate wait times at border crossings using optional GPS contribution and aggregated statistics. This policy describes what we collect, why, how long we keep it, and your choices. It is written for product transparency; have counsel review it before a public launch.
QuickPass is operated by the QuickPass project. For privacy requests, email support@lazydevsagency.com (placeholder — replace with your production address).
We use location data only when you start a contribution session, to:
Contribution is explicit: GPS sampling runs when you start a session. Background location, if granted, continues an active approach or queue session only. You can revoke location permission anytime in system settings.
We store a pseudonymous device id generated on your device — not your name, email, or phone number. Sessions and erasure requests are tied to that id: it is what lets the app show you your own trip history, and what an erasure request is carried out against. Wait-time math does not require knowing who you are.
Email support@lazydevsagency.com and ask us to erase your data. There is no delete button in the app — erasure is a request we carry out for you, and we would rather say that than point you at a control you would go looking for and not find.
We erase against the pseudonymous device id, so the request has to identify which device it is for — quote the id if you have it, and otherwise tell us enough about your use of the app (dates, crossings) for us to match it. We will confirm when it is done.
Erasure removes your contribution sessions and the raw location samples belonging to them, and switches contribution off for that device. Aggregates already computed from many drivers are not reconstructed to remove a single historical contribution.
Paid features are sold through the App Store / Google Play. We use RevenueCat to manage entitlements. Apple, Google, and RevenueCat process purchase receipts and subscription status under their own policies. We store entitlement fields (plan, status, expiry) keyed to your device id / RevenueCat app user id — not your payment card details.
Maps are drawn with the Mapbox Maps SDK. Displaying a map sends tile and style requests to Mapbox, and those requests carry the part of the world you are looking at. This happens whenever a map is on screen — it is not limited to contribution sessions, and it is separate from the GPS contribution described above. Mapbox handles that traffic, and its own SDK telemetry, under its privacy policy.
Every map in the app shows the Mapbox information control in a corner. That control is also where Mapbox telemetry can be turned off, which is why the app never hides it.
For crossings equipped with public cameras, the app can show live images or streams operated by the relevant border, road, or police authorities (for example national automobile clubs or ministries of interior). These feeds are loaded directly from the operator; viewing them is subject to the operator's own terms. Aggregate vehicle-queue observations may be derived from such public feeds to improve wait estimates; no personal data is involved.
If you enable notifications, we use them for wait-change alerts at crossings you follow and for a lock-screen summary while you are approaching or waiting at a border. You can turn notifications off in the app at any time.
API traffic uses TLS in production. Access to admin tooling is token-protected. No system is perfectly secure; we aim for least data and short raw retention.
Where GDPR or analogous laws apply, QuickPass processes location and device identifiers as needed to provide the service you request (contribution and estimates) and on the basis of your consent for optional GPS contribution. Depending on your region, you may have rights to access, rectify, erase, restrict, or object to certain processing, and to lodge a complaint with a supervisory authority. Exercise any of them by emailing support@lazydevsagency.com, as described under Delete my data above. You can withdraw consent for location collection at any time in your device's system settings; that stops further collection but does not by itself erase what was already contributed. Legal review is required before relying on this summary for a public launch.
QuickPass is intended for drivers and is not directed at children under 13 (or the minimum age in your country). We do not knowingly collect personal data from children.
We may update this policy. The “Last updated” date above will change when we do. Material changes should be reflected in the app store listing and in-app privacy screen.