# Investigating Wearable Fitness Applications: Data Privacy and Digital Forensics Analysis on Android
## 4 Findings
### Amazon Halo Artifacts
#### 4.2.2 Activity-Related Artifacts  
The _json_activities_ table within the \(\backslash\)_databases_\(\backslash\)_gcm_cache.db_ database holds the user's activity-related data. This table contains all the activities recorded with _timestamps_, _data_type_, and _cached_val_ as important columns to investigate. When a row has _data_type_ set to **ACTIVITY_DETAILS**, _cached_val_ contains the JSON-formatted entry with detailed information about the activity (see Figure 17 for the formatted JSON file using the codebeautiful JSON viewer). Similarly if a row has _data_type_ as **ACTIVITY_CHARTS**, the _cached_val_ column will have a JSON formatted entry that contains valuable information about the activity including but limited to, all GPS location of the activity, heart rate, speed, and distance (see Figure 18 for an example). Moreover, relating back to the last weather notification, if the row has a _data_type_ of **ACTIVITY_WEATHER**, in the _cached_val_ column we can find details of the weather notification such as **temp**, **dewPoint**, **relativeHumidity**, **windDirectionCompassPoint**, **windSpeed**, **latitude**, **longitude**, and **weatherStationDTO** which contains the ID and name of the station (see Figure 19).  
The Garmin vivosmart(r) 4 is also capable of recording stress, sleep oxygen, and sleep-related data. Within the _sleep_detail_ table inside the \(\backslash\)_database_s\(\backslash\)_cache-database_ database, we can find the user's sleep details. These details include date, sleep time in seconds, start sleep time and end sleep time, sleep status (e.g., light, deep, and awake), average O2 value, and lowest O2 value. Moreover, in the same database, the _user_daily_summary_ table contains overview activity details where each row represents a day. These data cover a variety of information to the user, such as stress data, total number of steps, distance covered, calories, active time, min and max heart rate, and many more. The _cache-database_ database contains multiple other tables, including tables _acclimation_pluse_ox_details_, _activity_summaries_, and _response_cache_. In addition, all the activities that are stored as JSON files in the _gcm_cache_db_ database are instead stored as rows in the _cache-database_ database, however, only general details about the activity as in _ACTIVITY_DETAILS_. The _cache-database-wal_ file also contained relevant data that may not have yet been pushed to the _db_ file. Another feature of the Garmin vivosmart(r) 4 is its capability of showing notifications on the device. One of these notification functions is for the weather. The \(\backslash\)_shared_prefs\(\backslash\)_weatherprefs.xml_ file contains the weather preferences and the last time the user received a weather notification. In addition, user menstrual notifications can be recovered from the \(\backslash\)_shared_prefs\(\backslash\)_MentrustualNotificationPrefs.xml_ file. Other user notifications delivered through the Garmin band can be recovered from the following database: \(\backslash\)_databases\(\backslash\)notification-database_ (see Figure 20 for example messages).  
Figure 19: Formatted, reduced, and redacted weather activity details where **name** is the name of the weather station being used.  
Figure 20: A reduced view of the notifications displayed on the Garmin vivosmart® 4 device.