Privacy policy for Little Go

Version 1

Back to main page


Little Go does not collect any personal data whatsoever. Little Go may, however, collect some non-personal data about the way how you use the app, for the sole purpose of identifying bugs in the software so that they can then be fixed. None of the data collected is transmitted without your approval.

The remainder of this page tries to explain the details in "no bullshit" terms - no legalese, just plain English written by a non-native speaker. If you have any questions, feel free to contact me.

Crash report data

When Little Go crashes, data about the crash is collected automatically and stored locally on your device. Next time you launch the app an alert is displayed, offering you the choice to send the collected data in the form of a crash report to the developer. If you decline, no data is sent.

In the "Diagnostics" area of the app, you can change the way how crash report data is collected and transmitted: You can turn off data collection entirely, you can decide that crash reports should be automatically sent without asking you first, or you can enter an email address that should be sent along with the crash report data so that the developer will be able to contact you if clarifications are needed about the problem.

A crash report contains the following information:

  • Hardware model (not the device ID!)
  • Operating system version
  • Type of crash
  • Technical information about the state of the application when the crash occurred

When you decide to send the crash report, Little Go transmits the data to the Crashlytics web service, which is part of the Google Firebase platform. Information about the network connection, such as the IP address of your device, is almost certainly logged by Google. Other than that, nothing about you or your device should be shared with Google - a best effort has been made to disable all other Google Firebase services and to only keep Crashlytics enabled. Notably, Firebase Analytics data collection has been explicitly disabled!

Logging data

In the "Diagnostics" area of the app, there is an option that lets you enable the collecting of logging data. The option is disabled by default.

While the option is enabled, a log file is written in the background that captures technical details about what you do with the app, which functions you execute, and what steps in detail the app performs in response to your requests.

Logging data is stored locally on your device. It leaves your device only if you send a bug report. See the next section.

Bug report data

In the "Diagnostics" area of the app, you will find a button labelled "Send a bug report". Tapping the button displays a pre-filled email view that you only need to supplement with your problem description before you can send off the report.

The email has a .zip file attached that contains the following information:

  • A version number that identifies the format of the information inside the attachment
  • iOS version and device type (only whether it is an iPhone or an iPad)
  • A snapshot of some of Little Go's in-memory objects that make it possible to reproduce the state of Little Go exactly the way it was at the time the diagnostics information file was generated
  • Your current preferences (including the players you have defined and the settings you use on GTP engine profiles)
  • The current game as an .sgf file
  • A screenshot of the "Play" area of the app (excluding the status bar, i.e. the name of your carrier is not in the screenshot)
  • The output of the "showboard" GTP command
  • The log files (if you have previously enabled logging - see the previous section)

The bug report email is just like any other email, so the usual email-related disclaimers apply. Notably, the recipient of the message will see your email address.