
2.2 Fitness Applications & Privacy Breach Incidents
Fitness applications allow users to track their workout his-
tory and provide them with statistics. Moreover, some fit-
ness applications have social network capabilities, as shown
in Table 1, and allow users to share workout summaries that
are known to motivate users and their social network con-
nections to achieve their goals [2]. Some fitness applications
also inherit user-blocking features and capabilities from
social network platforms, including user privacy options
such as private records–the activity records that are only
visible to the user.
Although fitness applications have configurable privacy
options, there have been a lot of privacy incidents concern-
ing location data obtained from those fitness applications.
We review some of those privacy breaches in the following
to contextualize our work in the broader privacy literature.
Revealing Secret U.S. Military Bases. Strava, which is
one the most popular fitness tracking applications in the
market today, collects users’ public data and publishes a
heatmap of the aggregates to highlight routes frequented
by users [10]. Although the aggregates in the heatmap do
not explicitly contain any identity information, activities in
desolate places revealed the location of many U.S. military
bases, which is considered sensitive information [11], [12].
Deanonymization Through Strava Segments. In Strava, the
heatmap feature was used to show “heat” made by the
aggregated and public activities of Strava users over the
past year. It is, however, shown that a dedicated adversary
can deanonymize heatmap to find out users who ran in a
specified route [13]. For example, by selecting a route from
the heatmap, a registered user can manually create a GPS
eXchange (GPX) track file and create a segment using it on
Strava. A segment is a portion of a road or a trail where
athletes compare their finishing times. Consequently, once
this segment is created, the users who previously ran that
route are shown on the leaderboard grouped by gender and
age. This feature is then leveraged to identify individuals
who ran that particular place.
Tracking and Bicycle Theft. Users of fitness applications
can share information related to the equipment used for
the activity, including bicycles, tracking devices, shoes, etc.,
along with the routes frequented. The combined shared
information makes them a target for robbery, and several
such incidents of bicycle theft are reported [14]–[17].
Attack on Privacy Zone. To cope with the increasing privacy
risks, Strava features privacy zones, a technique to obfuscate
the exact start and end points of a route. A recent study [18]
has demonstrated that it is possible to reveal the exact start
and end point of a route that utilizes the privacy zone
feature. The same study also claimed that around 95% of
the users are at risk of revealing their location information.
Live Activity Breach. In Runtastic, one of the popular
activity-tracking applications, users can share their live
activities. In theory, users should be able to configure the
privacy settings for their activities such that only privileged
users, such as connections on the application platform, can
track the shared live activity session. However, it has been
demonstrated [19] that the selected privacy settings are not
correctly applied to a live session. As a result, everyone can
go through live sessions and track Runtastic users in real
time, even though the associated privacy options should
have prevented this type of breach. Based on this incident, it
would be easy to stalk and locate a user, e.g., a lone runner
or cyclist with expensive equipment, in real time.
3 THREAT MODELS
We outline the potential threat models under which this
study is conducted. We describe three models under which
location privacy is breached only from associated elevation
profiles. We note that the following threat models are only
hypothetical: no attacks were actually launched on any
users. As mentioned earlier, this study in its entirety is
motivated by the aforementioned demands of users to have
more flexibility over-sharing partial data, such as elevation
profiles, and examines the ramifications of such sharing in
a hypothetical setting. We note, however, that those settings
are also plausible if such sharing is enabled.
Our study utilizes three threat models: TM-1,TM-2, and
TM-3, which we outline below with their justifications. The
adversarial capabilities in TM-1 are greater than in TM-2 and
TM-3, making it a more restrictive (powerful) model.
1TM-1.In TM-1, we assume an adversary with workout
history records of a target user, and the goal of the adversary
is to identify the last workout location of the target user from
the recently shared elevation profiles. TM-1 is justified by
multiple plausible scenarios in practice. For example, such
an adversary might have been a previous social network
connection of the target user that was later blocked. In
such a scenario, the adversary may have previous workout
records of the target from which the adversary may attempt
to de-anonymize the target’s activities. Another example
might include group activities, where two individuals (i.e.,
the adversary and target) may have shared the same route at
some point. In either case, by knowing the target’s previous
fitness activity records, the main goal of the adversary in
this model is to identify recent whereabouts only from
publicly shared elevation profiles in workout summaries,
thus breaching the target’s location privacy.
2TM-2.In TM-2, we assume an adversary with access to
limited information, such as the city where the target lives.
Such information is easily accessible from public profile
summaries, athlinks.com, public records, etc. The adver-
sary’s goal in TM-2 is to find out which region or part of a
given city the target’s activities are associated with. The TM-
2use scenario may include a targeted user sharing private
activities in which the route is hidden while the elevation
profile is shown. The adversary, knowing the city where
the target lives, would want to identify the region (e.g., a
borough in the city) associated with the user’s activity.
3TM-3.In TM-3, we assume an adversary trying to identify
the target user’s city using only publicly shared elevation
profiles without any prior information. We assume, how-
ever, the adversary has the ability to profile the elevation of
cities with information that is easily obtained from public
sources (e.g., Google Maps, OpenStreetMap). The use sce-
nario of TM-3 may be used as a stepping stone towards
launching the attack scenario in TM-2 upon narrowing
down the search space to a city.
3