Bridge Tracker Privacy Policy
Last updated: October 24, 2026
Bridge Tracker is provided by Zachary Perlman under the 305 Labs name. This policy covers the Bridge Tracker iPhone/iPad and Apple Watch apps, their widgets and complications, and the website at bridge.305labs.org. The initial App Store release is intended for the United States.
Contact us at support@305labs.org with privacy questions, support requests or requests concerning your information.
Information used to provide the service
You do not need an account to check the bridge. The current apps do not request GPS location, contacts, photos or microphone access. Public bridge status and opening history come from FL511; they are information about the bridge, not your travel history.
When your app, widget or browser connects, our hosting provider, Cloudflare, processes network information such as your IP address and request metadata to deliver and protect the service. Technical logs and service metrics may be used to investigate errors and abuse. An IP address can indicate an approximate location even though we do not request your device's GPS location.
Cached bridge readings, notification preferences and demo progress are stored on your device. The current website landing page does not save a theme preference; an earlier dashboard may have left a preference in browser local storage.
Optional bridge alerts
Alerts are off by default. If you enable and successfully save them, we store a randomly generated installation identifier, your Apple push token and its environment, your selected bridge changes and time windows, and registration timestamps. We also store a hash of a device credential used to protect your registration. The credential is stored in the device's Keychain and sent over HTTPS to authenticate registration changes; our application server persists only its hash.
We use this information to deliver the alerts you choose through Apple Push Notification service and to manage registration and delivery failures. It is not used to build a travel history. Notification enrollment also uses a hashed IP address for short-lived rate limiting.
If you enable Live Activities, we also store Apple Live Activity start/update tokens and the bridge opening timestamp to show elapsed time and dismiss the activity when the bridge comes down. Activity records and their credential hashes are retained for at most eight hours, then removed on the next maintenance pass. After opt-out, a pending activity record may remain briefly so an already-started activity can be dismissed. Start tokens follow the normal alert registration retention rules. This does not collect your location or trip history.
Optional commute monitoring
If you save My commutes or use Start now, we store a separate registration with your installation identifier, push tokens, chosen weekdays and Miami time windows, registration expiry, and a credential hash. We also store the current session and any skipped window or early-ending preference to start, update and end your commute Live Activity. These choices are not GPS measurements, and we do not record a history of your journeys. Commute activity records are removed after ending or within five minutes after their deadline on the next maintenance pass. Registrations expire after 90 days without renewal; opening the app can renew them.
General bridge alerts and commute monitoring have separate settings. To stop recurring commutes, turn off Scheduled commutes and save while online. End this commute stops the current session. Remove saved commute data removes the server registration and local saved schedule; a credential hash may remain until its original expiry to prevent another installation taking over the identifier. Delivery already handed to Apple cannot be recalled.
Optional one-minute demo
When you choose the one-minute demo, the app may send a separate random demo identifier, a demo Live Activity token, its environment, the simulated opening time and a credential to our server. Only a hash of the credential is stored there. These records are used only to close and dismiss that demo on your device, including while the app is in the background. They are removed after delivery or cancellation; otherwise they expire five minutes after the demo starts and are removed on the next maintenance pass. Hashed IP rate limits also apply. Optional sample notifications are scheduled locally on your device. The demo does not enroll you in real bridge updates or change bridge observations or history.
Optional in-app feedback
If you choose Settings โ Send feedback in the iPhone/iPad app, the app sends the message you type and whether it is a bug or an idea. If you leave Include app info on, it also sends the app version and build, the iOS or iPadOS version, the device model (such as iPhone16,1) and whether the app came from TestFlight or the App Store. The app shows this information before you send it. Feedback is sent only when you tap Send. It does not include your name, email, installation identifier, push token, alert choices, commutes or location.
Feedback goes through a 305 Labs relay hosted by Cloudflare at feedback.305labs.org, which files it in a private GitHub repository that only the developer can read. The relay uses your IP address only to limit how many reports can be sent each minute and does not store it or the feedback. We use feedback only to fix and improve our apps and keep it as long as it is useful for that. Because feedback is not linked to you, we can't reply to it or find it from your email address; email support@305labs.org if you want a reply.
Sharing and service providers
Cloudflare hosts the website, API and notification registration storage. Apple processes push tokens and notification content to deliver alerts. If you contact support, our email service processes your email address, message and any attachments you choose to send. GitHub stores feedback you send from the app.
We use these providers to operate, secure and support the service. Information may also be disclosed when required by law or necessary to protect users and the service. Providers may process information outside your state or country. Their own privacy practices also apply: Cloudflare Privacy Policy and Apple Privacy Policy.
Advertising
Versions of the iPhone/iPad app with advertising enabled use Google AdMob to display a small banner on the dashboard. The initial App Store release is built without advertising SDKs. Separate test builds may include them. The Apple Watch app, widgets, complications and CarPlay widgets do not include advertising.
We request non-personalized ads, enable Google's restricted data processing and disable the publisher first-party advertising ID. We do not request permission to track you across other companies' apps or websites or access your IDFA. This does not mean ads collect no information: Google may process your IP address (including approximate location), app- or device-bounded identifiers, ads seen and interactions, and crash and performance information to serve, measure and protect advertising.
Google's User Messaging Platform checks whether a privacy message is needed. Open Privacy & support in the app to read this policy and, when available for your region, manage Google's ad privacy choices. Declining optional uses does not disable bridge status or alerts. Ads may not be available when consent settings cannot be loaded or do not permit an ad request.
We do not send your alert registration, push token, notification schedule or bridge history selections to Google. We do not sell personal information or configure these ads for cross-context behavioral targeting. Google's processing and retention practices are described in its Privacy Policy and information about apps that use its services.
Retention and your choices
You can check bridge information without enabling alerts. To remove your notification registration and pending alerts, open Settings โ Bridge updates and switch off Bridge updates while online. Wait for the change to succeed. A notification already handed to Apple cannot be recalled.
You can also turn off notifications in iOS Settings, but that setting alone does not delete the server registration. Deleting the app does not immediately delete that registration either.
Registrations expire after 90 days without renewal; opening the app with alerts enabled can renew them. Temporary alerts stop at their selected deadline and do not extend when you reopen the app. Expired registrations are removed during server maintenance, normally within a day. Tokens reported invalid by Apple are removed. Rate-limit records have a one-minute validity window and are removed on a subsequent cleanup pass; they are not a browsing history.
Clear website data in your browser to remove its saved theme preference. Removing the app clears ordinary local app storage, although Keychain items may remain under Apple's operating-system behavior.
Support correspondence and operational records may be retained as needed to respond to requests, troubleshoot issues, prevent abuse and meet legal obligations. Provider-managed logs and backups have separate retention practices; deleting a registration does not promise immediate erasure of all provider records.
Email support@305labs.org to request access, correction or deletion of information we hold about you, or to ask about privacy choices and rights that apply where you live. We may need information to verify and locate the relevant record. Because there is no account or email attached to an alert registration, we may not be able to locate it from your email address alone. Do not email your device credential or private keys.
Security and children
We use HTTPS and restrict access to notification registration through a per-device credential. No method of transmission or storage is completely secure.
Bridge Tracker is a general-audience utility and is not directed to children under 13. If you believe a child has provided personal information to us, contact support@305labs.org so we can investigate and address it.
Changes to this policy
We will post updates on this page and revise the date above. Where required, we will provide additional notice or obtain consent before materially changing how information is used.