The reassuring answer can be to a different question
“You keep your password.”
That is relevant information. It tells a buyer something about account access. The difficulty comes when it is used to answer a second question: whether the ranked activity itself follows the game’s rules.
A service description needs both. Treating them as one can make a narrowly accurate statement sound much broader than it is.
This article compares named parts of League of Legends and Rocket League guidance. It doesn’t estimate ban rates or classify every paid duo arrangement as the same behaviour.
Two questions, with different evidence
| Question | Evidence that can address it | What that evidence leaves open |
|---|---|---|
| Who accesses the buyer’s account? | The service’s access arrangement and the session record | Whether the ranked conduct is permitted |
| What happens in ranked play? | The actual conduct and the named publisher rule | Whether account credentials were handled properly |
Keeping credentials private avoids giving another player direct login access. That is a meaningful distinction from a piloted service. It still doesn’t tell us which account the teammate uses, whether its rank was deliberately reduced or what the arrangement asks the players to do.
A shop can accurately describe the access arrangement while leaving the conduct question unanswered. A reviewer should preserve that distinction rather than treating a password statement as an approval from the publisher.
What Riot actually describes
Riot’s League rank-manipulation guidance covers someone else playing ranked on the account. It also names deliberate losing in Flex and using deranked accounts to push another account up the ladder. Its listed sanctions include suspension and loss of seasonal ranked rewards. This means the documented concern reaches beyond account access alone.
That doesn’t establish that every match with a stronger friend is prohibited. Nor does the page give us a universal finding about every commercial duo product. The conduct described in the rule is what needs to be compared with the session.
The distinction stops an overreach in both directions. A seller shouldn’t turn keeping a password into blanket publisher approval. A critic shouldn’t turn an ordinary friendship into an allegation of deliberate deranking without evidence.
Rocket League states its own rule
Rocket League’s Code of Conduct separately prohibits boosting, deranking and smurfing or matchmaking abuse. It describes a smurf account in terms of intentional matchmaking abuse for someone’s gain. The publisher also warns that consequences vary with the violation and circumstances.
A League description can’t simply be copied across to Rocket League. The games have their own text. Read the current rule for the game being sold, rather than relying on a general claim about what duo means across gaming.
That also avoids a common shortcut: assuming an account is a smurf purely because it looks new or because its owner plays well. A statement about intentional manipulation needs evidence of the conduct. The existence of a rule isn’t proof that a named player breached it.
Three situations a useful account would distinguish
Take these as hypothetical descriptions, not records of real sessions.
A player queues with a similarly ranked friend and they play normally. Another player pays for replay feedback delivered after the match. A third description alleges that a teammate deliberately reduced an account’s rank before using it to carry somebody else.
All three might involve the buyer keeping their password. That single fact cannot make the situations equivalent.
The record should say whether the purchase was instruction, partner time or a promised rank outcome. If manipulation is alleged, describe the evidence for that allegation separately. A billing label is useful context; it isn’t a substitute for the match record.
For coaching, the relevant deliverable might be an analysis and a practice exercise. For a rank-target offer, it might be progress towards the stated target. Confusing those purchases can also lead to an unfair review: playing alongside a skilled person doesn’t establish that a lesson was promised or delivered.
A provider’s refund exclusion makes the boundary visible
The DuoBoost refund page says it doesn’t refund rank decay or Riot penalties. That is a published commercial condition, not a measurement of how often penalties happen. It is also a reminder that the provider and publisher control different decisions.
A statement that the buyer retains account access cannot answer who bears the cost of a publisher action. Record the specific terms rather than inferring that an access feature changes the refund condition.
What to ask the description to explain
Look for a clear account-access arrangement. Then look for a description of the actual activity, including which game and queue it concerns. If the offer mentions publisher approval or a claimed absence of penalties, ask for the source and scope of that claim.
Don’t manufacture a probability from confidence, a handful of screenshots or the absence of a reported incident in one conversation. A measured rate would need a defined sample and a way of observing outcomes. This article has neither and doesn’t supply one.
The useful reading is modest but firm: keeping a login answers an access question. Publisher compliance needs its own evidence. Our Rocket League MMR article applies the same distinction to another reassuring detail: an exact-looking number that still leaves the job itself undefined.