Two kinds of player your game must serve
Yandex Games sets clear rules for how a game treats players. The requirements say a game must launch and be usable without registration or logging in, that authorization happens only after a deliberate action by the player, that the player can decline and keep playing, and that a guest's progress is saved. Authorization itself goes through Yandex ID.
Leaderboards add the second kind of player. The leaderboard documentation says submitting a score and viewing your own entry are available only to authorized users, and that unauthorized users are not included in the leaderboard and cannot see their progress there. So every release has a guest path and a signed-in path, and a careful developer wants to walk both.
Why your developer login is a poor test player
A solo developer usually plays builds with the same Yandex account used for the developer side. That login has seen every version, may already have authorized the game long ago, and carries your own history across Yandex services. It is the least typical player you could pick.
The guest path needs no account at all: open the released game in a private browser window. The signed-in path is where a second account earns its place. It lets you meet the authorization prompt the way a newcomer does, decide to accept it, and then see what a signed-in player sees on the leaderboard and in saved progress.
A puzzle game launch, worked through
Hypothetical: a solo developer releases a small puzzle game with a weekly leaderboard. She plays it first as a guest and checks that her progress survives a page reload, as the requirements expect. Then she wants to know what happens when a guest decides to sign in: when the prompt appears, whether the guest's progress carries on, and how the leaderboard looks once she is ranked.
Her own account is unsuitable because it authorized the game during development. She buys one separate Yandex account, signs in to it only inside the game when the prompt appears, and plays a normal session. She notes where the sign-in prompt is triggered, checks that the Leaderboard button opens the leaderboard rather than an authorization request, which the requirements forbid, and confirms that her player entry is shown.
She writes the results down as a short list beside the build number: where the prompt appeared, whether declining it left the game playable, whether progress continued after signing in, and what the leaderboard showed. That list is what she compares against when the next update ships, using the same account so the comparison stays like for like.
One account, not a test matrix
This decision is about one honest player view, not about building a collection of test profiles. A single fresh account answers the questions above; several accounts add nothing a solo developer needs for a release check.
Be careful with scores. Any score the player account submits is a real entry on a real leaderboard, seen by real players. Play a normal session, do not aim for the top, and never use extra accounts to fill the table or to push plays and ratings. That would mislead the people your game is for.
When a separate player account fits
It fits a solo developer or a very small team who has a leaderboard or cloud saves in the game and has no other signed-in account that has never seen it. It is most useful right after a release, when the signed-in path has not yet been walked by anyone outside development.
It does not fit if your game has no leaderboard and saves nothing for signed-in players; the guest path in a private window then shows everything. It also does not fit if a friend or colleague with their own Yandex ID is willing to try the game for you, because a real first-time player is better evidence than any account you control.
What the listing should say
For a player-view account, clean history is the whole point. Prefer a listing that describes the account as unused, states whether a phone number is linked and whether you can replace it, and includes the backup email and security question. An account that has played many games already would bring its own history into your check.
Plan the takeover before you play. Yandex ID Help says the secure number can only be replaced, and without access to the old number the change waits 14 days. Change the password and recovery details first, then sign in to your game.
Yandex's terms and the purchase
Yandex's user agreement holds the account holder responsible for all actions under the account and does not allow reselling access to Yandex services without Yandex's authorization. Buying a listing gives you no permission from Yandex, so follow Yandex's terms and the Yandex Games requirements when you use the account.
rStock is not affiliated with Yandex; it is an independent marketplace. Pay from your rStock balance, and find the account details in the delivery record on the order page, together with the window for opening a dispute. Check the account inside that window, then compare the Yandex accounts in the category and choose one clean enough to play your game for the first time.