9-Inning Dash is a free arcade baseball game designed for kids and families. We collect as little data as possible.
What we collect
- Optional account: a display name and a 4-digit PIN (stored as a secure password hash — never in plain text).
- Gameplay stats: scores, innings reached, times, streaks, cosmetic unlocks, and play session totals used for leaderboards and progression.
- Technical logs: basic server logs (for example request paths and errors) to keep the game running.
What we do not collect
- No email address, phone number, or real-world address is required to play.
- No advertising ID tracking for third-party ads in the free core game.
- No sale of personal information to data brokers.
- No precise location tracking.
Kids & families (COPPA-friendly design)
- Guest mode lets players try the game without creating an account.
- Accounts use a username + PIN only (no email signup wall).
- Inactive non-admin accounts may be cleaned up after a period of inactivity to limit data retention.
- Parents/guardians can contact us to request deletion of an account.
How we use data
- Run the game (login, leaderboards, unlocks, admin safety tools).
- Optional AI coach messages if enabled by the operator (may send first name + inning context to an AI provider).
- Improve reliability and prevent abuse (rate limits, anti-cheat run checks).
Cookies & sessions
We use a session cookie to keep you signed in. It is httpOnly and is not used for third-party advertising.
Third-party services
- Hosting / database: our server and PostgreSQL provider process account and score data to operate the game.
- Optional AI coaching: if enabled, short gameplay context may be sent to xAI (or similar) to generate kid-friendly tips. The free default uses local tips with no AI call.
Data retention & deletion
Game scores and accounts are kept while the service is active and the account is used. You (or a parent/guardian) may request deletion by contacting the operator with the player username. Admin cleanup tools may also remove long-inactive accounts.
Security
PINs are hashed with bcrypt. Sessions use server-side storage. No security measure is perfect; please do not reuse important passwords as a game PIN.
App Store / Play Store builds
Native builds (when published) use the same privacy practices. Device permissions are limited to what the game needs (for example, no camera/microphone requirement for core play).
Contact
Questions or deletion requests: contact the app operator via the support channel listed on the store listing or the project repository owner.
Changes
We may update this policy as the game evolves. The “Last updated” date at the top will change when we do.