How Hytale Character Recipes handles account data, submissions, contact messages, analytics, and screenshot storage.
2026/03/19
Hytale Character Recipes is a fan-run archive for Hytale avatar recipes, screenshots, and community-submitted variations. This Privacy Policy explains what data we collect, why we collect it, how long we keep it, and what third-party services are involved when you use the site.
This policy is written for the actual way the site works today. It is not a generic template. If the archive changes how it stores screenshots, submissions, analytics, or account data, we will update this page.
The site is operated under the Hytale Character Recipes brand. If you need to ask a privacy question, request removal, or report a problem with a published page, use the contact method listed on the Contact page.
We may collect the following categories of data:
We use data for a small number of concrete reasons:
We do not sell your personal information as a data broker. We also do not claim ownership over your underlying character concept just because you submitted a recipe or screenshot.
If you create an account, we store the information required to authenticate you and keep your session active. That can include your email address, hashed or provider-managed credentials, session tokens, and basic account profile fields. We use this data to:
If you delete your account, related records may be removed or retained where necessary for fraud prevention, moderation history, or legal compliance.
If you submit a preset, the site stores the JSON, screenshot reference, and editorial status needed to review the submission. Approved submissions may become public recipe pages or public variations tied to an existing recipe.
We may retain moderation history so the archive can keep track of what was submitted, reviewed, edited, approved, or rejected. If a submission becomes public, some of the information you provided may become visible on the public page, including:
If you later request removal, we review that request case by case, especially where copyright, trademark, impersonation, or image-use issues are involved.
If you contact us through the public form, your message is sent to the archive operator through our email provider. We keep the contents of that message for the time needed to respond, investigate the report, and maintain moderation context. Messages involving takedown, copyright, or safety issues may be retained longer where necessary to document what happened and how it was resolved.
We use analytics and related event tracking to understand how the archive is used. That can include page views, recipe opens, submission success events, and similar product signals. We use this information to improve content quality, discover weak pages, and measure whether the public archive is actually helping visitors.
Analytics data is used in aggregated or operational form. It is not used to build or sell personal advertising profiles outside the normal behavior of the analytics and advertising systems already running on the site.
The site may use cookies or similar storage for:
You can read more about site-side cookie categories on the Cookie Policy page.
Depending on how the site is configured, third-party services may process limited data on our behalf. These can include:
Those services receive only the data needed to perform their role. They also operate under their own privacy and security commitments.
We keep data for as long as it is reasonably needed to operate the archive, review submissions, investigate reports, and maintain security or moderation history. Different data types may be kept for different periods:
Where deletion is requested, we will remove or anonymize data when feasible unless we need to retain part of the record for legal, security, or moderation reasons.
You can contact us if you want to:
To help us process the request faster, include the exact page URL and enough context to identify the account or submission involved.
We take reasonable steps to protect the archive and its data, including authentication controls, hosted infrastructure protections, and moderation workflows. No website can promise perfect security, but we try to limit access to the people and systems that actually need it.
If the site changes how it handles accounts, submissions, screenshots, analytics, or advertising, we may update this Privacy Policy. The published date at the top of the page shows the latest effective version.