TavlaSkor is provided by Furkan Kaynar. Contact: devappgea@gmail.com.
Version scope
The telemetry switches and advertising consent controls below describe the current TavlaSkor release. Store rollout is gradual; this page does not confirm that your installed app has updated. Earlier versions collected on different terms, including the entered names and venues described below, and may not include the updated ad consent flow. Updating does not erase information already received by providers.
Game records
The app does not require an account. Player names, your display name, scores, match history, excuses and saved venues are stored on your device. These values are not sent to Firebase Analytics or Crashlytics. Device backups may include local app data under your Apple or Google backup settings.
Location
Location permission is optional and lets you tag matches with a venue. The app uses your device location and the operating system's geocoding service to find place names. Geocoding may send coordinates to Apple, Google or your device's location provider. Saved venues and coordinates remain in local game records. You can revoke location access in device settings or enter a venue yourself.
Advertising and privacy choices
Google AdMob supplies ads. Before ads start, the app refreshes privacy choices through Google's User Messaging Platform and shows a consent form when required. Ads stay disabled if that process fails. Where available, use Privacy choices on the main menu to review or change your selections. Device settings also control advertising identifiers and tracking permissions. AdMob and the consent service may process IP addresses, approximate location, device identifiers, device information, ad interactions and privacy selections. Ad personalization depends on your choices and the provider's settings. Google's privacy policy: https://policies.google.com/privacy
Usage analytics and crash reports
Both are optional and controlled separately. Open Privacy choices on the main menu for two switches, Usage analytics and Crash reports. Where consent is required by law (EEA, UK, Switzerland) both start off, and nothing is collected until you turn one on. Elsewhere both start on and either can be turned off. Advertising consent never enables either one, and neither does App Tracking Transparency on iOS. Your choice is remembered across launches.
With Usage analytics on, Firebase Analytics receives screen and session events, match and dice actions, app version, a random app-instance identifier and technical device information. Every event name and parameter is a fixed value chosen by us. Player names, your display name, saved venues, excuses and card text are never sent as an event name or a parameter, and the purchase identifier described below is never sent to Firebase.
With Crash reports on, Firebase Crashlytics receives a stack trace, device model, operating-system version, app version and a random installation identifier when the app crashes.
Turning Usage analytics off stops collection and resets the analytics identifiers held on your device. Turning Crash reports off stops collection and deletes crash reports that have not yet been sent. Records a provider already received are not deleted by either switch. Firebase privacy information: https://firebase.google.com/support/privacy
Purchases
RevenueCat manages optional tips and document purchases. It receives a generated purchase identifier and purchase history. On iOS, the identifier may sync through iCloud to restore supporter status. The app does not send entered player names, venues or payment card details to RevenueCat. Apple or Google processes payments. RevenueCat privacy policy: https://www.revenuecat.com/privacy Apple privacy policy: https://www.apple.com/legal/privacy/ Google privacy policy: https://policies.google.com/privacy
Sharing and removal
Sharing a card sends its visible contents to the app or recipient you choose. Check the names, scores and venues before sharing. You can delete player records and rounds inside the app. Uninstalling removes local app data subject to device backup behavior. Purchase records may remain with Apple, Google and RevenueCat.
Earlier versions and requests
Some analytics events in older versions included entered player names and saved venues. That no longer happens: names, venues and card text never reach an event. Records already received by those services are not erased by an update or by turning a switch off. Contact devappgea@gmail.com for access, correction or deletion requests. We will review the data we can locate and any records that must be retained. Third-party providers may process data outside your country under their published policies. Firebase privacy information: https://firebase.google.com/support/privacy
Children and security
This app is not directed at children under 13. Contact us if you believe a child provided personal information. We use reasonable safeguards, but cannot promise absolute security. A privacy notice describes processing; using the app does not replace consent where consent is required.
Updates
We will publish material privacy changes here. Contact devappgea@gmail.com with questions about this policy or your information.