Privacy Policy
HopStop is a calendar-based route planner. It reads your calendar events, calculates drive times, and schedules departure alerts. It works with Apple Calendar via EventKit and Google Calendar via OAuth. All processing happens on your device. HopStop has no backend server and does not transmit your data anywhere.
Data We Access
HopStop accesses two categories of data on your device, both of which remain on your device:
- Calendar data. HopStop reads events from the calendar sources you authorize. HopStop accesses Apple Calendar via Apple's EventKit framework, which covers all calendar sources configured on your device — including iCloud, Exchange, and local calendars. HopStop accesses Google Calendar via OAuth; see "Google API Services — Limited Use Disclosure" below for the full disclosure. HopStop uses calendar data only to populate your route. It does not store it beyond your session, does not transmit it to Mr. Jackdaw Company LLC, and does not share it with any third party.
- Location. HopStop accesses your location while the app is in use to calculate drive time to your first appointment and to schedule departure alerts. Your location is used only for these functions and is not stored or transmitted.
Google API Services — Limited Use Disclosure
HopStop signs in with Google using OAuth. This section covers what Google user data HopStop receives, how HopStop uses it, where it lives, and how to delete it. HopStop's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Google's handling of your account data is governed by Google's Privacy Policy.
Data Accessed
HopStop requests the following Google OAuth scopes:
openid,email,profile: basic sign-in scopes. Returns your Google account ID, email address, display name, and profile picture URL.https://www.googleapis.com/auth/calendar.readonly: read-only access to your Google calendar list and the events within calendars you select inside HopStop. HopStop never writes, modifies, or deletes Google Calendar data.
HopStop does not request any other Google API scope.
Data Usage
- Account identity (email, name, profile picture URL) appears in HopStop's account-switcher so you can identify which Google account is active.
- Calendar list and events populate your daily route. Events become numbered stops on a map, ordered by their scheduled start time. HopStop passes event locations to Apple MapKit on-device for geocoding and drive-time calculation. HopStop does not use Google user data for advertising, profiling, training generative AI or machine-learning models, or any purpose unrelated to the route-planning feature.
Data Sharing
HopStop does not share Google user data with any third party. HopStop does not transmit calendar data to Mr. Jackdaw Company LLC — Mr. Jackdaw Company LLC operates no backend server that receives it. Apple MapKit geocodes event locations on-device; those queries go directly from your device to Apple's MapKit service, governed by Apple's Privacy Policy.
Data Storage and Protection
- Calendar event data lives in memory only during an active session. HopStop does not write it to disk.
- Google OAuth tokens live in the iOS Keychain, where iOS protects them with hardware-backed encryption. HopStop transmits them only to Google's OAuth endpoints over HTTPS.
- Account identity (email, name, profile picture URL) lives locally in standard iOS application storage so the account-switcher persists across launches. HopStop removes it when you remove the account.
- The Google Sign-In SDK and Google's APIs enforce TLS on all network traffic between HopStop and Google.
Data Retention and Deletion
HopStop does not retain Google calendar event data. It lives in memory during an active session and clears when you close the app.
You can revoke HopStop's access to your Google account and delete all data HopStop holds about that account by any of the following means:
- From within HopStop: open Settings → Accounts, and remove the account. This deletes the OAuth tokens from your device's Keychain and discards the cached identity data for that account.
- From your Google Account: visit myaccount.google.com/permissions and revoke HopStop's access. This invalidates HopStop's tokens immediately.
- By deleting the app: uninstalling HopStop from your device removes all locally stored data, including OAuth tokens.
For data deletion requests, or any other privacy-related question, contact support@mrjackdaw.com. Mr. Jackdaw Company LLC responds within 30 days.
Analytics and Usage Data
HopStop does not currently collect any analytics or usage telemetry. In the future, Mr. Jackdaw Company LLC may collect anonymized, non-personally-identifiable usage data to understand how the app is used and improve it. Any such data would not identify you and would not be shared with third parties for advertising purposes. This policy will be updated before any such collection begins.
This describes the HopStop app. The website that hosts this policy uses Google Analytics for measurement. See the website privacy policy.
Third-Party Services
HopStop does not integrate any third-party analytics, advertising, or data-collection SDKs. Navigation handoff to Google Maps or Apple Maps is initiated by you and governed by those applications' own privacy policies.
Beta Signup Form
If you submit the beta signup form at apps.mrjackdaw.com/hopstop/beta, we collect the information you provide (name, email, and any optional fields) for the sole purpose of inviting you to the HopStop TestFlight beta. We do not share this information with third parties. We use Formspree as our form backend; your submission passes through their infrastructure and is delivered to us as email.
Once the beta program ends or we no longer need to contact you, we delete the submission data.
Children
HopStop does not knowingly collect any information from anyone, including children under the age of 13.
Contact
Questions about this policy can be directed to mrjackdaw.com/contact or support@mrjackdaw.com.
Changes to This Policy
If this policy changes materially, the updated version will be published at this URL with a revised effective date.