Privacy Policy

Effective Date: October 29, 2026

Welcome to Bogey Logger. This Privacy Policy explains how we collect, use, store, and protect your information when you use the Bogey Logger mobile application, the bogeylogger.com website, and Bogey Logger Tournaments. We aim to be straightforward about what these services do with your data.

The app works from a database on your device: your round history, scores, and course data are written there first, and scoring works without a connection. An account is required to use the app, and while you are signed in your finished rounds and saved courses are also copied to your own private cloud storage automatically, so you can restore them if you change or lose your phone. That copy is visible only to your account. Cloud services are otherwise used only for the specific features described below.

By using Bogey Logger, you agree to the practices described in this Privacy Policy. If you do not agree, please discontinue use of the application.

Information Stored on Your Device

The following data is written to local database storage on your device, and is what the app reads while you play:

Round history (scores, dates, courses played, format, results)
Course data (name, location, par, handicap ratings, yardage, tee information, and green reference points marked on a satellite map)
User profile preferences (name, handicap index, home course)
Friends list (locally cached after cloud lookup)
Skins scores and round summaries

Some of this is also copied to the cloud, as described in the next section — rounds and courses through automatic backup, scores and player names through a multiplayer round, course data through a community course contribution. Anything not covered there stays on the device.

If you delete the application, the local copy is removed from your device. Private cloud backups are removed by deleting your account. Shared course data and other retained records are described below (see Data Retention and Your Rights and Choices).

Information Stored in the Cloud

When you create an account and sign in, certain data is stored in Google Cloud Firestore to enable multiplayer and community features:

Account profile: display name, handicap index, a unique 6-character friend code, your email searchability preference, and your home-course sharing preference (your home course name is included only if you turn that sharing on).
Authentication credentials: managed entirely by Firebase Authentication (Google, Apple, or email/password). We never store or have access to your passwords.
Community course contributions: when you add a course while signed in, the course data and your display name are shared to the community database so others can find it. Green reference points you save on a shareable course are also shared, with account identifiers used for contribution and review. These points describe the course; they are not recordings of your GPS position.
Multiplayer round data: scores, player names, invite codes, and course info are stored temporarily to enable live score sync between devices.
Cloud backup: while you are signed in, each round you finish, and the course it was played on, is copied to your private cloud storage automatically, so you can restore it if you change or lose your phone. Backup runs as part of finishing a round rather than as a separate action you take. The backup is readable only by your account, is never shared with other users, and is removed when you delete your account.
Notifications: in-app round invitations and reminders are stored in the cloud and associated with your account.
Friends: friend relationships, friend codes, and requests are stored with the participating accounts to support the Friends feature. We do not read or import your phone's address book.
Push notification token: if you allow notifications, the app stores the push token your device is issued so invitations and round reminders can reach your phone. It identifies the app installation, not you personally, and is deleted when you sign out or delete your account.
Leaderboard statistics: only if you turn on “Appear on leaderboards” (off by default). Aggregate figures — rounds played, best scores, streaks, match record and similar — are stored on your account profile so friends can rank against you. Individual scorecards are never published, and turning the setting off clears them.
Subscription and scan-usage records: your trial dates, subscription status, and scorecard scan counters, used to apply account limits and protect API costs.
Trial-use record: we keep a separate, server-only record of trial dates and scan use. During a gradual rollout, accounts using repeat-trial checks have history keyed to protected hashes of verified email addresses and sign-in identities. These records preserve an earlier trial after account deletion. The identity history contains no raw email address or Firebase account ID; its hashes are pseudonymous identifiers, not anonymous data. A separate account-ID trial ledger is also used to enforce trial limits.
Community course reports: if you report a course or its green marks, we store the course identifier, your account identifier, the reason, any note provided, and the submission time. Reports are available to service operators, not to other app users.

This Website and the Launch List

This website (bogeylogger.com) is a static site. It uses no analytics, no advertising or tracking scripts, no third-party embeds, and no cookies.

The one exception is the email sign-up form. If you choose to enter your email address, that address is submitted to and stored by Netlify, Inc., the United States hosting provider that serves this site, using Netlify Forms.

We use it to tell you when Bogey Logger is released, and occasionally afterwards to share news about the app itself — a significant new feature, or an important change you would want to know about. We email rarely, and only ever about Bogey Logger. We do not sell your address, do not share it with anyone else for their own purposes, and do not add it to any other company's mailing list.

Every email we send includes an unsubscribe link, and unsubscribe requests are actioned promptly. You can also ask us to remove your address at any time by emailing birdie@bogeylogger.com — no account or explanation required. We keep your address until you unsubscribe or ask us to delete it, and no longer.

Providing your email is entirely optional. Every page of this site, including the guides, the calculator and these legal documents, is fully usable without submitting anything.

