This privacy policy describes how information is collected, used and shared when using services operated by Faithful.
Collected information:
TL;DR: Faithful has not, does not, and will not collect personal information unless it is explicitly given.
- Faithful user profiles can be customized by optionally providing a username, bio, Minecraft UUID, and social media links. All of this information is voluntarily provided, can be removed at any time, is stored locally, and will not be personally identifiable unless personally identifiable information is provided.
- By submitting an add-on for review, any information submitted with that add-on will be stored for the purposes of being listed on the site. All add-on information and images are voluntarily provided, can be removed at any time, are stored locally, and will not be personally identifiable unless personally identifiable information is provided.
- By submitting a texture on Discord, the image data and message content are stored in the generated submission embed. Texture submissions can be removed at any time and are stored on Discord's servers. All submission information is voluntarily provided and will not be personally identifiable unless personally identifiable information is provided.
If a texture passes voting, a record of the submission and its authors is created. Contribution history can be anonymized at the user's discretion. - A technology similar to cookies called "localstorage" is used to save preferred website themes, favorited add-ons, and recent searches. On the Faithful Studio, login information and persistent user-customizable settings also use localstorage. Localstorage is entirely stored on the user's device and cannot be read by Faithful or any other user.
- A record of the number of times a Discord bot command has been used is stored on a local database on the bot server. Faithful does not log messages, and these records are entirely anonymous metrics.
How information is used:
- Users can opt into having a public user page to display information about them, their contributions, and their add-ons. This is entirely voluntary and can be disabled by anonymizing one's user account. Additionally, user statistics are used to track project growth and aggregate statistics.
- Add-on information is used provide context for users interested in downloading the add-on, aggregate statistics, and list them on the website accurately and correctly.
- Texture submission information is used to provide context for submission voting, credit co-authors accurately, and push texture files to the correct locations. Contributions are tracked to aggregate statistics, prevent improper attribution, and preserve a historical record of the packs' evolutions.
- Localstorage data is used to remember user-configured settings between website visits and prevent the Faithful Studio logging out users between sessions.
- Discord bot command records are completely anonymous usage metrics used to improve the bot.
Opting out:
- A Faithful account and user profile can be deleted at any time using the profile page.
- An add-on submission can be deleted at any time using the delete button on the add-on submissions page.
- A texture submission can be deleted at any time by using the reaction tray on the relevant Discord submission embed.
- Localstorage usage can be avoided by not setting website-specific settings or deleted by clearing browser data.
- Adding to Discord bot records can be avoided by not interacting with bots.
Finally:
- Faithful services may use or contain links to third-party services that have their own privacy policies and terms of service. It is encouraged to review the privacy practices of any third-party service before sharing personal information with them, as Faithful is not responsible for the privacy practices, content, or data handling of these services.
- Faithful does not provide services to children under the age of 13. If you are a parent or guardian and you are aware that your child has provided Faithful with personal data, please contact us to remove it.
- We may update this privacy policy from time to time in order to reflect changes to our practices or for other operational, legal, or regulatory reasons.