Data policy

Last updated: 2026-08-06. This describes what the Bandrek client may transmit when you use Stegripe-backed features. It is written for users and contributors; it is not legal advice.

Scope

In scope	Out of scope
Bandrek desktop client	Third-party mods, plugins or forks
Stegripe API (/api/v1/mibb/*, /api/v1/mi/party/*)	Mojang / Microsoft services
Stegripe co-op relay (WebSocket)	Mine-imator.com official services

Offline use (no license validation retry, no co-op) keeps traffic to what the base program already did (e.g. optional skin downloads for custom heads).

Summary

When	What may be sent	Where	Stored?
License activate/validate	License key, HWID hash, Discord-linked account metadata	Stegripe API	Yes: license binding
Co-op create/join	Party code, session token, display name, roster	Stegripe API + relay	Session lifetime
Co-op heartbeat	Party/member IDs to keep the session alive	Stegripe API	Short-lived
Co-op sync	Project snapshots, asset bytes, edit operations (while in a party)	Stegripe relay	Not kept as permanent project storage
Upgrade / sign-in	Browser OAuth flow to Discord (Stegripe)	Your browser → Stegripe	Per Stegripe account policy

Not collected during normal editing

• Keystrokes or clipboard content outside co-op session scope
• Files unrelated to the project you are editing
• Microphone or camera

Stays on your disk

Projects, caches, logs and the license cache (key.midata) live in the application’s user/data directories. The client writes a local log.txt (and related traces when co-op debug is enabled). Nothing leaves unless you export it, send it manually or sync it through co-op.

Your choices

• Do not activate a license → co-op and full-feature gates remain unavailable.
• Do not create/join co-op → no relay traffic; license validation may still occur if you activated.
• Leave co-op anytime → stops sync and releases party holds.

Source: Docs/DATA_POLICY.md.