Nonprofit Teams · IAP Trust and Safety guide
Design one offer for nonprofit teams with a single acceptance goal: make age, accessibility, moderation, rights, privacy, regional wording, and platform-policy review part of release acceptance. Keep the exact Koin price and a safe refusal path visible.
Create this game flow
Focused keyword and player case
Review a 25 Koin cosmetic with no fake scarcity or social-pressure copy. Record age context, shared-screen privacy, artwork rights, moderation, accessibility, and the responsible release owner. For nonprofit teams, Run an age-appropriate language review, inspect shared and streamed screens, test accessible cancellation, and record unresolved policy work instead of implying approval.
Use the focused IAP Trust and Safety hub for an authentic screenshot, direct playable result, and the complete purchase-state checklist. Gameplay evidence supports placement testing; it does not prove a live transaction.
The experience must avoid donation claims and clearly separate virtual item value from charitable giving.
Make age, accessibility, moderation, rights, and platform-policy checks part of release expected.
Use one item and one Koin price so players can evaluate the complete choice without navigating a large shop.
Choose a calm point where nonprofit and cause-game teams understand the game context and can decline without interrupting active play.
Show the item, benefit, duration or quantity, full price in Koin, visible Koin balance, confirm, and cancel in plain language.
After a cancelled choice or an insufficient balance, preserve progress and return nonprofit and cause-game teams to an understandable game state.
Following a successful result, show ownership, equipped state, unlocked content, or remaining quantity where the item will be used.
Describe only the Koin item the player receives and never imply that buying it creates a donation, tax benefit, fundraising total, or verified social impact. Any real cause relationship needs separate evidence, legal review, reporting, and transparent ownership.
Check age context, parental or shared-account assumptions, accessibility, localization, regional wording, moderation, artwork rights, privacy on shared screens, competitive fairness, platform policy, support, refunds, security, and durable ownership with the responsible humans. Replace claims that the browser build cannot prove, especially native billing, identity, store approval, financial reporting, and guaranteed outcomes. Test confirm and cancel with keyboard, touch, assistive navigation, reduced motion, and low vision where relevant. Inspect livestream, classroom, family, and local multiplayer situations for exposed account details or coercive language. A safe prototype makes unresolved production work visible instead of hiding it behind a successful demonstration.
Use age-appropriate language and avoid assumptions about child accounts, parental consent, or who controls the Koin balance. For nonprofit and cause-game teams, the experience must avoid donation claims and clearly separate virtual item value from charitable giving.
Do not expose account details in livestreams, classrooms, local multiplayer, or other shared viewing situations. For nonprofit and cause-game teams, the experience must avoid donation claims and clearly separate virtual item value from charitable giving.
Confirm item artwork, brand use, moderation needs, accessibility, regional wording, and platform policy before release. For nonprofit and cause-game teams, the experience must avoid donation claims and clearly separate virtual item value from charitable giving.
Write this into the prompt before the item description: Avoid donation claims and clearly separate virtual item value from charitable giving.
Result: A clear design constraint
Make age, accessibility, moderation, rights, and platform-policy checks part of release expected. Carry the same principle through confirmation and delivery.
Result: A consistent player experience
Name the benefit, duration or quantity, ownership rule, clearly stated Koin cost, and delivered result.
Result: An understandable offer
Try confirmation, cancellation, not enough Koin, repeated input, interruption, delivery, and reload without coaching.
Result: Audience-specific feedback
Change one prompt instruction, regenerate, and compare whether players understand the choice more quickly.
Result: A focused second version
Create a browser-playable game purchase-flow prototype for nonprofit and cause-game teams. Optimize for trust and safety review: make age, accessibility, moderation, rights, and platform-policy checks part of release expected. Apply this audience requirement: avoid donation claims and clearly separate virtual item value from charitable giving. Use one item the player may decline priced directly in Koin with preview, explicit confirm and cancel, insufficient-balance feedback, success, and visible delivery. Do not include subscriptions, revenue reporting, payment-provider UI, or guaranteed outcomes.
Keep the item optional. Show its full price in Koin, visible Koin balance, confirm, cancel, low-balance, success, visible delivery, and reload states.
Run an age-appropriate language review, inspect shared and streamed screens, test accessible cancellation, and record unresolved policy work instead of implying approval.
Use audience-appropriate language while you make age, accessibility, moderation, rights, privacy, regional wording, and platform-policy review part of release acceptance. Keep quantity, duration, restrictions, and the delivered state explicit.
A browser prototype can validate wording, layout, and state behavior; identity, billing, policy approval, durable entitlements, refunds, and support still need production implementation.
Open the complete prompt in SEELE, adjust the item and Koin price, then generate a playable version you can test.
Open this prompt in Workspace