Scope and responsibility
Infernis Games operates this website and its restricted staff and QA workspace. References to “Infernis,” “we,” “us,” and “our” mean Infernis Games. This policy does not replace the policies of a separate game service or provider, including Discord, GitHub, OpenAI, YouTube, FormSubmit, email or hosting services. Their terms and privacy practices also apply when information reaches them.
The portal’s terms and privacy guidance and staff confidentiality agreement explain authorized handling of internal information. A label saying “staff” is an access rule, not permission to send somebody’s private details everywhere.
Information we collect
Information you choose to send
When you use the contact form, we receive your name, email address, inquiry type, message, and any project details you include. When you email us directly, we receive the message, attachments, headers, and contact details needed to reply. Please do not send passwords, payment card numbers, security keys, or confidential source code through an ordinary form.
Information collected automatically
Our host or security systems may record a limited technical log such as IP address, browser and device type, requested page, referrer, date, time, and basic error information. These records help us keep the site available, investigate abuse, understand broken links, and diagnose performance issues. We do not use advertising pixels, sell browsing histories, or build behavioral advertising profiles from this website.
Cookies and similar technologies
Public pages do not require a login or advertising cookies. The staff portal uses necessary session and security cookies for authentication, request protection and access controls. Signing out or clearing cookies does not delete your account, reports or records. A hosting, security, form, or analytics provider may set a necessary cookie or process a similar technical signal to deliver its service. Browser settings can limit cookies, although doing so may affect form or site functionality.
Staff and QA workspace
For approved accounts we keep identifying and access information such as names, email where supplied, Discord IDs and display details, relevant guild membership and roles, account status, permissions, staff/QA channel mappings, and linked Minecraft identity. We keep display, timezone, time-format and notification preferences. Birthday is optional: we collect month and day, not age or birth year; authenticated people with the relevant staff profile/calendar access can see it.
Workspace records may include onboarding and assignments, calendars, quizzes and results, documents and revisions, guide acknowledgments, comments, mentions, suggestions, bug reports, moderation evidence, applications and intake archives where those features are enabled. Guide progress and confirmations, policy versions and acceptance evidence, and security events support accountability. Administrators may manage authorized access and notification topics; a person with two roles may have access through either.
Bug reports, suggestions and evidence
Reports may contain your displayed submitter name, report title and description, server location, priority, status, comments, supporting links, screenshots and recordings. Submit only what helps reproduce or investigate the issue. Crop out private messages and redact credentials, access tokens, addresses and unrelated player information. A useful bug report is not a data dump.
Uploaded attachments are stored privately in the panel with authorization checks and encrypted file storage. Report evidence is viewed from its record rather than offered as a general searchable photo library. That does not make it anonymous or prevent authorized reviewers from downloading it. Browser video support varies; a download may work even when a preview does not.
Authorized bug review and approval can export report text, submitter attribution, comments and supported images to the configured GitHub repository. Correspondence and issue status may be brought back into the panel. Authorized Discord delivery can copy report images and send report summaries, updates and protected links. GitHub and Discord access follow their repository/channel permissions, not the panel’s permissions. A private panel link alone does not grant someone access; an image already copied elsewhere is a separate copy.
Direct attachments currently have a 100 MB combined limit, with smaller image limits shown on the form. For a larger non-sensitive recording, we recommend a YouTube Unlisted supporting link. Unlisted is not private: anyone with the link may watch and forward it. Use an approved private route for confidential evidence instead. External images and video links may contact their host when opened or displayed, and can expire or stop working.
Notifications, changelogs and AI assistance
Configured bot and webhook workflows can deliver onboarding, tasks, tags, quiz feedback, suggestions and bug updates to their approved destinations. Bug-update mentions are off by default and can be enabled in your profile; opted-in mentions are rate-limited. Administrators may manage notification topics. Muting a topic or a mention does not remove your records, change access, or stop necessary security/monitoring events.
Panel-visible fixes merged into the configured game repository may be summarized in the QA Discord changelog, including the change title, description and displayed contributor attribution. The label and channel settings define that audience; they are not a promise that the content is safe to share publicly.
When enabled and used, AI assistance may send your request and relevant permitted text or record excerpts to the configured OpenAI API to produce suggestions, drafts or reviews. Provider processing terms apply; the panel does not promise zero retention by a provider. AI output can be wrong. Do not submit secrets, unrelated personal data or confidential material outside the approved feature and purpose. Humans remain responsible for reviewing and approving consequential actions.
How we use information
We use submitted information to respond to inquiries, evaluate potential collaborations, discuss project work, provide support, prevent spam and abuse, maintain business records, improve the website, and meet legal or accounting obligations. We may use a message internally to understand what visitors need from the studio, but we do not add you to a marketing list merely because you contacted us.
Our legal bases, where applicable, are responding to your request, taking steps at your request before a potential engagement, pursuing legitimate interests such as security and business administration, complying with legal obligations, and obtaining consent where consent is specifically required.
Retention and deletion
We retain an inquiry for as long as it is useful to answer the request, evaluate or perform a project, maintain a reasonable business record, resolve a dispute, prevent repeat abuse, or satisfy legal, tax, and accounting requirements. Retention depends on the nature of the conversation, not an automatic promise that every message is deleted on a fixed day.
Closing a bug, completing a task, removing access or muting notifications is not an automatic deletion instruction. Shared work, evidence, revision history, guide and agreement acceptance records, delivery receipts and audit records may remain for operations, security, disputes or required recordkeeping. The portal does not promise a fixed automatic purge for all attachments or reports. Third-party exports and recipients’ copies are separate: we may need to coordinate corrections or deletion, and cannot promise to recall every download, forwarded message or external link.
You can ask us to delete a message, correct inaccurate details, or explain what we still retain by emailing contact@infernisgames.com. We may keep a limited record when deletion would interfere with legal obligations, a dispute, security investigations, or legitimate recordkeeping.
Your rights and choices
Depending on where you live, you may have rights to request access to personal information, correction of inaccurate information, deletion, a copy in a portable format, restriction or objection to certain processing, and withdrawal of consent where processing relies on consent. You may also have the right to complain to a privacy regulator.
To make a request, email contact@infernisgames.com with enough detail for us to understand the request. We may ask for reasonable verification before disclosing or changing information. We will not discriminate against you for making a privacy request, although certain requests may be limited by law or by our need to retain a record.
Security
We use reasonable administrative, technical, and organizational measures for the website and portal. Sensitive records and files use encryption and authorization controls, but not every piece of operational metadata is encrypted and authorized exports are processed by their destination services. No internet transmission, email message, hosted form, or storage system is guaranteed to be perfectly secure. If you believe you submitted sensitive information by mistake or see suspicious activity connected to the site, contact us promptly so we can investigate and take appropriate steps.
Children’s privacy
This website is not directed to children under 13, and we do not knowingly collect personal information from children under 13. If you believe a child has submitted personal information, email us and we will review the request and delete information when legally appropriate.
Changes and contact
We may update this policy when the website, studio, or service providers change. The effective date at the top identifies the current version. Material changes will be reflected in a revised date and, where appropriate, a more visible notice.
Privacy questions, requests, and concerns can be sent to contact@infernisgames.com. Infernis Games is based in Denver, Colorado. This policy is intended to explain our practices clearly, but it is not legal advice and does not create a contract beyond rights required by applicable law.