Privacy Policy for Ink Dots

App name: Ink Dots (Russian: «Точки») Package name: com.kirsulab.inkdots Publisher: KirsuLab LLC Contact: hello@kirsulab.com

This policy explains what Ink Dots collects and why. In short: we do not collect your name, email, contacts, photos, precise location, or any account information. We use Google Firebase to collect anonymous usage analytics and crash reports that help us understand how the game is used and fix bugs. Your gameplay against another person stays directly between the two phones.

1. Analytics and crash reporting (Firebase)

Ink Dots uses two Google Firebase services, which send data to Google (acting as our service provider):

• Firebase Analytics — collects anonymous, aggregated usage data: in-app events (for example, that a game was started or finished, and the chosen game mode, board size, difficulty, and outcome), a randomly generated app-instance identifier, your device model and operating-system version, app version, language, and a coarse region derived from your IP address (the IP address itself is not stored by us). This helps us see which features are used and how to improve the game.
• Firebase Crashlytics — when the app crashes, it collects a crash report: the diagnostic stack trace, the device state at the time (model, OS version, memory, app version), a randomly generated installation identifier, and a small amount of context we attach (the current game mode and board size). This lets us find and fix problems.

This data is not linked to your real-world identity, is not sold, and is not used for advertising — there are no ads in Ink Dots. It is processed by Google in accordance with Google's privacy and security terms (see Google's Firebase privacy documentation and Google Privacy Policy).

2. Data stored only on your device

The following stays locally on your phone and is removed when you uninstall:

• Game progress and settings — your current game, board size, difficulty, and sound/vibration preferences.
• Nickname — if you enter one for an online match, it is stored locally so you don't have to retype it.

3. Local two-player ("Play vs Human") connection

The optional two-phone mode connects two devices directly using Google Nearby Connections (Bluetooth and/or local Wi-Fi) — there is no game server. During such a match, and only with the phone you deliberately pair with by scanning its QR code, your chosen nickname and your moves are sent to the other player's device so the game can be played. This gameplay data is not routed through us and is not stored after the game.

4. Permissions and why they are used

• Internet / network state — only so Firebase can upload the anonymous analytics and crash reports described above.
• Camera — only to scan the opponent's QR code to start a local match. The camera image is processed on the device in real time and is never saved, uploaded, or shared.
• Bluetooth and nearby Wi-Fi (and, on older Android versions, location) — only to discover and connect to the other phone for a local match. Where the operating system requires location permission for Bluetooth scanning, it is used solely to enable that scan; we do not collect or store your location.
• Notifications — only to tell you it's your turn in an online game.
• Vibration — only for tactile feedback when you place a dot.

5. Data retention and your choices

Analytics and crash data are retained by Google/Firebase according to our project's retention settings and Google's policies, and are used only in aggregate to improve the app. You can limit analytics at the OS level (for example, by resetting or limiting your advertising ID in Android settings). To request that we delete crash/analytics data associated with your device, contact us at the address below and provide your app-instance or Crashlytics installation identifier if known.

6. Children's privacy

Ink Dots is a general-audience game and does not knowingly collect personal information from children. We do not collect names, emails, or precise location from anyone. If you believe a child has provided personal information, contact us and we will address it.

7. Data sharing and selling

We do not sell your data and do not share it with third parties for their own purposes. The only recipient is Google/Firebase, which processes the analytics and crash data on our behalf as described above.

8. Changes to this policy

If this policy changes, the updated version will be posted at this address with a new "last updated" date.

9. Contact

Questions about this policy? Contact KirsuLab LLC at hello@kirsulab.com.