Work out to your music.
This privacy policy applies to MC-Timer, version 1.0 or later.
If you disagree with the terms of this policy, please cease using the app.
MC-Timer is a commercial iOS/tvOS/watchOS app build by tredje design - Eric Roller. It is used to control the playback of music playlists for timed sports workouts.
The app is intended for use as is.
The app does not collect any information about the user.
However, if you choose to contact me by email, then, obviously, all the information that you disclose in the message will be visible to me. The app itself has no access to your mail messages, not even the message that you may have composed on the feedback form within the app. Depending on your request, I may choose to keep your email-address in a TODO-list to be able to contact you again later. I also make use of backups which will contain your message.
The app does not attempt to detect the age of the user and I do not knowingly collect personally identifiable information from children under 13. In the case I discover that a child under 13 has provided me with personal information, I shall immediately delete this from my servers. If you are a parent or guardian and you are aware that your child has provided me with personal information, please contact me so that I will be able to take all necessary actions.
There is no tracking or collection of your app usage patterns.
Workouts keep a record of how often and how recently you have used them. This information is not shared; it is only used for your convenience such that more popular workouts can be listed before other workouts. In other words, this is only used to guide the workout sort order. The usage count is also visible to you in the workout list; each workout shows a small comment in the format: Used: 42 times.
Apple may collect analytics information and crash data in a form that does not personally identify the user. You may choose not to share this data with me. To do so, open Settings on your iOS device, select Privacy, select Analytics, and turn off Share With App Developers. See also Analytics on Apple’s Privacy Policy.
When you use Apple Music, a security token needs to be kept up-to-date. The app will therefore download a new token from my server whenever the current token has expired or is about to expire. This may happen two or three times a year. The token is very small (about 200 bytes) and is specific to me and to the app. It contains neither any user-identifiable information, nor hints on how often you use the app or what music you might be listening to. I do not track where these tokens are sent to, but I expect that my hosting provider will probably log these as part of their standard web site usage analytics.
An example of such a Developer Token is described in Apple’s Developer Documentation for MusicKit, but the actual token will look like gibberish once it is encoded and signed.
Please note, however, that Apple does collect information about your Apple Music activity. This is described in their article about Apple Music & Privacy.
All data is stored locally on your device, such that it can be made available to you when you use the app next time. When iCloud is enabled for this app, the workout and playlist descriptions will be uploaded to iCloud to allow synchronization across multiple devices. No part of this data is tracked or analyzed; no statistics are collected; nothing is uploaded to other servers for analysis.
You should note, that backups, that you manually create in Finder or in iTunes or those that you have chosen to upload to iCloud, will also contain this data.
The app does not use ads. Therefore, no data is handed over to third-party agencies that would have provided such ads.
Cookies are files with a small amount of data that are commonly used to store unique identifiers. These are sent to your browser from the websites that you visit (and from third-party services that are included on that page) and are stored on your device’s internal memory. Cookies are site-specific, but they may be permanent or they may have expiration dates that allows them to stay in place for years. For as long as cookies are valid, they will be returned to their website (or to third-party services) with any future requests that you may make through your browser. This makes it possible to track your interactions with that website (or any other websites that use the same third-party service).
This app does not use cookies.
The app provides a small number of links for your convenience. If you tap to open one of these links, you will – obviously – be directed to that site. Data that you provide to those sites is not covered by this privacy policy. Therefore, I strongly advise you to review the privacy policy of these websites. I have no control over and assume no responsibility for the content, privacy policies, or practices of any third-party sites or services.
For the links to this site, I collect no analytics other than those collected automatically by my hosting provider.
I may update this Privacy Policy from time to time.
Any changes that I make take effect as soon as they are posted on this page. I endeavour to update the change log below whenever that happens.
If you have any questions or suggestion about this privacy policy, do not hesitate to contact me.
(2019–11–03) First version.
(2019–11–19) Added section about Apple Music Activity.
(2021–02–01) Added information regarding the use of iCloud.
(2021–02–03) Added tvOS and watchOS.
(2021–04–24) Rephrased the app usage section to mention that the workout database stores simple usage statistics which are used by the app to be able to list popular workouts before other ones.