BOWUR GAMES
← Back to Riftward

RIFTWARD

Riftward Privacy Policy

How Riftward Alpha 0.1.11 and its pages on bowur.com handle information in the browser and native clients, including solo play, online lobbies and matches. This notice does not announce store availability.

Updated 29 October 2026

Email support · support@iteleport.net

Who is responsible

Riftward is provided by BOWUR GAMES. For support and personal-data requests, email support@iteleport.net.

Local profile, preferences and session credentials

Nickname, language, audio volume, minimap settings and custom item builds are kept locally in browser storage or the native app preferences. The website also remembers your language. No email address, password or social sign-in is required to play. These settings are not an email-recoverable account or a game-provided cloud backup.

The game saves a resume credential separately for each server address so it can reconnect to the appropriate session. On macOS and iOS, native builds use Apple Keychain; Android native builds use storage protected by Android Keystore. Web, Linux and Steam Deck currently use local browser/app preference storage for this credential. Older preference-based credentials can be migrated to protected native storage after the new credential is accepted and saved. Do not publish or send these credentials to support.

Connection and online play

With a saved nickname, the game connects to our multiplayer server when it opens, including in the menu; selecting solo play does not guarantee that no connection exists. The connection exchanges your nickname, generated player identifier and resume credential, and measures latency. Online play also sends lobby and invitation identifiers, readiness, hero choices, game commands and match messages so the server can run and synchronize the game.

Other participants can see your nickname and the lobby or match information shared with them. Match chat is delivered to connected participants in the match, including opponents. Do not treat it as a private team channel. Use a nickname rather than personal contact details. Do not share private information in chat or publish your session credential; an invitation link gives access to its lobby.

Website logs and support

Requests to the site and game can produce technical logs containing IP address, time, requested URL, response status, transferred size, referring page and browser/device information. Server errors can also produce diagnostic records. We use these for delivery, troubleshooting and protection against abuse.

If you email support, we receive your email address, message and any attachments you choose to send. We use them to handle your request. Screenshots and logs are optional; review them before sending and remove session tokens or unrelated personal information.

Purpose, providers and advertising

We process game-session information to provide the game you request. Where data-protection law requires a legal basis, this processing is necessary to provide that service; service security, fault investigation and support are based on our legitimate interests in operating a reliable game and answering requests. Legal obligations may require us to retain or disclose particular records.

Hosting and email providers process the information needed to run these services, potentially in countries other than your own. Relevant game information is shared with other players as explained above. The current game and website have no integrated advertising or third-party analytics SDK. We do not sell player information or use it for cross-site advertising.

How long information remains

Local preferences and session credentials remain until they are replaced or removed through the game, browser or platform storage controls. The game server keeps player sessions in memory, without a persistent player database. A disconnected session with no active match becomes eligible for cleanup after 30 minutes by default and may be evicted earlier when capacity is needed. Active matches support reconnect while their state remains available. Completed-match results can remain in memory under a shared size limit of 32 MiB by default; older retained results may be removed to stay within this limit. This is not a permanent match-history account. Restarting the server clears this in-memory state.

Recipients can retain a limited chat history in the running client memory and can copy or capture messages. The current server does not provide a permanent chat archive. Do not assume messages missed during a disconnect will be restored.

Website logs are configured for weekly rotation with four archived files. Diagnostic records follow server log management; records needed for an incident may be retained longer. Support correspondence remains while needed to resolve the request, follow up or meet legal obligations.

Your choices and rights

You can change your nickname and settings in the game. Clearing bowur.com site data can remove the browser profile, preferences and resume credential, prevent rejoining an active match and also erase local data for other games on the same domain. Native app preferences and protected credentials are separate platform stores; clearing browser data does not clear native app data. Removing ordinary preferences does not necessarily remove a credential saved in protected storage. Local deletion does not automatically erase server memory or messages already received by other players. We cannot recover a local-only profile through email or password.

Email support@iteleport.net to request access, correction, deletion, restriction, objection or portability where applicable law provides these rights. We may need limited information to identify the relevant records and verify your request. You can complain to your competent data-protection authority.

Changes

We will update this policy when the game’s data handling changes. The date above identifies this version.