Privacy policy
Updated October 16, 2026
TeeTyme helps you find tee times and receive availability alerts. This policy explains how the app and website use your information.
Searches and bookings
Your search sends the selected courses, date, players, holes, and time window to the TeeTyme server, which checks the course’s booking provider. Book now opens the provider’s website. TeeTyme does not collect booking passwords or payment details and does not complete reservations. The provider’s privacy policy applies when you use its website.
On your device
Saved searches and their names stay in browser storage or on your device. On the website, your last search selections and cart pricing preference are saved in a first-party cookie for up to one year and sent to TeeTyme so the page can render your selections immediately. The mobile app keeps these preferences and your distance unit choice on your device. The mobile app also saves whether you completed the welcome guide and keeps a random device credential in secure storage to manage your alerts. When an invite is required, its code and app session are kept in secure storage too. TeeTyme does not require a personal account or request access to your contacts or calendar.
Optional location
When you first visit the website’s course-search pages, TeeTyme requests browser location permission. We remember that we requested permission in browser storage so we do not repeatedly prompt you after a refusal. If you already granted permission and the saved location has expired, we may refresh it on a later page load. In the app, you can request location permission from the welcome guide, course selector, or Settings. Once permission is granted, the app automatically refreshes an expired or missing approximate location while it is in the foreground, including on launch or return to the app. It does not request location in the background. TeeTyme rounds the coordinates to two decimal places before sending them to our server to calculate approximate straight-line distances to courses. Your exact coordinates are not sent by this feature. On the website, the rounded location is stored in a first-party cookie for up to one hour so distances can render on page reload; this cookie is sent to TeeTyme with website requests. In the app, a location request can provide either approximate or precise coordinates depending on your device settings; both are rounded before transmission. The rounded location stays in memory for up to one hour and is sent as an input to course-distance requests. We do not store these coordinates in our database, include them in shared course caches, or track location in the background. You can revoke location permission in your browser or device settings and remove the website’s saved location by clearing its cookies. Saved locations expire after one hour. Hosting infrastructure may process request data under its own retention policies.
Optional alerts
When you enable alerts, the server stores your push notification token, a hashed device credential, and your alert preferences: courses, specific dates or days of the week, players, holes, time windows, rate preferences, and any expiration date. We use these to check availability and send matching notifications. We also store recent observed availability identifiers to detect later openings, along with matched tee times, their booking links, and delivery records to avoid duplicate notifications and check delivery status. Tapping a tee-time notification opens the matched booking page in the in-app browser. Expo’s push service and Apple or Google process the token and notification content to deliver them. The app also keeps a notification inbox on the server, including the message, matched opening and booking link, sent time, and whether you have marked it as read. Viewing or marking a notification as read does not remove it.
App invitations
When invitations are enabled, the server stores an invitation name and optional notes supplied by the administrator, a hash and partial hint of the invite code, redemption counts, access timestamps, and hashed app-session and device credentials. These records let us grant, regenerate, or revoke app access. Invitation names and notes are not needed to search on the website.
Requests, reports, and support
If you request a course, we send the course name, city, and any website or notes you provide to TeeTyme’s owner through Pushover. Reports of incorrect information send the course name, course ID, and your description through the same service. The support form sends your name, email address, subject, message, and app and bundle versions through Pushover. Pushover processes the message to deliver it, and the owner uses it to review your suggestion or correction. Avoid including passwords or other sensitive information in messages. The server temporarily keeps hashed request identifiers to limit repeated submissions; it does not save the submitted message in its database.
Your controls
You can remove saved searches, pause or delete alerts in Watching, and change notification and location permissions in your phone’s settings. Turning off permission prevents notification delivery but does not delete server records. Deleting an alert removes its schedule and matching occurrence records from the server. Notifications already in your inbox remain available with their saved booking links. You can mark individual notifications or all current notifications as read. Clearing browser cookies removes website search and cart pricing preferences; clearing browser storage removes saved searches. Reinstalling the app may prevent access to alerts associated with an earlier device credential. You can use the contact link below to request deletion of server records or messages you submitted.
Retention
Expired, paused, and completed alert records are eligible for automatic cleanup after 90 days without an update. Notification inbox entries are retained for up to 90 days, whether read or unread. Occurrence records are eligible for cleanup after 90 days and notification delivery records after one day. Device records without alerts are eligible for cleanup after 90 days without an update. Active weekday alerts set to never expire remain until you pause or delete them. Revoking an invitation blocks access but does not delete its administrator record. Course request, report, and support messages may remain on the owner’s devices until deleted or removed by Pushover’s configured message limit. TeeTyme does not set a message expiry. Pushover deletes messages from its servers after verified delivery, or after 21 days if delivery is not verified. Infrastructure backups may retain earlier records until those backups expire.
Services and security
Course providers process availability requests, and OpenGolf and GolfCourseAPI supply course information. Imported public course information is refreshed on the server and saved in our database; administrator corrections take precedence. Flagsmith supplies feature configuration and app copy. Our update service delivers app updates. Requests to these services and our hosting infrastructure may include connection information such as an IP address. TeeTyme does not include advertising or analytics tracking and does not sell your personal information. We use HTTPS on the public service and device credentials to limit access to alerts. Embedded maps load from OpenStreetMap, which receives connection information, including your IP address. Open map launches your device’s map app or Google Maps on the web with the course’s location. Those services and booking websites apply their own privacy policies.
Operational logs
When private operational logging is enabled, we record page and API route templates, response status and timing, random request identifiers, approved GraphQL operation names and outcomes, broad referral categories and approved source labels, logging delivery counters, background-job outcomes, server versions, and client-reported platform and format-validated app, web, or update versions. These logs help diagnose reliability issues. They do not include form contents, precise location, authentication credentials, IP addresses, raw referring URLs, query documents or variables, or device identifiers. Logs are stored in our private logging system and currently remain until manually deleted. We do not collect client screen-view or interaction events.
Questions and data requests
TeeTyme is operated by Tayden Flitcroft. Use the contact option on the creator’s website for privacy questions or data requests. Do not send passwords or device credentials. We may ask for information to identify the relevant device records.
Contact Tayden FlitcroftPolicy updates
We update this page when our features or data practices change. The date above shows the latest revision.