Last updated: March 31st 2018
Once Quickplay is installed, the client starts off by contacting this web server to gather necessary data (i.e. the list of games on the server). The client will NOT send information about your computer, game, or environment unless specified. On first launch, once the user joins a world, the user will be prompted whether or not they wish to send anonymous data which helps me create better mods for your game. The client will continue to prompt the user until a choice is chosen by the user (either YES or NO). For the purpose of analytics, your decision is logged anonymously regardless of whether you choose "YES" or "NO".
By choosing "NO", the client will make the least amount of connections to this web server necessary, sending as little data as necessary to the game, computer, user, or environment. Data considered "necessary" includes your statistics token, the version of Quickplay you are using, and the mod manager you are using. Mod manager refers to the front-end system used to deliver data such as GUIs to the client (e.g. The normal Quickplay .jar versus a specialized modpack that implements Quickplay's services).
By choosing "YES", the user agrees to send some anonymous data about their game and environment which helps me develop better mods. This data does not contain any information I would be able to use to identify you. The data does contain a "token" which can be used to link the data sent to your client, assuming the user shares their token publicly. If the user does not share their token, there is no way to determine who the owner of any given token is.
If deemed necessary, your token can be used to send data back to your client. This could be anything from a chat message to an instruction to your mod to reload the list of games. Quickplay is by no means a spam service, and therefore sending messages to users will be avoided at all costs. This token will not reveal your identity without your consent.
As of Quickplay v2.0.0-beta, if you agree to send anonymous data by choosing "YES", your client will send the following data whenever it contacts my web server:
Additionally, regardless of whether you agree to send anonymous data or not, your client will send the following data whenever it contacts my web server:
All of this data helps me fix any issues that arise within the mod as well as determine what kind of users use my mod, which in turn allows me to create ods designed specifically for the type of users who use my mod.
As of Quickplay 2.0.2, if you agree to send anonymous data by choosing "YES", your client will send the following data to Google Analytics for analytical tracking whenever necessary:
All Google Analytics reports may contain the following additional information:
As of Quickplay v2.0.0-beta, Quickplay clients contact my web server:
The frequency of pings is dynamic and may differ between clients, but will never occur more than once per 10 minutes per client. These pings contain all the normal data and are used to make sure everything with the client is up to date. Things verified may include but aren't limited to the current list of games and whether your client's Quickplay should be enabled. It also helps me track when Quickplay users are most active, which is useful for determining when to turn off Quickplay temporarily for maintenance or otherwise if ever deemed necessary.
Quickplay will send event data to Google Analytics at the time of those events or shortly after in groups of data. This allows for relatively accurate session tracking, which can be used to determine when and how long users are using Quickplay for.
I will only ever share data that is necessary to fulfill your or anyone else's experience using Quickplay. This includes but is not necessarily limited to the following examples:
Your data will never be shared with or sold to third party services.
In addition to the above terms, Quickplay Premium comes with a couple caveats that you agree to upon installing or purchasing Quickplay Premium. In order to properly supply you with your Quickplay Premium features, your MC UUID is stored in a database. This UUID is an identifier that tells me who you are (what your username is).
Whenever it is necessary for you to verify your identity, you will be prompted to enter your Hypixel API key.
You should be careful who you share your API keys with, and don't give them out publicly. Quickplay never
saves or logs your API key for longer than 24 hours. Despite your key being stored for short periods of time,
it is never visible to anyone, including the developers of Quickplay. If you don't know what your Hypixel
API key is, you can retrieve a new one by connecting to
mc.hypixel.net and typing
If Quickplay Premium is installed on a client, it sends your MC UUID to the Quickplay web server on initial startup of the game. This is required in order to verify your Quickplay Premium subscription. In addition to this, your Quickplay Premium version is sent as well. Whenever the client executes a command, their client may send their API token and/or UUID to the web server to authorize and process the command.
Premium users may customize their Quickplay Glyph by changing variables such as the image, size, or position of their Glyph. All Glyph data is shared with other clients on startup. This includes the MC UUID that the Glyph is linked to. Whenever a Premium client changes their Glyph, their Glyph is subject for review by bugfroggy or other Quickplay developers to make sure it follows all rules. If it is deemed that the Glyph violates one or multiple rules, the Glyph may be removed. Multiple violations may result in a Premium user being restricted from customizing a Glyph or using Quickplay features in the future.
As of Quickplay Premium v1.0.1, when a Premium user uses the in-game Daily Reward feature, analytical data is sent to both Quickplay and Hypixel. This data includes but isn't necessarily limited to:
This policy could change without notice.
Copyright © bugfroggy 2019 | License