Slopes and Your Data
I don't want to do anything creepy with your data. I charge users directly for Slopes Passes so I can avoid having to sell your data or do anything else questionable to make money and stay in business. I may use some of your data responsibly to improve Slopes, but that's it.
Let's unpack how I use and store your data:
A) Identifiable Data: If You Don't Have a Slopes Account
- All your recorded GPS data stays local to your phone and never hits the Slopes servers.
- You don't have an account or any purchase history, so there's nothing there to send to my servers, either.
B) Identifiable Data: With a Slopes Account
What specifically do I store, and how?
At this point I'm giving you free online backup / sync, which does mean your recorded data is now on my servers.
- Data transmitted via the app to and from Slopes servers is encrypted following industry best practices.
- To provide sync the GPS data tracking your movements throughout the day is stored on my servers. This data is encrypted and stored in such a way to prevent public access.
- Personality identifiable account information, such as name and email, are stored separate from your private GPS data (so it is hard to match all that GPS data to your specific account unless all my servers are compromised).
- More generic data about your recordings (metadata) such as the resort it was at, time spent on lifts vs runs, speeds & verticals, notes, etc are also stored on my servers along side your account information to provide sync.
- Your purchase history within Slopes is stored on my servers along side your account information, too, to make all Slopes Pass purchases work on any device you log in from.
- I do not upload any of your health data to my servers. Calories burned, weight, and heart rate all stay local to your phone inside of HealthKit.
What I do with your uploaded data?
I act responsibly with it. Beyond what is needed to run Slopes I will not share your data with third parties, unless you enable a third-party integration such as connecting your Slopes account to Strava. But at that point sharing your data with a third party was kinda the point, right?
I will never, ever, sell your data.
How is your data shared with third parties so I can run Slopes?
- Your GPS data, account metadata, purchase history, and activity metadata are stored on the third-party servers I pay for to host sync and run Slopes.
- If you email in and ask for assistance your email address and our conversations are also then stored within my customer service helpdesk provider.
How is your data used inside Slopes?
- If you email in with a problem I will access your data, as needed, to assist with the problem.
- I may privately use your GPS data or generic activity data (anonymously, without knowing who it belongs to) to improve Slopes. For example, I may use some of your GPS data to help test improvements to my tracking algorithms, I may query for random users' days recorded at a specific resort to help track down new lifts or runs to identify, or I may aggregate a bunch of recorded data to help get the average wait times at lifts at a given resort. When I'm doing this I take care to not look up account information about who the data belongs to; I just grab the anonymous raw GPS data or activity metadata.
- If I do access your GPS data anonymously I will never publish it, even combined with a lot of other users' GPS data at that same location to make it anonymous, publically. I may publish resort-level information like "the average wait time for the Mountain Tripple is 3min" based on it, but not the GPS data itself.
If at any point you'd like to remove all of your data from the Slopes servers you can do so in-app under More -> My Account -> Delete.
C) Anonymous Data Captured in-app to Improve Slopes
Beyond your account, purchase, and activity data outlined above, there is some anonymous/pseudonymous usage data Slopes tracks in-app:
- I do track pseudonymous usage data through Firebase: for example "someone recorded a day at Whistler for 7hrs" or "someone just started recording via Watch". Firebase doesn't get access to your account data or any of the GPS data you recorded; just high level events about what is happening in the app. I do this so I can track popularity of resorts to prioritize improvements, gauge what kind of battery usage targets I should aim for, if people are even using certain features, etc.
- My premium map provider, MapBox, reports some annonymous non-identifiable data when using their maps to help them improve their mapping data and service (more here).
- You can turn off both of these anonymous trackings in-app under More -> Settings.
- Slopes also uses a crash reporter (Crashlytics) to aggregate and track crashes. These reports include non-identificable information such as what iPhone you have, where the crash occurred, my own logs I create to help me track down what happened, and an installation unique identifier to help correlate how many users experienced the crash vs repeat crashes for the same user.
I do occasionally advertise Slopes on Instagram, so I have the Facebook advertising SDK (code library) in Slopes which is pseudonymous. I do not share any data you enter into or capture with Slopes with Facebook; it is only used to track how many installs come from Instagram ads so they can accurately charge me. Removed in 2019.12, because Facebook is creepy and can't be trusted.