Information We Do NOT Collect

Apart from a launch-list email address you choose to give us (described directly above), Bogey Logger does not collect any of the following, in the app or on this website:

Your live GPS readings, movement path, and shot-measurement start and end coordinates are never sent to our cloud services.
Advertising identifiers, or any identifier used to track you across apps or websites
We do not add analytics or advertising tracking to record how you play or profile you. Map providers may process technical information to deliver satellite imagery, as described under Third-Party Services.
Health or fitness data
Payment-card numbers or bank-account details. Apple or Google handles subscription payments; we do receive subscription status and purchase history to provide Pro access. Skins is score record-keeping only.
Your phone's address book or browsing history. In-app friend relationships are stored separately to support the Friends feature.

Some technical identifiers are unavoidable in order for the app to function: your Firebase account identifier, a device push-notification token if you enable notifications, and a subscriber identifier held by our payment provider. These identify your installation to those services so the app can work. They are never used for advertising or cross-app tracking.

How We Use Your Information

We use your app information solely to provide and improve Bogey Logger: to manage your profile and friend code, synchronize multiplayer scores and invitations, deliver notifications, back up and restore your rounds, power the community course database and review reports, provide scorecard scanning when you choose to use it, manage subscription access and scan limits, prevent repeat trials, calculate course handicaps, and calculate GPS green distances and shot measurements on your device. Tournament information is used to run tournaments as described below. We do not use this information for advertising, marketing, profiling, or sale to third parties.

Location and GPS Distances

GPS distances, shot measuring, and map centering are optional. If you allow location access, Bogey Logger reads your location while the round's scoring or GPS page is visible and active, or briefly to center a course map. Green and shot distances are calculated on your phone. Live fixes and shot-measurement endpoints stay in temporary device memory and are not uploaded to Bogey Logger, other players, or cloud backup. A map centered on you sends requests for the surrounding area to the map provider, as described below. We do not record a movement history or use background location access. An unfinished measurement can remain in memory while you leave the screen, and is cleared when you turn GPS off, clear it, finish the round, change accounts, or close that scorecard session.

Green reference points are different from your GPS position. You choose those points by tapping satellite imagery. They describe the golf course and may be shared through the community course database, multiplayer course snapshots, and course backups. Community green-mark records include contributor and latest-editor account identifiers, edit times, and reviewers' account identifiers and confirmations. Other signed-in users can read these records. Community geometry may remain after an account is deleted, with that account's contributor and reviewer identifiers removed.

Temporary green marks for one round are saved with that round on your device and, in multiplayer, shared with the players in that round. They do not update the saved course or community marks, and are excluded from cloud backups.

Your scorecard GPS on/off choice and a manually remembered course view are stored on this device. The green editor starts with saved course marks or a remembered course view when available. Otherwise, it may briefly use location permission you already granted to center near you automatically; it does not ask for permission just to do this. If no usable position arrives within five seconds, the map stays at its United States starting view. "Use my location" also reads your phone's position briefly and then stops its location request. A phone-derived view is not remembered automatically. "Find this course" sends the course name and town you enter to the platform's geocoding service, not your current GPS position. Android requires foreground location permission for that search. These actions do not place green marks: you choose those course reference points by tapping the map.

Map yardages lets you choose a temporary target on the map and shows straight-line estimates from your current position to that target and from the target to the marked green middle. The target is not a green edit. Its coordinates stay in temporary device memory and clear when you leave that map, change accounts or holes, or stop GPS. Map-area requests still go to the map provider.

Round Hole Edits

Changes to a hole's par, stroke index, or yardage are saved with the round on your device. In a shared round, the host's hole edits are sent to the other players. Finished-round backups include these hole edits. At the end of the round you can keep them for just that round, update your saved course, or save a new course. These choices do not submit a community course correction. New courses saved from round edits and guests' copies of multiplayer courses are excluded from community sharing. Updating an existing saved course does not make it private; the usual community sharing rules still apply.

Third-Party Services

We rely on Firebase Authentication and Cloud Firestore (Google) for sign-in, cloud data, usage counters, and secure backend functions. Scorecard scanning, when used, sends the scorecard photo and course details you provide to our secure backend and to OpenAI's API so a structured course-data draft can be returned for your review. Push notifications are delivered through Expo's push service, which receives your device's push token and the text of the notification. Subscription access is managed through Apple, Google Play, and RevenueCat; RevenueCat is sent your account identifier along with your email address and display name so a subscription can be matched to your account and support requests can be answered. These services are governed by their own privacy policies and terms, including Google's Privacy Policy at https://policies.google.com/privacy.

