Hunters Guild
Hunters Guild privacy notice
Notice version: 2026-10-12. Effective date: October 12, 2026.
Surely Works LLC operates Hunters Guild and is responsible for the game information described here. This notice covers the game client, launcher, and online services. The studio website privacy notice covers these informational web pages.
Hunters Guild is in development and game accounts are for adults aged 18 and older. Development builds use Steam sign-in. Email, Epic Games, and Sign in with Apple are being prepared and are not yet publicly available; their planned handling is identified below.
Questions and requests about your information go directly to the studio operator at contact@surely-works.studio.
What we collect and how we use it
Information from sign-in and account actions
When you sign in through a supported platform, the client or sign-in flow sends authentication proof to our service. We verify it with that platform and receive its account identifier, such as your Steam ID. We use the verified identifier to find or create your game account. We do not ask for your Steam, Epic, or Apple password.
Our game service creates an internal account identifier and stores account roles, verified sign-in identifiers, and authentication session records. These let you access the game, authorize account actions, and recover the same characters and progress. Supported account-linking actions are intended to connect sign-in methods to the same game account.
Planned email sign-in collects the email address and password you enter. It will store a salted password hash, not a plaintext password. Verification and password reset use expiring, one-use links. Planned Cloudflare email delivery receives the recipient address and link to deliver the message, not your password. Planned Apple sign-in uses the verified Apple account identifier.
Information from play and messages
Your client sends gameplay actions and chat messages to the game service. We process characters, inventory, progression, and gameplay and match records to run the game and save your progress. Where legal documents require acceptance, we record the accepted version and time to document your agreement.
Chat messages and sender information are delivered to the intended recipients. The game does not keep a permanent server chat-history database; client scrollback lasts for the session. Other players can see or copy messages they receive. Copies you send to us in a support or privacy request become part of that correspondence.
When you email us, we receive your email address, message, and any attachments or account details you choose to include. We use them to answer you, investigate the issue, verify ownership when needed, and handle your request. These public pages do not take payments.
Information collected by online connections
Connecting to an online service exposes your IP address and connection endpoint to the receiving infrastructure. The game also measures latency and traffic and creates operational logs to maintain connections, diagnose faults, and investigate security or abuse. Server operational records can include match, session, or trace identifiers used to connect events in an investigation.
Optional client error reports
Client error reporting is off by default. If you enable it and a reporting service is configured, the client sends reports to Sentry containing limited error categories, code locations, and build or environment information. The client filters those reports to exclude chat, account and character identifiers, credentials, arbitrary log messages, and local file paths. The receiving service still processes connection information, so these reports are not described as anonymous.
Turning the setting off stops new client reports and discards pending reports. It does not erase reports already received or control the server operational records needed to provide online play.
Planned Epic Games sign-in
Epic sign-in is being prepared with Basic Profile permission. This permission covers the Epic account ID, display name, language, and linked-account display names. The prepared integration uses the Epic account ID to verify identity; it does not read or store the other profile fields. It requests no Friends List or Presence permission.
The planned flow receives an authorization code after you approve sign-in, exchanges it with Epic through our service, and verifies the resulting authentication proof. Once enabled, we will store the verified Epic account ID as a linked sign-in identifier with your internal game account ID. We will use it to create or find your game account, authenticate access, and link Epic sign-in to an existing account when you request it. Authentication codes and tokens are used for sign-in verification, not as player profile information.
This describes our handling of information for Hunters Guild. For Epic's own services, consult Epic's privacy notice. We will update this notice before enabling a change that collects or uses additional Epic profile information.
How long information is retained
Retention follows the purpose of each category. During development, account and authentication databases do not have a general automatic deletion schedule based only on the age of a record.
- Account identifiers, linked sign-in identifiers, credentials, and saved game progress remain while the game account is maintained, including during inactivity. On a verified deletion request, the studio operator removes account and progression records and linked identifiers that are no longer needed. Any information needed for an unresolved security matter, claim, or legal obligation is identified when we respond.
- Authentication sessions and verification or reset records have limited validity. One-use links stop working after use; sessions and other credentials stop working on expiry or revocation. These limits do not automatically erase every stored record. Stored records and replay-prevention information support account security and investigation while the account is maintained. On deletion, we remove records no longer needed and explain any security records that must remain.
- Chat payloads are held for delivery and client session scrollback, rather than a permanent server history. Copies retained by recipients are outside our control; copies sent to us follow correspondence retention.
- Connection records, operational logs, and received diagnostics are retained for service operation and active fault, abuse, or security investigations. We do not currently apply a fixed age-based deletion schedule to records we control. On a verified deletion request, the operator reviews these records and removes information no longer needed, explaining any unresolved matter or legal obligation. Provider-held copies follow the receiving service's retention settings; we explain relevant provider limits in our response.
- Support and privacy correspondence remains while handling the request and documenting the action taken. On a verified deletion request, the operator manually reviews and removes correspondence no longer needed, explaining any continuing dispute or legal recordkeeping need. There is no fixed age-based deletion schedule.
Deleting active records may not immediately remove copies from backups or operational records. We explain the relevant retention limits, any necessary exceptions, and the scope of deletion when responding to a verified request. Credential expiry does not itself purge every copy of a stored record.
Access, correction, export, and deletion requests
Email contact@surely-works.studio to request access to, a copy of, correction of, or deletion of your game information. The studio operator handles requests directly. Include the sign-in method and enough account information to help locate your records. Do not send passwords, authentication codes, or reset links.
We verify that the account or information is yours before providing information or making changes. We then arrange the requested access, copy, correction, or deletion and explain any information that must be retained for an unresolved matter or legal obligation. Account and data requests are handled manually; there is no public self-service deletion or export flow at present. Depending on your location, you may have additional privacy rights or the right to complain to your local data protection authority.
Do not create a game account if you are under 18. Contact the same address if you believe someone under 18 has created an account, or if you need help changing linked sign-in methods.
Changes to this notice
We update this notice when features or services change how game information is handled. The effective date above identifies the current version. New collection or uses will be described before those changes become available.