loot-box-disclosure

Detect randomized reward purchases lacking odds disclosure in iOS/macOS apps.

13|1|Updated Mar 29, 2026

Search Tags:#compliance #in-app-purchase #apple-guidelines #loot-box #odds-disclosure #gacha

Ready to run

npx skills add https://github.com/cruisediary/apple-app-review-skills --skill loot-box-disclosure

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: loot-box-disclosure
Source: https://github.com/cruisediary/apple-app-review-skills/tree/main/skills/business/loot-box-disclosure
Command: npx skills add https://github.com/cruisediary/apple-app-review-skills --skill loot-box-disclosure

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Loot boxes, gacha, and randomized reward systems often disclose odds too late or not at all, risking non-compliance with platform guidelines and eroding user trust.

Core Features & Use Cases

Detects loot-box, gacha, and randomized reward mechanics that lack visible odds disclosure prior to purchase.
Provides guidance on embedding clear probability information directly in the purchase UI to meet guideline 3.1.1.
Useful for iOS/macOS apps with in-app purchases that employ randomized rewards and for audit teams evaluating app-submission readiness.

Quick Start

Use this skill to scan an Xcode project for randomized purchases and verify that each loot box option displays its drop rate before the user taps buy.

Frequently Asked Questions about loot-box-disclosure

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I check if my iOS app meets Apple guidelines for loot box odds disclosure?▼

Scanning an Xcode project for randomized in-app purchases verifies loot box odds disclosure compliance by detecting gacha mechanics lacking visible drop rates. This identifies purchase flows missing pre-purchase probability information required by Apple guideline 3.1.1.

What are the Apple guideline 3.1.1 requirements for gacha and randomized rewards?▼

Apple guideline 3.1.1 requires apps with randomized in-app purchase rewards to disclose odds before purchase. This means embedding clear probability information directly in the purchase UI so users see drop rates before tapping buy.

Can I use this to audit an existing macOS app submission for mystery box compliance?▼

Yes, you can audit an existing macOS app submission for mystery box compliance. It analyzes code for randomized reward purchase mechanics, making it useful for audit teams evaluating app-submission readiness and verifying visible odds disclosure.

How do I add visible drop rates to my in-app purchase UI?▼

To add visible drop rates, embed clear probability information directly in your purchase UI prior to the buy action. This skill provides guidance on integrating drop rate displays into existing purchase flows to satisfy odds disclosure requirements.

Does odds disclosure before purchase apply to all in-app purchases?▼

Odds disclosure before purchase applies specifically to in-app purchases using randomized rewards, including gacha and mystery box patterns. Standard non-randomized in-app purchases do not require drop rate visibility under Apple guideline 3.1.1.