Tithe Privacy Policy | Bitspire Studio

1. Scope and who is responsible

This Privacy Policy explains how Bitspire Studio handles personal data. In this policy, “Bitspire”, “we”, “us”, and “our” mean Bitspire Studio.

This policy applies to these services:

Tithe, including test, preview, early-access, and release versions of the game;
the official Tithe and Bitspire Studio pages at bitspire.studio, including Steam sign-in and playtest access;
Tithe multiplayer, voice chat, text chat, lobbies, achievements, and related online functions; and
the Tithe Discord application and integration, including Rich Presence, invitations, and join functions.

In this policy, “Game” means Tithe. “Site” means the official pages at bitspire.studio. “Discord Integration” means the Tithe functions for Discord. “Services” means the Game, Site, online functions, and Discord Integration together.

Bitspire is the data controller when it decides why and how it processes personal data.

Controller: Bitspire Studio
Privacy email: bitspiredev@gmail.com
Website: bitspire.studio

Steam, Discord, and other platforms are separate controllers for some processing. In player-hosted multiplayer, the host and other players receive some data directly. Bitspire does not operate a central gameplay server for these sessions.

2. Summary

Tithe mainly uses local storage and peer-hosted multiplayer.

The Game stores saves, settings, character files, local achievements, screenshots, and a persistent multiplayer identifier on your device.
During multiplayer, the Game sends necessary player, gameplay, text-chat, and voice data to the host and other players.
The Game processes voice in real time for proximity chat. The inspected build does not intentionally record ordinary voice chat or send it to Bitspire for storage.
The inspected build keeps ordinary text chat in memory. It shows up to 100 recent lines. It does not intentionally write these lines to a Bitspire chat database.
The Services use Steam for Site sign-in, playtest access, lobbies, network relay, identity, persona information, and achievements.
When you enable the Discord Integration, it sends limited live activity data to Discord. Discord uses this data for Rich Presence, invitations, and joining.
Bitspire does not sell personal data.
Bitspire does not use personal data for third-party behavioural advertising.
Bitspire does not use ordinary chat or voice data to train artificial-intelligence models.

3. Information that the Game handles

3.1 Information on your device

The Game creates or stores this information on your device:

a random persistent user identifier for multiplayer reconnection;
your chosen player name, appearance, colours, cosmetic items, custom markings, and generated character portrait;
save data, such as progress, items, environment seed, actor state, game time, achievement progress, and cheat status;
local achievements and cosmetic unlocks;
graphics, audio, control, accessibility, microphone, and input-device settings;
screenshots that you request in the Game;
optional developer performance captures or audio-reference recordings that a specific development tool starts; and
diagnostic output from the game engine or operating system.

This data usually stays on your device. It can leave your device if you share a file, a platform synchronises the data, or a multiplayer function sends part of it. If you uninstall the Game, some save or screenshot files can remain.

3.2 Multiplayer identity and character data

When you host or join multiplayer, the Game can process and share this data in the session:

your temporary peer ID and persistent random user identifier;
your Steam ID when you use Steam multiplayer;
your chosen player name;
your character appearance, custom markings, and portrait;
your assigned player colour;
your connection, host, spectator, alive, and speaking status; and
data that reconnects you to an interrupted session.

The host keeps this data in memory during the lobby or game session. Other players receive the data that they need to show players and the roster.

3.3 Gameplay and session data

The host and players process gameplay data to synchronise the game. This data can include position, movement, interactions, health, inventory, held items, world state, map, weather, random seeds, objectives, match results, distance, damage, extracted item value, death status, and cause of death.

The Game uses this data to operate the session. It can show the data in the roster or round summary. The inspected build does not intentionally upload ordinary session data to a central Bitspire gameplay database.

3.4 Text chat

If you use text chat, the Game sends your player name, persistent user identifier, message, chat channel, and approximate in-game position to the players. The Game uses this data for nearby chat, spectator chat, and local mute settings.

A text message can contain up to 150 characters. Each running client keeps up to 100 recent lines in memory. The inspected build does not intentionally save ordinary chat history to disk or to a Bitspire server. Other players receive messages in real time. They can capture them with external tools.

3.5 Voice chat and microphone data

Tithe uses microphone access for proximity voice chat and the microphone setup meter. You can use an open microphone, push-to-talk, or toggle mode. You can mute your microphone in the Game. You can also deny microphone permission in your operating system.

