HackMan3D Control Deck uses a minimal first-party audience counter to understand whether the project is actually being used and to guide its development.
When audience measurement is enabled, the desktop application sends:
- a random installation identifier generated by the application;
- a random temporary identifier for the current running session;
- start, heartbeat and clean-stop events;
- an aggregate count of actions executed.
The identifier is not calculated from the computer and contains no name, email, account, serial number, MAC address or other hardware identifier. The server stores only its SHA-256 hash. It cannot reliably identify a person: two computers count as two installations, while multiple users of one installation count once.
Profiles, configured actions, application names, shortcuts, website addresses, icons and documents are never sent.
The data is used only to produce private aggregate project statistics: active instances, launches, action totals, new installations, installations seen over 30 days and total unique installations. It is not used for advertising, sold, shared with other projects or combined with external data. Only HackMan3D can access the private statistics endpoint.
Audience measurement is enabled by default and does not interrupt startup with a consent dialog. It can be disabled at any time in the desktop application's settings. Disabling it stops future events; the application continues to work normally.
Because the server never receives an identity or account, it cannot associate a stored hash with a named person. Removing the application's local settings also removes its random identifier; a later launch will then be counted as a new installation.
HCD Supporter activation is separate from audience measurement. When a member activates the optional monthly Ko-fi membership, Ko-fi sends the payment event to the HackMan3D service. The service stores only keyed hashes of the Ko-fi email address and transaction ID, the membership tier and its validity date. It does not store the payer name, message, amount, application profiles, configured actions or hardware identifiers.
The desktop application exchanges the first transaction ID for a random access token and stores that token in its local settings. Later monthly payments renew the same access automatically. Disconnecting the computer removes its local token. PayPal contributions and one-time Ko-fi tips do not create a Supporter account or unlock membership features.