Privacy Policy
Last updated: April 24, 2026
1. Overview
Always Tee'd is a self-hosted application that helps a golf club member retrieve tee-time availability and upcoming member reservation rows from the club website and optionally submit booking or registration actions on the member's behalf.
This Privacy Policy explains what information the application stores, how it is used, and how it is protected.
2. Information We Store
The Service stores information needed to operate the application, including:
- Account email used for this application's sign-in flow.
- Club member number or username.
- Club website password, stored in encrypted form.
- Player names, groups, and booking preferences.
- Scheduled bookings, booking attempts, booking outcomes, and tee-time history.
- Cached member reservation rows from the club website, including reservation type, title, inferred location, date, time or duration, status, member or family reservation section label, and sync timestamp.
- Session records, audit logs, and limited operational diagnostics.
- Cached tee-time, club calendar/event, and weather data used by the web interface.
3. How Information Is Used
The Service uses stored information to:
- Authenticate you to this application.
- Log in to the club website using the credentials you provided.
- Scrape tee-time availability, calendar/event data, and upcoming reservation rows displayed to your club account.
- Submit booking, cancellation, change, add-player, and event-registration actions that you request or schedule.
- Show tee-time, booking, reservation, event, and weather information in the web interface.
- Maintain security, troubleshoot failures, and operate the application.
The Service is not used for advertising and is not intended to profile users for marketing purposes.
4. Third-Party Interactions
When you use the Service, the application communicates with third-party services, including:
- The club website, to authenticate, retrieve tee-time, event, and reservation data, and submit requested booking or registration actions.
- AWS Cognito, to manage sign-in for this application.
- Open-Meteo, to retrieve weather data shown in the interface.
The Service is not affiliated with the golf club or the operator of the club website.
5. Credential Handling
Club credentials are stored only to support the automation features of the application. Sensitive credentials are encrypted at rest before being written to the database.
No security measure is perfect. You should assume that storing credentials in any system carries some risk and use the Service only if you accept that risk.
6. Data Sharing
The Service does not sell personal information and does not share your credentials with advertisers.
Information is disclosed only as needed to operate the application, such as sending authentication requests to AWS Cognito, fetching weather data, or logging into the club website on your behalf.
7. Data Retention
Data is retained while your account is active and for a reasonable period afterward for operational history, troubleshooting, and audit purposes, unless deleted sooner by the system administrator.
Encrypted credentials may remain stored until you update them, remove them, or your account is deleted.
8. Your Choices
Subject to how this deployment is administered, you may be able to:
- Update or replace stored club credentials.
- Edit player and booking preference data.
- Delete scheduled bookings.
- Refresh or replace cached tee-time, event, and member reservation data through normal application syncs.
- Request deletion of your account and related stored data.
Deleting your account or credentials will stop future automated login and booking activity.
9. Security
The application uses measures intended to reduce risk, including encrypted credential storage, authenticated sessions, and application logging. These measures reduce risk but do not guarantee absolute security.
10. Changes to This Policy
We may revise this Privacy Policy from time to time. The revised version becomes effective when posted with a new "Last updated" date.
11. Contact
Questions about this Privacy Policy should be directed to the system administrator responsible for this deployment.