Privacy Policy

1.Information We Collect

When you use "Can I Make It?", your location is used to calculate travel time to the ferry terminal. You can share your device's location or type an address. Your coordinates are sent to our server to query Google's Routes API for travel time. A typed address is sent to Google's Geocoding API to turn it into coordinates. We combine your location with ferry data from WSDOT and travel-time data from Google to work out whether you can make a sailing. Your device location is requested only with your permission, which you can withdraw at any time in your device's settings. Your precise location is used only for the duration of that request and is never stored or written to our logs. We keep a coarse, rounded version of the location (to roughly one kilometre) with no identifier attached for 30 days, solely to measure and improve prediction accuracy, and then clear it.

Drive times and distances returned by Google, and the values we store that are taken directly from them (such as the predicted drive time saved with an accuracy record), are kept for 30 days and then cleared, as Google's terms require. The results we calculate ourselves, such as the odds we showed you, are kept.

Reminders are optional. If you opt in to a reminder for a specific sailing, the app registers a push token with your device's notification service and stores it alongside a randomly generated device ID, together with the sailing you asked to be reminded about. On iPhone the token comes from Apple Push Notification service; on Android it comes from Firebase Cloud Messaging, a Google service. The token and device ID exist only to route your reminder back to your device and to show whether a reminder is set; they are not linked to a name, an account, or any contact information. We do not share notification content with anyone other than the delivery service. Declining the notification permission disables reminders and affects nothing else in the app.

On the website, we use Vercel Analytics to collect anonymous usage data including page views, device type, browser, and country. Vercel Analytics does not use cookies and identifies visitors via a privacy-friendly hash that resets daily, so visitors cannot be tracked across days or websites. The iPhone and Android apps do not load Vercel Analytics.

If you respond to the "Did you make the boat?" prompt, we store your response (yes or no) along with the predicted probability, the sailing, and your travel mode. No device ID or other identifier is sent or stored with it. It is anonymous and used only to calibrate prediction accuracy.

The app stores preferences on your device, such as favourite routes and whether you have dismissed the welcome card. These stay on your device. The one exception is the randomly generated device ID described above. It is stored on your device and sent to our server only to set, check, or cancel a reminder. In the iPhone and Android apps, checking your odds for a sailing also checks whether you already have a reminder set for it, which sends the device ID; that check reads reminder records and stores nothing. The website does not send it.

2.Information We Do Not Collect

We do not collect names, email addresses, phone numbers, payment information, or any personally identifiable information. We do not require account creation. We do not use cookies for tracking.

3.How We Use Information

• Your precise location is used solely to calculate your travel time to the terminal during your request. It is never stored or logged. A coarse, rounded version is kept for 30 days, with no identifier attached, to measure prediction accuracy, and then cleared.
• Analytics data from the website is used to understand general usage patterns and improve the service.
• Outcome feedback is anonymous and is used to measure and improve prediction accuracy.
• Push tokens and device IDs are used solely to deliver the sailing reminders you opt in to.

4.Third-Party Services

Your location, or the address you type, is sent to Google to calculate travel time and to find the address. Use of Google Maps features and content is subject to the Google Maps End User Additional Terms of Service and the Google Privacy Policy, which apply to this data.

Hosts the application and provides privacy-friendly analytics for the website. Like most web hosts, Vercel's request logs record the IP address of each request. Vercel's privacy policy applies.

Delivers reminder notifications to iPhones. Apple's privacy policy applies to this data.

Delivers reminder notifications to Android devices. Google's privacy policy applies to this data.

Our database. It stores ferry schedule data, historical space readings, anonymous outcome feedback, the coarse location and Google travel-time values described above (each cleared after 30 days), and, only if you opt in to reminders, your push token, device ID, and reminder records. No name, account, or contact information is stored.

Public ferry data is fetched from WSDOT. No user data is sent to WSDOT.

5.Data Retention and Deletion

• Location data: Precise coordinates and typed addresses are never stored or logged; they are used only for the duration of your request. A coarse, rounded version (to roughly one kilometre), carrying no identifier, is kept for 30 days for prediction calibration and then cleared.
• Travel-time data from Google: Drive times and distances returned by Google, and values we store that are taken directly from them, are cleared 30 days after the check (a clean-up job runs daily). The results we calculate ourselves, such as the odds we showed, are kept.
• Analytics: Retained per Vercel's standard retention period.
• Outcome feedback: Retained indefinitely, anonymously, for prediction calibration.
• Push token, device ID, and reminders: Retained while reminders are in use. When we next try to send you a reminder and Apple reports the token is no longer registered, or Firebase Cloud Messaging reports it is unregistered (for example, after the app is uninstalled), the token, the device record, and its reminders are deleted automatically.
• Reminder delivery log: Each reminder we try to send is logged with its device ID, the sailing, and whether delivery succeeded, so we can diagnose failed reminders. This log is kept until you ask us to delete it.
• Deleting your data: Email maketheferry@gmail.com to delete your device's reminder data. We will delete your push token, device ID, reminders, and reminder delivery log. Outcome feedback and coarse location carry no identifier, so they cannot be traced back to your device.

6.Children's Privacy

Make the Ferry does not knowingly collect information from children under 13.

7.Changes to This Policy

We may update this privacy policy at any time. Changes will be reflected by the "Last updated" date.

8.Contact

Questions about this privacy policy can be directed to maketheferry@gmail.com.