View source for FirefoxOS/Metrics/FoxFooding

= Metrics & Telemetry Data Collection =

Mozilla collects the following information only for the purposes of improving the Foxfooding Program. Data collection is limited to Foxfooding builds of Firefox OS only, and there is no intention to require this data from users who have not explicitly opted into it and given their written consent.

The following data is collected:

* App usage metrics, including but not limited to app launches. This data is tied to an IMEI (see Glossary).
* First-time usage pings, which are sent when the phone is first activated and taken through the whole FTU process. This process is over when the user can see the Homescreen.
* When using Bugzilla Lite, some additional data may be collected. While the nature of this data is difficult to clearly and very specifically define, it may include the following: memory records which may be enough to piece together a user's activities, IMEI's, apps installed, some data and usage history.
* Note that Bugzilla Lite data is explicitly opt-in, and on a case-by-case basis. The user must specifically submit a bug report, and opt to include this information each and every time.
* Sign-up data will be stored, which includes the Foxfooder's name, address, phone number, email address.

== Data Storage and Deletion Policy ==

Data is stored on Mozilla's Telemetry servers. The data will be destroyed on the following conditions, depending on the type of data:

* Aggregated app usage metrics, i.e. those not associated with an IMEI and/or person, will be stored indefinitely.
* Bugzilla Lite data will be stored indefinitely. This data is stored on Mozilla's Bugzilla servers. It may be marked as private so that only Mozilla employees can see. It can also optionally be marked as high security, so that only those on the Security team can view it, but this exception will rarely be granted without extenuating circumstances.
* Sign-up data will be stored the shorter of: a) 180 days after the Foxfooding program ends, b) the Foxfooder opts out of the Foxfooding Program.

== Glossary ==

 IMEI: An identifier associated with a SIM card slot. Each SIM card slot in existence has a unique one. In practice, since the Sony Z3C only has one SIM card slot, the IMEI is effectively associated with the phone. When we distribute these devices, we record Foxfooders and IMEI's associated with their phones.

== Collected data for dogfooding telemetry ==
== Gaia metrics ==

In Gaia, the following information are recorded and sent to telemetry:

=== Hardware & build information about the device: ===

* IMEI of the device
* screen data (width, height, pixel ratio)
* Hardware related information:
** deviceinfo.hardware
** deviceinfo.os
** deviceinfo.product_model
* Firefox OS build information:
** deviceinfo.software
** deviceinfo.platform_build_id
** deviceinfo.platform_version
* app.update.channel

=== Device settings: ===

* language
* is the developer menu enabled or not?


=== Information about the SIM card: ===

* whether a SIM is there and locked or not.
* If the SIM is accessible, we records IccInfo:
** mcc - Mobile Country Code (MCC) of the subscriber's home network.
** mnc - Mobile Network Code (MNC) of the subscriber's home network
** spn - Service Provider Name (SPN) of the subscriber's home network.


=== App usage: ===

* records which apps are installed, opened and uninstalled
* when we’re on the homescreen
* when an attention window is opened/closed
* when there is a screen change
* is the phone locked? (i.e is the lockscreen app running)
** record the time spent on the lockscreen
** record the time we ran the app
* the URL of the app the user is currently using
* when did the currently running app start?
* the URL of the used lockscreen app
* opened attention window manifest URLs and their start times
* activities usage : if the current app launches an inline activity, we record that and maintain a count of how many times each activity (by url) has been invoked by this app. This will give us interesting data about which apps use which other apps. Note that we do not track the amount of time the user spends in the activity handler.
* is the user idle?

=== User information: ===

* record of the name of the search provider which is used (Yahoo, Duck Duck Go, etc)

=== Data related to telemetry: ===

* when there is a time change on the phone (to adjust time measurement for metrics)
* the last time a transmission attempt failed
* end of metrics batch time

== FTU ping ==

These are the information sent to telemetry when the user goes through the First Time Use:

=== Hardware & build information about the device: ===
* the screen height, width and pixel ratio
* IMEI
* deviceinfo.os
* app update channel URL
* platform version
* platform build ID


=== Apps: ===

* preinstalled non-Gaia apps


=== Telephony: ===

* mobile operator network
* mcc - Mobile Country Code (MCC) of the subscriber's home network.
* mnc - Mobile Network Code (MNC) of the subscriber's home network
* spn - Service Provider Name (SPN) of the subscriber's home network.


=== Data related to telemetry: ===

* activation time
* ping time (time of the data being transmitted)

== Stored signed up data ==

=== Personal information: ===

* name
* physical address
* email address 
* phone number

=== Device: ===
* IMEI

== Bugzilla Lite info, which are opt-in ==

Data related to the bug being reported will be collected. This is opt-in only, on a case-by-case basis.


== Previous issue - FIXED: ==
All these data were initially linked to the IMEI of the phone, which enables to uniquely identify a user. For a better privacy practice, data have been anonymised. 
See: https://bugzilla.mozilla.org/show_bug.cgi?id=1171685