Time to Board.Your trip. Your information.
Updated 1 November 2026. Time to Board is published by Nick Port. For privacy questions, access, correction or deletion requests, or complaints, email n51265248@gmail.com.
On your iPhone
No account is required. Time to Board saves your selected public stops, services, settings and cached departure data on your iPhone, including storage shared with its widgets. Remove saved services in the app to remove those selections.
Nearby search requests a foreground location fix only after you tap. Matching happens on your iPhone. Time to Board does not store that device coordinate, log it or send it to our servers. Approximate location works, and manual search remains available. There is no background location tracking.
Maps, timetables and live information
Apple provides Location Services, MapKit maps and typed place search. Apple processes information under its privacy policy. Our handling of a nearby location fix does not describe all processing performed by Apple's operating-system services.
Cloudflare hosts Time to Board's timetable and transport services. Requests include ordinary connection information, such as IP addresses. Timetable requests may include requested dates. Departure, vehicle and alert requests send public transport identifiers, such as selected stops, routes, directions or trips. Your device coordinate and map bounds are not sent to Time to Board's transport servers. These requests provide the information you ask for; they are not used for advertising.
App security
Apple App Attest helps our server verify requests from the app and prevent abuse and replayed requests. The server stores an installation identifier, an App Attest key identifier and public key, a verification counter, and creation and last successful verification times. These records can distinguish installations even though no account name is attached. They are not advertising identifiers.
Security challenges expire after two minutes. Scheduled cleanup removes expired challenges and registration records after 90 days without a successfully verified request. Returning installations can register again. Cleanup runs periodically, so removal can follow the expiry time. We do not retain your private App Attest key on our server.
Optional disruption notifications
In-app alert matching happens on your iPhone. If you enable push notifications for a saved Metro or tram service, Time to Board's Cloudflare-hosted service stores your installation's device token, selected public service identifiers and labels, and chosen travel days and windows. Apple Push Notification service (APNs) delivers notifications. Disruption push is currently disabled while its delivery setup is pending. If a separate delivery provider is introduced, this policy will be updated. No device coordinates are sent.
Turning notifications off or removing a service removes its subscription when the app connects. Subscriptions expire after 30 days without renewal from the app. Delivery records are kept for up to 30 days to prevent duplicates, subject to periodic cleanup. Invalid-token responses can remove a subscription earlier. Uninstalling does not immediately contact our server; expiry or token invalidation handles remaining subscriptions. Change notification permission in iOS Settings.
Optional commute Live Activities
Enabling a commute schedule sends its selected days and travel times, public service identifiers and labels, and Apple Live Activity push tokens to our Cloudflare-hosted service. These allow activities to start, update and end without opening the app. The current production server sends commute updates directly to APNs. No device coordinates are sent.
Disabling a schedule or removing its saved service removes the server subscription when the app connects. Schedules and associated tokens expire after 30 days without renewal from the app and are removed by periodic cleanup. Open Time to Board while online at least once every 30 days to keep scheduled activities enabled. Existing server schedules receive a 30-day grace period when this retention update first processes them. Tokens for completed activity sessions are cleared when the server finishes that session. Missed pushes may delay a visible change or removal on your phone.
Diagnostics and support
The app keeps operational diagnostics locally: up to 1,000 events in memory and a file limited to approximately 1 MiB, rotated to the latest 500 events. These include app version, request timing, status codes and feed health. Logs are not uploaded automatically. Diagnostics lets you clear logs or choose to export and share them. Shared exports may include request identifiers and timing metadata. Time to Board's diagnostic events exclude device coordinates, search text, saved stop names, request bodies, push tokens and installation identifiers.
Our server records operational events such as request status, timing and feed failures to operate, secure and troubleshoot the service. Cloudflare, our delivery host and Vercel may also process connection and security information under their own retention settings. Provider logs and backups have separate retention from the live records described above; we do not promise immediate erasure from provider backups. Contact us with questions about provider retention.
If you email support, your email address, message, attachments and any diagnostics you choose to share are available to Nick Port to respond and investigate. TestFlight diagnostics and feedback are handled through Apple and may be made available to Nick Port. Only include information needed to explain the issue. Support correspondence is retained while needed to resolve the issue and handle related requests; you may request its deletion.
Service providers and overseas processing
Time to Board uses Apple for maps, Location Services, TestFlight and APNs; Cloudflare for transport services and server storage; Vercel for this website; and Google/Gmail for support email and beta registration notifications. No separate push-delivery relay is configured in the current production service. These providers operate the features described above and allow us to respond to support. Their infrastructure and personnel may process information outside Australia, including in the United States and other countries where they operate. Data is not guaranteed to remain in Australia. See Cloudflare's privacy policy, Vercel's privacy notice Google's privacy policy, and Apple's policy linked above. Contact us for information about the providers used for your request.
This website
Vercel hosts this website and processes technical requests to deliver and secure it. There is no account system or analytics script. Beta registration collects your full name and email address. Cloudflare processes the submission and emails it to Nick Port through Gmail to manage TestFlight invitations manually. The registration endpoint uses request limits and a hidden spam field to reduce automated submissions. Registration details are not written to a separate signup database or application logs. These providers may process information outside Australia. Details are retained while needed to manage beta testing; contact Nick to request access, correction or deletion. Registration is optional and is not a marketing subscription.
Your choices, requests and complaints
You can use manual search without location access, change location and notification permissions in iOS Settings, and disable optional server features in the app. Server changes require a connection; uninstalling alone does not immediately delete server records. Security records expire separately from notification and commute subscriptions.
To request access, correction or deletion, or complain about our handling of information, email Nick Port at the address above. Describe the feature and request without sending passwords, private keys or push tokens. We may ask for proportionate verification to locate a record and protect it from unauthorised disclosure. Without an account, we may be unable to associate an email address with a particular installation. We will explain any inability to locate, change or delete information, including any legal or security reason for retaining it.
We aim to acknowledge privacy complaints within seven days and respond within 30 days. If more time is needed, we will explain why. If unresolved, you can contact the Office of the Australian Information Commissioner, which can explain whether your complaint falls within its jurisdiction.