Satellite maps use Apple Maps on iOS and Google Maps on Android. These services receive requests for the map area you view and may receive technical information such as your IP address and device or application information. The area may be centered on you automatically with existing location permission, through "Use my location", or from an active GPS reading in Map yardages, so the map provider can infer the area where you are. We do not enable the map's built-in user-location tracking layer or upload a route or shot-measurement history. Map providers may also process SDK identifiers, map interactions and crash diagnostics to maintain and improve their services. Map providers' own privacy policies apply.

Bogey Logger Tournaments stores and processes tournament data with Firebase Authentication, Cloud Firestore and Cloud Functions (Google), and the tournament website is hosted by Netlify.

Scorecard Scanning, Insights, and AI

Scorecard scanning uses cloud-based AI to help read printed scorecards and create an editable draft of course data, including tees, pars, yardages, ratings, slopes, and stroke indexes where visible. This feature is available during the Pro trial and paid Pro subscription, subject to usage limits. You must review, edit, and confirm scanned data before it is saved. AI output may be incomplete or wrong, and course rating/slope details should be verified when accuracy matters.

Scorecard photos used for scanning are uploaded only to process the scan request. Bogey Logger is designed not to use scorecard photos for advertising, user profiling, or automated eligibility decisions. Personal insights are generated from deterministic calculations based on your own scoring history.

Bogey Logger Tournaments

Bogey Logger Tournaments (live.bogeylogger.com) is a separate web tool that golf clubs and organizers use to run tournaments with a live leaderboard. Organizers sign in with email and password through the same Bogey Logger sign-in system as the app, so one account can serve both. Tournament data stays in its own database; players and group scorers need no app or account.

What is collected

Organizer accounts: the email address and password an organizer signs up with. Sign-in is handled by Firebase Authentication; we never see the password.
Tournament details the organizer enters: the event's name, date and course; each player's or team's name; Handicap Index or handicap and tee; team and group assignments; tee times.
Scores: hole-by-hole scores entered by a group's scorer or by the organizer's staff, and a record of every score change (the hole, the old and new score, whether a group scorer or staff made it, and when).
Group scorers do not create accounts. A scorer's phone remembers their group's scoring code in the browser's local storage so it does not have to be typed again; clearing the browser's site data removes it.
The tournament site uses no advertising or analytics cookies and does not track visitors.

Who can see it

The leaderboard is public to anyone with its link. It shows the tournament's name, date and course; each player's or team's name; scores hole by hole; positions; and, when the organizer uses handicaps, strokes received and net scores. Leaderboard links are long and random and are not listed or searchable, but anyone the link is shared with can view it.
Everything else — the player list with handicaps, the scoring codes and the change record — is visible only to the organizer who created the tournament.
Before a tournament goes live, the organizer must confirm that the players agreed to have their names and scores shown on the leaderboard — and, for any player under 18, that a parent or guardian agreed — and that they asked each player whether they are 18 or older.
A player marked as under 18 appears on the leaderboard by initials only (for example "J. S."). Their full name stays in the organizer's private player list.

How long it is kept

A tournament — its players, scores, change record and public leaderboard — is deleted automatically one year after the organizer marks it final, unless the organizer chooses to keep it for 2 or 5 years, or until they delete it. A tournament never marked final is deleted one year after its date. Organizers can delete a tournament at any time.
Organizer accounts are kept until the organizer deletes them.

Your choices

Players: to have your name or scores corrected or removed from a tournament, ask the organizer who ran it, or email birdie@bogeylogger.com and we will work with the organizer.
Organizers: you can edit or delete your tournaments at any time, and delete your account from the tournament site (Your account → Delete my account), which removes every tournament you created. If you sign in to the tournament site with your Bogey Logger app account, that sign-in is kept and can be deleted in the app (Me → Delete Account).

Junior golfers

Tournaments may include players under 18 only when a parent or guardian has agreed to the player taking part. The organizer confirms this before the tournament goes live.

Players under 18 must tell the organizer (or a parent or guardian must). The leaderboard then shows only the player's initials. A parent or guardian can ask the organizer, or us at birdie@bogeylogger.com, to remove a junior's scores at any time.

When We Share Your Data

We share data only in limited ways: community course contributions, green marks, their contribution and review records, and your contributor display name are visible to other signed-in users; multiplayer participants can see your display name, handicap index, scores, and the course and hole edits for that round; if you opt into leaderboards (off by default), other signed-in users can see the aggregate statistics described above alongside your display name; if you opt into email searchability (off by default), others can look you up by email, and your email address is stored on your shared account profile; and if you opt into home-course sharing (off by default), friends who add you can see your home course. Tournament leaderboards are public to anyone with their link, as described above. We do not sell, rent, or trade your personal information.

Data Retention

