Effective date: October 11, 2026

Oche — Darts Scorer is published by 7afidi. This policy explains how information is handled when you use the Android app. For privacy questions or requests, contact [email protected].

1. Your games and players

Oche works without creating an account. Player names, avatars, teams, match scores, statistics, tournament information and preferences are stored in the app's private storage on your device. We do not operate a server that receives your player profiles or match history.

Oche keeps up to five rolling local backups. Android may also back up or transfer the app's database according to your device and Google backup settings. Those backups are managed by your backup provider.

When you choose to export a backup, export scores or share a result, the information you select is passed to the destination or app you choose. Exported files and shared results can contain player names and scores. Their handling then depends on that destination. Importing a backup reads the file you explicitly select.

If you enable the voice caller, player names and score announcements are passed to your selected Android text-to-speech engine. Some engines or voices may use a network service. Their processing depends on your selected provider and device settings; Oche does not record microphone audio.

2. Optional usage analytics

You can choose to share usage analytics through Google Analytics for Firebase. Analytics is off until you enable it in Oche. You can change this choice in Settings → Privacy & about → Usage analytics. Declining does not prevent you from playing or buying Pro.

When enabled, analytics helps us understand navigation, popular game and practice modes, game starts and completions, use of scoring controls and settings, the Pro purchase journey, and advertising delivery. Our custom events contain categories and counts, such as game mode, number of players, input method, screen, and purchase or ad delivery status. We do not include player names, complete score histories, backup contents, file paths, email addresses, purchase tokens or order IDs in these custom events, and we do not set an account-based analytics user ID.

The Firebase SDK also processes app-instance identifiers, app and device information, operating system, language, session and engagement information, and general location derived by Google's services from network information. These identifiers are pseudonymous, not a promise of complete anonymity. Oche disables Firebase's collection of the advertising ID and does not enable use of Firebase analytics for ad personalization. AdMob has separate data practices described below.

Turning analytics off stops future collection by this integration and resets the analytics data and identifier stored on the device. It does not automatically erase information previously received by Google.

3. Crash reports

Crash reporting helps us find and fix failures in Oche. It is on by default for all users, based on our legitimate interest in keeping the app stable and repairing errors. You can turn it off at any time in Settings → Privacy & about → Crash reports; playing and purchasing Pro remain available either way. If you declined crash reports in an earlier version of Oche, that refusal remains in force.

Google Firebase Crashlytics receives diagnostic information when reporting is enabled, including stack traces, app version, operating system and device information, crash/session timestamps, and installation identifiers. These identifiers are pseudonymous. We add limited technical context, such as the current screen, theme and Pro status. We do not deliberately add player names, score histories or backup contents to crash logs. If you separately enable usage analytics, Crashlytics may include analytics event breadcrumbs.

We use crash diagnostics to maintain app stability and repair errors, not to target advertisements or sell crash-report data. Google processes reports under the Firebase Crashlytics terms and data-processing arrangements. Crash information may be stored locally even while submission is disabled.

Turning crash reporting off stops future submissions and requests deletion of reports still waiting on the device. Firebase states that disabling reporting takes full effect on the next app run. Previously submitted reports follow Google's retention and deletion processes. Earlier recorded refusals remain in force after an app update.

4. Advertising and consent

The free app uses Google AdMob to display advertisements. AdMob and its advertising partners may process IP addresses and approximate location, advertising and other device or app identifiers, device information, ad interactions and diagnostic information to deliver and measure ads, prevent fraud and maintain their services.

Where required, Google's User Messaging Platform presents advertising privacy choices before ads can be requested. The Ad privacy choices option appears in Settings → Privacy & about when Google requires it to be available. You can also manage or delete your advertising ID through Android's advertising privacy settings. Some ads may still be shown without personalization, depending on your choices, region and Google's requirements.