1. Operator and scope
The operator of Game Pulse is HeroCraft Ltd. Its headquarters address is Capital Center, 9th Floor, 2-4 Arch. Makariou III Avenue, 1065 Nicosia, Cyprus.
This policy describes the processing of information through the Game Pulse website, service accounts and Discord feedback integration, including the AI-assisted analysis of feedback collected through that integration. Game Pulse helps game teams review community feedback, identify recurring problems and topics, and investigate changes in player sentiment.
Discord's own handling of information is governed by Discord's Privacy Policy. A game publisher or community may also have a privacy notice explaining its use of Game Pulse and its handling of community information. This policy does not replace those notices.
2. Information processed
Discord community feedback
When a Discord integration is configured, Game Pulse retrieves messages from the selected channels using the Discord API and the access permissions granted to its bot. The information processed can include:
- Message text and text descriptions contained in message embeds.
- Discord message, channel, server and thread identifiers, where supplied by Discord; reply references and source links.
- Author identifiers, usernames and display names, and indicators that an author is a bot or system account.
- Message creation and edit timestamps.
- Attachment and embedded-media references and associated metadata, such as URLs, media type, dimensions and file size, where supplied by Discord.
Availability depends on Discord's API, the bot's permissions and the integration's configuration. The Discord connector described here polls configured channels; it is not a feature for collecting private direct messages. Messages that mention personal information can cause that information to be included in the feedback we receive. Avoid posting passwords, payment details or other sensitive information in feedback channels.
Service accounts
For Game Pulse service accounts, the service processes account identifiers, email addresses, names, organization membership, roles and project-access information. Passwords used for service authentication are stored as salted password hashes. Authentication and account operations also involve session and security information.
Website enquiries and technical information
If you submit the website's pilot enquiry form, the website sends your email address and selected page language to the Game Pulse service for delivery through its email gateway. The enquiry is used to communicate about your request. The form handler does not maintain a separate database of pilot enquiries; the resulting correspondence is held in email systems.
Website requests generate technical information in server logs, such as request time, requested resources, IP address and browser information supplied with the request.
The website uses Yandex Metrica to measure visits and interactions. Its configuration includes session replay, click maps and link tracking. It loads resources from Yandex and can use cookies and send visit, referral, device and interaction information to Yandex. The pilot email input is marked to exclude its contents from session-replay recording. See Yandex's Privacy Policy for Yandex's processing practices.
The website stores language and theme preferences in your browser's local storage.
3. How information is used
The Discord integration uses collected feedback and its context to:
- Display feedback and links to its source to game-team users with access to the relevant project.
- Organize messages and conversation context for review.
- Classify feedback by topic, sentiment and severity, identify recurring issues and group related feedback.
- Translate feedback, support search and generate summaries and AI-assisted answers about collected feedback.
- Support configured notifications and alerts for game teams.
Account information is used for authentication, organization and project access, and account administration. Technical information is used to operate the service, diagnose failures and support security. Website enquiry information is used to respond to enquiries, and website analytics are used to understand visits and interactions.
4. AI processing
Game Pulse uses existing AI models to process feedback. Depending on the operation, message text and relevant conversation or project context are sent to a model service to produce classifications, translations, summaries or answers. Message text can also be sent for the creation of numerical representations called embeddings, which support grouping and retrieval.
This is AI inference: existing models process an input and return a result. Creating an embedding or assigning a topic is not, by itself, training or fine-tuning a model. The feedback-analysis workflows described here are inference workflows, not model-training workflows. HeroCraft Ltd prohibits using Discord message content to train or fine-tune AI or machine-learning models within its own organization. This organizational policy permits inference and the creation of embeddings; it is not a claim about contractual guarantees from upstream providers.
AI requests are routed through a corporate AI gateway and, for configured operations or fallback processing, OpenRouter. Those services can route requests to underlying model providers. Processing is therefore not confined to Discord or to Game Pulse's own database.
AI request and response information can also be recorded in the service's diagnostic tracing system for investigating processing behaviour and failures. AI-generated results can be inaccurate and should be checked against the underlying feedback.
The description of inference in this policy is not a representation that every upstream provider uses a particular retention setting or has a contractual prohibition on using data for training. Upstream providers' handling of requests is governed by the terms and settings applicable to the services used.
5. Storage, access and recipients
Game Pulse stores copies of collected Discord feedback outside Discord in its PostgreSQL database. Stored information includes message text, associated author information and metadata. The service also stores derived analysis, embeddings and operational records. Diagnostic traces and database backups are additional copies that must be considered when handling information.
Game-team users who have access to the relevant Game Pulse organization and project can view feedback and analysis in the service. Application access uses authenticated sessions, organization membership and project-access checks. Operational administration also involves access to the infrastructure running the service.
Other systems involved in processing can include infrastructure and backup systems, the corporate AI gateway, OpenRouter and underlying AI model providers, diagnostic tracing, and configured notification delivery services. Website enquiries pass through an email gateway. Yandex receives website analytics information when its counter runs.
Message text and author identifiers are not necessarily anonymous merely because they originated in a community channel. Analyses and summaries can also contain quotations or information from the original messages.
6. Retention
Different information has different retention behaviour. A cleanup process uses a 30-day window for certain operational records, including raw ingestion events and AI-run records, with exceptions for records that must remain available to ongoing operations.
That operational cleanup does not delete all stored feedback after 30 days. Canonical feedback messages, author records, derived analysis and embeddings are not subject to a blanket 30-day automatic deletion rule. They can remain in the service beyond that period. Removing the bot or preventing further channel access does not itself erase information already stored in Game Pulse.
Diagnostic traces, email correspondence, website logs and backup copies have separate retention arrangements. A retention window for an operational table must not be understood as a guarantee that every copy of a message has been erased. In particular, deletion in Discord is not a guarantee of deletion from Game Pulse or its backups.
7. Controlling collection and raising privacy requests
Discord server administrators can stop the bot from retrieving further messages from a channel by removing its access to that channel, or stop its access to the server by removing the bot. These controls affect future access; they do not automatically delete previously collected information or cancel processing of information already collected.
Individual community members can opt out. Email info@game-pulse.pro with your Discord username or user ID and the name of the Discord server. After verifying the request, we add your Discord account to the excluded accounts of that community's Game Pulse project. Your messages are then excluded from Game Pulse analysis, topics, alerts and search. Messages you post later in a connected channel can still be retrieved by the connector, but they remain excluded from analysis.
You can also ask us to delete your Discord messages already stored in Game Pulse. After verifying the request, we delete them together with the analysis and embeddings derived from them. Existing database backup copies are not modified individually. Community members can also raise concerns with their community's administrators, including which channels are connected.
Send Game Pulse privacy enquiries, opt-out and deletion requests, and reports of issues or misuse of the integration to info@game-pulse.pro. Requests are reviewed after verification of the requester and the information involved. If your enquiry concerns a connected Discord community, identify the community and relevant messages using Discord identifiers or source links where possible. Do not send passwords, authentication tokens or unnecessary sensitive information. Your community administrator can also help identify the relevant Game Pulse project and raise the matter with the service operator.
You may ask about the processing of your information or raise a request concerning access, correction, deletion or future collection. Such a request is separate from removing information in Discord and may require verification of the requester and the information involved. Requests are handled manually by the Game Pulse team, and verified requests are carried out promptly.
Browser controls can be used to remove local-storage preferences or manage cookies. Browser or network tools that block Yandex resources can prevent its counter from loading; that is separate from Game Pulse's Discord integration.
8. Policy changes
The policy published at https://game-pulse.pro/policy will describe the version in effect when it is published. Changes to integrations, AI processing or privacy controls may require updates to this policy. Review the published policy when deciding how to use the website or connect a community.