Privacy Policy

1. Information we collect

Account and authentication information

RivalLinx uses Firebase Authentication. Depending on how you use the app, we may process:

• a temporary anonymous account identifier when you first use the app;
• your email address and account display name;
• authentication provider information when you use a supported sign-in provider;
• a Firebase user identifier and authentication/session information; and
• password-reset and account-security information handled by Firebase Authentication.

When a temporary account is upgraded to a permanent account, RivalLinx is designed to preserve the same underlying account identity so authorized Group access and history remain associated with that account.

Golf, Group, and competition information

When you create, join, organize, score, or follow golf in RivalLinx, we may process information such as:

• Group names, membership, roles, invitations, and Member-to-Player links;
• Player display names, Handicap Index values, tee assignments, and course/tee information;
• Competition, Round, Game, Match, team, Playing Group, and scorer-assignment configuration;
• hole scores, score corrections, Game inputs, derived results, standings, and Competition points;
• side-game, wager, or settlement configuration and calculated amounts; and
• timestamps and limited audit/provenance information needed to explain who created, scored, corrected, or managed shared golf activity.

A Player can exist without a RivalLinx account. Sporting identity and account identity are separate, and RivalLinx does not treat a matching name or handicap as proof that a Player is associated with a particular account.

Device, local, and operational information

RivalLinx uses Firestore’s local persistence so an already-loaded Round can continue to support score entry during temporary connectivity loss. Scores or other authorized changes may remain cached or queued locally until they synchronize. The app also stores a small local preference indicating whether a user explicitly signed out.

Our service providers may process standard operational information such as IP address, request metadata, device/browser information, timestamps, authentication events, and service logs as needed to deliver, secure, troubleshoot, and operate their services.

Support and communications

If you contact us, we may retain your email address, message, and information you choose to provide so we can respond, troubleshoot, and maintain a support history.

Website information

rivallinx.com is delivered through Cloudflare. Cloudflare may process standard network and security information, such as IP address and HTTP request metadata, to deliver and protect the website. The current RivalLinx website does not use advertising or analytics scripts.

2. How we use information

We use information described above to:

• create and authenticate accounts;
• provide Groups, Competitions, Rounds, Games, scoring, results, standings, and related features;
• support local-first scoring and later synchronization after connectivity returns;
• enforce membership, role, scorer-authority, privacy, and security controls;
• calculate and explain sporting results and organizer-configured settlement information;
• respond to support requests and beta feedback;
• protect the service, investigate errors or abuse, and maintain necessary integrity records; and
• comply with applicable legal obligations and enforce our agreements.

RivalLinx does not sell personal information and does not use personal information for third-party targeted advertising.

3. How information is shared

Other authorized RivalLinx users

RivalLinx is a shared golf product. Information such as Member and Player names, roles, competition configuration, scores, results, standings, and related golf activity is made available to other users who are authorized to access the relevant Group, Competition, Round, or related experience.

Service providers

We use service providers to operate RivalLinx, including:

• Google Firebase / Google Cloud for authentication, Firestore data storage and synchronization, Cloud Functions, and related backend infrastructure;
• Google Sign-In when that sign-in method is used;
• Apple for TestFlight beta distribution and, when made available, Apple sign-in or App Store distribution; and
• Cloudflare to deliver and protect rivallinx.com.

These providers process information under their own service terms and privacy commitments. We expect providers handling RivalLinx data to protect it appropriately for the services they perform.

Legal, safety, and business reasons

We may disclose information when reasonably necessary to comply with law or valid legal process, protect users or the service, investigate fraud or security issues, or as part of a merger, financing, acquisition, reorganization, or sale of all or part of the business, subject to appropriate protections.

4. Payments, wagers, and settlement information

RivalLinx may let organizers configure golf side games, wager amounts, buy-ins, or settlement calculations. RivalLinx does not currently process payments, hold funds, transfer money, or collect payment-card or bank-account information through the app. These values are used for golf competition calculation and recordkeeping.

5. Data retention

We do not use one fixed retention period for every type of information. We retain information for as long as reasonably needed for the purpose for which it was collected, to provide the service, protect users and the integrity of shared golf history, meet legal or security needs, and resolve disputes.

• Account/profile and active-access information is generally retained while the account is active and as needed to operate the service.
• Invitations, sessions, tokens, and similar access records are revoked or deleted when no longer needed, subject to security and operational requirements.
• Shared golf history may remain after account deletion when removing it would alter the legitimate history of other participants. In that case, personal account links may be detached or de-identified while the sporting record remains.
• Limited integrity, security, privacy-control, or audit records may be retained in minimized form when necessary to prevent erased data from being recreated, preserve shared-history integrity, or meet legal/security obligations.
• Local cached data may remain on a device until the operating system or user clears the app’s local data, but an erased or restricted account is not permitted to recreate deleted server-side identity or access links.

6. Your choices and account deletion

You may contact us to request access, correction, or deletion of personal information associated with your RivalLinx account. To request account deletion or another privacy action, email support@rivallinx.com from the email address associated with your account when possible and include “Privacy Request” in the subject line. We may need to verify your identity before completing a request.

When an account-erasure request is completed, RivalLinx is designed to remove or revoke account access and direct profile/account linkage and to delete the Firebase Authentication identity where applicable. Shared sporting history may be retained with account links detached or de-identified so that other participants’ legitimate golf history is not corrupted.

Some information may be retained when required for security, integrity, dispute resolution, legal compliance, or other legitimate obligations. If information cannot be deleted for one of those reasons, we will limit it to what is reasonably necessary for that purpose.

7. Beta testing

If you participate in a beta program, Apple TestFlight or Firebase App Distribution may process tester contact information, installation status, device/app information, crash or diagnostic information, and feedback in accordance with the provider’s terms and privacy practices. RivalLinx may receive information you choose to submit through those beta-testing channels.

8. Security

We use technical and organizational safeguards designed to protect RivalLinx information, including authenticated access, role- and scope-based authorization, server-enforced privacy controls, and restricted administrative/deployment boundaries. No method of storage or transmission is completely secure, so we cannot guarantee absolute security.

9. U.S. operation and international processing

RivalLinx, LLC is a Michigan company and currently operates RivalLinx as a U.S.-first service. Information may be processed in the United States and other locations where our service providers operate, subject to their service terms and applicable law.

10. Changes to this policy

We may update this Privacy Policy as RivalLinx changes. When we make material changes, we will update the effective date and publish the revised policy at this URL. If a change requires additional notice or consent under applicable law, we will provide it as appropriate.

11. Contact us

RivalLinx, LLC
Auburn Hills, Michigan, United States
Email: support@rivallinx.com