The Weekend Classic
Privacy Policy
Effective date: March 22, 2026. This Privacy Policy explains how The Weekend Classic collects, uses, stores, and shares information when you use the app and its shared-event services.
Information You Provide
The app can store your display name, optional default handicap, event setup details, course details, player names, teams, groupings, scores, beers or bonus entries, leaderboard settings, and scorekeeper assignments. When you join a shared event, your name, handicap, scoring activity, and event-related data may be visible to other participants in that same event.
Photos and Scorecard Import
If you choose to import a scorecard from a photo, the selected image is sent to the app's scorecard import service and to OpenAI so course details can be extracted. This feature is optional. Imported course values remain editable before you save them.
How Information Is Used
The Weekend Classic uses this information to create and manage golf events, sync shared events across participants, assign scorekeepers, calculate leaderboards and live scorecards, remember your profile and saved events, and support optional scorecard photo import.
Where Data Is Stored
Profile data, saved courses, event snapshots, and related app state are stored locally on your device. If you use only local-only events, that event data stays on your device unless you choose scorecard photo import. Shared-event data is also stored on the app backend so invited or joined participants can retrieve the same event and see updated scores. Membership tokens used to rejoin backend-owned events are stored locally in Apple's Keychain.
Third-Party Services
The Weekend Classic currently relies on Vercel for hosting and API delivery, Neon-hosted PostgreSQL infrastructure for shared-event database storage, and OpenAI for optional scorecard photo extraction. Apple may also provide device-level services such as Photos access and Keychain storage when you use those features. When user data is processed by service providers for these features, those providers are expected to handle the data in a manner consistent with this policy and to provide the same or equal protection of user data.
Data Sharing
Shared-event information is shared with the participants in that event so scoring, leaderboard, and live scorecard features can work. The current app build does not include third-party advertising SDKs or cross-app tracking code.
Retention
Locally stored app data remains on your device until you remove it, delete the app, or clear that event data from the app. Backend-hosted shared-event data does not currently have an automatic expiration period. It remains on the backend until the event is deleted, the in-app profile deletion flow removes or disconnects the data where supported, or a verified manual privacy or deletion request is completed. Verified manual privacy, access, or deletion requests are typically handled within 30 days.
Your Choices
You can choose whether to create or join shared events, whether to enter an optional handicap, and whether to use scorecard photo import. If you do not want score data shared with other participants, do not use shared-event features. You can revoke Photos access for scorecard import in iOS Settings, delete your local profile and supported backend-linked profile data from My Profile in the app, delete the app to remove locally stored data, or contact support for a manual privacy, access, or deletion request.
Children's Privacy
The Weekend Classic is not directed to children under 13, and the app is not intended to knowingly collect personal information from children under 13.
Changes to This Policy
This Privacy Policy may be updated from time to time. Material updates will be reflected by posting the revised policy in the app or on this page.
Privacy Questions and Deletion Requests
For privacy questions, data access requests, or deletion requests related to backend-hosted shared-event data, email WeekendClassicSupport@gmail.com or use the support page below. Verified manual privacy, access, or deletion requests are typically handled within 30 days after enough information is provided to reasonably identify the relevant records.