No. Microsoft/Minecraft account linking uses Microsoft OAuth device-code sign-in. PulseAFK never asks for or stores your Microsoft password.

Java Edition on recent versions, set per server when you add an account. Bedrock Edition isn’t supported yet.

PulseAFK doesn’t try to evade anti-cheat systems or hide what it does — it’s a remote Minecraft client, not a detection bypass. Whether an AFK session is allowed is entirely up to the server you connect to; running one on a server that prohibits it is against that server’s rules and can get you banned there. Only connect to servers where you’ve confirmed it’s allowed, which account setup requires you to do.

Yes. Each plan has an account-slot limit. The dashboard keeps status, runtime, commands, activity and analytics separate per account.

No. A proxy is optional and can be attached per account if you want one — it’s not required to run a session.

PulseAFK creates a fixed-price, network-specific invoice through SHKeeper. Access activates automatically once PulseAFK independently confirms the payment — never from a client-side success screen alone.

Crypto payments are final once confirmed on-chain, since they can’t be reversed. If a payment goes wrong — wrong network, wrong amount, invoice issue — contact support before doing anything else.

PulseAFK does not support Bedrock Edition, anti-cheat bypass, CAPTCHA solving, ban evasion, or hidden server data. Features labeled Coming soon on the pricing page are not active yet.