Privacy Policy

Depending on how you use BirdiePay, we may collect:

• Customer name, email address, and phone number provided when booking a tee time
• Tee-time and booking details (course, date, time, player count, transport preference, price, booking source)
• Check-in status and related timestamps, and payment-status information recorded for the booking
• Operator-entered notes and roster details associated with a booking
• IP address and login-attempt information used to protect operator and admin sign-in
• Course and operator account information needed to run the product
• Optional CRM golfer profile fields (such as display name, email, and phone) when a course uses golfer records

• Process and manage tee-time reservations
• Operate course tools (tee sheet, check-in, carts, CRM views, and related workflows)
• Provide customer and course support
• Help prevent fraud, abuse, and unauthorized access
• Maintain, troubleshoot, and improve BirdiePay

BirdiePay uses third-party infrastructure to run the product, including:

• Supabase — database, authentication, and related backend services
• Vercel (or the then-current application host) — application hosting and delivery
• Open-Meteo and the National Weather Service — course weather for operations dashboards. BirdiePay does not intentionally send golfer personal information to these weather providers.
• Stripe — planned payment provider. Card processing through Stripe is not yet implemented in the live product as of this Privacy Policy.

Retention periods for bookings, golfer profiles, notes, security logs, and related records are being formalized with course partners. This Privacy Policy does not promise specific automatic deletion timelines that are not yet implemented in the product.

Failed login rate-limit records may be purged after they are no longer needed for active lockouts; see operational documentation for the current cleanup approach.

You may request access to, correction of, or deletion of personal information we hold about you, subject to:

• Verification of your identity
• The golf course’s operational needs and any lawful retention requirements
• Records that must be retained for fraud prevention, accounting, disputes, or security

Contact us at privacy@birdiepay.golf. This Privacy Policy does not state statutory deadlines.

BirdiePay uses reasonable administrative, technical, and organizational safeguards appropriate to a booking and operations product (for example, authenticated operator access, row-level access controls in the database, and login rate limiting). No method of transmission or storage is completely secure, and we do not claim absolute security.

BirdiePay is not directed to children under 13, and we do not knowingly collect personal information from children under 13 through the public booking flow.

We may update this Privacy Policy from time to time. The “Last updated” date at the top of this page will change when this policy is revised.

Privacy questions and requests: privacy@birdiepay.golf

Related: Terms