Regulatory Updates

4 Probability Disclosure Issues to Check After the July 2026 GRAC Roundtable

TheGameAgent Team
July 13, 2026
5 min read

At the July 10, 2026 domestic agent roundtable jointly held by Korea’s Ministry of Culture, Sports and Tourism (MCST) and the Game Rating and Administration Committee (GRAC), officials focused on practical violations of Korea’s probability disclosure requirements.

Many compliance failures are not caused by intentional manipulation. They often arise from incomplete disclosures, inconsistent data, or small implementation errors that developers and live-operations teams overlook.

The following checklist reflects the compliance issues discussed at the roundtable and recurring violations identified in Korea’s official probability disclosure guidance.

Common Violation #1: Probability Information Is Missing from the Official Website

One of the most common mistakes is assuming that displaying probability information inside the game alone is sufficient.

Korea’s probability disclosure rules generally require applicable information to be displayed both within the game and on the game’s official website. Advertising and promotional materials are also subject to separate disclosure requirements.

Example

Probability information is available through the in-game UI, but the same information is missing from the game’s official website—or the website displays outdated values after a game update.

Compliance Tip

Maintain probability disclosures in both the game and the official website, and verify that the following information remains consistent:

  • Item names
  • Obtainable rewards
  • Individual probabilities
  • Reward quantities
  • Probability change conditions
  • Effective dates and update history

Whenever probability data changes, all applicable disclosure channels should be updated at the same time.

Common Violation #2: Only Grade-Level Probabilities Are Disclosed

Displaying only the probability of obtaining a reward grade—such as SS, S, or A—may be insufficient if users cannot determine the acquisition probability of each individual item within that grade.

Example

Insufficient disclosure:

  • SS Grade: 1%

Users can see the overall probability of receiving an SS-grade reward, but they cannot determine the probability of obtaining each item included in that grade.

Recommended Practice

List every obtainable item and disclose its individual acquisition probability.

For example:

  • SS Sword: 0.30%
  • SS Armor: 0.25%
  • SS Character A: 0.20%
  • SS Character B: 0.25%

The item-level probabilities should accurately correspond with the disclosed grade-level total.

Common Violation #3: Different Reward Quantities Are Combined

Another recurring issue involves grouping different quantities of the same reward into a single probability range.

If users can receive different quantities, each quantity is a separate obtainable outcome and should generally have its own probability.

Example

Insufficient disclosure:

  • Gold ×100–1,000: 10%

This format does not allow users to determine the probability of receiving each specific quantity.

Recommended Practice

Disclose every obtainable quantity separately.

For example:

  • Gold ×100: 5%
  • Gold ×500: 3%
  • Gold ×1,000: 2%

Avoid combining multiple results into a range or using an aggregated probability that prevents users from identifying the probability of each actual outcome.

Common Violation #4: Incorrect Decimal Precision

Probability values must be expressed as percentages and displayed with the level of precision required under Korea’s probability disclosure rules.

A uniform decimal-place rule should not be applied to every probability value. The required rounding position depends on where the first non-zero digit appears.

Example

Actual probability: 0.93512345%

Insufficient disclosure: ❌ 0.93%

Appropriate disclosure: ✅ 0.9351%

In this example, the first non-zero digit appears in the first decimal place. The value may be rounded at the fifth decimal place or lower, resulting in a displayed value of 0.9351%.

Recommended Practice

When formatting probability values:

  • Express each probability as a percentage.
  • Identify the first non-zero digit.
  • Round at a decimal place at least four places lower than the position of the first non-zero digit.
  • Ensure the displayed value reflects the probability actually applied by the game system.
  • Apply the same calculation method to the server data, in-game UI, official website, and regulatory materials.
  • Automate probability calculations and formatting wherever possible to reduce manual errors.

Developers should not arbitrarily shorten decimal values or apply inconsistent calculation rules across different disclosure channels.

Why Small Disclosure Errors Matter

Probability disclosures must accurately reflect the game system and remain consistent across applicable channels.

A missing item, an outdated webpage, an improperly rounded value, or an undisclosed probability change can result in a compliance review even when the publisher did not intend to mislead users.

Disclosure violations may lead to correction requests, corrective orders, service-distribution risks, and potential civil liability when users suffer losses.

Pre-Launch Compliance Checklist

Before launching a game or deploying a probability-related update in Korea, confirm that:

  • Probability information is available both in-game and on the official website.
  • Every obtainable item has an individual probability.
  • Different quantities of the same reward are disclosed separately.
  • Decimal values satisfy the required precision rules.
  • Server data, UI values, and website disclosures are consistent.
  • Dynamic or conditional probability changes are clearly explained.
  • Probability changes are reflected across all applicable channels when an update goes live.

Probability disclosure compliance should be integrated into the game’s development and live-operations workflow—not treated as a one-time legal review.

TheGameAgent helps overseas developers and publishers review probability tables, disclosure pages, update procedures, and communications with Korean regulators before issues escalate.

For additional guidance, read our Probability Disclosure Compliance: 5 essencial Q&As.

Need help reviewing your game’s probability disclosures? Contact TheGameAgent for a practical compliance assessment before your next Korean launch or content update.

Additional Resources

Is your company’s Korean compliance framework ready for the next regulatory request? Contact TheGameAgent for a practical review of your domestic agent structure and probability disclosure process.

This article provides general information and does not constitute legal advice. Regulatory requirements and administrative guidance may change, so developers should confirm the latest rules before launch.

関連記事

Korea Domestic Agent
Regulatory Updates

How to Get an Adult-Only Game Rated in Korea: A Step-by-Step Guide

A step-by-step guide for global developers preparing a Korean adult-only game rating application, including required materials, review timing, and store integration.

July 6, 2026
5 min read
Read More
Korea Domestic Agent
Regulatory Updates

Korea Game Advertising Compliance: A Practical Guide to GSOK

A practical guide to GSOK’s game-advertising standards, monitoring process, major compliance risks, and pre-launch review checklist.

June 29, 2006
7 min read
Read More
Korea Domestic Agent
Regulatory Updates
Case Studies

Korea Game Advertising Compliance: KFTC Enforcement and GSOK Standards

The Soul Strike case shows how broad “ad-free” claims can create Korean consumer-protection risk. Learn how KFTC enforcement and GSOK self-regulation apply.

May 29, 2006
7 min read
Read More

国内代理人をお探しですか?

弊社のサービス詳細は会社案内をダウンロードいただくか、チームとの個別相談をご予約ください。