Privacy Policy

1. Account and social sign-in information

If you sign in with Google or Apple, RADIA receives a provider account identifier and the basic account information the provider supplies, such as your email address, name and profile picture. Apple may supply a private relay email instead of your personal address. Availability of a name or picture depends on the provider and your choices.

We use this information to authenticate you, maintain your RADIA account, display account/profile information and determine access to your golf and tournament records. Supabase processes and stores authentication identifiers, account metadata and session information for RADIA. Your device/browser stores session credentials needed to keep you signed in.

Google sign-in requests basic identity information, not access to your Gmail messages, Google Drive files, contacts or calendar. RADIA does not use Google sign-in data for advertising or AI model training. We share it with our authentication service provider as needed to operate sign-in; it is not sent to the Ball Search image-analysis service.

Email/password sign-in also processes the email address and authentication credentials you provide. Use the same sign-in method as your existing RADIA account; matching email addresses alone do not guarantee two sign-in methods identify the same account.

2. Profile, golf and shared event information

RADIA processes information you provide or generate while using its features: profile details, username, home course, handicap details, rounds, scores, club distances, course choices, saved marks, settings and sync/recovery records.

Social and tournament features process memberships, invitations, identity claims, pairings, assignments, scores and change histories. Information you share can be visible to authorized friends, group members or event participants according to the feature's access rules. Joining an event or claiming a player identity does not automatically grant scoring authority.

3. Location and camera

When relevant app features are active and you grant permission, device location supports course lookup, distances and maps. Saved shots or user-marked course positions may contain coordinates. This is different from keeping a continuous server-side movement history; RADIA does not maintain such a history.

Ball Search's current tap-to-check interaction captures a photo and sends a bounded image crop through RADIA's server to Anthropic for AI verification. The RADIA verification function does not store or log the submitted image. Providers may retain request data under their own service policies; this is not a promise of zero provider retention. Image-free search/verification diagnostics, such as timings, outcomes and session references, may be processed in service logs.

A separate development-only, consent-controlled collector can retain local Ball Search examples for review. It is off by default and is not an automatic cloud upload. Ordinary cloud verification and optional local example collection are different flows. Automatic ball finding is not a generally available feature.

4. Website, support and service providers

If you join the mailing list, Mailchimp handles the information you enter on its signup page. Clicking the signup link alone does not subscribe you. This public site does not save a copy of your signup email in browser storage or install an advertising/analytics tracker.

We receive messages you send to support. Netlify hosts our web pages and may process ordinary delivery/security information such as IP addresses and request details. Supabase supports authentication, databases and server functions; Apple and Google support sign-in; Anthropic processes Ball Search verification crops; GolfCourseAPI and OpenStreetMap supply course data; Mailchimp supports mailing-list signup. Providers can process information in the United States and other countries where they operate.

We use information to provide and secure RADIA, sync golf records, support sharing you choose, troubleshoot issues, answer requests, prevent abuse and meet legal obligations. RADIA does not sell personal information or use account data, precise location or Ball Search imagery for third-party advertising.

5. Storage, deletion and your choices

Account-linked cloud records generally remain while the account exists. The app also keeps local round/recovery records, settings, clubs, course marks, queued sync work and session information. Some public course caches and harmless device preferences may remain after sign-out. Signing out is not account deletion.

In-app account deletion clears the deleting account's data on that device and requests deletion of its authentication account and associated personal cloud records. It does not erase shared tournament event records: display names, scores, official results and audit history can remain while account identity links are removed. Nor can deletion remotely erase exports or copies on other devices. To request deletion, sign in to the app, open Settings and choose Delete account. If you cannot access the app, email contactus@radia.golf; we will need to verify account ownership before acting. Emailing us does not automatically delete an account.

Control camera/location permissions in device settings, manage profile/sharing in the app and use the unsubscribe link for marketing emails. Contact us to request access, correction or deletion, or to ask about rights available in your region. We may need to verify account ownership. Do not send passwords, tokens or verification codes.

6. Children and policy changes

RADIA is not directed to children under 13. If you believe a child has provided personal information, contact us. Additional regional age requirements may apply. We will update this policy as data handling changes; the current published version and date will be available here.