Privacy at Hynoe
This notice covers hynoesmp.com, the Hynoe Outpost browser game, and this website's community features. It does not replace the notices for separate Hynoe products or third-party services.
1. Browser storage and community identity
The game and guide use browser storage, including localStorage, for progress, preferences, a callsign or local player identifier, and related state. Community features also keep a display name and authentication session in browser storage. A pseudonymous or “anonymous” sign-in means an email address is not required; it does not mean the service holds no information about you.
When you join the community, the site can create an authentication user identifier and a server-side profile containing your display name, normalized display name, and avatar seed. A returning session can reconnect automatically on pages that load the community panel.
2. Global Chat, presence, reactions, and reports
Messages, replies, display names, reactions, and message times are shared community content. Treat Global Chat as public, not a private conversation. Other participants may copy or capture what you post. Do not submit real names, contact details, private identifiers, or another person's information unnecessarily.
The service stores community profiles, messages, reactions, and moderation reports. While connected, presence can include your community user identifier, display name, current page path, and last-seen time. Report submissions include the reported message, a reason, optional details, and the reporting user's identifier; they are submitted for moderation rather than as ordinary chat messages.
2a. Minecraft Chat connects the website, Discord, and the game
Minecraft Chat is a separate public channel. It displays messages from the connected Discord minecraft-chat channel. Posts sent from its website composer are relayed to Discord and the Minecraft server, where other participants can see and copy them. Choose Global Chat for website-only public discussion; Ask Hynoe is the separate help conversation.
Sending through Minecraft Chat uses your community session for authentication and sends the message and a request identifier to the Hynoe bridge service hosted on Render. Connected services can keep their own message history and technical logs. Clearing a website conversation or browser storage does not remove Discord messages, Minecraft logs, or copies held by other participants.
3. Ask Hynoe is server-processed help
Asking a question sends the question, a limited recent conversation history, and the page path to Hynoe's server-side help service. The request is associated with your community session. The service records request metrics and help-feedback records. Where model-assisted answers are configured, a model provider may also process the request to generate an answer.
“Private” means not posted to Global Chat. It does not mean offline-only, anonymous to the operator, end-to-end encrypted, or free of service-side records. Do not enter passwords, access tokens, payment details, medical information, or other sensitive information.
Clear conversation removes the conversation displayed in the current page. It does not send a server-side deletion request. Closing a page or clearing browser data likewise does not erase server records. See Data deletion.
4. Optional leaderboard publication
The Hall of Legends can load public rankings. Viewing the board is different from publishing a score. The score-publication control is optional and off by default. When enabled, it can send a random local player identifier, callsign, and gameplay metrics for ranking. Turning it off stops future score submissions but does not automatically remove an existing record.
5. Providers and technical requests
Hosting, DNS, security, content-delivery, and backend providers may process IP addresses, request times, requested URLs, browser information, and technical logs needed to deliver or secure the service. Supabase provides the configured community authentication, database, realtime, and server-function infrastructure. Cloudflare verification may be used when configured. No government ID, biometric scan, or contact list is required by the current local-game interface.
YouTube video features use YouTube services, including the embedded player/API. Loading or using an embedded player may allow Google/YouTube to process device, network, playback, cookie, or similar information and serve content or advertisements under the Google Privacy Policy and YouTube Terms of Service. A privacy-enhanced player is not a guarantee of zero data processing.
Links to Discord, Streamlabs, Modrinth, and other independent services are governed by those services' own practices. Reading this privacy page does not initialize the community panel, a model request, or a video player; ordinary hosting requests still occur.
6. Uses, retention, and your choices
Information is used to operate the features you use, maintain community history and identity, generate help responses, rank voluntarily submitted scores, address reports, and protect the service. Local data generally remains until you or your browser remove it. Community and help records are server-side data; do not assume they expire when you close the browser or press Clear conversation.
Retention and removal of server records depend on the record, the service's operational needs, and applicable legal or security obligations. This notice does not claim that a fixed automatic deletion schedule or universal self-service account-erasure feature is already implemented. Requests concerning Hynoe-controlled records can be made through the private route below. Any necessary retention after a deletion request must be assessed under applicable law.
7. Children and age-related safeguards
Local-only gameplay is separate from posting information online, but even a page visit may involve technical requests to service providers. The planned initial email cloud-save account remains an 18+ feature, separate from the current community session. An age statement is not a parental-consent mechanism, and omitting an email field does not supply parental consent.
Do not submit a child's personal information through community tools. A parent or guardian who believes a child's information was collected should contact Hynoe privately so the record and any required restriction, deletion, or consent response can be assessed. This notice does not authorize collection that is otherwise prohibited by applicable children's privacy law.
8. Privacy requests, security, and contact
Depending on applicable law, you may have access, correction, deletion, objection, restriction, or portability rights. See Data deletion for the difference between local controls and a service-side request.
Use the official Hynoe Discord linked from the home page to request a private conversation with the owner or moderation team. Do not place private identifiers, credentials, a child's information, or security details in a public channel or GitHub issue. Only information reasonably necessary to locate a record and verify the requester should be requested. A separate, publicly verified privacy-contact inbox and complete account-rights workflow remain necessary before expanding account services; they are not claimed to exist here.
No service can promise perfect security. A public configuration key is not permission to access other users' records. Suspected vulnerabilities should be reported privately, not exploited.
9. Changes and scope
The date above identifies this notice version. Material changes to processing require an updated notice and any notices or consent required by applicable law. These disclosures describe website features; they do not certify every Hynoe service, server, platform integration, or jurisdiction as legally compliant.