Privacy

ParkRide Planner Privacy Policy

Effective date: 14 July 2026

ParkRide Planner is an independent iOS app for checking supported NSW Park & Ride availability and related planning information. This policy explains what information the app and backend use.

Information used by the app

The app stores favourites, display preferences, alert schedules, snooze state, Supporter entitlement state, preview feature choices, optional commute-guidance settings, and optional saved Location Context on your device.

If you choose to share your location, the app uses it for nearby sorting, distance display, and optional Apple Maps drive-time estimates. You can also save an address, suburb, or nearby place locally as your Location Context so the app can ask Apple Maps for nearby sorting and optional drive-time guidance. Your device location, saved Location Context, entered address, suburb or place, and route estimate inputs are not sent to the ParkRide Planner backend.

Information sent to the backend

The app requests parking availability, history, typical patterns, Plan results, service notices, and related data from the ParkRide Planner backend. Like most web services, the backend and its hosting provider may process ordinary request metadata such as IP address, request time, URL, and user agent for delivery, security, logging, and operations.

If you enable alerts or Live Activity updates, the app sends an installation identifier, Apple Push Notification service token or ActivityKit push token, selected parking locations, selected weekdays, alert time windows, repeat interval, and snooze state. This information is used to send requested notifications and Live Activity updates.

If you use a Supporter Home Screen widget or Apple Watch complication, the app may send the same installation identifier plus Supporter entitlement status and expiry information to issue a short-lived widget access token. The widget and complication use that token to request parking availability for the selected car park.

The app may send a daily active-use heartbeat with an installation identifier, app version, build number, platform, distribution channel such as TestFlight or App Store, and coarse Supporter state. The backend hashes the installation identifier before storing the daily heartbeat and uses it for capacity, cost, reliability, build-channel, and supporter/free trend monitoring. The heartbeat does not include your location, saved Location Context, selected car parks, routes, or screen-level interaction history.

The backend may also aggregate app version, build number, platform, and broad endpoint group from normal app API request headers. This is used to understand whether older app versions are still actively calling the service before changing backend compatibility support. This aggregate request signal does not store installation identifiers, IP addresses, selected car parks, routes, or screen-level interaction history.

Purchases

Supporter subscriptions are handled by Apple using StoreKit. ParkRide Planner reads StoreKit entitlement state to unlock supported app features, short-lived widget access, and Supporter/free operational trends. The app does not run its own payment processing.

Tracking and advertising

ParkRide Planner does not show third-party advertising and does not track you across apps or websites.

Data sources

ParkRide Planner uses Transport for NSW Open Data through a backend proxy. Parking availability can lag actual conditions and should be treated as guidance. ParkRide Planner is not an official Transport for NSW app and is not endorsed by Transport for NSW.

Retention

Alert registration data is kept while alerts or Live Activity updates are enabled or until it is replaced by a newer registration. When alerts are disabled, the backend deletes the alert device registration and alert schedule rows. A one-way hashed registration-order marker may remain so a delayed older request cannot restore a disabled registration. Notification delivery events, backend operational events, and daily active-use heartbeat rows are retained for limited periods for deduplication, reliability, capacity, cost, and operations.

Contact

For privacy questions or support, email [email protected].