01 / Collection
Account and service records
Minibot stores issuer-scoped account identity, entitlement and plan state, payment status and references, device metadata, public-key material or fingerprints used for authorization, signed release grants, device authorization state, and security audit events.
Minibot also stores the release and device records needed to operate the service. Support cases contain the subject, affected device or release when provided, and the bounded diagnostic references you select, not unrestricted logs.
02 / Not requested
Secrets stay out of Minibot
Minibot does not ask for game passwords, recovery phrases, browser profiles, cookies, access tokens, or payment-provider credentials. Provider secrets remain in their provider-controlled secret stores. Use the safe support guidance before sharing any diagnostic.
03 / Why it exists
What each record is used for
Identity and entitlement
Authenticate the dedicated Minibot account and decide whether access is active.
Payments and audit
Verify billing state, prevent replay, and preserve a trace of sensitive changes.
Devices and releases
Authorize one device and deliver verified, expiring release grants.
Support and account records
Connect bounded diagnostics to the affected device, release, payment, or account.
04 / Retention
Deletion requests may leave required records in place
Request account data access or deletion through authenticated support Minibot can revoke the account when the identity provider reports deletion, but financial, fraud-prevention, security, and audit records may need to remain where required. User-owned device and support records can also have their own deletion state.
For a privacy question, use the same authenticated route and describe the request without including secrets.