# Investigating Wearable Fitness Applications: Data Privacy and Digital Forensics Analysis on Android
## 4 Findings
### Amazon Halo Artifacts
#### 4.1.2 Activity-Related Artifacts  
Table _catalystLocalStorage_ also records the bulk of activity-related data. The _redux-Persist:appsync_ and _reduxPersist:appsync-metadata_ rows both hold varying combinations of hourly, daily, weekly, and monthly values for health metrics, such as maximum, average, and resting heart rates, sleep summaries, and skin temperatures, and activity related data, such as workouts, steps, and tone analysis results. All artifacts discussed in this section were recovered from either of these two rows, unless otherwise specified.  
A session is generated whenever the user does a workout, which may be recorded manually by the user or automatically by the device and app, or uses Tone Analysis. An example of an automatically recorded workout session is shown in Figure 6, where the session ID is **35 ec53 fe-d316-4e05-919f-c0088538b4 ba**. Along with the workout session start and end times, the authors are also able to recover session-related details such as the number of steps the user took, the number of calories the user burned in kilocalories, the length of time the user spent doing intense, moderate, and light activity in milliseconds, and the user's maximum and average heart rates. The details associated with the session **35 ec53 fe-d316-4e05-919f-c0088538b4 ba** are shown in Figure 7.  
\"Session:35 ec53 fe-d316-4e05-919f-c0088538b4 ba\": { \"id\": \"35 ec53 fe-d316-4e05-919f-c0088538b4 ba\", \"version\": \"95 cc338b-3988-48e9-8 ee2-11239c5 ff19d\", \"type\": \"Workout\", \"startTime\": \"2021-06-28T15:00:00.2442\", \"endTime\": \"2021-06-28T15:12:41.8932\", \"sessionSubtype\": \"Walking\", \"creationType\": \"Automatic\", \"sessionSummary\": { \"type\": \"Id\", \"generated\": true, \"id\": \"Session:35 ec53 fe-d316-4e05-919f-c0088538b4 ba.sessionSummary\", \"typename\": \"ActivitySessionSummary\" },  
Figure 4: Amazon Halo device **(top)** and firmware **(bottom)** information as shown in DB Browser for SQLite.  
Figure 5: Amazon Halo device **(top)** and firmware **(bottom)** information as shown in DB Browser for SQLite.  
In addition to session-related details, the authors were also able to recover Activity and Sleep related data at varying degrees, as shown below.  
* Resting Heart Rate
- Maximum and Average Heart Rate, taken every 5 min
- Time spent doing Vigorous, Moderate, Light, and Sedentary Activity, taken every hour
- Calories, taken every hour
- Steps, taken every hour
- Sleep Summary
- The following metrics were recorded weekly for the last two weeks (**28 June 2021 to 7 July 2021**) of our data population, excluding Sundays:
- Sleep Summary data
- Activity Summary data
- The following metrics were recorded monthly:
- Sleep Summary data for the last five weeks (**1 June 2021 to 7 July 2021**) of our data population.
- Activity Summary data for the last week (**1 July 2021 to 7 July 2021**) of our data population.  
The row _browseWorkouts_ of the sameTable _catalystLocalStorage_ holds the search query and the associated results when the user searched for a workout using the criteria: **Strength, 20-25 min, Intermediate**, representing the category of workout, duration, and difficulty,  
Figure 7: Session summary from the workout the Amazon Halo user did during session **35 ec53 fe-d316-4e05-919f-c0088538b4 ba.sessionSummary_week1**: - [->=amount> - 1167] - [->=amount> - - - - - - - - - - - - - - - - - - - - - - - - - - - - -  
respectively. This query is shown in Figure 8. It should be noted that although there is a **lastSyncEpochMillis** timestamp in this record, this value does not correspond with when our tester performed the search and instead aligns with when last the app was used.