Privacy Policy

Last Updated: October 12, 2026

Pickle Billers ("we," "our," or "us") is committed to protecting your privacy. This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use our mobile application and related services (collectively, the "App").

1. Information We Collect

1.1 Information You Provide

• Account Information: Email address, display name, sign-in provider and account or player identifiers used to authenticate you and associate your records with your account.
• Guest invitations: When you invite a guest after a game, you may provide their name, email address or phone number. We store the supplied invitation contact details in Firebase with the inviter account, guest player and match context to deliver the invitation and let the guest claim their result. Provide only contact details you are authorized to use, and let the recipient know you are inviting them. These contact details are not displayed as part of the shared match score. Authorized administrators and backend services can access the invitation record; ordinary users cannot directly browse the invitation-contact collection. Someone holding a valid invitation link can see the invitation's email address when validating the link; the phone number is not included in that preview.
• Match Data: Scores, opponents, dates, and locations of matches you log.
• Profile Information: Username, avatar selection, skill level, and visibility preferences.
• Camera and photos: Taking or choosing an avatar is optional. When you use this feature, we request camera or photo-library access and upload the selected profile image to Firebase Storage, associated with your account. We do not upload your entire photo library. Saving or sharing a match scorecard is a separate action you choose.
• Pro Analytics (Pro Subscribers Only): Shot-level statistics (e.g., third shot drop success rates) and heat map coordinates for winning shots, when you use Pro features.

1.2 Automatically Collected Information

• Device and installation information: Device type, operating system, app version, installation identifiers and notification tokens. Firebase authentication, messaging and app-integrity services also process information needed to sign you in, deliver notifications and prevent abuse.
• Google sign-in: If you choose Google sign-in, its SDK processes account and sign-in information and can derive coarse location from your IP address for authentication and fraud prevention. This functional use is separate from Analytics location collection.
• Usage and analytics: Firebase Analytics is enabled in release mobile builds and records app interactions, sessions and purchase events. Its SDK may collect app-instance and advertising identifiers and derive coarse location from IP addresses, depending on platform and configuration. Our own usage records, such as app opens, matches logged and invitations, are associated with your account identifier. These records are not all anonymous.
• Crash and performance reports: Builds configured for Sentry can send errors, stack traces, interaction context, device and app information, and sampled performance reports. Reports can include your account identifier. Sentry is disabled when the build has no Sentry configuration; Firebase Crashlytics is not the App's crash-reporting service. Error text can contain information about the action that failed, so do not put sensitive information in free-text fields.

1.3 Location and Maps

• Nearby courts: With your permission, the App uses your device location to center the court map. This permission is optional; centering the map does not directly save your GPS coordinates to your account. Map tile requests can reveal the viewed geographic area and your IP address to the map provider. Location-related SDK collection, including Analytics coarse location, is separate from this permission.
• Court check-ins: When you check in, we store the selected court, your account or player identifier, display name, time and visibility or audience choices. A check-in records a place you chose; it is not continuous GPS tracking. Check-ins can remain stored after they stop appearing as recent activity.
• Place search: Entered place-search text is sent to OpenStreetMap's Nominatim service. Map tiles are requested from OpenStreetMap. These services receive ordinary network information, including your IP address.

1.4 Optional Workout and Health Data

• Permission and selection: If you choose to link a workout, the App can request read access to workouts, heart rate and active calories in Apple Health (HealthKit) or Google Health Connect. You can decline permission and continue logging scores, or enter workout information manually.
• Off-device storage: When you select and link a workout, or submit manual workout information, we save the supplied fields to the match record in Firebase: duration, calories, average and peak heart rate, distance, source and source identifier, and start and end times, where available. This information leaves your device and is associated with the saved match and its participants.
• Purpose and control: We use linked workout information to display fitness details alongside your match history. Linking is optional. Turning off Health permissions stops further authorized reads but does not remove workout information you already linked. Information attached to a match may be visible to people who can access that match.

2. How We Use Your Information

We use your information to:

• Provide, maintain, and improve the App and its features
• Calculate and display your stats, evolution progress, and rankings
• Enable social features (friends, following, leaderboards) when you opt in
• Manage Pro and Organizer purchases, subscriptions and entitlements; Apple or Google processes native store payments
• Display workout and fitness information you choose to link to matches
• Send transactional messages, including guest invitations by email or SMS where delivery is available, welcome emails and Pro upgrade confirmations
• Respond to support requests and comply with legal obligations
• Analyze usage patterns to improve the user experience

3. Incognito Mode

Incognito and participation settings control selected public-profile, leaderboard and social displays. You can change these preferences in Settings. They do not delete your account or saved records, make all analytics anonymous, or guarantee that every match record is private. Matches can include other players and appear in shared scoring and history features. Previously shared copies are not recalled by changing a setting.

4. Data Sharing and Disclosure

We do not sell your personal information. We may share data with:

• Service Providers: Google Firebase provides authentication, database and image storage, messaging, analytics, app integrity, remote configuration and hosting. RevenueCat processes purchase history, subscription status and your account identifier to manage entitlements and purchase analytics. Sentry processes configured crash and performance reporting. Resend processes transactional email. Configured Brevo invitation delivery receives the chosen email address or phone number, invitation link and match-result context to send transactional email or SMS. Creating an invitation stores the supplied contact details even if delivery is unavailable or fails. These providers receive the data needed for the features you use; using an identifier instead of your name does not make the information anonymous.
• Other Users: Names, profiles, scores, match participants, standings and check-ins can be displayed through the relevant shared features and visibility controls. Workout details linked to a match follow access to that match. Do not assume that all saved match information is private.
• Map Services: OpenStreetMap tile and place-search services receive the requests described above. Opening an external map or link also sends requests to its operator.
• Legal Requirements: When required by law, court order, or to protect our rights and safety.

5. Data Retention

• Account and history: We retain account, match, linked workout and profile records to provide the App and history features. We have not implemented one automatic retention period for every category.
• Previously recorded information: A visibility change, expired check-in display window, revoked permission or expired subscription does not automatically erase earlier records.
• Invitation contacts: An invitation link expiring does not automatically delete its stored email address, phone number or associated invitation record. We have not established an automatic deletion period for these contacts; contact us with a privacy or deletion request.
• Deletion requests: Requests require ownership verification and review of shared records and service-provider data. Any information that needs to be retained for a legitimate security or legal reason, and any anonymization of shared records, must be explained as part of completing your request.

6. Your Rights

You may:

• Access your account data and profile
• Correct or update your information in Settings
• Request account and associated-data deletion using the contact below
• Opt out of marketing emails (unsubscribe links in emails)
• Enable Incognito Mode to limit public visibility

7. Children's Privacy

The App is not intended for users under 13. We do not knowingly collect personal information from children under 13. If you believe we have collected such data, please contact us and we will delete it promptly.

8. Security

We use industry-standard security measures (encryption, secure authentication) to protect your data. However, no method of transmission over the internet is 100% secure.

9. Changes to This Policy

We may update this Privacy Policy from time to time. We will notify you of material changes by posting the updated policy in the App and updating the "Last Updated" date.

10. Contact Us

For questions about this Privacy Policy or your data:

• App: Pickle Billers
• Jurisdiction: Henderson, Nevada, United States
• Contact: partners@paddlecompare.com, including privacy and deletion requests.