TubeFixer for iOS
Upon every startup of the YouTube app provided by Apple on iOS 3.0 through 5.1.1 (and installed manually on iOS 6.0-6.1.6), your device version, model, and a base64-encoded version of your device's YouTube activation ticket is uploaded to TubeFixer's authentication endpoint. If this is the first connection the device has made since activation with Apple, TubeFixer's server will store a salted SHA512 hash of the YouTube activation ticket, alongside the currently installed TubeFixer version (e.g. 2.0-152+debug), the current device iOS version (e.g. 5.1.1) and the currently used device model identifier (e.g. iPad1,1). This information is only used to provide TubeFixer with knowledge of the devices most commonly used in order to gain an understanding of which devices need most attention, and is not tracable back to any specific device, given a restore.No other user-inputted data is collected, which includes search history and video watching history.
If you do not agree to this information being collected, do not use TubeFixer.
All information included in the TubeFixer as a service section applies to TubeFixer for iOS.
TubeFixer, as a service
Requests made to the TubeFixer API (via the TubeFixer for iOS tweak or otherwise) are not logged, stored or associated with any identifier. All information entered into the TubeFixer API is forwarded to Google's YouTube Data API with no information that can be associated to the user who initiated the request. When requests are made using a user-specified API key, the user's API key is forwarded to, but is not stored on, the TubeFixer server, and the API key is only used to make the internal request to the Google-provided API. No response data from the Google API is stored on TubeFixer's server and is immediately discarded upon returning the response to the user.