Privacy policy

Effective November 3, 2026. Beta version, written to be read.

The short version

• About players of games that use Heartbeat: we process numeric platform ids and gameplay events on behalf of the game's developer. No names, no emails, no chat, no device fingerprints, no ads, no resale, no cross-game profiles.
• About you, the developer: your email, a password hash, and billing details handled by our payment processor when paid plans launch.

Player data

Game developers using Heartbeat send us gameplay telemetry from their own games: session start and end, progression milestones, purchases, performance samples, and custom events they define. Players are identified only by the numeric id their platform assigns (a SteamID or a Roblox userId). The ingest API rejects requests that put usernames or emails in player fields.

This data is used solely to show that game's developer their own analytics. It is never combined across games, sold, shared with advertisers, or used to profile players.

Retention follows the developer's plan (30 days of raw data on Free, longer on paid plans). Developers can purge a game's data at any time; purges are permanent.

If you are a player and want data about you removed from a game's analytics, contact that game's developer, who can delete your rows, or email us and we will help route the request.

Developer accounts

During the current beta, accounts are stored in your own browser and nothing account-related reaches our servers. When hosted accounts launch, we will store your email, a salted password hash, and your configuration, and this policy will be updated before that happens.

Cookies and tracking

The website uses no advertising trackers and no third-party analytics. The dashboard uses browser storage to keep you signed in and remember your settings.

Your rights

Ask us what we hold about you, ask for it to be corrected or deleted, at hello@gameheartbeat.dev. We answer within 30 days, usually much faster.

Changes

Material changes to this policy are announced on the changelog with the effective date above updated.