TFTF PRESENCE
PUBLIC PRESENCE / PRIVACY

What gets shared.

TF Presence is disabled until you explicitly accept it in TuffLauncher. The launcher remains usable without accepting.

Data transmitted

While active on multiplayer, TuffClient sends your Minecraft UUID, a SHA-256 hash of the multiplayer server address, and a short-lived client session token to this server about every 12 seconds. The hash is not encryption and may be guessable for popular server addresses.

Who sees it?

The service returns UUIDs of opted-in players who report the same server hash. Other TuffClient users can then display a TF badge. It does not provide a public directory of players.

Retention

Presence records are kept in server memory only and expire about 42 seconds after the last update. Restarting the service clears them. No user database or analytics tracking is included in this software. The hosting provider may process connection metadata under its own policies.

Your choices

Choose “Continue without Presence” at first launch, or switch off “Share TF Presence” at any time. After switching off, local badges clear; the server entry expires naturally unless a client sends a leave request.

Identity security

This protocol currently accepts self-reported UUIDs. A TF badge indicates an active Presence claim, not cryptographic proof of Minecraft account ownership. Do not use it for authorization or moderation decisions.

Secure transport

For internet access, use HTTPS. The service does not need Microsoft passwords or access tokens. Do not provide such credentials to the Presence server.

← Back to overview