Numbiro Privacy Policy
Numbiro does not collect any personal data such as your name, email address or photo. It does send anonymized
data
to third parties for the purposes of monitoring and improving the app. Below is a summary of the data
collected by
Numbiro or third
parties:
Google Analytics
From version 2.0.0 onwards, Numbiro uses Google Analytics to understand user behaviour, with the intention of
improving the functionality of the app in the future.
You can read information about the data which Google Analytics collects on their Data Collection document.
According to this document, the following information is collected by Google:
- Number of users
- Session statistics
- Approximate geolocation
- Browser and device information
In addition, Numbiro explicitly sends the following information to Google Analytics:
- Quiz parameters (the number range, quiz time and Japanese counters selected)
- In-app purchases, including which screen of the app the user was viewing when a purchase was made
To achieve this, Google will use a unique identifier to recognize you across subsequent visits. This is not tied
to
your real identity at all. You also have control over whether this unique identifier can be used - see the
document
above for more detail.
Appsflyer
From version 1.3.2 onwards, Numbiro uses AppsFlyer to help understand where users are installing the app
from.
You can read information about the data which AppsFlyer collects on their Safety Section Form
document.
According to this document, the following information is collected by AppsFlyer:
- Approximate Location: the IP address is received and mapped to a region/city level.
- In-app purchases and subscriptions
- App launches
- Launch time
- Battery levels
- Ad ID, if accessible
Firebase Crashlytics
From version 1.2 onwards, Numbiro uses Firebase Crashlytics to report any crashes which occur, so that we can
improve the app and fix bugs in the future. You can read information about the data which Crashlytics sends
in the
Firebase Crashlytics and Firebase App Distribution
Terms
of
Service, and the Crashlytics
and App
Distribution Data Processing and Security Terms. This is also summarized in Privacy and Security in Firebase.
According to these documents, when a crash occurs, the following is an example of the information is sent to
Google:
- A unique identifier for the device, allowing Crashlytics to identify duplicate crashes
- The timestamp of when the crash occurred
- Numbiro's bundle identifier and full version number
- The device's operating system name and version number
- A boolean indicating whether the device was jailbroken/rooted
- The device's model name, CPU architecture, amount of RAM and disk space
- The uint64 instruction pointer of every frame of every currently running thread
- If available in the runtime, the plain-text method or function name containing each instruction pointer.
- If an exception was thrown, the plain-text class name and message value of the exception
- If a fatal signal was raised, its name and integer code
- For each binary image loaded into the application, its name, UUID, byte size, and the uint64 base
address at
which it was loaded
into RAM
- A boolean indicating whether or not the app was in the background at the time it crashed
- An integer value indicating the rotation of the screen at the time of crash
- A boolean indicating whether the device's proximity sensor was triggered
Note that the unique identifier effectively counts as a tracking ID, since it allows crashes to be recognized as
originating from the same device over time. However, it is not used for any other purpose. There is NO
personally
identifiable information being sent. Firebase says they delete the data after 90 days. The data may be processed
anywhere in the world.
Numbiro analytics
From version 1.2 onwards, every time you start a quiz session, the quiz parameters are sent to Numbiro's
servers.
We store this information to help
understand how the app is being used, and to improve it in the future. Specifically, the data sent is:
- The number range
- The quiz time
- The Japanese counters selected
The data does NOT include the name of the preset you selected. The data is COMPLETELY anonymized: that is,
there
is
NO way to identify records which originated from the same user or same device.