When voice transmission is active, the Game does these actions:

It captures microphone audio on your device.
It temporarily buffers approximately 200 milliseconds of audio. This buffer helps to prevent clipped speech.
It measures the audio level for the activation threshold and setup meter.
It encodes speech as Opus voice packets.
It sends the packets and limited in-game acoustic data to the host.
The host sends the data through the session.
Each receiving client applies spectator and mute rules before playback.

The acoustic data describes the sound environment in the Game. It can describe an enclosure or room effect. It does not describe the physical location or acoustic profile of your real room.

The inspected build does not intentionally record ordinary voice chat to disk. It does not send ordinary voice chat to Bitspire for storage. A development audio tool can record the Game’s main audio output. This tool operates only when a command-line option starts it. Other players can record a session with external tools. Bitspire does not control their recordings.

Your voice can reveal sensitive information. Do not say or type information that you do not want other players to receive.

3.6 Network information

For local network play, the Game broadcasts the host device name on the local network. It shows the sender’s local IP address to clients that search for sessions. During a direct connection, a host or peer can receive IP addresses and connection data.

For Steam multiplayer, Steam networking and relay services process connection and lobby data. Valve policies apply. A relay can reduce direct IP exposure. Bitspire does not control the Steam network design.

4. Discord Integration

When you enable the Discord Integration and permit Discord activity sharing, Tithe can send live activity data to the Discord client or service. The intended Rich Presence data is limited to:

that you are playing Tithe;
a general gameplay state or area, such as a lobby or named map;
the session start time or elapsed time;
the current and maximum party size;
whether the session is joinable; and
a party or join secret for an invitation, Ask to Join action, or Join action.

The Game can also receive limited Discord account data that the integration needs. The final functions and permissions determine this data. It can include your Discord user ID, display name, avatar, authentication status, and invitation or relationship events.

Tithe will not request or receive your Discord password through Rich Presence. It will not receive your private messages, server-message history, or voice-call contents through Rich Presence.

Other Discord users can see Rich Presence according to your Discord privacy and activity settings. Treat a join secret as a temporary access credential. Tithe uses it only to connect an invited or permitted user to a session.

Bitspire does not intend to keep a separate server history of your Discord Rich Presence. Tithe updates the activity while the Game operates. It clears or expires the activity when the integration disconnects. Discord separately processes and can keep data under its Privacy Policy.

You can change activity visibility in Discord settings. You can close Discord, disconnect the integration if that control is available, or play without it. If you disable the integration, Discord Rich Presence, invitations, and joining might not work. You can still play offline.

Before Bitspire adds more Discord permissions or data, it will update this policy. Bitspire will get consent when the law requires consent.

5. Steam and the Site

5.1 Steam sign-in

The Site uses Steam sign-in to confirm your Steam identity. After sign-in, the Site and its Supabase authentication functions can process:

your Steam ID and persona name;
your Steam profile and avatar URLs;
public Steam profile data that the sign-in and display process returns;
whether your Steam account is on the Tithe playtest list;
whether Tithe is available through Steam and whether downloads are enabled; and
a Bitspire session token that keeps you signed in.

The Site stores the session token in browser local storage. It temporarily stores the sign-in return path in session storage. When you log out, the Site removes the token from browser storage. It also asks the authentication service to invalidate the session. You can clear stored Site data in your browser settings.

The Site does not receive your Steam password. Steam handles your credentials and returns an authentication result.

5.2 Playtest access and downloads

The Site compares your authenticated Steam ID with the Tithe access list. The result allows or denies access. For an approved account, the Site can provide a private build link or Steam link. If you think the result is wrong, ask Bitspire for a human review.

The Site can send an approved user to Steam, Google Drive, or another authorised distributor. The provider receives the usual data when you follow a link or request a download. Its privacy policy applies.

5.3 Device and log data

The Site estimates your operating-system family in your browser. It uses the estimate to suggest a compatible build. Your browser provides platform, user-agent, and touch data for this local estimate. Bitspire does not intentionally send the estimate to its authentication service only to show this suggestion.

Hosting and backend providers can process request data. This data can include an IP address, user agent, request time, URL, response status, and security or error log. GitHub Pages hosts bitspire.studio. Supabase hosts the authentication and access functions.

