Privacy

Birdie Book is a golf score tracker. This page explains, in plain language, what we collect and why. We keep it minimal on purpose.

What we collect

• Your account: the name and email you sign up with.
• Your golf data: the rounds, scores, courses, players, handicap estimate, and stats you enter.
• Shared event and league operations: roster and group assignments, RSVP and arrival state, contest and league results, course or league roles, and an audit history of authorized changes.
• Organizer financial-status records: organizer-entered dues, prizes, payer names, covered seats, and payment-status entries for money collected elsewhere. Birdie Book does not collect card or bank credentials and does not process or move this money.
• Optional event messaging: a mobile number, event-specific consent evidence, message and delivery status, and the operational message body when an organizer uses configured transactional SMS.
• Basic technical and security data: standard server logs, bounded product-usage events, and privacy-filtered error details needed to operate, secure, and repair the service.
• Founder support records: when the restricted founder-support console is used to troubleshoot an account, round, scorecard, or event, we record who opened the support view and which account or record was opened. The audit does not copy the scorecard, note, or event configuration.
• Course-business contacts: limited organization, work-contact, opportunity, follow-up, and interaction notes used for direct course outreach and customer support. This is not a bulk-marketing list and is not sourced from event text-message consent.

How we use it

To run the app: save your rounds, calculate your Birdie Book handicap estimate, show your stats, and let you share rounds with players you add. We also use the applicable event, league, course, consent, and audit records to let authorized organizers operate the workflows described above. We do not sell your data, and we do not show third-party ads.

Where it lives

Your data is stored in a managed Postgres database (Supabase) and the app is hosted on Vercel. Access is protected by authentication and row-level database rules. Players in the same round and authorized event or course organizers can access the shared-round information needed to run that round. Accepted friends can see your career scores and analytics only when you explicitly enable that sharing in Settings. Public event boards intentionally show event names, player names, standings, and event results to anyone with the public link.

A tightly restricted Founder Support role may inspect a person's profile, regular rounds, live scorecards, events, and non-sensitive event configuration to answer support questions even when a friendship request is pending or score sharing with friends is off. This does not sign the founder in as that person, change their friendship or privacy settings, or permit score, round, event, or profile edits. Every account, round, and event support view is recorded in the append-only founder audit, and the view is unavailable if that audit cannot be written. Passwords, tokens, full phone data, message bodies, consent evidence, provider identifiers, and payment details are excluded from these support views.

When the corresponding feature is configured, Resend delivers account and invite email, Twilio delivers event-scoped text messages, and Sentry may receive privacy-filtered client or server error reports. These providers receive only the information needed for that function. Transactional SMS is optional and is covered in more detail below; error reporting is configured to exclude request bodies, query strings, headers, cookies, SQL, user identity, and application breadcrumbs.

How long we keep it

Our current operating policy uses different retention targets for different records. Readable event phone numbers and rendered text-message bodies are scheduled to be removed 90 days after the event; consent hashes and message metadata remain. To prevent an authenticated inbound STOP or START from being applied twice or out of order, we permanently retain its opaque provider message identifier, action, time, and a one-way phone hash; that receipt contains no raw phone number or message body. Public-board usage events use a 90-day window, while authenticated active-day and named-feature usage events use a 400-day window. Expired password-reset, email-verification, and retry-receipt records are scheduled for short cleanup after expiration.

Inactive accounts are scheduled for anonymization after 18 months without observed activity. Personal round and score history has a five-year archive target, and audit history may be kept for seven years so shared score, organizer, founder-support, security, and financial-status activity remains accountable. Course-business CRM records have a target of the end of the relationship plus 24 months, or earlier on a verified request; interaction history follows its organization's window. Account-deletion requests may remove or anonymize personal identifiers sooner, while shared and audited records can retain the limits described under Your choices.

During the founding-course pilot, the retention runner is a reviewed, manual operation rather than an automatic schedule, so a scheduled cleanup may happen later than its target. We do not describe a purge as complete until its operator evidence has been reviewed.

Aggregate website measurement

Birdie Book records aggregate page displays to understand which parts of the product are useful. Each display contains a fixed page category, time, broad arrival-source and screen-width categories, and whether an account was signed in. Shared course detail views can include that course's identifier. These records do not contain your account identifier, IP address, a persistent visitor identifier, raw URL, search text, invitation token, or referral text. We do not join them to an individual account. They count displays, including repeat displays, rather than identifying distinct people.

We respect Do Not Track and Global Privacy Control for this browser measurement. Admin and demo activity is excluded. A browser-local exclusion preference can also prevent collection; it is a preference, not a tracking identifier. Page-display records have a 180-day retention target, enforced by a bounded, reviewed manual cleanup during the pilot. Visits before activation or blocked collection are not reconstructed.

Earlier Vercel Web Analytics

Earlier versions of Birdie Book used Vercel Web Analytics for aggregate, cookie-less page views. The current application uses the native measurement described above and does not automatically send new Vercel analytics events. Historical Vercel reporting remains separate from individual Birdie Book accounts.

Optional AI phrasing

Coach's Corner findings are calculated by Birdie Book. If you deliberately choose Get the coach's take, Birdie Book sends a prompt-safe version of those deterministic findings and their structured numeric evidence to Google's Gemini API only to phrase the note. The request excludes your name, email, raw scorecard, internal source identifiers, and user-authored course and tee labels. The returned note is not saved in Birdie Book's database; your browser may cache it locally. You can use all deterministic Coach's Corner findings without requesting this optional AI phrasing.

Text messages (SMS)

If you give your mobile number to an event organizer and the organizer records your consent for a specific event, Birdie Book may send you text messages about that event. These are operational messages only — participation confirmation, schedule or assignment reminders, an event-day check-in link, organizer updates, and final results. We never send marketing or promotional texts.

• We do not share or sell your mobile number. Mobile numbers and consent are never shared with third parties or affiliates for their own marketing purposes. They are shared only with the messaging provider that delivers the message on our behalf.
• Message frequency varies and depends on the events you join. Expect roughly 1–5 messages per event.
• Message and data rates may apply.
• Reply STOP at any time to stop all messages, or HELP for help. STOP requests take effect immediately. Text START to lift the global messaging block. START does not restore consent for any event; an organizer must record fresh consent for that specific event before event texts resume.
• Consent is limited to that event and is never a condition of participating in it or using Birdie Book.

Your choices

• You can generally edit or delete personal rounds from within the app. Shared completed scorecards and event, league, consent, audit, or organizer financial-status history may have correction, role, and retention limits because other participants or organizers rely on the same record.
• You can enable or disable career score and analytics sharing with accepted friends in Settings.
• You can request deletion of your account and associated data by emailing us.

This is a plain-language summary for an early-stage app. Questions or account-deletion requests can be sent to hello@birdiebook.pro.