Local data: kept on your device until you delete it. You can enable auto-delete of old rounds (30 days, 90 days, 6 months, 1 year, or never). Deleting a local round, including through auto-delete, does not remove its cloud backup.
Account profile, cloud backup, leaderboard statistics, push token, and subscription records: retained as long as your account exists; deletable at any time (see Your Rights). Turning off leaderboards clears the published statistics immediately, and signing out clears the push token for that device.
Multiplayer round data: scheduled for automatic cloud deletion 5 days after the round is created. Your local scores remain on your device until you delete them or the account's local data is removed.
Community courses: course reference data, including green marks, may be retained while useful. If an account is deleted, its contributor attribution and validation and green-review identifiers are removed from retained community course records. Community courses are not automatically deleted at a set age.
Community course reports and the server-only trial-use record are retained after account deletion, without a fixed automatic expiry. We remove a report's reporter account identifier and replace its account-linked record ID; text you entered may still contain personal information, so contact us to request a review. Where identity-based trial history was recorded, protected hashes, original trial dates, and scan use remain to prevent repeat trials. We remove the separate account-ID trial ledger after authentication-account deletion succeeds; a cleanup failure can leave that ledger for follow-up removal. Contact us about retained records.
Tournament data: deleted automatically one year after the tournament is marked final unless the organizer chooses longer (see Bogey Logger Tournaments above).
Email sign-up addresses: kept until you unsubscribe or ask us to delete your address, then removed promptly (see "This Website and the Launch List" above).

Data Security

Cloud data is protected by Firebase Authentication and enforced Firestore security rules that restrict access based on identity (you can only read and modify data you are authorized to access). Passwords are never stored by the app. Scorecard scanning is processed through a backend service so API keys are not stored in the mobile app. No method of electronic storage or transmission is 100% secure, so we cannot guarantee absolute security.

Your Rights and Choices

Access & correction: view and update your profile in the Me tab at any time.
Deletion: delete your account and associated cloud data in the app (Me tab → Delete Account). This removes your authentication account, profile, lookup records, friend relationships, private backups, notifications, push token, leaderboard statistics, entitlement and scan-usage records under your account, subscription provider customer record, hosted multiplayer rounds, and your linked participation and score-change references in other temporary rounds. Copies saved by other players on their own devices are not erased remotely. Community course reference data may remain after your contributor attribution and validation and green-review identifiers are removed. Community course reports and trial-use records are retained as described under Data Retention. In version 1.1, after cloud deletion succeeds, the app signs out and removes only the deleted account's local database on this device before showing completion. If local cleanup cannot finish, the app shows a retry screen and keeps a pending cleanup marker so it can retry after a restart. Older app versions may leave local data until you clear app storage or uninstall. An email-requested deletion cannot erase data from a device remotely. You can also submit a request without the app through our account deletion page.
Email searchability: control whether others can find you by email (off by default; Me tab → Privacy).
Leaderboards and home-course sharing: both off by default, both switchable at any time (Me tab → Privacy). Turning leaderboards off removes your published statistics.
Notifications: you can decline or later revoke the notification permission in your device settings. The in-app inbox still works without it.
Location: GPS distances, shot measuring, and map centering are optional. You can decline location access, turn GPS off in the scorecard, or revoke permission in your device settings. Scoring and manual green marking by panning the map remain available without permission. Android's course-name search requires foreground location permission; you can still pan and zoom without it.
Community sharing: saving a manually entered or scanned course while signed in automatically shares eligible course data with the community. Saving green marks on a shareable course also queues them for sharing; there is no general community-sharing opt-out. Guests' multiplayer course copies and new courses saved from round edits are excluded. Cloud backup and multiplayer also use account-based cloud storage; deletion and its exceptions are described above.
Data portability: export any round as a text summary via the Share function.

Children's Privacy

The Bogey Logger app is not directed at individuals under 18. Bogey Logger Tournaments may show the scores of junior golfers entered by an organizer, with a parent's or guardian's agreement. Players under 18 appear by initials only (see Bogey Logger Tournaments above). We do not knowingly collect information directly from anyone under 18. If you believe a minor has provided us information directly, contact us at the email below and we will delete it promptly.

Camera and Photo Library Access

We request camera and photo access for scorecard scanning and for scanning a friend's QR code to send a friend request. Friend QR scans are processed on-device. Scorecard photos selected for scorecard scanning are uploaded only when you choose to use that feature. You can revoke these permissions anytime in your device settings.

Changes to This Policy

We may update this Privacy Policy to reflect changes in our practices, features, or applicable law. Material changes will update the Effective Date above. Continued use after changes constitutes acceptance.

Contact Us

Questions or requests about this Privacy Policy can be sent to birdie@bogeylogger.com. We will respond to privacy-related inquiries within 30 days.