Privacy Policy

Last updated

This policy explains what data the Final Inning Baseball app and website (final-inning-baseball.com) collect, how it is used, which service providers handle it, and what you can do about it. The game is developed and run by independent developer Leo Kuo, referred to below as "we".

The short version

  • The app doesn't require a login right now, and it doesn't ask for your name or email.
  • The app collects gameplay data and error reports, linked by a randomly generated install ID, to improve the game and fix problems.
  • We don't use the advertising identifier (IDFA), don't track you across other apps or websites, and don't sell data.

What the app collects today

  • Install ID: a random string generated the first time you open the app and stored on your device. We use it to connect gameplay data and error reports from the same install. It doesn't contain your name or email.
  • Gameplay data: app opens, sessions, and the mode of each game you start and finish. Once career mode opens, this also includes the talent, position, difficulty and growth rates chosen at creation, plus progress, ability values, difficulty, games played and play time for each stage. This is limited to numbers and preset options. It doesn't include the names you give your players or anything else you type.
  • Device and app information: for example device model, OS version, app version and language, plus the app instance ID generated by Firebase and the Identifier for Vendor (IDFV) provided by Apple.
  • General location: Firebase estimates your general location from connection information, such as your IP address. It doesn't use your device's location services.
  • Error reports: when the app hits an error, crashes, freezes or has a network request fail, it sends the error details, stack trace, device and system information, app version, install ID, and a log of what happened beforehand (such as screen changes, program output and the URLs of network requests). Error reports also include a hash calculated from the IDFV, device model and app identifier. If the install ID isn't set yet, they carry the identifier the error reporting tool generates instead (see stability data below). We don't deliberately put personal data in error reports.
  • Stability data: even without an error, the app sends the error reporting provider session status (such as start, end and whether it ended abnormally), the app version, and an identifier the error reporting tool generates and stores on your device (separate from your install ID) when the app launches and runs. This is used to measure how many sessions run without problems. When error reports and stability data are sent, the provider can see the IP address of your connection, but the app isn't set up to add your IP address to this data.
  • Announcements: the app fetches the latest announcements from Firebase Hosting, and that provider receives the connection data it needs, such as your IP address.
  • Surveys (optional): when you open a survey from the app, the form may be pre-filled with your install ID so we can compare your answers with gameplay data. Surveys are collected by Google Forms. If you'd rather not share this, you can skip submitting or clear that field yourself.

The install ID, gameplay data, device and app information, and general location are collected and processed by Google Analytics for Firebase. For details, see How Google uses information from sites or apps that use our services.

Your saves and custom players and teams stay on your device. They aren't uploaded to our servers at this time.

How we use this data

  • To understand how far players get, how long they play, where they stop, and whether difficulty and balance are working.
  • To find and fix errors and crashes.
  • To compare survey feedback with what actually happened in the game.

We don't use this data for advertising, and we don't combine it with third-party data to identify you.

What the website collects

  • Traffic statistics: we use Umami to understand how the site is used, including URL paths and query strings, referring URLs, page titles, screen size, language, browser, operating system, device type, general location, which outbound links were clicked and in which part of the page, and successful launch notification sign-ups (with page language and source tag). Umami doesn't use cookies. It calculates a regularly rotated visitor identifier from your IP address and browser information instead. According to Umami, IP addresses aren't stored as analytics fields but may appear in its operational and security logs.
  • Launch notifications: when you leave your email, we record the email, sign-up time, source tag and page language, and keep them in a Google Sheet and a list held by the developer. Notifications are sent through Gmail. The list is only used to send launch notifications and important news. The source tag comes from the tag in the URL you arrived on during this visit (for example, from scanning an event QR code). It's kept in your browser's sessionStorage so it still applies if you sign up on another page, cleared when you close the tab, and not sent anywhere except with your sign-up.
  • Bot protection: Cloudflare Turnstile starts when the launch notification form comes into or near view, or when you tap the email field, without waiting for you to submit. It receives your IP address, TLS fingerprint and browser information to detect bots, and Cloudflare also uses this data to improve its detection. We don't pass the email you enter to Turnstile.
  • Running the site: the site is hosted by Netlify, images and videos are served by Cloudflare, and the body font is served by Google Fonts. When you browse, these providers receive the connection data they need, such as your IP address and browser information.
  • Demo player card: the player's name, scores, ability values, appearance and similar details sit after the # in the URL. Only your browser reads them, and they aren't sent to us or to the traffic statistics service. If you share the link, anyone who receives it can see them.
  • Surveys: the demo player card page and the survey short link lead to Google Forms. Filling them in is up to you.

Service providers

These providers process data and may transfer it outside Taiwan, including to the United States. Some also use data under their own policies, such as Cloudflare improving its bot detection. They are required by their terms to protect data to a standard equivalent to this policy.

We don't sell data to anyone or share it with data brokers.

How long data is kept

  • Google Analytics for Firebase: user-level and event-level data is kept for up to 14 months. Aggregated reports aren't subject to this limit.
  • BigQuery: exported event data is currently kept for 60 days.
  • Error reports: currently kept for 30 days.
  • Launch notification list: kept until you unsubscribe or we no longer need the list.
  • Survey responses: kept until analysis is finished and they're no longer needed.
  • Stability data, website statistics and provider connection logs: kept according to each provider's settings and policies.

What you can do

  • Stop collection: the app doesn't currently have a setting to turn off data collection. Uninstalling the app stops collection and deletes the saves and install ID on your device. Reinstalling generates a new install ID.
  • Ask about or delete gameplay data: email us. Gameplay data and error reports are linked only by random IDs, and the app doesn't currently show your install ID anywhere, so we usually can't find your data from a name or email alone. We'll do what we can and tell you what's actually possible.
  • Unsubscribe from launch notifications: reply to a notification or email us, and we'll remove you from the list.
  • Delete survey responses: email us with when you filled in the survey and what you wrote, so we can find your response.

Minors

The game doesn't ask for your age, and we don't knowingly collect personal data from minors. If you're a parent or guardian with questions about your child's data, please email us.

Features not yet available: accounts and cloud saves

These features aren't available yet. The app doesn't offer login today and doesn't upload saves. What follows is a preview only, and the policy will be updated with the actual details when they launch.

  • Accounts: we plan to offer sign-in with Google and Apple. Once available, we'd receive the account identifier from the sign-in provider and any data you agree to share, such as your email.
  • Cloud saves: we plan to store your saves in Google Firestore, in a data center in Taiwan (asia-east1), so your progress can carry across devices.
  • Account deletion: when login opens, you'll also be able to delete your account from within the app.

Before these features launch, we'll update this policy and add the full terms for accounts and cloud saves.

Changes to this policy

When this policy changes, we'll update this page and the last updated date above. For significant changes, we'll also let you know through an in-app announcement or on the website.

Contact us

If you have any questions about this policy or your data, email us: final.inning.baseball@gmail.com