Quick answer: On October 16, 2026, Apple updated the App Store Review Guidelines. For state lottery iOS apps, Guideline 5.3 (Gaming, Gambling, and Lotteries) did not change. What matters is new creative assets (2.3.14), a clearer ban on hidden or dormant features (2.5.19), sharper user-generated content moderation risk (1.2), and minor clarifications elsewhere.
If your team only skims for ticket-sales rules, you will miss the updates that actually affect ASO, App Review, and release process.
This guide is for lottery product, digital, marketing, compliance, and vendor partners who ship official state lottery apps on iOS.
What Apple changed on October 16, 2026
Apple’s public changelog called out these revisions:
- Before You Submit / After You Submit: more links to documentation (testing, review access, appeals, and related guidance).
- 1.2 User-Generated Content: clarified which apps and content types are in scope, including AI-related abuse patterns, and tied weak moderation after notice to possible Developer Code of Conduct violations.
- 2.3.14 Creative assets (new): rules for new image and video placements on the product page header, search, and related App Store surfaces.
- 2.5.19 Hidden, dormant, or undocumented features (new number): long-standing policy clarified in its own guideline, with removal and account-termination risk.
- 3.1.1(a): Music Streaming Services Entitlement language folded into StoreKit External Purchase Link Entitlements; links must go to a permitted destination.
- Section 5 Legal intro: apps that facilitate human trafficking or child exploitation are removed from the App Store and blocked from alternative distribution.
Translations of the updated guidelines were noted to follow on the Apple Developer site within about a month.
What did not change for lottery apps (Guideline 5.3)
This is the part most lottery Slack threads will get wrong.
Apple did not rewrite the core lottery rules in 5.3 Gaming, Gambling, and Lotteries. Official lottery apps still need:
- Necessary licensing and permissions where the app is used
- Geo-restriction to those locations
- A free App Store listing (not a paid download)
- No in-app purchase for credit or currency used with real-money gaming
- Lottery apps with consideration, chance, and a prize
Highly regulated gambling apps should still be submitted by the legal entity that provides the service (5.1.1(ix)), not by an individual developer account.
Lottery read: Ticket commerce rules did not suddenly open or close. Your risk this week is store presentation, review honesty, and social features, not a silent rewrite of 5.3.
2.3.14 Creative assets: the real ASO opportunity
Apple introduced creative assets as a new metadata type. Unlike screenshots and app previews (which must show the app in use), creative assets can highlight brand, seasonal offerings, and new content. They can appear in places like the product page header and search results, and can be managed through App Store Connect’s Asset Library, including standalone asset submissions without a new binary every time.
For state lotteries, that is a meaningful Expansion surface:
- Draw-night brand moments
- Scratchers seasons and new game art
- Responsible-play or civic-value campaigns that still feel on-brand
- Seasonal creatives approved ahead of a jackpot or holiday push
Related reading: How to use App Store Connect analytics for lottery apps.
Creative asset constraints lottery teams will hit
Guideline 2.3.14 and Apple’s asset best practices put hard edges on the opportunity:
- Appropriate for all audiences. App Store assets still need to feel safe at a broad (effectively 4+) presentation level, even when the app itself is rated higher.
- No specific or discounted pricing in creative assets (ticket prices, promo dollar amounts, and similar price theater).
- No unverifiable product claims (best odds, award badges you cannot defend, vague superiority claims).
- No misleading references to other apps.
- Assets must pertain to the app’s content, functionality, or overarching brand.
Lottery read: Brand and seasonality win. Jackpot-dollar hero creatives and “buy $X get…” overlays are where reviews get ugly. Treat creatives as trust and recognition, not as a second ad server for retail pricing.
2.5.19 Hidden or dormant features: the Stability landmine
Apple moved the long-standing ban on hidden, dormant, or undocumented features into Guideline 2.5.19 (formerly covered under accurate-metadata / 2.3.1 territory). The app’s functionality must be clear to end users and App Review. Hiding undocumented features in the binary, including through obfuscation, can lead to removal from the App Store and termination of the developer account.
Apple’s own framing is blunt: misrepresenting what the app does during review, then changing after approval (adding features that were not in the reviewed version), is bait-and-switch. That conduct can remove the app and the developer program membership.
State lottery release patterns that need a second look:
- Soft launches gated only by remote flags
- “Dormant” games or purchase paths shipped in the binary but invisible to review
- Post-approval feature flips that materially change what reviewers saw
- Demo accounts that hide the real flow players get in production
Lottery read: Feature flags are fine when they are honest. Feature flags that make App Review see a different product than citizens see are now framed as an account-level risk. Put new and changed functionality in Notes for Review. Make the demo path show the real thing.
Also remember 2.3.1(a): all new features, functionality, and product changes must be described with specificity in Notes for Review. Generic “bug fixes and improvements” notes will not cover a new game lane.
1.2 User-Generated Content: only if your lottery app is social
Guideline 1.2 applies to apps where users create, generate, upload, share, or contribute content, including social platforms and AI content-creation experiences. Apple clarified that nonconsensual intimate imagery (including imagery generated with AI tools) is in the moderation blast radius, and that failing to implement safeguards, or failing to remediate after notice, can be treated as a Developer Code of Conduct problem.
Required safeguards still include filtering, reporting, blocking abusive users, and published contact information.
Lottery read:
- Ticket check / results / account apps with no UGC: low direct impact from this change.
- Winner stories, photo uploads, community boards, chat, AI avatars or generators: treat moderation as release-critical infrastructure, not a help-desk afterthought.
What lottery teams can mostly ignore (for now)
3.1.1(a) External purchase link entitlements
The cleanup around Music Streaming Services Entitlements and StoreKit External Purchase Link Entitlements is about linking to permitted destinations for digital goods and services. It is not a new App Store lane for selling lottery tickets via Apple IAP. Real-money gaming credit and lottery ticket purchase rules still sit under 5.3 / 3.1 constraints.
Section 5 trafficking / exploitation language
Apple clarified that apps facilitating human trafficking or child exploitation are removed and blocked from alternative distribution. That is a hard safety ban clarification. It is serious. It is not a lottery-product-design change.
How to prioritize: Expansion vs Stability
At Lissiland we use a simple sequence for lottery mobile: Stability → Engagement → Expansion.
- Creative assets (2.3.14) are Expansion: more perception surface on the App Store.
- Honest review narrative and clean feature flags (2.5.19 + 2.3.1) are Stability: keep the app shippable and the account alive.
- UGC moderation (1.2) is trust infrastructure for any social layer.
Fund Expansion creatives after the review story matches the binary. Otherwise you pay for a photoshoot while a dormant feature or a soft-launch flag creates the outage.
If you are measuring whether listing changes actually move downloads, keep using App Store Connect the boring way: State lottery mobile app analytics in App Store Connect.
Action checklist for state lottery iOS teams
- Brief marketing and ASO on creative assets: brand and seasonality in; pricing, discounts, and unverifiable claims out.
- Audit Asset Library workflow so seasonal creatives can be approved ahead of draw campaigns without forcing an unnecessary binary.
- Inventory remote flags and soft-launch paths in the current production binary. Anything material that App Review cannot exercise needs a plan: document it, demo it, or do not ship it dormant.
- Tighten Notes for Review for the next submission: specific feature list, demo credentials or demo mode, geo notes, and license docs as required.
- If you have UGC or AI content tools, verify filtering, reporting, blocking, contact paths, and a remediation playbook after Apple notice.
- Do not reopen a 5.3 rewrite panic. Confirm licenses, geo-fencing, and free listing status are still correct, then spend the week on creatives and review honesty.
FAQ: Apple App Store Review Guidelines and state lottery apps
Did Apple change lottery ticket sales rules in October 2026?
No. Guideline 5.3 on gaming, gambling, and lotteries was not rewritten in this update. Licensing, geo-restriction, free App Store distribution, and restrictions on IAP for real-money gaming credit remain the baseline.
What is Guideline 2.3.14 creative assets?
Creative assets are new App Store image and video placements that can highlight brand, seasonal offerings, and new content beyond in-use screenshots and previews. They must still follow metadata rules, be appropriate for all audiences, and avoid specific or discounted pricing and unverifiable claims.
Can lottery apps show jackpot amounts in creative assets?
Treat jackpot dollars and ticket prices as high risk. Apple explicitly bans specific or discounted pricing in creative assets and requires assets appropriate for all audiences. Prefer brand and seasonal storytelling over price or jackpot theater in those placements.
What is Guideline 2.5.19 for lottery apps?
It clarifies that apps cannot include hidden, dormant, or undocumented features. Functionality must be clear to users and App Review. Soft-launching major features after approval, or obfuscating gated functionality, can lead to app removal and developer account termination.
Do state lottery apps with no social features need to worry about Guideline 1.2?
Usually not for this update. Guideline 1.2 targets apps where users create, upload, share, or generate content. Ticket check and results apps without UGC have low direct exposure. Apps with photo uploads, communities, chat, or AI generators do not.
Does 3.1.1(a) let lotteries sell tickets through external purchase links?
No. The 3.1.1(a) clarification is about entitlements and permitted destinations for certain digital-goods purchase links. It does not replace Guideline 5.3 rules for lotteries and real-money gaming.
Where can I read Apple’s official guidelines?
Apple publishes the current App Store Review Guidelines at developer.apple.com/app-store/review/guidelines/. Review the October 16, 2026 news post on the Apple Developer site for the official change list and Apple’s commentary on 1.2, 2.5.19, and Section 5.
Bottom line
Apple’s October 16, 2026 App Store Review Guidelines update is not a rewrite of state lottery commerce rules. It is a store-presentation and review-honesty update with social-moderation teeth for apps that need them.
Creative assets give lottery teams a new way to win perception on the product page and in search, if creatives stay brand-first and price-claim-clean. Dormant features and soft launches that App Review never saw are now framed as Stability risk with account consequences. UGC apps need real safeguards, not a PDF policy.
Sequence it right: honesty with App Review first, then the campaign creatives.
Want a review of your lottery app’s creative asset plan, Notes for Review narrative, or feature-flag posture against this update? Email me. cbluford@lissiland.com