The Site uses browser local storage and session storage for authentication and navigation state. It does not currently use third-party advertising cookies or behavioural analytics. If this changes, Bitspire will update this policy. It will also provide cookie or consent controls when the law requires them.

6. Steam functions in the Game

When Steam is available, the Game can use it for:

Steam initialisation and account availability;
your persona name and Steam ID;
public and friends-only lobbies, lobby discovery, lobby names, lobby IDs, ownership, invitations, and join requests;
Steam peer-to-peer networking and relay;
achievement status and updates; and
distribution, updates, purchases, and platform support.

People who search for Tithe lobbies can see public lobby names. The default lobby name can use the host’s Steam persona name. Local network discovery can use the host device name. You can edit the lobby name before you host. Do not put personal data in a lobby name or player name.

Valve processes Steam data under the Steam Privacy Policy and Steam Subscriber Agreement.

7. How we use information and our legal bases

Data-protection law can require Bitspire to state a lawful basis. Bitspire uses personal data for these purposes and bases:

To provide the Services. Bitspire uses data to perform its contract with you. This includes Steam sign-in, access checks, multiplayer identity, synchronisation, chat, Discord functions, and support.
To follow your choices. Bitspire uses consent when the law requires it. This can apply to microphone permission, optional Discord functions, and future optional processing. You can withdraw consent at any time. This does not change processing that occurred before withdrawal.
To secure and improve the Services. Bitspire has legitimate interests in access control, fault diagnosis, user and system protection, term enforcement, compatibility, and performance. Bitspire balances these interests against your rights. It does not use this basis when your rights override its interests.
To meet legal duties. Bitspire can process data for a valid legal request, consumer law, applicable tax or accounting duties, and legal claims.
To protect vital interests. Bitspire can process data during a rare emergency with an immediate risk to life or safety.

The law does not usually require you to provide a player name, microphone audio, Steam data, Discord data, or the other data in this policy. However, a function can need some data. Steam identity is necessary for Steam sign-in and lobbies. Multiplayer needs network and player data. Voice chat needs microphone data. Rich Presence needs activity data. If you do not provide necessary data, that function might not work. Other parts of Tithe can remain available.

9. Peer-hosted sessions and other players

In peer-hosted multiplayer, the host and players receive data directly from your Game client. Bitspire usually cannot control how another player uses data that they receive. Examples are a player name, message, voice, portrait, screenshot, and IP address. Other players can be in countries with different privacy laws.

Use the mute and host-removal tools when necessary. Use names and portraits that do not identify you. Do not disclose sensitive or confidential information in multiplayer. You can report serious misuse under the Terms of Service. Bitspire might not have a copy of the related chat or voice data.

10. Retention

Bitspire keeps personal data only for as long as it reasonably needs the data. Security, disputes, and legal duties can affect the period.

Local Game files stay on your device until you delete or reset them, or the operating system removes them. Some files can remain after you uninstall the Game.
Ordinary session identity and gameplay data in memory usually clears when the host closes the lobby or the Game process ends.
Each client keeps up to 100 recent text-chat lines in memory. The inspected build does not intentionally keep them after the process ends.
The Game buffers and sends ordinary voice audio in real time. Bitspire does not intentionally keep ordinary voice history. The Game overwrites the short buffers during use or when processing stops.
Discord Rich Presence exists while the Game and integration are active. Bitspire does not intend to store a separate history.
A Site session token stays in browser local storage until logout, expiry, invalidation, or manual deletion. Server session records remain until expiry or invalidation. Bitspire can keep limited security logs for longer.
Bitspire keeps Steam identity and playtest-access records while it needs them for the playtest, distribution, security, and support. Bitspire deletes or anonymises the records when it no longer needs them, unless the law requires a longer period.
Bitspire keeps support and enforcement records while it needs them for the request, safety, the Services, legal rights, and legal duties.
Provider settings and Bitspire operational needs determine the retention period for hosting, security, and backend logs.

Bitspire can preserve data that relates to a security incident, dispute, or legal duty. It can keep the data until the issue ends and the applicable legal period expires.

11. Security

Bitspire uses reasonable technical and organisational controls for the Services. Current controls include HTTPS, a restrictive content-security policy, limited domains for profile and avatar links, scoped session tokens, private-build access checks, input and packet limits, and local mute controls.

No system or transmission is fully secure. A peer-hosted session gives the host and players access to session data. Bitspire cannot guarantee the security of another player’s device. Secure your platform accounts. Use care when you join an unknown host. Do not share a session token, join secret, or private download link.

12. International data transfers

Bitspire, other players, and the providers in this policy can process data outside your country. These countries can have different data-protection laws.

When the law requires a transfer safeguard, Bitspire will use a lawful safeguard. This can include an adequacy regulation or decision, approved contract clauses, or another permitted method. Contact Bitspire for information about safeguards for data that Bitspire controls.

Steam, Discord, Supabase, GitHub, Google, and other separate providers explain their transfer arrangements in their privacy information.

13. Your choices and rights

You can make these choices:

Play offline or do not join multiplayer.
Deny microphone permission, select an activation mode, or mute the microphone.
Mute another player’s chat and voice on your device.
Use a player, character, or lobby name and portrait that do not identify you.
Disable Discord activity sharing or the Discord Integration.
Log out of the Site and clear its local storage or session storage.
Delete local saves, character files, settings, screenshots, achievement data, and the random user identifier.
Use Steam and Discord controls to manage data on those platforms.

Your location determines your legal rights. Subject to legal exceptions, you can have a right to:

know if Bitspire processes your personal data and get a copy;
correct inaccurate or incomplete data;
ask Bitspire to delete data;
restrict processing;
receive some data in a portable format;
object to processing based on legitimate interests or direct marketing;
withdraw consent when processing uses consent; and
complain to a data-protection authority.

Your right to object

You can object when Bitspire uses legitimate interests for processing. Your objection must relate to your situation. Bitspire will stop the processing unless it has a compelling legal reason to continue or needs the data for a legal claim. Bitspire does not currently use personal data for direct marketing.

You can contact Bitspire at bitspiredev@gmail.com. Bitspire can ask you to confirm your identity before it acts. It will respond within the period that the law requires. Bitspire might not have Game data that stays only on your device or with other players. Bitspire will tell you when this applies.

Use the privacy tools or contact methods from Steam or Discord for data that those platforms control.

If you are in the United Kingdom, you can complain to the Information Commissioner’s Office. If you are in the European Economic Area, you can complain to the authority where you live, work, or think a violation occurred. In another country, contact your local privacy authority.

14. Children

The Services are not for children under 13. Bitspire does not knowingly collect personal data from a child under 13. A higher minimum age can apply in your country or on Steam or Discord.

If you are not a legal adult, use the Services only with permission from a parent or legal guardian.

If you think a child gave personal data contrary to this section, contact Bitspire at bitspiredev@gmail.com. Bitspire will investigate and delete the data when appropriate.

15. Automated decisions

The Site automatically checks if an authenticated Steam ID is on the Tithe playtest list. This check controls private-build access. It does not use behavioural profiling. A person maintains the access rules or list.

If you think the result is wrong, ask for a human review by emailing bitspiredev@gmail.com.

Bitspire does not otherwise use personal data for fully automated decisions that have legal or similarly important effects.

16. United States state privacy information

An applicable US state privacy law can give you rights. You can ask for access, correction, deletion, or portability. You can appeal a refusal. You can also use an authorised agent when the law permits it. Bitspire will not discriminate against you because you use a privacy right.

You can contact Bitspire at bitspiredev@gmail.com to exercise your rights.

Bitspire does not sell personal information. It does not share it for behavioural advertising or use it for targeted advertising. It does not knowingly sell or share the personal information of children. It does not use sensitive personal information to infer characteristics about you. Tithe uses microphone audio for the voice function that you select. Bitspire does not intentionally keep it as ordinary voice-chat history.

17. Third-party privacy policies

These third-party policies can apply:

Steam Privacy Policy
Steam Subscriber Agreement
Discord Privacy Policy
Discord Terms of Service
Supabase Privacy Policy
GitHub Privacy Statement
Google Privacy Policy, if Google Drive provides a download

Bitspire provides these links for convenience. Each third party is responsible for its policy and practices.

18. Changes to this policy

Bitspire can update this policy when the Services, Discord Integration, providers, or legal requirements change. Bitspire will publish the new policy and change the effective date.

If a change has an important effect on the use of personal data, Bitspire will give more notice or get consent when the law requires it.

19. Contact

You can send questions, requests, and complaints about this policy or Bitspire’s use of personal data to Bitspire.

Controller: Bitspire Studio
Privacy email: bitspiredev@gmail.com
Website: bitspire.studio