Check server response of
Server response
NS records
Whois domain
301 Moved Permanently - asrgh.com
HTTP Status: 301
User-Agent: Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; ClaudeBot/1.0; [email protected])
Server: nginx
Date: Tue, 13 May 2025 06:40:14 GMT
Content-Type: text/html; charset=UTF-8
Transfer-Encoding: chunked
Connection: close
Cache-Control: no-store, no-cache, must-revalidate, max-age=7200
Cache-Control: post-check=0, pre-check=0
Pragma: no-cache
Expires: Tue, 13 May 2025 08:40:14 GMT
X-Redirect-By: Simply.com
Strict-Transport-Security: max-age=0;
Location: http://www.appstorereviewguidelineshistory.com
HTTP Code 301 Moved Permanently
301 status code means that the requested resource has been permanently moved to a new URL. All future requests should use the new address.
When is Code 301 used?
- When changing a website domain
- When modifying URL structures
- When setting up redirects for SEO
What does Code 301 mean for the user?
The browser will automatically redirect the user to the new address, and search engines will update their indexes.
200 OK - http://www.appstorereviewguidelineshistory.com
HTTP Status: 200
User-Agent: Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; ClaudeBot/1.0; [email protected])
Connection: keep-alive
Content-Length: 350677
Server: GitHub.com
Content-Type: text/html; charset=utf-8
Last-Modified: Wed, 18 Sep 2024 09:46:23 GMT
Access-Control-Allow-Origin: *
ETag: "66eaa16f-559d5"
expires: Tue, 13 May 2025 06:50:14 GMT
Cache-Control: max-age=600
x-proxy-cache: MISS
X-GitHub-Request-Id: EC3E:3A9242:A4AECA:A66F44:6822E94E
Accept-Ranges: bytes
Age: 0
Date: Tue, 13 May 2025 06:40:14 GMT
Via: 1.1 varnish
X-Served-By: cache-hel1410020-HEL
X-Cache: MISS
X-Cache-Hits: 0
X-Timer: S1747118415.609656,VS0,VE180
Vary: Accept-Encoding
X-Fastly-Request-ID: fc25278f9f713ab9021cb843f01df31c694261cb
HTTP Code 200 OK
200 status code is a standard successful HTTP server response. It means that the client’s request (e.g., from a browser) was successfully processed, and the server is delivering the requested data.
When is Code 200 used?
- When loading a web page
- When successfully receiving an API response
- When processing a form or another HTTP request
What does Code 200 mean for the user?
The user receives content without errors, and the page or application functions properly. If Code 200 is accompanied by data, the browser or program processes and displays it to the user.
GET / HTTP/1.1 Host: asrgh.com Accept: */* User-Agent: Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; ClaudeBot/1.0; [email protected])
<!DOCTYPE html><html lang="en"><head><meta charset="utf-8"><meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1"><meta name="viewport" content="width=device-width"><title>App Store Review Guidelines History</title><link rel="alternate" href="http://appstorereviewguidelineshistory.com/feed.xml" type="application/rss+xml" title=""><script src="//use.typekit.net/uzm7ejy.js"></script><script>try{Typekit.load();}catch(e){}</script><link rel="stylesheet" href="/css/main.css"><script>
(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
(i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),
m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
})(window,document,'script','//www.google-analytics.com/analytics.js','ga');
ga('create', 'UA-17036676-7', 'auto');
ga('send', 'pageview');
</script><script>
!function(f,b,e,v,n,t,s)
{if(f.fbq)return;n=f.fbq=function(){n.callMethod?
n.callMethod.apply(n,arguments):n.queue.push(arguments)};
if(!f._fbq)f._fbq=n;n.push=n;n.loaded=!0;n.version='2.0';
n.queue=[];t=b.createElement(e);t.async=!0;
t.src=v;s=b.getElementsByTagName(e)[0];
s.parentNode.insertBefore(t,s)}(window,document,'script',
'https://connect.facebook.net/en_US/fbevents.js');
fbq('init', '140326516726695');
fbq('track', 'PageView');
</script>
<noscript>
<img height="1" width="1"
src="https://www.facebook.com/tr?id=140326516726695&ev=PageView
&noscript=1"/>
</noscript></head><body><div id="header-box"><div class="content-wrap"><div class="left-side"><a href="/" alt="App Store Review Guidelines front page"><img class="site-logo" src="/asrgh_logo.png"></a></div><div class="right-side"><p>Powered by</p><a href="http://www.shape.dk" alt="Shape logo"><img class="shape-logo" src="/shape_logo.png"></a></div></div></div><header class="header"><div class="content-wrap"><div class="logo"><p class="description">Hi. We're<a href="http://www.shape.dk"> Shape</a>, an app development agency in Copenhagen and Zurich. We refer to the App Store Review Guidelines all the time. It's hard to spot the changes, so we made this site for ourselves and our clients. We hope it can help you as well.</p></div></div></header><div id="content"><div class="content-wrap"><!--div.mailchimp-container--><div class="mailchimp-form"><!-- Begin MailChimp Signup Form -->
<!--<link href="//cdn-images.mailchimp.com/embedcode/slim-081711.css" rel="stylesheet" type="text/css">-->
<style type="text/css">
#mc_embed_signup{background:#fff; clear:left; font:14px Helvetica,Arial,sans-serif; }
/* Add your own MailChimp form style overrides in your site stylesheet or in this style block.
We recommend moving this block and the preceding CSS link to the HEAD of your HTML file. */
</style>
<div id="mc_embed_signup">
<form action="//shape.us1.list-manage.com/subscribe/post?u=f12eda42ceddc32cb1a4e04fc&id=2f3b6be996" method="post" id="mc-embedded-subscribe-form" name="mc-embedded-subscribe-form" class="validate" target="_blank" novalidate>
<div id="mc_embed_signup_scroll">
<input type="email" value="" name="EMAIL" class="email" id="mce-EMAIL" placeholder="Email address" required>
<!-- real people should not fill this in and expect good things - do not remove this or risk form bot signups-->
<div style="position: absolute; left: -5000px;"><input type="text" name="b_f12eda42ceddc32cb1a4e04fc_2f3b6be996" tabindex="-1" value=""></div>
<input type="submit" value="Subscribe" name="subscribe" id="mc-embedded-subscribe" class="button">
</div>
</form>
<!--<a href="https://twitter.com/shapedk" class="twitter-follow-button" data-show-count="false" data-size="large" data-dnt="true">Follow @shapedk</a> <script>!function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?'http':'https';if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+'://platform.twitter.com/widgets.js';fjs.parentNode.insertBefore(js,fjs);}}(document, 'script', 'twitter-wjs');</script>-->
</div>
<!--End mc_embed_signup--><!--include twitter.html--><p class="mail-form-policy">We will never spam you or give your email to others.</p></div><article class="article intro"><header><p class="date"><span>September 18, 2024</span></p><h2><a href="/articles/2024-09-18-ipad-apps-on-alternative-app-stores/">iPadOS apps can now be downloaded on alternative app stores in the EU</a></h2></header><section class="content"><p>Apple has updated their <a href="https://developer.apple.com/app-store/review/guidelines/">App Store Review Guidelines</a> to add iPadOS to Notarization, meaning that <span class="caps">EU</span> users can now download iPadOS apps on the App Store and through alternative distribution.</p>
<p><br><br></p>
<p><a href="https://developer.apple.com/news/?id=4sn7e783">Apple’s own summary can be found here</a>.</p>
<p><br><br></p>
<p>The complete set of changes can be seen below:</p>
</section><p class="changes"><section class="apple">
<h3 data-sidenav id="introduction">Introduction</h3>
<p>The guiding principle of the App Store is simple—we want to provide a safe experience for users to get apps and a great opportunity for all developers to be successful. We do this by offering a highly curated App Store where every app is reviewed by experts and an editorial team helps users discover new apps every day. We also scan each app for malware and other software that may impact user safety, security, and privacy. These efforts have made Apple’s platforms the safest for consumers around the world.</p>
<p>In the European Union, developers can also distribute notarized iOS <span class="insert">and iPadOS </span>apps from alternative app marketplaces<span class="insert"> and directly from their website</span>. Learn more about <a href="https://developer.apple.com/help/app-store-connect/distributing-apps-in-the-european-union/manage-distribution-on-an-alternative-app-marketplace">alternative app marketplaces</a><span class="insert">, </span><a href="https://developer.apple.com/support/web-distribution-eu/"><span class="insert">Web Distribution</span><span class="loc-en-only"></span></a><span class="insert">,</span> and <a href="https://developer.apple.com/support/dma-and-apps-in-the-eu/#notarization-for-ios-apps">Notarization for iOS<span class="insert"> and iPadOS</span> apps<span class="loc-en-only"></span></a>. You can see which guidelines apply to Notarization for iOS <span class="insert">and iPadOS </span>apps by clicking on “Show Notarization Review Guidelines Only” in the menu to the left.</p>
<p>For everything else there is always the open Internet. If the App Store model and guidelines or alternative app marketplaces and Notarization for iOS <span class="insert">and iPadOS </span>apps are not best for your app or business idea that’s okay, we provide Safari for a great web experience too.</p>
<h3 data-sidenav id="before-you-submit">Before You Submit</h3>
<p>To help your app approval go as smoothly as possible, review the common missteps listed below that can slow down the review process or trigger a rejection. This doesn’t replace the guidelines or guarantee approval, but making sure you can check every item on the list is a good start. If your app no longer functions as intended or you’re no longer actively supporting it, it will be removed from the App Store. <a href="https://developer.apple.com/support/app-store-improvements/">Learn more about App Store Improvements</a>.</p>
<p data-nr class="margin-top">Guidelines that include <img src="https://developer.apple.com/app-store/review/images/key-icon.svg" height="17" class="asr-nr" alt="ASR & NR" /> apply to <a href="https://developer.apple.com/support/dma-and-apps-in-the-eu/#notarization-for-ios-apps">Notarization for iOS<span class="insert"> and iPadOS</span> apps<span class="loc-en-only"></span></a> in the EU.</p>
<h3 data-nr data-sidenav id="safety"><span id="1"></span>1. Safety</h3>
<p class="section-intro">When people install an app from the App Store, they want to feel confident that it’s safe to do so—that the app doesn’t contain upsetting or offensive content, won’t damage their device, and isn’t likely to cause physical harm from its use. We’ve outlined the major pitfalls below, but if you’re looking to shock and offend people, the App Store isn’t the right place for your app. Some of these rules are also included in Notarization for iOS<span class="insert"> and iPadOS</span> apps.</p>
</section></p></article><article class="article intro"><header><p class="date"><span>August 08, 2024</span></p><h2><a href="/articles/2024-08-08-missing-in-app-items-and-pc-emulator-game-downloads/">Requiring review explanations for missing in-app items, allowing PC emulator apps to offer downloads, and more</a></h2></header><section class="content"><p>This entry covers 2 separate updates to <a href="https://developer.apple.com/app-store/review/guidelines/">Apple’s guidelines</a> made by Apple on June 10, 2024 and August 1, 2024.</p>
<p><br><br></p>
<p>On June 10, among other things, changes were made to require developers to explain why configured in-app items cannot be found or reviewed in their apps, when they submit for review. Apple also made it clear that they will no longer reject apps that simulate multi-app widget experiences. (<a href="https://developer.apple.com/news/?id=og4hxxz8">Summary</a>)</p>
<p><br><br></p>
<p>On August 1, changes were made to support updated policies, upcoming features and to provide clarification, e.g. that <span class="caps">PC</span> emulator apps can offer to download games. (<a href="https://developer.apple.com/news/?id=ty0avr2s">Summary</a>)</p>
<p><br><br></p>
<p>The complete set of changes can be seen below:</p>
</section><p class="changes"><section class="apple">
<h3 data-sidenav id="introduction">Introduction</h3>
<p>A few other points to keep in mind about distributing your app on our platforms:</p>
<ul class="disc top-level">
<li>Some features and technologies that are not generally available to developers may be offered as an <a href="https://developer.apple.com/documentation/bundleresources/entitlements">entitlement</a> for limited use cases. For example, we offer entitlements for CarPlay Audio, HyperVisor, and Privileged File Operations.<span class="delete"> Review our documentation on developer.apple.com to learn more about entitlements.</span></li>
</ul>
<h3 data-sidenav id="before-you-submit">Before You Submit</h3>
<p><strong><span class="delete">Development Guidelines</span><span class="insert">Developer Documentation</span></strong></p>
<ul class="links small">
<li class="document"><a href="https://developer.apple.com/documentation/swiftui"><span class="insert">SwiftUI</span><span class="loc-en-only"></span></a></li>
<li class="document"><a href="https://developer.apple.com/documentation/uikit">UIKit<span class="loc-cj"></span></a></li>
<li class="document"><a href="https://developer.apple.com/documentation/appkit">AppKit<span class="loc-en-only"></span></a></li>
<li class="document"><span class="delete">WatchKit</span><a href="https://developer.apple.com/app-extensions/"><span class="insert">App extensions</span></a></li>
<li class="document"><a href="https://developer.apple.com/documentation/foundation/optimizing_your_app_s_data_for_icloud_backup/"><span class="insert">Optimizing Your App’s Data for iCloud Backup</span><span class="loc-en-only"></span></a></li>
<li class="document"><span class="delete">App extensions</span>
<span class="delete">iOS Data Storage Guidelines</span>
<a href="https://developer.apple.com/documentation/foundation/file_system/about_apple_file_system">Apple File System<span class="loc-en-only"></span></a></li>
<li class="document"><a href="https://developer.apple.com/help/app-store-connect/">App Store Connect Help</a></li>
<li class="document"><a href="https://developer.apple.com/help/account/">Developer Account Help</a></li>
</ul>
<h3 data-nr data-sidenav id="performance"><span id="2"></span>2. Performance</h3>
<ul class="no-bullet">
<li data-nr data-sidenav="2.1 App Completeness" id="app-completeness"><span id="2.1"></span><strong>2.1 App Completeness</strong>
<ul class="no-bullet margin-top-small">
<li data-nr><strong><span class="insert">(a)</span></strong><span class="custom-tooltip-icon"><img src="https://developer.apple.com/app-store/review/images/key-icon.svg" height="17" class="asr-nr" alt="ASR & NR" /></span> Submissions to App Review, including apps you make available for pre-order, should be final versions with all necessary metadata and fully functional URLs included; placeholder text, empty websites, and other temporary content should be scrubbed before submission. Make sure your app has been tested on-device for bugs and stability before you submit it, and include demo account info (and turn on your back-end service!) if your app includes a login. If you are unable to provide a demo account due to legal or security obligations, you may include a built-in demo mode in lieu of a demo account with prior approval by Apple. Ensure the demo mode exhibits your app’s full features and functionality. <span class="insert">We will reject incomplete app bundles and binaries that crash or exhibit obvious technical problems.</span></li>
<li><strong><span class="insert">(b)</span></strong> If you offer in-app purchases in your app, make sure they are complete, up-to-date, <span class="delete">and </span>visible to the reviewer<span class="insert"> and functional. If any configured in-app purchase items cannot be found or reviewed in your app</span>, <span class="delete">or that you </span>explain <span class="delete">why not</span><span class="insert">the reason</span> in your review notes.<span class="delete"> Please don’t treat App Review as a software testing service. We will reject incomplete app bundles and binaries that crash or exhibit obvious technical problems.</span>
</li>
</ul>
</li>
<li data-nr data-sidenav="2.3 Accurate Metadata" id="accurate-metadata"><span id="2.3"></span><strong>2.3<span class="custom-tooltip-icon"><img src="https://developer.apple.com/app-store/review/images/key-icon.svg" height="17" class="asr-nr" alt="ASR & NR" /></span><span> Accurate Metadata</span></strong>
<p data-nr>Customers should know what they’re getting when they download or buy your app, so make sure all your app metadata, including privacy information, your app description, screenshots, and previews accurately reflect the app’s core experience and remember to keep them up-to-date with new versions.</p>
<ul class="no-bullet margin-top-small">
<li id="2.3.10"><strong>2.3.10</strong> Make sure your app is focused on the <span class="delete">iOS</span><span class="insert">experience of the Apple platforms it supports</span>, <span class="delete">iPadOS, macOS, tvOS or watchOS experience, </span>and don’t include names, icons, or imagery of other mobile platforms or alternative app marketplaces in your app or metadata, unless there is specific, approved interactive functionality. Make sure your app metadata is focused on the app itself and its experience. Don’t include irrelevant information.</li>
</ul>
</li>
<li data-nr data-sidenav="2.4 Hardware Compatibility" id="hardware-compatibility"><span id="2.4"></span><strong>2.4 Hardware Compatibility</strong>
<ul class="no-bullet margin-top-small">
<li id="2.4.1"><strong>2.4.1</strong> To ensure people get the most out of your app, iPhone apps should run on iPad whenever possible. We encourage you to consider building <span class="delete">universal </span>apps so customers can use them on <a href="https://developer.apple.com/documentation/xcode/configuring-a-multiplatform-app-target">all of their devices<span class="delete">. Learn more about </span><span class="delete">Universal apps</span></a>.</li>
</ul>
</li>
<li data-nr data-sidenav="2.5 Software Requirements" id="software-requirements"><span id="2.5"></span><strong>2.5 Software Requirements</strong>
<ul class="no-bullet margin-top-small">
<li id="2.5.8"><strong>2.5.8</strong> Apps that create alternate desktop/home screen environments<span class="delete"> or simulate multi-app widget experiences</span> will be rejected.</li>
</ul>
</li>
</ul>
<h3 data-sidenav id="business"><span id="3"></span>3. Business</h3>
<ul class="no-bullet">
<li data-sidenav="3.1 Payments" id="payments"><span id="3.1"></span><strong>3.1 Payments</strong>
<ul class="no-bullet margin-top-small">
<li data-sidenav="3.1.1 In-App Purchase" id="in-app-purchase"><span id="3.1.1"></span><strong>3.1.1 In-App Purchase:</strong>
<ul class="disc margin-top-small">
<li>Non-subscription apps may offer a free time-based trial period before presenting a full unlock option by setting up a Non-Consumable IAP item at Price Tier 0 that follows the naming convention: “XX-day Trial.” Prior to the start of the trial, your app must clearly identify its duration, the content or services that will no longer be accessible when the trial ends, and any downstream charges the user would need to pay for full functionality. Learn more about managing content access and the duration of the trial period using <a href="https://developer.apple.com/documentation/storekit/original_api_for_in-app_purchase/choosing_a_receipt_validation_technique">Receipts<span class="loc-en-only"></span></a> and <span class="delete">Device Check</span><a href="https://developer.apple.com/documentation/devicecheck"><span class="insert">DeviceCheck</span><span class="loc-en-only"></span></a>.</li>
</ul>
</li>
</ul>
</li>
</ul>
<h3 data-nr data-sidenav id="design"><span id="4"></span>4. Design</h3>
<ul class="no-bullet">
<li><span id="4.6"></span><strong>4.6<span class="delete"> Alternate App Icons</span></strong>
<span class="delete">Apps may display customized icons, for example, to reflect a sports team preference, provided that each change is initiated by the user and the app includes settings to revert to the original icon</span><span class="insert"> Intentionally omitted</span>.<span class="delete"> All icon variants must relate to the content of the app and changes should be consistent across all system assets, so that the icons displayed in Settings, Notifications, etc. match the new springboard icon.</span>
</li>
<li data-nr data-sidenav="4.7 Mini apps, mini games, streaming games, chatbots, plug-ins, and game emulators" id="third-party-software"><span id="4.7"></span> <strong>4.7<span class="custom-tooltip-icon"><img src="https://developer.apple.com/app-store/review/images/key-icon.svg" height="17" class="asr-nr" alt="ASR & NR" /></span> Mini apps, mini games, streaming games, chatbots, plug-ins, and game emulators</strong>
<p data-nr>Apps may offer certain software that is not embedded in the binary, specifically HTML5 mini apps and mini games, streaming games, chatbots, and plug-ins. Additionally, retro game console <span class="insert">and PC </span>emulator apps can offer to download games. You are responsible for all such software offered in your app, including ensuring that such software complies with these Guidelines and all applicable laws. Software that does not comply with one or more guidelines will lead to the rejection of your app. You must also ensure that the software adheres to the additional rules that follow in 4.7.1 <span class="delete">and</span><span class="insert">through</span> 4.7.5. These additional rules are important to preserve the experience that App Store customers expect, and to help ensure user safety.</p>
</li>
</ul>
</section></p></article><article class="article intro"><header><p class="date"><span>April 10, 2024</span></p><h2><a href="/articles/2024-04-10-music-streaming-services-and-retro-games-emulators/">Clarification on alternative music streaming app payment methods and allowing downloads in retro game console emulator apps</a></h2></header><section class="content"><p>Apple has updated their <a href="https://developer.apple.com/app-store/review/guidelines/">App Store Review Guidelines</a> to clarify how music streaming apps in particular can inform users about alternative payment methods and prices. The updated guidelines also now specify that it’s allowable for retro game console emulator apps to offer to download games.
<br><br></p>
<p><a href="https://developer.apple.com/news/?id=0kjli9o1">Apple’s own summary can be found here</a>.
</br></br></p>
<p>The complete set of changes can be seen below:</p>
</section><p class="changes">
<section class="apple">
<li data-sidenav="3.1 Payments" id="payments"><span id="3.1"></span><strong>3.1 Payments</strong>
<ul class="no-bullet margin-top-small">
<li data-sidenav="3.1.1(a) Link to Other Purchase Methods" id="link-to-other-purchase-methods"><span id="3.1.1a"></span><strong>3.1.1(a) Link to Other Purchase Methods:</strong> Developers may apply for <span class="delete">an</span><span class="insert">entitlements to provide a link in their app to a website the developer owns or maintains responsibility for in order to purchase digital content or services. Please see additional details below.
</span><ul class="disc margin-top-small">
<li><span class="insert">StoreKit External Purchase Link Entitlements: apps on the App Store in specific regions may offer in-app purchases and also use a StoreKit External Purchase Link Entitlement to include a link to the developer’s website that informs users of other ways to purchase digital goods or services. Learn more about these </span><a href="https://developer.apple.com/documentation/storekit/external_purchase"><span class="insert">entitlements</span></a><span class="insert">. In accordance with the</span> entitlement <span class="insert">agreements, the link may inform users about where and how to purchase those in-app purchase items, and the fact that such items may be available for a comparatively lower price. The entitlements are limited to use only in the iOS or iPadOS App Store in specific storefronts. In all other storefronts, apps and their metadata may not include buttons, external links, or other calls to action that direct customers to purchasing mechanisms other than in-app purchase.</span></li>
<li><span class="insert">Music Streaming Services Entitlements: music streaming apps in specific regions can use Music Streaming Services Entitlements to include a link (which may take the form of a buy button) to the developer’s website that informs users of other ways to purchase digital music content or services. These entitlements also permit music streaming app developers to invite users </span>to provide <span class="insert">their email address for the express purpose of sending them </span>a link <span class="delete">in their </span><span class="insert">to the developer’s website to purchase digital music content or services. Learn more about these </span><a href="https://developer.apple.com/documentation/storekit/external_purchase"><span class="insert">entitlements</span></a><span class="insert">. In accordance with the entitlement agreements, the link may inform users about where and how to purchase those in-</span>app <span class="delete">to a website the developer owns or maintains responsibility for in order to </span>purchase <span class="insert">items, and the price of </span>such items. <span class="delete">Learn more about the </span><span class="delete">entitlement</span><span class="insert">The entitlements are limited to use only in the iOS or iPadOS App Store in specific storefronts</span>. In <span class="delete">accordance with the entitlement agreement</span><span class="insert">all other storefronts</span>, <span class="delete">the link</span><span class="insert">streaming music apps and their metadata</span> may <span class="delete">inform users about where and how to purchase those</span><span class="insert">not include buttons, external links, or other calls to action that direct customers to purchasing mechanisms other than</span> in-app <span class="delete">purchase items, and the fact that such items may be available for a comparatively lower price. The entitlement is limited to use only in the iOS or iPadOS App Store on the United States storefront. In all other storefronts, apps and their metadata may not include buttons, external links, or other calls to action that direct customers to purchasing mechanisms other than in-app </span>purchase. </li>
</li>
</ul>
</li>
</ul>
</li>
<li data-sidenav="4.7 Mini apps, mini games, streaming games, chatbots, plug-ins, and game emulators" id="third-party-software"><span id="4.7"></span><strong>4.7 Mini apps, mini games, streaming games, chatbots,<span class="delete"> and</span> plug-ins<span class="insert">, and game emulators</span></strong>
<p>Apps may offer certain software that is not embedded in the binary, specifically <span class="insert">HTML5 </span>mini apps<span class="delete">,</span><span class="insert"> and</span> mini games, streaming games, chatbots, and plug-ins. <span class="insert">Additionally, retro game console emulator apps can offer to download games. </span>You are responsible for all such software offered in your app, including ensuring that such software complies with these Guidelines and all applicable laws. Software that does not comply with one or more guidelines will lead to the rejection of your app. You must also ensure that the software adheres to the additional rules that follow in 4.7.1 and 4.7.5. These additional rules are important to preserve the experience that App Store customers expect, and to help ensure user safety.</p>
</li>
</section></p></article><article class="article intro"><header><p class="date"><span>March 08, 2024</span></p><h2><a href="/articles/2024-03-08-updated-policies-features-and-clarifications/">Updated policies, upcoming features and clarifications</a></h2></header><section class="content"><p>Apple has updated their <a href="https://developer.apple.com/app-store/review/guidelines/">App Store Review Guidelines</a> to support updated policies, upcoming features, and to provide clarification.
<br><br></p>
<p><a href="https://developer.apple.com/news/?id=flmb6ri3">Apple’s own summary can be found here</a>.
</br></br></p>
<p>The complete set of changes can be seen below:</p>
</section><p class="changes"><section class="apple">
<h1 class="typography-headline">App <span class="delete">Store</span> Review Guidelines</h1>
<p class="typography-intro">Apps are changing the world, enriching people’s lives, and enabling developers like you to innovate like never before. As a result, the App Store has grown into an exciting and vibrant ecosystem for millions of developers and more than a billion users. Whether you are a first <span class="insert">-</span>time developer or a large team of experienced programmers, we are excited that you are creating apps for <span class="delete">the </span><span class="delete">App Store</span><span class="insert">our platforms,</span> and want to help you understand our guidelines so you can be confident your app will get through the review process quickly.</p>
<h3 data-sidenav id="introduction">Introduction</h3>
<p>The guiding principle of the App Store is simple—we want to provide a safe experience for users to get apps and a great opportunity for all developers to be successful. We do this by offering a highly curated App Store where every app is reviewed by experts and an editorial team helps users discover new apps every day. <span class="insert">We also scan each app for malware and other software that may impact user safety, security, and privacy. These efforts have made Apple’s platforms the safest for consumers around the world.</span></p>
<p><span class="insert">In the European Union, developers can also distribute notarized iOS apps from alternative app marketplaces. Learn more about </span><a href="https://developer.apple.com/support/dma-and-apps-in-the-eu/"><span class="insert">alternative app marketplaces</span></a><span class="insert"> and </span><a href="https://developer.apple.com/support/dma-and-apps-in-the-eu/#notarization-for-ios-apps"><span class="insert">Notarization for iOS apps</span></a><span class="insert">. You can see which guidelines apply to Notarization for iOS apps by clicking on “Show Notarization Review Guidelines Only” in the menu to the left.</span></p>
<p>For everything else there is always the open Internet. If the App Store model and guidelines <span class="insert">or alternative app marketplaces and Notarization for iOS apps </span>are not best for your app or business idea that’s okay, we provide Safari for a great web experience too.</p>
<p>On the following pages you will find our latest guidelines arranged into five clear sections: Safety, Performance, Business, Design, and Legal. The App Store is always changing and improving to keep up with the needs of our customers and our products. Your apps should change and improve as well in order to stay on the App Store.</p>
<p>A few other points to keep in <span class="delete">mind:</span><span class="insert">mind about distributing your app on our platforms:</span></p>
<ul class="disc top-level">
<li>We have lots of kids downloading lots of apps. Parental controls work great to protect kids, but you have to do your part too. So know that we’re keeping an eye out for the kids.</li>
<li>The App Store is a great way to reach hundreds of millions of people around the world. If you build an app that you just want to show to family and friends, the App Store isn’t the best way to do that. Consider using Xcode to install your app on a device for free or use Ad Hoc distribution available to Apple Developer Program members. If you’re just getting started, learn more about the <a href="https://developer.apple.com/programs/">Apple Developer Program</a>.</li>
<li>We strongly support all points of view being represented on the App Store, as long as the apps are respectful to users with differing opinions and the quality of the app experience is great. We will reject apps for any content or behavior that we believe is over the line. What line, you ask? Well, as a Supreme Court Justice once said, “I’ll know it when I see it”. And we think that you will also know it when you cross it.</li>
<li>If you attempt to cheat the system (for example, by trying to trick the review process, steal user data, copy another developer’s work, manipulate ratings or App Store discovery) your apps will be removed from the store and you will be expelled from the Apple Developer Program.</li>
<li>You are responsible for making sure everything in your app complies with these guidelines, including ad networks, analytics services, and third-party SDKs, so review and choose them carefully.</li>
<li>Some features and technologies that are not generally available to developers may be offered as an entitlement for limited use cases. For example, we offer entitlements for CarPlay Audio, HyperVisor, and Privileged File Operations. Review our documentation on developer.apple.com to learn more about entitlements.</li>
</ul>
<p>We hope these guidelines help you sail through the <span class="delete">App Review</span><span class="insert">review</span> process, and that approvals and rejections remain consistent across the board. This is a living document; new apps presenting new questions may result in new rules at any time. Perhaps your app will trigger this. We love this stuff too, and honor what you do. We’re really trying our best to create the best platform in the world for you to express your talents and make a living, too.</p>
<h3 data-nr data-sidenav id="safety"><span id="1"></span>1. Safety</h3>
<p class="section-intro">When people install an app from the App Store, they want to feel confident that it’s safe to do so—that the app doesn’t contain upsetting or offensive content, won’t damage their device, and isn’t likely to cause physical harm from its use. We’ve outlined the major pitfalls below, but if you’re looking to shock and offend people, the App Store isn’t the right place for your app.<span class="insert"> Some of these rules are also included in Notarization for iOS apps. </span></p>
<li data-nr data-sidenav="2.3 Accurate Metadata" id="accurate-metadata"><span id="2.3"></span><strong>2.3 Accurate Metadata</strong><span class="custom-tooltip-icon"><img src="https://developer.apple.com/app-store/review/images/key-icon.svg" height="17" class="asr-nr" alt="ASR & NR" />
</span>
<ul class="no-bullet margin-top-small">
<li data-nr id="2.3.1"><strong>2.3.1</strong>
<ul class="no-bullet margin-top-small">
<li data-nr><strong>(a)</strong><span class="custom-tooltip-icon"><img src="https://developer.apple.com/app-store/review/images/key-icon.svg" height="17" class="asr-nr" alt="ASR & NR" /></span> Don’t include any hidden, dormant, or undocumented features in your app; your app’s functionality should be clear to end users and App Review. All new features, functionality, and product changes must be described with specificity in the Notes for Review section of App Store Connect (generic descriptions will be rejected) and accessible for review. Similarly, marketing your app in a misleading way, such as by promoting content or services that it does not actually offer (e.g. iOS-based virus and malware scanners) or promoting a false price, whether within or outside of the App Store, is grounds for removal of your app from the App Store<span class="insert"> or a block from installing via alternative distribution</span> and termination of your developer account.</li>
<li><strong>(b)</strong> Egregious or repeated behavior is grounds for removal from the Apple Developer Program. We work hard to make the App Store a trustworthy ecosystem and expect our app developers to follow suit; if you’re dishonest, we don’t want to do business with you.</li>
</ul>
</li>
<li data-nr id="2.3.8"><strong>2.3.8</strong><span class="custom-tooltip-icon"><img src="https://developer.apple.com/app-store/review/images/key-icon.svg" height="17" class="asr-nr" alt="ASR & NR" /></span> Metadata should be appropriate for all audiences, so make sure your app and in-app purchase icons, screenshots, and previews adhere to a 4+ age rating even if your app is rated higher. For example, if your app is a game that includes violence, select images that don’t depict a gruesome death or a gun pointed at a specific character. Use of terms like “For Kids” and “For Children” in app metadata is reserved <span class="insert">in the App Store </span>for the Kids Category. Remember to ensure your metadata, including app name and icons (small, large, Apple Watch app, alternate icons, etc.), are similar to avoid creating confusion.</li>
<li id="2.3.10"><strong>2.3.10</strong> Make sure your app is focused on the iOS, iPadOS, macOS, tvOS or watchOS experience, and don’t include names, icons, or imagery of other mobile platforms <span class="insert">or alternative app marketplaces </span>in your app or metadata, unless there is specific, approved interactive functionality. Make sure your app metadata is focused on the app itself and its experience. Don’t include irrelevant information.</li>
</ul>
</li>
<li data-nr data-sidenav="2.5 Software Requirements" id="software-requirements"><span id="2.5"></span><strong>2.5 Software Requirements</strong>
<ul class="no-bullet margin-top-small">
<li data-nr id="2.5.18"><strong>2.5.18</strong><span class="custom-tooltip-icon"><img src="https://developer.apple.com/app-store/review/images/key-icon.svg" height="17" class="asr-nr" alt="ASR & NR" /></span> Display advertising should be limited to your main app binary, and should not be included in extensions, App Clips, widgets, notifications, keyboards, watchOS apps, etc. Ads displayed in an app must be appropriate for the app’s age rating, allow the user to see all information used to target them for that ad (without requiring the user to leave the app), and may not engage in targeted or behavioral advertising based on sensitive user data such as health/medical data (e.g. from the HealthKit APIs), school and classroom data (e.g. from ClassKit), or from kids (e.g. from apps in the <span class="insert">App Store’s </span>Kids Category), etc. Interstitial ads or ads that interrupt or block the user experience must clearly indicate that they are an ad, must not manipulate or trick users into tapping into them, and must provide easily accessible and visible close/skip buttons large enough for people to easily dismiss the ad. Apps that contain ads must also include the ability for users to report any inappropriate or age-inappropriate ads.</li>
</ul>
</li>
<li data-nr data-sidenav="4.4 Extensions" id="extensions"><span id="4.4"></span><strong>4.4 Extensions</strong><span class="custom-tooltip-icon"><img src="https://developer.apple.com/app-store/review/images/key-icon.svg" height="17" class="asr-nr" alt="ASR & NR" />
</span>
<p data-nr>Apps hosting or containing extensions must comply with the <a href="https://developer.apple.com/library/archive/documentation/General/Conceptual/ExtensibilityPG/index.html#apple_ref/doc/uid/TP40014214/">App Extension Programming Guide<span class="loc-en-only"></span></a>, the <a href="https://developer.apple.com/documentation/safariservices/safari_app_extensions/">Safari <span class="delete">App Extensions</span><span class="insert">app extensions</span> documentation<span class="loc-en-only"></span></a>, or the <a href="https://developer.apple.com/documentation/safariservices/safari_web_extensions">Safari <span class="delete">Web Extensions</span><span class="insert">web extensions</span> documentation<span class="loc-en-only"></span></a> and should include some functionality, such as help screens and settings interfaces where possible. You should clearly and accurately disclose what extensions are made available in the app’s marketing text, and the extensions may not include marketing, advertising, or in-app purchases.</p>
</li>
<li data-nr data-sidenav="4.5 Apple Sites and Services" id="apple-sites-and-services"><span id="4.5"></span><strong>4.5<span class="custom-tooltip-icon"><img src="https://developer.apple.com/app-store/review/images/key-icon.svg" height="17" class="asr-nr" alt="ASR & NR" /></span> Apple Sites and Services</strong>
<ul class="no-bullet margin-top-small">
<li data-nr id="4.5.2"><strong>4.5.2</strong><span class="custom-tooltip-icon"><img src="https://developer.apple.com/app-store/review/images/key-icon.svg" height="17" class="asr-nr" alt="ASR & NR" /></span> Apple Music <ul class="no-bullet margin-top-small">
<li data-nr><strong>(ii)</strong> Using the MusicKit APIs is not a replacement for securing the licenses you might need for a deeper or more complex music integration. For example, if you want your app to play a specific song at a particular moment, or to create audio or video files that can be shared to social media, you’ll need to contact rights-holders directly to get their permission (e.g. synchronization or adaptation rights) and assets. Cover art and other metadata may only be used in connection with music playback or playlists (including <span class="delete">App Store</span> screenshots displaying your app’s functionality), and should not be used in any marketing or advertising without getting specific authorization from rights-holders. Make sure to follow the <a href="https://www.apple.com/itunes/marketing-on-music/identity-guidelines.html">Apple Music Identity Guidelines<span class="loc-en-only"></span></a> when integrating Apple Music services in your app.</li>
</ul>
</li>
</ul>
</li>
<li data-nr data-sidenav="4.8 Login Services" id="login-services"><span id="4.8"></span><strong>4.8 Login Services</strong><span class="custom-tooltip-icon"><img src="https://developer.apple.com/app-store/review/images/key-icon.svg" height="17" class="asr-nr" alt="ASR & NR" />
</span>
<p data-nr>Apps that use a third-party or social login service (such as Facebook Login, Google Sign-In, Sign in with Twitter, Sign In with LinkedIn, Login with Amazon, or WeChat Login) to set up or authenticate the user’s primary account with the app must also offer as an equivalent option another login service with the following features:</p>
<ul data-nr class="disc margin-top-small">
<li data-nr>the login service limits data collection to the user’s name and email address<span class="insert">;</span></li>
<li data-nr>the login service allows users to keep their email address private as part of setting up their account<span class="insert">; and</span></li>
<li data-nr>the login service does not <span class="delete">track users as</span><span class="insert">collect interactions with your app for advertising purposes without consent.</span></li>
</ul>
<p data-nr><span class="insert">A user’s primary account is the account</span> they <span class="delete">interact</span><span class="insert">establish</span> with your app
<span class="delete">A user’s primary account is the account they establish with your app</span> for the purposes of identifying themselves, signing in, and accessing your features and associated services.</p>
<p data-nr>Another login service is not required if:
<ul data-nr class="disc margin-top-small">
<li data-nr>Your app exclusively uses your company’s own account setup and sign-in systems.</li>
<li>
Your app<span class="insert"> is an alternative app marketplace, or an app distributed from an alternative app marketplace, that uses a marketplace-specific login for account, download, and commerce features.</span></li>
<li data-nr><span class="insert">Your app</span> is an education, enterprise, or business app that requires the user to sign in with an existing education or enterprise account.</li>
<li data-nr>Your app uses a government or industry-backed citizen identification system or electronic ID to authenticate users.</li>
<li data-nr>Your app is a client for a specific third-party service and users are required to sign in to their mail, social media, or other third-party account directly to access their content.</li>
</ul>
</p>
</li>
<li data-nr data-sidenav="5.1 Privacy" id="privacy"><span id="5.1"></span><strong>5.1 Privacy</strong><span class="custom-tooltip-icon"><img src="https://developer.apple.com/app-store/review/images/key-icon.svg" height="17" class="asr-nr" alt="ASR & NR" />
</span>
<ul class="no-bullet margin-top-small">
<li data-nr data-sidenav="5.1.1 Data Collection and Storage" id="data-collection-and-storage"><span id="5.1.1"></span><strong>5.1.1 Data Collection and Storage</strong><span class="custom-tooltip-icon"><img src="https://developer.apple.com/app-store/review/images/key-icon.svg" height="17" class="asr-nr" alt="ASR & NR" /></span>
<ul class="no-bullet margin-top-small">
<li data-nr id="5.1.1v"><strong>(v) Account Sign-In: </strong>If your app doesn’t include significant account-based features, let people use it without a login. If your app supports account creation, you must also <a href="https://developer.apple.com/support/offering-account-deletion-in-your-app/">offer account deletion within the app</a>. Apps may not require users to enter personal information to function, except when directly relevant to the core functionality of the app or required by law. If your core app functionality is not related to a specific social network (e.g. Facebook, WeChat, Weibo, <span class="delete">Twitter</span><span class="insert">X</span>, etc.), you must provide access without a login or via another mechanism. Pulling basic profile information, sharing to the social network, or inviting friends to use the app are not considered core app functionality. The app must also include a mechanism to revoke social network credentials and disable data access between the app and social network from within the app. An app may not store credentials or tokens to social networks off of the device and may only use such credentials or tokens to directly connect to the social network from the app itself while the app is in use.</li>
<li data-nr><strong>(viii) </strong>Apps that compile personal information from any source that is not directly from the user or without the user’s explicit consent, even public databases, are not permitted on the App Store<span class="insert"> or alternative app marketplaces</span>.</li>
</ul>
</li>
<li data-nr data-sidenav="5.1.5 Location Services" id="location"><span id="5.1.5"></span><strong>5.1.5 Location Services</strong><span class="custom-tooltip-icon"><img src="https://developer.apple.com/app-store/review/images/key-icon.svg" height="17" class="asr-nr" alt="ASR & NR" />
</span>
<p data-nr>Use Location <span class="insert">Services in your app only when it is directly relevant to the features and </span>services <span class="delete">in your app only when it is directly relevant to the features and services </span>provided by the app. Location-based APIs shouldn’t be used to provide emergency services or autonomous control over vehicles, aircraft, and other devices, except for small devices such as lightweight drones and toys, or remote control car alarm systems, etc. Ensure that you notify and obtain consent before collecting, transmitting, or using location data. If your app uses <span class="delete">location services</span><span class="insert">Location Services</span>, be sure to explain the purpose in your app; refer to the <a href="https://developer.apple.com/design/human-interface-guidelines/patterns/accessing-private-data/">Human Interface Guidelines<span class="loc-cj"></span></a> for best practices for doing so.</p>
</li>
</ul>
</li>
<li data-nr data-sidenav="5.4 VPN Apps" id="vpn-apps"><span id="5.4"></span><strong>5.4 VPN Apps</strong><span class="custom-tooltip-icon"><img src="https://developer.apple.com/app-store/review/images/key-icon.svg" height="17" class="asr-nr" alt="ASR & NR" />
</span>
<p data-nr>Apps offering VPN services must utilize the <a href="https://developer.apple.com/documentation/networkextension/nevpnmanager/">NEVPNManager API<span class="loc-en-only"></span></a> and may only be offered by developers enrolled as an organization. You must make a clear declaration of what user data will be collected and how it will be used on an app screen prior to any user action to purchase or otherwise use the service. Apps offering VPN services may not sell, use, or disclose to third parties any data for any purpose, and must commit to this in their privacy policy. VPN apps must not violate local laws, and if you choose to make your VPN app available in a territory that requires a VPN license, you must provide your license information in the App Review Notes field. Parental control, content blocking, and security apps, among others, from approved providers may also use the NEVPNManager API. Apps that do not comply with this guideline will be removed from the App Store<span class="insert"> and blocked from installing via alternative distribution</span> and you may be removed from the Apple Developer Program.</p>
</li>
<li data-nr data-sidenav="5.5 Mobile Device Management" id="mobile-device-management"><span id="5.5"></span><strong>5.5 Mobile Device Management</strong><span class="custom-tooltip-icon"><img src="https://developer.apple.com/app-store/review/images/key-icon.svg" height="17" class="asr-nr" alt="ASR & NR" />
</span>
<p data-nr>Mobile Device Management Apps that offer Mobile Device Management (MDM) services must request this capability from Apple. Such apps may only be offered by commercial enterprises, educational institutions, or government agencies, and in limited cases, companies using MDM for parental control services or device security. You must make a clear declaration of what user data will be collected and how it will be used on an app screen prior to any user action to purchase or otherwise use the service. MDM apps must not violate any applicable laws. Apps offering MDM services may not sell, use, or disclose to third parties any data for any purpose, and must commit to this in their privacy policy. In limited cases, third-party analytics may be permitted provided that the services only collect or transmit data about the performance of the developer’s MDM app, and not any data about the user, the user’s device, or other apps used on that device. Apps offering configuration profiles must also adhere to these requirements. Apps that do not comply with this guideline will be removed from the App Store<span class="insert"> and blocked from installing via alternative distribution</span> and you may be removed from the Apple Developer Program.</p>
</li>
<li data-nr data-sidenav="5.6 Developer Code of Conduct" id="code-of-conduct"><span id="5.6"></span><strong>5.6 Developer Code of Conduct</strong><span class="custom-tooltip-icon"><img src="https://developer.apple.com/app-store/review/images/key-icon.svg" height="17" class="asr-nr" alt="ASR & NR" />
</span>
<p data-nr>Customer trust is <span class="delete">the</span><span class="insert">a</span> cornerstone of the App <span class="delete">Store’s</span><span class="delete"> success</span><span class="insert">ecosystem</span>. Apps should never prey on users or attempt to rip off customers, trick them into making unwanted purchases, force them to share unnecessary data, raise prices in a tricky manner, charge for features or content that are not delivered, or engage in any other manipulative practices within or outside of the app.</p>
<ul class="no-bullet margin-top-small">
<li data-nr id="5.6.2"><strong>5.6.2 Developer Identity</strong><span class="custom-tooltip-icon"><img src="https://developer.apple.com/app-store/review/images/key-icon.svg" height="17" class="asr-nr" alt="ASR & NR" />
</span>
<p data-nr>Providing verifiable information to Apple and customers is critical to customer trust. Your representation of yourself, your business, and your offerings on the App Store<span class="insert"> or alternative app marketplaces</span> must be accurate. The information you provide must be truthful, relevant, and up-to-date so that Apple and customers understand who they are engaging with and can contact you regarding any issues.</p>
</li>
</ul>
</li>
<h3 data-sidenav id="after-you-submit">After You Submit</h3>
<ul class="disc top-level">
<li><strong>Timing</strong>: App Review will examine your app as soon as we can. However, if your app is complex or presents new issues, it may require greater scrutiny and consideration. And remember that if your app is repeatedly rejected for the same guideline violation or you’ve attempted to manipulate the <span class="delete">App Review</span><span class="insert">review</span> process, review of your app will take longer to complete. Learn more about <a href="https://developer.apple.com/distribute/app-review/" class="nowrap">App Review</a>.</li>
<li><strong>Bug Fix Submissions</strong>: For apps that are already on the App Store<span class="insert"> or an alternative app marketplace</span>, bug fixes will <span class="delete">no longer</span><span class="insert">not</span> be delayed over guideline violations except for those related to legal or safety issues. If your app has been rejected, and qualifies for this process, please use App Store Connect to communicate directly with the App Review team indicating that you would like to take advantage of this process and plan to address the issue in your next submission.</li>
</ul>
</section></p></article><article class="article intro"><header><p class="date"><span>January 29, 2024</span></p><h2><a href="/articles/2024-01-29-notarization-in-european-union/">Updated rules on app distribution in the European Union and more</a></h2></header><section class="content"><p>Apple has updated their <a href="https://developer.apple.com/app-store/review/guidelines/">App Store Review Guidelines</a> to support updated policies, upcoming features, and to provide clarification. They now also indicate which guidelines only apply to <a href="https://developer.apple.com/support/dma-and-apps-in-the-eu/">Notarization for iOS apps in the European Union</a>.
<br><br></p>
<p>As you will see in the changes, Apple is now indicating which guidelines apply to Notarization with a small key icon. To better understand the context, we are showing the full guidelines for a section that has a key icon, even though the guidelines themselves nay not have changed.<br><br></p>
<p>For sections where only some guidelines apply for Notarization, only those guidelines have been included, unless they have changed in some other way. For example, guideline 2.5.15 is not included, since it is does not apply for Notarization even though some of the other guidelines under section 2.5 do.<br><br></p>
<p><a href="https://developer.apple.com/news/?id=7j1f99yf">Apple’s own summary can be found here</a>.
</br></br></p>
<p>The complete set of changes can be seen below:</p>
</section><p class="changes"><section class="apple">
<h3 data-sidenav id="before-you-submit">Before You Submit</h3>
<p class="margin-top"><span class="insert">Guidelines that include </span><img src="https://developer.apple.com/app-store/review/images/key-icon.svg" height="17" class="asr-nr" alt="ASR & NR" /><span class="insert"> apply to </span><a href="https://developer.apple.com/support/dma-and-apps-in-the-eu/#notarization-for-ios-apps"><span class="insert">Notarization for iOS apps</span></a><span class="insert"> in the EU.</span></p>
<li data-sidenav="1.1 Objectionable Content" id="objectionable-content"><span id="1.1"></span><strong>1.1 Objectionable Content</strong>
<ul class="no-bullet margin-top-small">
<li id="1.1.6"><strong>1.1.6</strong><span class="insert"><img src="https://developer.apple.com/app-store/review/images/key-icon.svg" height="17" class="asr-nr" alt="ASR & NR" /></span> False information and features, including inaccurate device data or trick/joke functionality, such as fake location trackers. Stating that the app is “for entertainment purposes” won’t overcome this guideline. Apps that enable anonymous or prank phone calls or SMS/MMS messaging will be rejected.</li>
</ul>
</li>
<li data-sidenav="1.4 Physical Harm" id="physical-harm"><span id="1.4"></span><strong>1.4 Physical Harm</strong><span class="insert"><img src="https://developer.apple.com/app-store/review/images/key-icon.svg" height="17" class="asr-nr" alt="ASR & NR" /></span>
<p>If your app behaves in a way that risks physical harm, we may reject it. For example:</p>
<ul class="no-bullet margin-top-small">
<li id="1.4.1"><strong>1.4.1</strong><span class="insert"><img src="https://developer.apple.com/app-store/review/images/key-icon.svg" height="17" class="asr-nr" alt="ASR & NR" /></span> Medical apps that could provide inaccurate data or information, or that could be used for diagnosing or treating patients may be reviewed with greater scrutiny.
<ul class="disc margin-top-small">
<li>Apps must clearly disclose data and methodology to support accuracy claims relating to health measurements, and if the level of accuracy or methodology cannot be validated, we will reject your app. For example, apps that claim to take x-rays, measure blood pressure, body temperature, blood glucose levels, or blood oxygen levels using only the sensors on the device are not permitted.</li>
<li>Apps should remind users to check with a doctor in addition to using the app and before making medical decisions.</li>
</ul>
If your medical app has received regulatory clearance, please submit a link to that documentation with your app.</li>
<li id="1.4.2"><strong>1.4.2</strong><span class="insert"><img src="https://developer.apple.com/app-store/review/images/key-icon.svg" height="17" class="asr-nr" alt="ASR & NR" /></span> Drug dosage calculators must come from the drug manufacturer, a hospital, university, health insurance company, pharmacy or other approved entity, or receive approval by the FDA or one of its international counterparts. Given the potential harm to patients, we need to be sure that the app will be supported and updated over the long term.</li>
<li id="1.4.3"><strong>1.4.3</strong><span class="insert"><img src="https://developer.apple.com/app-store/review/images/key-icon.svg" height="17" class="asr-nr" alt="ASR & NR" /></span> Apps that encourage consumption of tobacco and vape products, illegal drugs, or excessive amounts of alcohol are not permitted<span class="delete"> on the </span><span class="delete">App Store</span>. Apps that encourage minors to consume any of these substances will be rejected. Facilitating the sale of controlled substances (except for licensed pharmacies and licensed or otherwise legal cannabis dispensaries), or tobacco is not allowed.</li>
<li id="1.4.4"><strong>1.4.4</strong><span class="insert"><img src="https://developer.apple.com/app-store/review/images/key-icon.svg" height="17" class="asr-nr" alt="ASR & NR" /></span> Apps may only display DUI checkpoints that are published by law enforcement agencies, and should never encourage drunk driving or other reckless behavior such as excessive speed.</li>
<li id="1.4.5"><strong>1.4.5</strong><span class="insert"><img src="https://developer.apple.com/app-store/review/images/key-icon.svg" height="17" class="asr-nr" alt="ASR & NR" /></span> Apps should not urge customers to participate in activities (like bets, challenges, etc.) or use their devices in a way that risks physical harm to themselves or others.</li>
</ul>
</li>
<li data-sidenav="1.5 Developer Information" id="developer-information"><span id="1.5"></span><strong>1.5 Developer Information</strong><span class="insert"><img src="https://developer.apple.com/app-store/review/images/key-icon.svg" height="17" class="asr-nr" alt="ASR & NR" /></span>
<p>People need to know how to reach you with questions and support issues. Make sure your app and its Support URL include an easy way to contact you; this is particularly important for apps that may be used in the classroom. Failure to include accurate and up-to-date contact information not only frustrates customers, but may violate the law in some countries or regions. Also ensure that Wallet passes include valid contact information from the issuer and are signed with a dedicated certificate assigned to the brand or trademark owner of the pass.</p>
</li>
<li data-sidenav="1.6 Data Security" id="data-security"><span id="1.6"></span><strong>1.6 Data Security</strong><span class="insert"><img src="https://developer.apple.com/app-store/review/images/key-icon.svg" height="17" class="asr-nr" alt="ASR & NR" /></span>
<p>Apps should implement appropriate security measures to ensure proper handling of user information collected pursuant to the <span class="nowrap">Apple Developer</span> Program License Agreement and these Guidelines (see Guideline 5.1 for more information) and prevent its unauthorized use, disclosure, or access by third parties.</p>
</li>
<li data-sidenav="2.3 Accurate Metadata" id="accurate-metadata"><span id="2.3"></span><strong>2.3 Accurate Metadata</strong><span class="insert"><img src="https://developer.apple.com/app-store/review/images/key-icon.svg" height="17" class="asr-nr" alt="ASR & NR" /></span>
<p>Customers should know what they’re getting when they download or buy your app, so make sure all your app metadata, including privacy information, your app description, screenshots, and previews accurately reflect the app’s core experience and remember to keep them up-to-date with new versions.</p>
<ul class="no-bullet margin-top-small">
<li id="2.3.1"><strong>2.3.1</strong>
<ul class="no-bullet margin-top-small">
<li><strong><span class="insert">(a)</span></strong><span class="insert"><img src="https://developer.apple.com/app-store/review/images/key-icon.svg" height="17" class="asr-nr" alt="ASR & NR" /></span> Don’t include any hidden, dormant, or undocumented features in your app; your app’s functionality should be clear to end users and <span class="nowrap">App Review.</span> All new features, functionality, and product changes must be described with specificity in the Notes for Review section of <span class="nowrap">App Store Connect</span> (generic descriptions will be rejected) and accessible for review. Similarly, marketing your app in a misleading way, such as by promoting content or services that it does not actually offer (e.g. iOS-based virus and malware scanners) or promoting a false price, whether within or outside of the <span class="nowrap">App Store,</span> is grounds for removal of your app from the <span class="nowrap">App Store</span> and termination of your developer account.</li>
<li><strong><span class="insert">(b)</span></strong> Egregious or repeated behavior is grounds for removal from the <span class="nowrap">Apple Developer</span> Program. We work hard to make the <span class="nowrap">App Store</span> a trustworthy ecosystem and expect our app developers to follow suit; if you’re dishonest, we don’t want to do business with you.</li>
</ul>
</li>
<li id="2.3.5"><strong>2.3.5</strong><span class="insert"><img src="https://developer.apple.com/app-store/review/images/key-icon.svg" height="17" class="asr-nr" alt="ASR & NR" /></span> Select the most appropriate category for your app, and check out the <a href="https://developer.apple.com/app-store/categories/"><span class="nowrap">App Store</span> Category Definitions<span class="loc-apac"></span></a> if you need help. If you’re way off base, we may change the category for you.</li>
<li id="2.3.6"><strong>2.3.6</strong><span class="insert"><img src="https://developer.apple.com/app-store/review/images/key-icon.svg" height="17" class="asr-nr" alt="ASR & NR" /></span> Answer the age rating questions in <span class="nowrap">App Store Connect</span> honestly so that your app aligns properly with parental controls. If your app is mis-rated, customers might be surprised by what they get, or it could trigger an inquiry from government regulators. If your app includes media that requires the display of content ratings or warnings (e.g. films, music, games, etc.), you are responsible for complying with local requirements in each territory where your app is available.</li>
<li id="2.3.7"><strong>2.3.7</strong><span class="insert"><img src="https://developer.apple.com/app-store/review/images/key-icon.svg" height="17" class="asr-nr" alt="ASR & NR" /></span> Choose a unique app name, assign keywords that accurately describe your app, and don’t try to pack any of your metadata with trademarked terms, popular app names, pricing information, or other irrelevant phrases just to game the system. App names must be limited to 30 characters. Metadata such as app names, subtitles, screenshots, and previews should not include prices, terms, or descriptions that are not specific to the metadata type. App subtitles are a great way to provide additional context for your app; they must follow our standard metadata rules and should not include inappropriate content, reference other apps, or make unverifiable product claims. Apple may modify inappropriate keywords at any time or take other appropriate steps to prevent abuse.</li>
<li id="2.3.8"><strong>2.3.8</strong><span class="insert"><img src="https://developer.apple.com/app-store/review/images/key-icon.svg" height="17" class="asr-nr" alt="ASR & NR" /></span> Metadata should be appropriate for all audiences, so make sure your app and in-app purchase icons, screenshots, and previews adhere to a 4+ age rating even if your app is rated higher. For example, if your app is a game that includes violence, select images that don’t depict a gruesome death or a gun pointed at a specific character. Use of terms like “For Kids” and “For Children” in app metadata is reserved for the Kids Category. Remember to ensure your metadata, including app name and icons (small, large, <span class="nowrap">Apple Watch</span> app, alternate icons, etc.), are similar to avoid creating confusion.</li>
</ul>
</li>
<li data-sidenav="2.4 Hardware Compatibility" id="hardware-compatibility"><span id="2.4"></span><strong>2.4 Hardware Compatibility</strong>
<ul class="no-bullet margin-top-small">
<li id="2.4.2"><strong>2.4.2</strong><span class="insert"><img src="https://developer.apple.com/app-store/review/images/key-icon.svg" height="17" class="asr-nr" alt="ASR & NR" /></span> Design your app to use power efficiently and be used in a way that does not risk damage to the device. Apps should not rapidly drain battery, generate excessive heat, or put unnecessary strain on device resources. For example, apps should not encourage placing the device under a mattress or pillow while charging or perform excessive write cycles to the solid state drive. Apps, including any third-party advertisements displayed within them, may not run unrelated background processes, such as cryptocurrency mining.</li>
<li id="2.4.4"><strong>2.4.4</strong><span class="insert"><img src="https://developer.apple.com/app-store/review/images/key-icon.svg" height="17" class="asr-nr" alt="ASR & NR" /></span> Apps should never suggest or require a restart of the device or modifications to system settings unrelated to the core functionality of the app. For example, don’t encourage users to turn off Wi-Fi, disable security features, etc.</li>
</ul>
</li>
<li data-sidenav="2.5 Software Requirements" id="software-requirements"><span id="2.5"></span><strong>2.5 Software Requirements</strong>
<ul class="no-bullet margin-top-small">
<li id="2.5.1"><strong>2.5.1</strong><span class="insert"><img src="https://developer.apple.com/app-store/review/images/key-icon.svg" height="17" class="asr-nr" alt="ASR & NR" /></span> Apps may only use public APIs and must run on the currently shipping OS. Learn more about <a href="https://developer.apple.com/documentation/">public APIs<span class="loc-en-only"></span></a>. Keep your apps up-to-date and make sure you phase out any deprecated features, frameworks or technologies that will no longer be supported in future versions of an OS. Apps should use APIs and frameworks for their intended purposes and indicate that integration in their app description. For example, the HomeKit framework should provide home automation services; and HealthKit should be used for health and fitness purposes and integrate with the Health app.</li>
<li id="2.5.2"><strong>2.5.2</strong><span class="insert"><img src="https://developer.apple.com/app-store/review/images/key-icon.svg" height="17" class="asr-nr" alt="ASR & NR" /></span> Apps should be self-contained in their bundles, and may not read or write data outside the designated container area, nor may they download, install, or execute code which introduces or changes features or functionality of the app, including other apps. Educational apps designed to teach, develop, or allow students to test executable code may, in limited circumstances, download code provided that such code is not used for other purposes. Such apps must make the source code provided by the app completely viewable and editable by the user.</li>
<li id="2.5.3"><strong>2.5.3</strong><span class="insert"><img src="https://developer.apple.com/app-store/review/images/key-icon.svg" height="17" class="asr-nr" alt="ASR & NR" /></span> Apps that transmit viruses, files, computer code, or programs that may harm or disrupt the normal operation of the operating system and/or hardware features, including Push Notifications and Game Center, will be rejected. Egregious violations and repeat behavior will result in removal from the <span class="nowrap">Apple Developer Program.</span></li>
<li id="2.5.4"><strong>2.5.4</strong><span class="insert"><img src="https://developer.apple.com/app-store/review/images/key-icon.svg" height="17" class="asr-nr" alt="ASR & NR" /></span> Multitasking apps may only use background services for their intended purposes: VoIP, audio playback, location, task completion, local notifications, etc.</li>
<li id="2.5.6"><strong>2.5.6</strong> Apps that browse the web must use the appropriate WebKit framework and WebKit JavaScript.<span class="insert"> You may apply for an entitlement to use an alternative web browser engine in your app. </span><a href="https://developer.apple.com/support/alternative-browser-engines/"><span class="insert">Learn more about these entitlements</span></a><span class="insert">.</span></li>
<li id="2.5.7"><strong>2.5.7</strong> <span class="delete">Video streaming content over a cellular network longer than 10 minutes must use HTTP Live Streaming and include a baseline 192 kbps HTTP Live stream</span><span class="insert">Intentionally omitted</span>.</li>
<li id="2.5.9"><strong>2.5.9</strong><span class="insert"><img src="https://developer.apple.com/app-store/review/images/key-icon.svg" height="17" class="asr-nr" alt="ASR & NR" /></span> Apps that alter or disable the functions of standard switches, such as the Volume Up/Down and Ring/Silent switches, or other native user interface elements or behaviors will be rejected. For example, apps should not block links out to other apps or other features that users would expect to work a certain way.<span class="delete"> Learn more about proper handling of </span><span class="delete">links</span><span class="delete">. </span></li>
<li id="2.5.11"><strong>2.5.11</strong><span class="insert"><img src="https://developer.apple.com/app-store/review/images/key-icon.svg" height="17" class="asr-nr" alt="ASR & NR" /></span> SiriKit and Shortcuts
<ul class="no-bullet margin-top-small">
<li><strong>(i)</strong> Apps integrating SiriKit and Shortcuts should only sign up for intents they can handle without the support of an additional app and that users would expect from the stated functionality. For example, if your app is a meal planning app, you should not incorporate an intent to start a workout, even if the app shares integration with a fitness app.</li>
<li><strong>(ii)</strong> Ensure that the vocabulary and phrases in your plist pertains to your app and the Siri functionality of the intents the app has registered for. Aliases must relate directly to your app or company name and should not be generic terms or include third-party app names or services.</li>
<li><strong>(iii)</strong> Resolve the Siri request or Shortcut in the most direct way possible and do not insert ads or other marketing between the request and its fulfillment. Only request a disambiguation when required to complete the task (e.g. asking the user to specify a particular type of workout).</li>
</ul>
</li>
<li id="2.5.12"><strong>2.5.12</strong><span class="insert"><img src="https://developer.apple.com/app-store/review/images/key-icon.svg" height="17" class="asr-nr" alt="ASR & NR" /></span> Apps using CallKit or including an SMS Fraud Extension should only block phone numbers that are confirmed spam. Apps that include call-, SMS-, and MMS- blocking functionality or spam identification must clearly identify these features in their marketing text and explain the criteria for their blocked and spam lists. You may not use the data accessed via these tools for any purpose not directly related to operating or improving your app or extension (e.g. you may not use, share, or sell it for tracking purposes, creating user profiles, etc.).</li>
<li id="2.5.13"><strong>2.5.13</strong><span class="insert"><img src="https://developer.apple.com/app-store/review/images/key-icon.svg" height="17" class="asr-nr" alt="ASR & NR" /></span> Apps using facial recognition for account authentication must use <a href="https://developer.apple.com/documentation/localauthentication/">LocalAuthentication<span class="loc-en-only"></span></a> (and not ARKit or other facial recognition technology) where possible, and must use an alternate authentication method for users under 13 years old.</li>
<li id="2.5.14"><strong>2.5.14</strong><span class="insert"><img src="https://developer.apple.com/app-store/review/images/key-icon.svg" height="17" class="asr-nr" alt="ASR & NR" /></span> Apps must request explicit user consent and provide a clear visual and/or audible indication when recording, logging, or otherwise making a record of user activity. This includes any use of the device camera, microphone, screen recordings, or other user inputs.</li>
<li id="2.5.16"><strong>2.5.16</strong><span class="insert"><img src="https://developer.apple.com/app-store/review/images/key-icon.svg" height="17" class="asr-nr" alt="ASR & NR" /></span><span class="insert"> Widgets, extensions, and notifications should be related to the content and functionality of your app.
</span><ul class="no-bullet margin-top-small">
<li><strong><span class="insert">(a)</span></strong><span class="insert"> Additionally, all</span> <span class="nowrap">App <span class="delete">Clips,</span><span class="insert">Clip</span></span> <span class="delete">widgets, extensions, and notifications should be related to the content</span><span class="insert">features</span> and functionality <span class="delete">of your</span><span class="insert">must be included in the main</span> app<span class="insert"> binary</span>.<span class="delete"> Additionally, all</span> <span class="nowrap">App <span class="delete">Clip</span><span class="delete"> features and functionality must be included in the main app binary. </span><span class="delete">App </span>Clips</span> cannot contain advertising.</li>
</ul>
</li>
<li id="2.5.17"><strong>2.5.17</strong><span class="insert"><img src="https://developer.apple.com/app-store/review/images/key-icon.svg" height="17" class="asr-nr" alt="ASR & NR" /></span> Apps that support Matter must use Apple’s support framework for Matter to initiate pairing. In addition, if you choose to use any Matter software component in your app other than the <span class="nowrap">Matter SDK</span> provided by Apple, the software component must be certified by the <a href="https://csa-iot.org/">Connectivity Standards Alliance<span class="loc-c"></span></a> for the platform it runs on.</li>
<li id="2.5.18"><strong>2.5.18</strong><span class="insert"><img src="https://developer.apple.com/app-store/review/images/key-icon.svg" height="17" class="asr-nr" alt="ASR & NR" /></span> Display advertising should be limited to your main app binary, and should not be included in extensions, App Clips, widgets, notifications, keyboards, watchOS apps, etc. Ads displayed in an app must be appropriate for the app’s age rating, allow the user to see all information used to target them for that ad (without requiring the user to leave the app), and may not engage in targeted or behavioral advertising based on sensitive user data such as health/medical data (e.g. from the HealthKit APIs), school and classroom data (e.g. from ClassKit), or from kids (e.g. from apps in the Kids Category), etc. Interstitial ads or ads that interrupt or block the user experience must clearly indicate that they are an ad, must not manipulate or trick users into tapping into them, and must provide easily accessible and visible close/skip buttons large enough for people to easily dismiss the ad. Apps that contain ads must also include the ability for users to report any inappropriate or age-inappropriate ads.</li>
</ul>
</li>
<li data-sidenav="3.1 Payments" id="payments"><span id="3.1"></span><strong>3.1 Payments</strong>
<ul class="no-bullet margin-top-small">
<li data-sidenav="3.1.2 Subscriptions" id="subscriptions"><span id="3.1.2"></span><strong>3.1.2 Subscriptions:</strong> Apps may offer auto-<span class="delete">renewing</span><span class="insert">renewable</span> in-app purchase subscriptions, regardless of category on the <span class="nowrap">App Store.</span> When incorporating auto-renewable subscriptions into your app, be sure to follow the guidelines below.</li>
<li id="permissible-uses"><span id="3.1.2a"></span><strong>3.1.2(a) Permissible uses:</strong> If you offer an auto-<span class="delete">renewing</span><span class="insert">renewable</span> subscription, you must provide ongoing value to the customer, and the subscription period must last at least seven days and be available across all of the user’s devices. While the following list is not exhaustive, examples of appropriate subscriptions include: new game levels; episodic content; multiplayer support; apps that offer consistent, substantive updates; access to large collections of, or continually updated, media content; software as a service (“SAAS”); and cloud support. In addition:
<ul class="disc margin-top-small">
<li>Auto-<span class="delete">renewing</span><span class="insert">renewable</span> subscription apps may offer a free trial period to customers by providing the relevant information set forth in <span class="nowrap">App Store Connect.</span> <a href="https://developer.apple.com/app-store/subscriptions/#providing-subscription-offers">Learn more about providing subscription offers<span class="loc-apac"></span>.</a></li>
<li>Cellular carrier apps may include auto-<span class="delete">renewing</span><span class="insert">renewable</span> music and video subscriptions when purchased in bundles with new cellular data plans, with prior approval by Apple. Other auto-<span class="delete">renewing</span><span class="insert">renewable</span> subscriptions may also be included in bundles when purchased with new cellular data plans, with prior approval by Apple, if the cellular carrier apps support in-app purchase for users. Such subscriptions cannot include access to or discounts on consumable items, and the subscriptions must terminate coincident with the cellular data plan.</li>
</ul>
</li>
<li><span id="3.1.2c"></span><strong>3.1.2(c) Subscription Information:</strong> Before asking a customer to subscribe, you should clearly describe what the user will get for the price. How many issues per month? How much cloud storage? What kind of access to your service? Ensure you clearly communicate the requirements described in <a href="https://developer.apple.com/support/terms/apple-developer-program-license-agreement/#S2">Schedule 2 of the Apple Developer Program License Agreement<span class="delete">, found in </span><span class="delete">Agreements, Tax, and Banking</span></a>.</li>
<li><span class="delete"><b>3.1.6 Apple Pay:</b></span><span class="delete"> Apps using </span><span class="delete">Apple Pay</span><span class="delete"> must provide all material purchase information to the user prior to sale of any good or service and must use </span><span class="delete">Apple Pay</span><span class="delete"> branding and user interface elements correctly, as described in the </span><span class="delete">Apple Pay</span><span class="delete"> Marketing Guidelines</span><span class="delete"> and </span><span class="delete">Human Interface Guidelines</span><span class="delete">. Apps using </span><span class="delete">Apple Pay</span><span class="delete"> to offer recurring payments must, at a minimum, disclose the following information:<br>
</span>
<ul>
<li><span class="delete">The length of the renewal term and the fact that it will continue until canceled</span></li>
<li><span class="delete">What will be provided during each period</span></li>
<li><span class="delete">The actual charges that will be billed to the customer</span></li>
<li><span class="delete">How to cancel</span></li>
</ul>
</li>
</ul>
</li>
<li data-sidenav="3.2 Other Business Model Issues" id="other-business-model-issues"><span id="3.2"></span><strong>3.2 Other Business Model Issues</strong>
<ul class="no-bullet margin-top-small">
<li data-sidenav="3.2.2 Unacceptable" id="unacceptable"><span id="3.2.2"></span><strong>3.2.2 Unacceptable</strong>
<ul class="no-bullet margin-top-small">
<li><strong>(ii)</strong> <span class="delete">Monetizing built-in capabilities provided by the hardware or operating system, such as Push Notifications, the camera, or the gyroscope; or Apple services, such as </span><span class="delete">Apple Music</span><span class="delete"> access or iCloud storage</span><span class="insert">Intentionally omitted</span>.</li>
<li><strong>(vi)</strong> <span class="delete">Apps should allow a user to get what they’ve paid for without performing additional tasks, such as posting on social media, uploading contacts, checking in to the app a certain number of times, etc. Apps should not require users to rate the app, review the app, watch videos, download other apps, tap on advertisements, enable tracking, or take other similar actions in order to access functionality, content, use the app, or receive monetary or other compensation, including but not limited to gift cards and codes</span><span class="insert">Intentionally omitted</span>.</li>
</ul>
</li>
</ul>
</li>
<li data-sidenav="4.1 Copycats" id="copycats"><span id="4.1"></span><strong>4.1 Copycats</strong>
<ul class="no-bullet margin-top-small">
<li><strong><span class="insert">(a)</span></strong> Come up with your own ideas. We know you have them, so make yours come to life. Don’t simply copy the latest popular app on the <span class="nowrap">App Store,</span> or make some minor changes to another app’s name or UI and pass it off as your own. In addition to risking an intellectual property infringement claim, it makes the <span class="nowrap">App Store</span> harder to navigate and just isn’t fair to your fellow developers.</li>
<li><strong><span class="insert">(b)</span></strong><span class="insert"><img src="https://developer.apple.com/app-store/review/images/key-icon.svg" height="17" class="asr-nr" alt="ASR & NR" /></span> Submitting apps which impersonate other apps or services is considered a violation of the Developer Code of Conduct and may result in removal from the Apple Developer Program.</li>
</ul>
</li>
<li data-sidenav="4.2 Minimum Functionality" id="minimum-functionality"><span id="4.2"></span><strong>4.2 Minimum Functionality</strong>
<ul class="no-bullet margin-top-small">
<li id="4.2.4"><strong>4.2.4</strong> <span class="delete">Apple Watch apps that appear to be a watch face are confusing, because people will expect them to work with device features such as swipes, notifications, and third-party complications. Creative ways of expressing time as an app interface is great (say, a tide clock for surfers), but if your app comes too close to resembling a watch face, we will reject it</span><span class="insert">Intentionally omitted</span>.</li>
<li id="4.2.5"><strong>4.2.5</strong> <span class="delete">Apps that are primarily iCloud and iCloud Drive file managers need to include additional app functionality to be approved</span><span class="insert">Intentionally omitted</span>.</li>
</ul>
</li>
<li data-sidenav="4.3 Spam" id="spam"><span id="4.3"></span><strong>4.3 Spam</strong>
<ul class="no-bullet margin-top-small">
<li><strong><span class="insert">(a)</span></strong><span class="insert"><img src="https://developer.apple.com/app-store/review/images/key-icon.svg" height="17" class="asr-nr" alt="ASR & NR" /></span> Don’t create multiple Bundle IDs of the same app. If your app has different versions for specific locations, sports teams, universities, etc., consider submitting a single app and provide the variations using in-app purchase.</li>
<li><strong><span class="insert">(b)</span></strong> Also avoid piling on to a category that is already saturated; the <span class="nowrap">App Store</span> has enough fart, burp, flashlight, fortune telling, dating, drinking games, and Kama Sutra apps, etc. already. We will reject these apps unless they provide a unique, high-quality experience. Spamming the store may lead to your removal from the <span class="nowrap">Apple Developer Program.</span></li>
</ul>
</li>
<li data-sidenav="4.4 Extensions" id="extensions"><span id="4.4"></span><strong>4.4 Extensions</strong><span class="insert"><img src="https://developer.apple.com/app-store/review/images/key-icon.svg" height="17" class="asr-nr" alt="ASR & NR" /></span>
<p>Apps hosting or containing extensions must comply with the <a href="https://developer.apple.com/library/archive/documentation/General/Conceptual/ExtensibilityPG/index.html#apple_ref/doc/uid/TP40014214/">App Extension Programming Guide<span class="loc-en-only"></span></a>, the <a href="https://developer.apple.com/documentation/safariservices/safari_app_extensions/">Safari App Extensions documentation<span class="loc-en-only"></span></a>, or the <a href="https://developer.apple.com/documentation/safariservices/safari_web_extensions">Safari Web Extensions documentation</a> and should include some functionality, such as help screens and settings interfaces where possible. You should clearly and accurately disclose what extensions are made available in the app’s marketing text, and the extensions may not include marketing, advertising, or in-app purchases.</p>
<ul class="no-bullet margin-top-small">
<li id="4.4.1"><strong>4.4.1</strong><span class="insert"><img src="https://developer.apple.com/app-store/review/images/key-icon.svg" height="17" class="asr-nr" alt="ASR & NR" /></span> Keyboard extensions have some additional rules.<br>
<p class="margin-top-small">They must:</p>
<ul class="disc margin-top-small">
<li>Provide keyboard input functionality (e.g. typed characters);</li>
<li>Follow Sticker guidelines if the keyboard includes images or emoji;</li>
<li>Provide a method for progressing to the next keyboard;</li>
<li>Remain functional without full network access and without requiring full access;</li>
<li>Collect user activity only to enhance the functionality of the user’s keyboard extension on the iOS device.</li>
</ul>
<p>They must not:</p>
<ul class="disc margin-top-small">
<li>Launch other apps besides Settings; or</li>
<li>Repurpose keyboard buttons for other behaviors (e.g. holding down the “return” key to launch the camera).</li>
</ul>
</li>
<li id="4.4.2"><strong>4.4.2</strong><span class="insert"><img src="https://developer.apple.com/app-store/review/images/key-icon.svg" height="17" class="asr-nr" alt="ASR & NR" /></span> Safari extensions must run on the current version of Safari on the relevant Apple operating system. They may not interfere with System or Safari UI elements and must never include malicious or misleading content or code. Violating this rule will lead to removal from the <span class="nowrap">Apple Developer</span> Program. Safari extensions should not claim access to more websites than strictly necessary to function.</li>
<li id="4.4.3"><strong>4.4.3</strong> <span class="delete">Stickers
</span><span class="delete">Stickers are a great way to make Messages more dynamic and fun, letting people express themselves in clever, funny, meaningful ways. Whether your app contains a sticker extension or you’re creating free-standing sticker packs, its content shouldn’t offend users, create a negative experience, or violate the law.</span>
<ul>
<li><span class="delete">(i)</span><span class="delete"> In general, if it wouldn’t be suitable for the </span><span class="delete">App Store,</span><span class="delete"> it doesn’t belong in a sticker</span><span class="insert">Intentionally omitted</span>.</li>
<li><span class="delete">(ii)</span><span class="delete"> Consider regional sensitivities, and do not make your sticker pack available in a country or region where it could be poorly received or violate local law.</span></li>
<li><span class="delete">(iii)</span><span class="delete"> If we don’t understand what your stickers mean, include a clear explanation in your review notes to avoid any delays in the review process.</span></li>
<li><span class="delete">(iv)</span><span class="delete"> Ensure your stickers have relevance beyond your friends and family; they should not be specific to personal events, groups, or relationships.</span></Li>
<li><span class="delete">(v)</span><span class="delete"> You must have all the necessary copyright, trademark, publicity rights, and permissions for the content in your stickers, and shouldn’t submit anything unless you’re authorized to do so. Keep in mind that you must be able to provide verifiable documentation upon request. Apps with sticker content you don’t have rights to use will be removed from the </span><span class="delete">App Store</span><span class="delete"> and repeat offenders will be removed from the </span><span class="delete">Apple Developer Program.</span><span class="delete"> If you believe your content has been infringed by another provider, </span><span class="delete">submit a claim here</span><span class="delete">.</span></li>
</ul>
</ul>
</li>
<li data-sidenav="4.5 Apple Sites and Services" id="apple-sites-and-services"><span id="4.5"></span><strong>4.5 Apple Sites and Services</strong>
<ul class="no-bullet margin-top-small">
<li id="4.5.1"><strong>4.5.1</strong><span class="insert"><img src="https://developer.apple.com/app-store/review/images/key-icon.svg" height="17" class="asr-nr" alt="ASR & NR" /></span> Apps may use approved Apple RSS feeds such as the <span class="nowrap">iTunes Store</span> RSS feed, but may not scrape any information from Apple sites (e.g. apple.com, the <span class="nowrap">iTunes Store,</span> <span class="nowrap">App Store,</span> <span class="nowrap">App Store Connect,</span> developer portal, etc.) or create rankings using this information.</li>
<li id="4.5.2"><strong>4.5.2</strong><span class="insert"><img src="https://developer.apple.com/app-store/review/images/key-icon.svg" height="17" class="asr-nr" alt="ASR & NR" /></span> Apple Music
<ul class="no-bullet margin-top-small">
<li><strong>(i)</strong> MusicKit on iOS lets users play <span class="nowrap">Apple Music</span> and their local music library natively from your apps and games. When a user provides permission to their <span class="nowrap">Apple Music</span> account, your app can create playlists, add songs to their library, and play any of the millions of songs in the <span class="nowrap">Apple Music</span> catalog. Users must initiate the playback of an <span class="nowrap">Apple Music</span> stream and be able to navigate using standard media controls such as “play,” “pause,” and “skip.” Moreover, your app may not require payment or indirectly monetize access to the <span class="nowrap">Apple Music</span> service (e.g. in-app purchase, advertising, requesting user info, etc.). Do not download, upload, or enable sharing of music files sourced from the MusicKit APIs, except as explicitly permitted in <a href="https://developer.apple.com/musickit/">MusicKit<span class="loc-en-only"></span></a> documentation.</li>
<li><strong>(ii)</strong> Using the MusicKit APIs is not a replacement for securing the licenses you might need for a deeper or more complex music integration. For example, if you want your app to play a specific song at a particular moment, or to create audio or video files that can be shared to social media, you’ll need to contact rights-holders directly to get their permission (e.g. synchronization or adaptation rights) and assets. Cover art and other metadata may only be used in connection with music playback or playlists (including <span class="nowrap">App Store</span> screenshots displaying your app’s functionality), and should not be used in any marketing or advertising without getting specific authorization from rights-holders. Make sure to follow the <a href="https://www.apple.com/itunes/marketing-on-music/identity-guidelines.html"><span class="nowrap">Apple Music</span> Identity Guidelines<span class="loc-en-only"></span></a> when integrating <span class="nowrap">Apple Music</span> services in your app.</li>
<li><strong>(iii)</strong> Apps that access <span class="nowrap">Apple Music</span> user data, such as playlists and favorites, must clearly disclose this access in the purpose string. Any data collected may not be shared with third parties for any purpose other than supporting or improving the app experience. This data may not be used to identify users or devices, or to target advertising. </li>
</ul>
</li>
<li id="4.5.3"><strong>4.5.3</strong><span class="insert"><img src="https://developer.apple.com/app-store/review/images/key-icon.svg" height="17" class="asr-nr" alt="ASR & NR" /></span> Do not use Apple Services to spam, phish, or send unsolicited messages to customers, including <span class="nowrap">Game Center,</span> Push Notifications, etc. Do not attempt to reverse lookup, trace, relate, associate, mine, harvest, or otherwise exploit Player IDs, aliases, or other information obtained through <span class="nowrap">Game Center,</span> or you will be removed from the <span class="nowrap">Apple Developer Program.</span></li>
<li id="4.5.4"><strong>4.5.4</strong><span class="insert"><img src="https://developer.apple.com/app-store/review/images/key-icon.svg" height="17" class="asr-nr" alt="ASR & NR" /></span> Push Notifications must not be required for the app to function, and should not be used to send sensitive personal or confidential information. Push Notifications should not be used for promotions or direct marketing purposes unless customers have explicitly opted in to receive them via consent language displayed in your app’s UI, and you provide a method in your app for a user to opt out from receiving such messages. Abuse of these services may result in revocation of your privileges.</li>
<li id="4.5.5"><strong>4.5.5</strong><span class="insert"><img src="https://developer.apple.com/app-store/review/images/key-icon.svg" height="17" class="asr-nr" alt="ASR & NR" /></span> Only use <span class="nowrap">Game Center</span> Player IDs in a manner approved by the <span class="nowrap">Game Center</span> terms and do not display them in the app or to any third party.</li>
<li id="4.5.6"><strong>4.5.6</strong><span class="insert"><img src="https://developer.apple.com/app-store/review/images/key-icon.svg" height="17" class="asr-nr" alt="ASR & NR" /></span> Apps may use Unicode characters that render as Apple emoji in their app and app metadata. Apple emoji may not be used on other platforms or embedded directly in your app binary.</li>
</ul>
</li>
<li data-sidenav="4.6 Alternate App Icons" id="alternate-app-icons"><span id="4.6"></span><strong>4.6 Alternate App Icons</strong><span class="insert"><img src="https://developer.apple.com/app-store/review/images/key-icon.svg" height="17" class="asr-nr" alt="ASR & NR" /></span>
<p>Apps may display customized icons, for example, to reflect a sports team preference, provided that each change is initiated by the user and the app includes settings to revert to the original icon. All icon variants must relate to the content of the app and changes should be consistent across all system assets, so that the icons displayed in Settings, Notifications, etc. match the new springboard icon<span class="delete">. This feature may not be used for dynamic, automatic, or serial changes, such as to reflect up-to-date weather information, calendar notifications, etc</span>.</p></li>
<li data-sidenav="4.7 Mini apps, mini games, streaming games, chatbots, and plug-ins" id="third-party-software"><span id="4.7"></span><strong>4.7 <span class="delete">HTML5 Games</span><span class="insert">Mini apps</span>, <span class="delete">Bots</span><span class="insert">mini games</span>, <span class="delete">etc.</span><span class="insert">streaming games, chatbots, and plug-ins</span></strong>
<p>Apps may <span class="delete">contain or run code</span><span class="insert">offer certain software</span> that is not embedded in the binary<span class="delete"> (e.g. HTML5-based</span><span class="insert">, specifically mini apps, mini</span> games, <span class="delete">bots</span><span class="insert">streaming games</span>, <span class="delete">etc</span><span class="insert">chatbots, and plug-ins</span>.<span class="delete">), as long as code distribution isn’t the main purpose of the</span><span class="insert"> You are responsible for all such software offered in your</span> app, <span class="delete">the code is</span><span class="insert">including ensuring that such software complies with these Guidelines and all applicable laws. Software that does</span> not <span class="delete">offered in a store or store-like interface, and provided</span><span class="insert">comply with one or more guidelines will lead to the rejection of your app. You must also ensure</span> that the software adheres to the additional rules that follow in 4.7.1 and 4.7.<span class="delete">2</span><span class="insert">5</span>. These additional rules are important to preserve the experience that App Store customers expect, and to help ensure user safety.</p>
<ul class="no-bullet margin-top-small">
<li id="4.7.1"><strong>4.7.1</strong> Software offered <span class="insert">in apps </span>under this rule must:
<ul class="disc margin-top-small">
<li><span class="delete">be free or purchased using</span><span class="insert">follow all privacy guidelines, including but not limited to the rules set forth in Guideline 5.1 concerning collection, use, and sharing of data, and sensitive data (such as health and personal data from kids);</span></li>
<li><span class="insert">include a method for filtering objectionable material, a mechanism to report content and timely responses to concerns, and the ability to block abusive users; and</span></li>
<li><span class="insert">use</span> in-app purchase<span class="delete">;</span>
<span class="delete">only use capabilities available in a standard WebKit view (e.g. it must open and run natively in Safari without modifications or additional software); and use WebKit and JavaScript Core to run third-party software and should not attempt to extend or expose native platform APIs to third-party software;</span>
<span class="delete">be offered by developers that have joined the </span><span class="delete">Apple Developer</span><span class="delete"> Program and signed the </span><span class="delete">Apple Developer</span><span class="delete"> Program License Agreement;</span>
<span class="delete">not provide access to real money gaming;</span>
<span class="delete">adhere to the terms of these </span><span class="delete">App Store</span><span class="delete"> Review Guidelines (e.g. do not include objectionable content); and</span>
<span class="delete">not</span><span class="insert"> in order to</span> offer digital goods or services <span class="delete">for sale</span><span class="insert">to end users</span>.</li>
</ul>
</li>
<li id="4.7.2"><strong>4.7.2</strong> <span class="delete">Upon request, you</span><span class="insert">Your app may not extend or expose native platform APIs to the software without prior permission from Apple.</span></li>
<li id="4.7.3"><strong><span class="insert">4.7.3</span></strong><span class="insert"> Your app may not share data or privacy permissions to any individual software offered in your app without explicit user consent in each instance.</span></li>
<li id="4.7.4"><strong><span class="insert">4.7.4</span></strong><span class="insert"> You</span> must provide an index of software and metadata available in your app. It must include <span class="delete">Apple Developer</span><span class="delete"> Program Team IDs for the providers</span><span class="insert">universal links that lead to all</span> of the software <span class="delete">along with a URL which </span><span class="delete">App Review</span><span class="delete"> can use to confirm that the software complies with the requirements above</span><span class="insert">offered in your app</span>.</li>
<li id="4.7.5"><strong><span class="insert">4.7.5</span></strong><span class="insert"> Your app must share the age rating of the highest age-rated content available in your app.</span></li>
</ul>
</li>
<li data-sidenav="4.8 Login Services" id="login-services"><span id="4.8"></span><strong>4.8 <span class="delete">Sign in with Apple</span><span class="insert">Login Services</span></strong><span class="insert"><img src="https://developer.apple.com/app-store/review/images/key-icon.svg" height="17" class="asr-nr" alt="ASR & NR" /></span>
<p>Apps that use a third-party or social login service (such as Facebook Login, Google Sign-In, <span class="nowrap">Sign in with Twitter</span>, <span class="nowrap">Sign In with LinkedIn</span>, <span class="nowrap">Login with Amazon</span>, or WeChat Login) to set up or authenticate the user’s primary account with the app must also offer <span class="delete">Sign in with Apple </span>as an equivalent option<span class="delete">. A</span><span class="insert"> another login service with the following features:</span></p>
<ul class="disc margin-top-small">
<li><span class="insert">the login service limits data collection to the</span> user’s <span class="insert">name and email address</span></li>
<li><span class="insert">the login service allows users to keep their email address private as part of setting up their account</span></li>
<li><span class="insert">the login service does not track users as they interact with your app</span></li>
</ul>
<p><span class="insert">A user’s </span>primary account is the account they establish with your app for the purposes of identifying themselves, signing in, and accessing your features and associated services.</p>
<p><span class="delete">Sign in with Apple</span><span class="insert">Another login service</span> is not required if:
<ul class="disc margin-top-small">
<li>Your app exclusively uses your company’s own account setup and sign-in systems.</li>
<li>Your app is an education, enterprise, or business app that requires the user to sign in with an existing education or enterprise account.</li>
<li>Your app uses a government or industry-backed citizen identification system or electronic ID to authenticate users.</li>
<li>Your app is a client for a specific third-party service and users are required to sign in to their mail, social media, or other third-party account directly to access their content.</li>
</ul>
</p>
</li>
<li data-sidenav="4.9 Apple Pay" id="apple-pay"><span id="4.9"></span><strong>4.9 <span class="delete">Streaming games</span><span class="insert">Apple Pay</span></strong><span class="insert"><img src="https://developer.apple.com/app-store/review/images/key-icon.svg" height="17" class="asr-nr" alt="ASR & NR" /></span>
<p><span class="delete">Streaming games are permitted so long as they adhere to</span><span class="insert">Apps using Apple Pay must provide</span> all <span class="delete">guidelines—for example</span><span class="insert">material purchase information to the user prior to sale of any good or service and must use Apple Pay branding and user interface elements correctly</span>, <span class="insert">as described in the Apple Pay Marketing Guidelines and Human Interface Guidelines. Apps using Apple Pay to offer recurring payments must, at a minimum, disclose the following information:</span></p>
<ul class="disc margin-top-small">
<li><span class="insert">The length of the renewal term and the fact that it will continue until canceled</span></li>
<li><span class="insert">What will be provided during </span>each <span class="delete">game update must be submitted for review, developers must provide appropriate metadata for search, games must use in-app purchase to unlock features or functionality, etc. Of course, there is always the open Internet and web browser apps to reach all users outside of the </span><span class="delete">App Store.</span><span class="insert">period</span></li>
<li><span class="insert">The actual charges that will be billed to the customer</span></li>
<li><span class="insert">How to cancel</span></li>
</ul>
</li>
<li data-sidenav="4.10 Monetizing Built-In Capabilities" id="monetizing-built-in-capabilities"><span id="4.10"></span>
<strong>4.<span class="delete">9</span><span class="insert">10 Monetizing Built-In Capabilities</span></strong><span class="insert"><img src="https://developer.apple.com/app-store/review/images/key-icon.svg" height="17" class="asr-nr" alt="ASR & NR" /></span>
<p><span class="insert">You may not monetize built-in capabilities provided by the hardware or operating system, such as Push Notifications, the camera, or the gyroscope; or Apple services and technologies, such as Apple Music access, iCloud storage, or </span><span class="nowrap"><span class="insert">Screen Time APIs</span></span>.<span class="delete">1</span><span class="delete"> Each streaming game must be submitted to the </span><span class="delete">App Store</span><span class="delete"> as an individual app so that it has an </span><span class="delete">App Store</span><span class="delete"> product page, appears in charts and search, has user ratings and review, can be managed with ScreenTime and other parental control apps, appears on the user’s device, etc.</span></p>
</li>
<li><span class="delete"><b>4.9.2</b></span><span class="delete"> Streaming game services may offer a catalog app on the </span><span class="delete">App Store</span><span class="delete"> to help users sign up for the service and find the games on the </span><span class="delete">App Store,</span><span class="delete"> provided that the app adheres to all guidelines, including offering users the option to pay for a subscription with in-app purchase and use Sign in with Apple. All the games included in the catalog app must link to an individual </span><span class="delete">App Store</span><span class="delete"> product page.</span></li>
</ul>
<h3 data-sidenav="5. Legal" id="legal"><span id="5"></span>5. Legal <span class="insert"><img src="https://developer.apple.com/app-store/review/images/key-icon.svg" height="17" class="asr-nr" alt="ASR & NR" /></span></h3>
<p class="section-intro">Apps must comply with all legal requirements in any location where you make them available (if you’re not sure, check with a lawyer). We know this stuff is complicated, but it is your responsibility to understand and make sure your app conforms with all local laws, not just the guidelines below. And of course, apps that solicit, promote, or encourage criminal or clearly reckless behavior will be rejected. In extreme cases, such as apps that are found to facilitate human trafficking and/or the exploitation of children, appropriate authorities will be notified.</p>
<ul class="no-bullet">
<li data-sidenav="5.1 Privacy" id="privacy"><span id="5.1"></span><strong>5.1 Privacy</strong><span class="insert"><img src="https://developer.apple.com/app-store/review/images/key-icon.svg" height="17" class="asr-nr" alt="ASR & NR" /></span>
<p>Protecting user privacy is paramount in the Apple ecosystem, and you should use care when handling personal data to ensure you’ve complied with <a href="https://developer.apple.com/documentation/uikit/protecting_the_user_s_privacy/">privacy best practices<span class="loc-cj"></span></a>, applicable laws, and the terms of the <a href="https://developer.apple.com/support/terms/"><span class="nowrap">Apple Developer</span> Program License Agreement</a>, not to mention customer expectations. More particularly:</p>
<ul class="no-bullet margin-top-small">
<li data-sidenav="5.1.1 Data Collection and Storage" id="data-collection-and-storage"><span id="5.1.1"></span><strong>5.1.1 Data Collection and Storage</strong><span class="insert"><img src="https://developer.apple.com/app-store/review/images/key-icon.svg" height="17" class="asr-nr" alt="ASR & NR" /></span>
<ul class="no-bullet margin-top-small">
<li><strong>(i) Privacy Policies: </strong>All apps must include a link to their privacy policy in the <span class="nowrap">App Store Connect</span> metadata field and within the app in an easily accessible manner. The privacy policy must clearly and explicitly:
<ul class="disc">
<li>Identify what data, if any, the app/service collects, how it collects that data, and all uses of that data.</li>
<li>Confirm that any third party with whom an app shares user data (in compliance with these Guidelines)—such as analytics tools, advertising networks and third-party SDKs, as well as any parent, subsidiary or other related entities that will have access to user data—will provide the same or equal protection of user data as stated in the app’s privacy policy and required by these Guidelines.</li>
<li>Explain its data retention/deletion policies and describe how a user can revoke consent and/or request deletion of the user’s data.</li>
</ul>
</li>
<li><strong>(ii) Permission: </strong>Apps that collect user or usage data must secure user consent for the collection, even if such data is considered to be anonymous at the time of or immediately following collection. Paid functionality must not be dependent on or require a user to grant access to this data. Apps must also provide the customer with an easily accessible and understandable way to withdraw consent. Ensure your purpose strings clearly and completely describe your use of the data. Apps that collect data for a legitimate interest without consent by relying on the terms of the European Union’s General Data Protection Regulation (“GDPR”) or similar statute must comply with all terms of that law. Learn more about <a href="https://developer.apple.com/documentation/uikit/protecting_the_user_s_privacy/">Requesting Permission<span class="loc-cj"></span></a>.</li>
<li><strong>(iii) Data Minimization: </strong>Apps should only request access to data relevant to the core functionality of the app and should only collect and use data that is required to accomplish the relevant task. Where possible, use the out-of-process picker or a share sheet rather than requesting full access to protected resources like Photos or Contacts.</li>
<li><strong>(iv) Access: </strong>Apps must respect the user’s permission settings and not attempt to manipulate, trick, or force people to consent to unnecessary data access. For example, apps that include the ability to post photos to a social network must not also require microphone access before allowing the user to upload photos. Where possible, provide alternative solutions for users who don’t grant consent. For example, if a user declines to share Location, offer the ability to manually enter an address.</li>
<li id="5.1.1v"><strong>(v) Account Sign-In: </strong>If your app doesn’t include significant account-based features, let people use it without a login. If your app supports account creation, you must also <a href="https://developer.apple.com/support/offering-account-deletion-in-your-app/">offer account deletion within the app</a>. Apps may not require users to enter personal information to function, except when directly relevant to the core functionality of the app or required by law. If your core app functionality is not related to a specific social network (e.g. Facebook, WeChat, Weibo, Twitter, etc.), you must provide access without a login or via another mechanism. Pulling basic profile information, sharing to the social network, or inviting friends to use the app are not considered core app functionality. The app must also include a mechanism to revoke social network credentials and disable data access between the app and social network from within the app. An app may not store credentials or tokens to social networks off of the device and may only use such credentials or tokens to directly connect to the social network from the app itself while the app is in use.</li>
<li><strong>(vi) </strong>Developers that use their apps to surreptitiously discover passwords or other private data will be removed from the <span class="nowrap">Apple Developer Program.</span></li>
<li><strong>(vii) </strong>SafariViewController must be used to visibly present information to users; the controller may not be hidden or obscured by other views or layers. Additionally, an app may not use SafariViewController to track users without their knowledge and consent.</li>
<li><strong>(viii) </strong>Apps that compile personal information from any source that is not directly from the user or without the user’s explicit consent, even public databases, are not permitted on the <span class="nowrap">App Store.</span></li>
<li><strong>(ix) </strong>Apps that provide services in highly regulated fields (such as banking and financial services, healthcare, gambling, legal cannabis use, and air travel) or that require sensitive user information should be submitted by a legal entity that provides the services, and not by an individual developer. Apps that facilitate the legal sale of cannabis must be geo-restricted to the corresponding legal jurisdiction.</li>
<li><strong>(x) </strong>Apps may request basic contact information (such as name and email address) so long as the request is optional for the user, features and services are not conditional on providing the information, and it complies with all other provisions of these guidelines, including limitations on collecting information from kids.</li>
</ul>
</li>
<li data-sidenav="5.1.2 Data Use and Sharing" id="data-use-and-sharing"><span id="5.1.2"></span><strong>5.1.2 Data Use and Sharing</strong><span class="insert"><img src="https://developer.apple.com/app-store/review/images/key-icon.svg" height="17" class="asr-nr" alt="ASR & NR" /></span>
<ul class="no-bullet margin-top-small">
<li><strong>(i) </strong>Unless otherwise permitted by law, you may not use, transmit, or share someone’s personal data without first obtaining their permission. You must provide access to information about how and where the data will be used. Data collected from apps may only be shared with third parties to improve the app or serve advertising (in compliance with the <a href="https://developer.apple.com/support/terms/"><span class="nowrap">Apple Developer</span> Program License Agreement</a>). You must receive explicit permission from users via the App Tracking Transparency APIs to track their activity. Learn more about <a href="https://developer.apple.com/app-store/user-privacy-and-data-use/">tracking<span class="loc-apac"></span></a>. <span class="insert">Your app may not require users to enable system functionalities (e.g., push notifications, location services, tracking) in order to access functionality, content, use the app, or receive monetary or other compensation, including but not limited to gift cards and codes. </span>Apps that share user data without user consent or otherwise complying with data privacy laws may be removed from sale and may result in your removal from the <span class="nowrap">Apple Developer Program.</span></li>
<li><strong>(ii) </strong>Data collected for one purpose may not be repurposed without further consent unless otherwise explicitly permitted by law. </li>
<li><strong>(iii) </strong>Apps should not attempt to surreptitiously build a user profile based on collected data and may not attempt, facilitate, or encourage others to identify anonymous users or reconstruct user profiles based on data collected from Apple-provided APIs or any data that you say has been collected in an “anonymized,” “aggregated,” or otherwise non-identifiable way.</li>
<li><strong>(iv) </strong>Do not use information from Contacts, Photos, or other APIs that access user data to build a contact database for your own use or for sale/distribution to third parties, and don’t collect information about which other apps are installed on a user’s device for the purposes of analytics or advertising/marketing.</li>
<li><strong>(v) </strong>Do not contact people using information collected via a user’s Contacts or Photos, except at the explicit initiative of that user on an individualized basis; do not include a Select All option or default the selection of all contacts. You must provide the user with a clear description of how the message will appear to the recipient before sending it (e.g. What will the message say? Who will appear to be the sender?). </li>
<li><strong>(vi) </strong>Data gathered from the HomeKit API, HealthKit, Clinical Health Records API, MovementDisorder APIs, ClassKit or from depth and/or facial mapping tools (e.g. ARKit, Camera APIs, or Photo APIs) may not be used for marketing, advertising or use-based data mining, including by third parties. Learn more about best practices for implementing <a href="https://developer.apple.com/documentation/callkit/">CallKit<span class="loc-en-only"></span></a>, <a href="https://developer.apple.com/documentation/healthkit/">HealthKit<span class="loc-en-only"></span></a>, <a href="https://developer.apple.com/documentation/classkit/">ClassKit<span class="loc-en-only"></span></a>, and <a href="https://developer.apple.com/documentation/arkit/">ARKit<span class="loc-cj"></span></a>.</li>
<li><strong>(vii) </strong>Apps using <span class="nowrap">Apple Pay</span> may only share user data acquired via <span class="nowrap">Apple Pay</span> with third parties to facilitate or improve delivery of goods and services.</li>
</ul>
</li>
<li data-sidenav="5.1.4 Kids" id="kids"><span id="5.1.4"></span><strong>5.1.4 Kids</strong>
<ul class="no-bullet margin-top-small">
<li>
<p><strong><span class="insert">(a)</span></strong><span class="insert"><img src="https://developer.apple.com/app-store/review/images/key-icon.svg" height="17" class="asr-nr" alt="ASR & NR" /></span> For many reasons, it is critical to use care when dealing with personal data from kids, and we encourage you to carefully review all the requirements for complying with laws like the Children’s Online Privacy Protection Act (“COPPA”), the European Union’s General Data Protection Regulation (“GDPR”), and any other applicable regulations or laws.</p>
<p>Apps may ask for birthdate and parental contact information only for the purpose of complying with these statutes, but must include some useful functionality or entertainment value regardless of a person’s age.</p>
<p>Apps intended primarily for kids should not include third-party analytics or third-party advertising. This provides a safer experience for kids.</p>
</li>
<li>
<p><strong><span class="insert">(b)</span></strong> In limited cases, third-party analytics and third-party advertising may be permitted provided that the services adhere to the same terms set forth in <a href="#1.3">Guideline 1.3</a>.</p>
<p>Moreover, apps in the Kids Category or those that collect, transmit, or have the capability to share personal information (e.g. name, address, email, location, photos, videos, drawings, the ability to chat, other personal data, or persistent identifiers used in combination with any of the above) from a minor must include a privacy policy and must comply with all applicable children’s privacy statutes. For the sake of clarity, the <a href="#kids-category">parental gate requirement</a> for the Kid’s Category is generally not the same as securing parental consent to collect personal data under these privacy statutes.</p>
<p>As a reminder, <a href="#2.3.8">Guideline 2.3.8</a> requires that use of terms like “For Kids” and “For Children” in app metadata is reserved for the Kids Category. Apps not in the Kids Category cannot include any terms in app name, subtitle, icon, screenshots or description that imply the main audience for the app is children.</p>
</li>
</ul>
</li>
<li data-sidenav="5.1.5 Location Services" id="location"><span id="5.1.5"></span><strong>5.1.5 Location Services</strong><span class="insert"><img src="https://developer.apple.com/app-store/review/images/key-icon.svg" height="17" class="asr-nr" alt="ASR & NR" /></span>
<p>Use Location services in your app only when it is directly relevant to the features and services provided by the app. Location-based APIs shouldn’t be used to provide emergency services or autonomous control over vehicles, aircraft, and other devices, except for small devices such as lightweight drones and toys, or remote control car alarm systems, etc. Ensure that you notify and obtain consent before collecting, transmitting, or using location data. If your app uses location services, be sure to explain the purpose in your app; refer to the <a href="https://developer.apple.com/design/human-interface-guidelines/patterns/accessing-private-data/">Human Interface Guidelines<span class="loc-en-only"></span></a> for best practices for doing so.</p>
</li>
</ul>
</li>
<li data-sidenav="5.2 Intellectual Property" id="intellectual-property"><span id="5.2"></span><strong>5.2 Intellectual Property</strong>
<ul class="no-bullet margin-top-small">
<li id="5.2.4"><strong>5.2.4 Apple <span class="delete">Endorsements:</span><span class="insert">Endorsements</span></strong>
<ul class="no-bullet margin-top-small">
<li><strong><span class="insert">(a)</span></strong><span class="insert"><img src="https://developer.apple.com/app-store/review/images/key-icon.svg" height="17" class="asr-nr" alt="ASR & NR" /></span> Don’t suggest or imply that Apple is a source or supplier of the App, or that Apple endorses any particular representation regarding quality or functionality.</li>
<li><strong><span class="insert">(b)</span></strong> If your app is selected as an “Editor’s Choice,” Apple will apply the badge automatically.</li>
</ul>
</li>
<li id="5.2.5"><strong>5.2.5 Apple <span class="delete">Products:</span><span class="insert">Products</span></strong><span class="insert"><img src="https://developer.apple.com/app-store/review/images/key-icon.svg" height="17" class="asr-nr" alt="ASR & NR" /></span> Don’t create an app that appears confusingly similar to an existing Apple product, interface (e.g. Finder), app (such as the <span class="nowrap">App Store,</span> <span class="nowrap">iTunes Store,</span> or Messages) or advertising theme. Apps and extensions, including third-party keyboards and Sticker packs, may not include Apple emoji. Music from iTunes and <span class="nowrap">Apple Music</span> previews may not be used for their entertainment value (e.g. as the background music to a photo collage or the soundtrack to a game) or in any other unauthorized manner. If you provide music previews from iTunes or <span class="nowrap">Apple Music,</span> you must display a link to the corresponding music in iTunes or <span class="nowrap">Apple Music.</span> If your app displays Activity rings, they should not visualize Move, Exercise, or Stand data in a way that resembles the Activity control. The <a href="https://developer.apple.com/design/human-interface-guidelines/patterns/workouts/#activity-rings">Human Interface Guidelines<span class="loc-en-only"></span></a> have more information on how to use Activity rings. If your app displays Apple Weather data, it should follow the attribution requirements provided in the <a href="https://developer.apple.com/weatherkit/get-started/#attribution-requirements">WeatherKit documentation<span class="loc-apac"></span></a>.</li>
</ul>
</li>
<li data-sidenav="5.4 VPN Apps" id="vpn-apps"><span id="5.4"></span><strong>5.4 VPN Apps</strong><span class="insert"><img src="https://developer.apple.com/app-store/review/images/key-icon.svg" height="17" class="asr-nr" alt="ASR & NR" /></span>
<p>Apps offering VPN services must utilize the <a href="https://developer.apple.com/documentation/networkextension/nevpnmanager/">NEVPNManager API<span class="loc-en-only"></span></a> and may only be offered by developers enrolled as an organization. You must make a clear declaration of what user data will be collected and how it will be used on an app screen prior to any user action to purchase or otherwise use the service. Apps offering VPN services may not sell, use, or disclose to third parties any data for any purpose, and must commit to this in their privacy policy. VPN apps must not violate local laws, and if you choose to make your VPN app available in a territory that requires a VPN license, you must provide your license information in the <span class="nowrap">App Review</span> Notes field. Parental control, content blocking, and security apps, among others, from approved providers may also use the NEVPNManager API. Apps that do not comply with this guideline will be removed from the <span class="nowrap">App Store</span> and you may be removed from the <span class="nowrap">Apple Developer</span> Program.</p>
</li>
<li data-sidenav="5.5 Mobile Device Management" id="mobile-device-management"><span id="5.5"></span><strong>5.5 Mobile Device Management</strong><span class="insert"><img src="https://developer.apple.com/app-store/review/images/key-icon.svg" height="17" class="asr-nr" alt="ASR & NR" /></span>
<p>Mobile Device Management Apps that offer Mobile Device Management (MDM) services must request this capability from Apple. Such apps may only be offered by commercial enterprises, educational institutions, or government agencies, and in limited cases, companies using MDM for parental control services or device security. You must make a clear declaration of what user data will be collected and how it will be used on an app screen prior to any user action to purchase or otherwise use the service. MDM apps must not violate any applicable laws. Apps offering MDM services may not sell, use, or disclose to third parties any data for any purpose, and must commit to this in their privacy policy. In limited cases, third-party analytics may be permitted provided that the services only collect or transmit data about the performance of the developer’s MDM app, and not any data about the user, the user’s device, or other apps used on that device. Apps offering configuration profiles must also adhere to these requirements. Apps that do not comply with this guideline will be removed from the <span class="nowrap">App Store</span> and you may be removed from the <span class="nowrap">Apple Developer Program.</span></p>
</li>
<li data-sidenav="5.6 Developer Code of Conduct" id="code-of-conduct"><span id="5.6"></span><strong>5.6 Developer Code of Conduct</strong><span class="insert"><img src="https://developer.apple.com/app-store/review/images/key-icon.svg" height="17" class="asr-nr" alt="ASR & NR" /></span>
<p>Please treat everyone with respect, whether in your responses to <span class="nowrap">App Store</span> reviews, customer support requests, or when communicating with Apple, including your responses in <span class="nowrap">App Store Connect.</span> Do not engage in harassment of any kind, discriminatory practices, intimidation, bullying, and don’t encourage others to engage in any of the above. Repeated manipulative or misleading behavior or other fraudulent conduct will lead to your removal from the <span class="nowrap">Apple Developer Program.</span></p>
<p>Customer trust is the cornerstone of the <span class="nowrap">App Store’s</span> success. Apps should never prey on users or attempt to rip off customers, trick them into making unwanted purchases, force them to share unnecessary data, raise prices in a tricky manner, charge for features or content that are not delivered, or engage in any other manipulative practices within or outside of the app.</p>
<p>Your Developer Program account will be terminated if you engage in activities or actions that are not in accordance with the Developer Code of Conduct. To restore your account, you may provide a written statement detailing the improvements you plan to make. If your plan is approved by Apple and we confirm the changes have been made, your account may be restored.</p>
<ul class="no-bullet margin-top-small">
<li id="5.6.2"><strong>5.6.2 Developer Identity</strong><span class="insert"><img src="https://developer.apple.com/app-store/review/images/key-icon.svg" height="17" class="asr-nr" alt="ASR & NR" /></span>
<p>Providing verifiable information to Apple and customers is critical to customer trust. Your representation of yourself, your business, and your offerings on the <span class="nowrap">App Store</span> must be accurate. The information you provide must be truthful, relevant, and up-to-date so that Apple and customers understand who they are engaging with and can contact you regarding any issues.</p>
</li>
</ul>
</li>
</ul>
<h3 data-sidenav id="after-you-submit">After You Submit</h3>
<ul class="disc top-level">
<li><strong>Appeals</strong>: If you disagree with the outcome of your review, <span class="delete">or would like to suggest a change to the guideline itself, </span>please <a href="https://developer.apple.com/contact/app-store/?topic=appeal">submit an appeal<span class="loc-en-only"></span></a>. This may help get your app on the store<span class="delete">, and it can</span><span class="insert">. You may also </span><a href="https://developer.apple.com/contact/app-store/?topic=guideline"><span class="insert">suggest changes to the guidelines</span></a><span class="insert"> themselves to</span> help us improve the <span class="nowrap">App Review</span> process or identify a need for clarity in our policies.</li>
</ul>
</section></p></article><article class="article intro"><header><p class="date"><span>January 17, 2024</span></p><h2><a href="/articles/2024-01-17-storekit-review-guideline-update/">US apps can now link to payment options on developer's website</a></h2></header><section class="content"><p>Apple has updated their <a href="https://developer.apple.com/app-store/review/guidelines/">App Store Review Guidelines</a> to now allow apps in the United States, that offer in-app purchases, the ability to include a link to the developer’s website that informs users of other ways to purchase digital goods or services.
<br><br></p>
<p><a href="https://developer.apple.com/news/?id=plt8qzea">Apple’s full summary can be found here</a>.
</br></br></p>
<p>The complete set of changes can be seen below:</p>
</section><p class="changes"><section class="apple">
<li data-sidenav="3.1 Payments" id="payments"><span id="3.1"></span><strong>3.1 Payments</strong>
<ul class="no-bullet margin-top-small">
<li data-sidenav="3.1.1 In-App Purchase" id="in-app-purchase"><span id="3.1.1"></span><strong>3.1.1 In-App Purchase:</strong>
<ul class="disc no-margin-top">
<li>Apps <span class="delete">and their metadata </span>may <span class="delete">not include buttons, external links, or other calls to action that direct customers to purchasing mechanisms other than</span><span class="insert">use</span> in-app purchase<span class="delete">, except as set forth in 3.1.3(a).</span>
<span class="delete">Apps may use in-app purchase</span> currencies to enable customers to “tip” the developer or digital content providers in the app.</li>
</ul>
</li>
<li data-sidenav="3.1.1(a) Link to Other Purchase Methods" id="link-to-other-purchase-methods"><span id="3.1.1a"></span><strong><span class="insert">3.1.1(a) Link to Other Purchase Methods:</span></strong><span class="insert"> Developers may apply for an entitlement to provide a link in their app to a website the developer owns or maintains responsibility for in order to purchase such items. Learn more about the </span><a href="/support/storekit-external-entitlement-us/"><span class="insert">entitlement</span></a><span class="insert">. In accordance with the entitlement agreement, the link may inform users about where and how to purchase those in-app purchase items, and the fact that such items may be available for a comparatively lower price. The entitlement is limited to use only in the iOS or iPadOS App Store on the United States storefront. In all other storefronts, apps and their metadata may not include buttons, external links, or other calls to action that direct customers to purchasing mechanisms other than in-app purchase.
</span><p style="margin-top: 0.7em;"><span class="insert">If your app engages in misleading marketing practices, scams, or fraud in relation to the entitlement, your app will be removed from the App Store and you may be removed from the Apple Developer Program.</span></p></li>
</ul>
</li>
</section></p></article><article class="article intro"><header><p class="date"><span>June 06, 2023</span></p><h2><a href="/articles/2023-06-06-ads-reporting-and-more/">Ads reporting requirements, consequences of impersonating apps, spelling error fixes and clarifications</a></h2></header><section class="content"><p>Apple has updated their <a href="https://developer.apple.com/app-store/review/guidelines/">App Store Review Guidelines</a> on reporting requirements for apps with ads, consequences of impersonating other apps, and more.
<br><br></p>
<p><a href="https://developer.apple.com/news/?id=3cwqvk28">Apple’s full summary can be found here</a>.
</br></br></p>
<p>The complete set of changes can be seen below:</p>
</section><p class="changes"><section class="apple">
<li data-sidenav="2.5 Software Requirements" id="software-requirements"><span id="2.5"></span><strong>2.5 Software Requirements</strong>
<ul class="no-bullet margin-top-small">
<li id="2.5.6"><strong>2.5.6</strong> Apps that browse the web must use the appropriate WebKit framework and WebKit <span class="delete">Javascript</span><span class="insert">JavaScript</span>.</li>
<li id="2.5.18"><strong>2.5.18</strong> Display advertising should be limited to your main app binary, and should not be included in extensions, App Clips, widgets, notifications, keyboards, watchOS apps, etc. Ads displayed in an app must be appropriate for the app’s age rating, allow the user to see all information used to target them for that ad (without requiring the user to leave the app), and may not engage in targeted or behavioral advertising based on sensitive user data such as health/medical data (e.g. from the HealthKit APIs), school and classroom data (e.g. from ClassKit), or from kids (e.g. from apps in the Kids Category), etc. Interstitial ads or ads that interrupt or block the user experience must clearly indicate that they are an ad, must not manipulate or trick users into tapping into them, and must provide easily accessible and visible close/skip buttons large enough for people to easily dismiss the ad.<span class="insert"> Apps that contain ads must also include the ability for users to report any inappropriate or age-inappropriate ads.</span></li>
</ul>
</li>
<li data-sidenav="3.1 Payments" id="payments"><span id="3.1"></span><strong>3.1 Payments</strong>
<ul class="no-bullet margin-top-small">
<li id="permissible-uses"><span id="3.1.2a"></span><strong>3.1.2(a) Permissible uses:</strong> If you offer an auto-renewing subscription, you must provide ongoing value to the customer, and the subscription period must last at least seven days and be available across all of the user’s devices. While the following list is not exhaustive, examples of appropriate subscriptions include: new game levels; episodic content; multiplayer support; apps that offer consistent, substantive updates; access to large collections of, or continually updated, media content; software as a service (“SAAS”); and cloud support. In addition:
<ul class="disc margin-top-small">
<li>Cellular carrier apps may include auto-renewing music and video subscriptions <span class="delete">in pre-defined</span><span class="insert">when purchased in</span> bundles with <span class="insert">new </span>cellular data plans, with prior approval by Apple. Other auto-renewing subscriptions may also be included in <span class="delete">pre-defined </span>bundles <span class="delete">with</span><span class="insert">when purchased with new</span> cellular data plans, with prior approval by Apple, if the cellular carrier apps support in-app purchase for <span class="delete">new </span>users<span class="delete"> and the carrier provides a mechanism for customers to revert to in-app purchase upon termination of the customer’s bundled service</span>. Such subscriptions cannot include access to or discounts on consumable items<span class="insert">, and the subscriptions must terminate coincident with the cellular data plan</span>.</li>
</ul>
</li>
</ul>
</li>
<li data-sidenav="4.1 Copycats" id="copycats"><span id="4.1"></span><strong>4.1 Copycats</strong><p>Come up with your own ideas. We know you have them, so make yours come to life. Don’t simply copy the latest popular app on the <span class="nowrap">App Store,</span> or make some minor changes to another app’s name or UI and pass it off as your own. In addition to risking an intellectual property infringement claim, it makes the <span class="nowrap">App Store</span> harder to navigate and just isn’t fair to your fellow developers<span class="insert">. Submitting apps which impersonate other apps or services is considered a violation of the Developer Code of Conduct and may result in removal from the Apple Developer Program</span>.</p></li>
<li data-sidenav="4.4 Extensions" id="extensions"><span id="4.4"></span><strong>4.4 Extensions</strong>
<p>Apps hosting or containing extensions must comply with the <a href="/library/archive/documentation/General/Conceptual/ExtensibilityPG/index.html#apple_ref/doc/uid/TP40014214/">App Extension Programming Guide<span class="loc-en-only"></span></a><span class="delete"> or the </span><span class="insert">, the </span><a href="/documentation/safariservices/safari_app_extensions/">Safari App Extensions <span class="delete">Guide</span><span class="insert">documentation</span><span class="loc-en-only"></span></a><span class="insert">, or the </span><a href="/documentation/safariservices/safari_web_extensions"><span class="insert">Safari Web Extensions documentation</span></a> and should include some functionality, such as help screens and settings interfaces where possible. You should clearly and accurately disclose what extensions are made available in the app’s marketing text, and the extensions may not include marketing, advertising, or in-app purchases.</p>
<ul class="no-bullet margin-top-small">
<li id="4.4.2"><strong>4.4.2</strong> Safari extensions must run on the current version of Safari on <span class="delete">macOS</span><span class="insert">the relevant Apple operating system</span>. They may not interfere with System or Safari UI elements and must never include malicious or misleading content or code. Violating this rule will lead to removal from the <span class="nowrap">Apple Developer</span> Program. Safari extensions should not claim access to more websites than strictly necessary to function.</li>
</ul>
</li>
<li data-sidenav="5.1 Privacy" id="privacy"><span id="5.1"></span><strong>5.1 Privacy</strong>
<ul class="no-bullet margin-top-small">
<li data-sidenav="5.1.3 Health and Health Research" id="health-and-health-research"><span id="5.1.3"></span><strong>5.1.3 Health and Health Research</strong>
<p>Health, fitness, and medical data are especially sensitive and apps in this space have some additional rules to make sure customer privacy is protected:</p>
<ul class="no-bullet margin-top-small">
<li><strong>(i)</strong> Apps may not use or disclose to third parties data gathered in the health, fitness, and medical research context—including from the Clinical Health Records API, HealthKit API, Motion and Fitness, <span class="delete">MovementDisorderAPIs</span><span class="insert">MovementDisorder APIs</span>, or health-related human subject research—for advertising, marketing, or other use-based data mining purposes other than improving health management, or for the purpose of health research, and then only with permission. Apps may, however, use a user’s health or fitness data to provide a benefit directly to that user (such as a reduced insurance premium), provided that the app is submitted by the entity providing the benefit, and the data is not shared with a third party. You must disclose the specific health data that you are collecting from the device.</li>
</ul>
</li>
</ul>
</li>
<li data-sidenav="5.2 Intellectual Property" id="intellectual-property"><span id="5.2"></span><strong>5.2 Intellectual Property</strong>
<ul class="no-bullet margin-top-small">
<li id="5.2.3"><strong>5.2.3 Audio/Video Downloading:</strong> Apps should not facilitate illegal file sharing or include the ability to save, convert, or download media from third-party sources (e.g. <span class="nowrap">Apple Music,</span> YouTube, SoundCloud, Vimeo, etc.) without explicit authorization from those sources. Streaming of audio/video content may also violate Terms of Use, so be sure to check before your app accesses those services. <span class="delete">Documentation</span><span class="insert">Authorization</span> must be provided upon request.</li>
</ul>
</li>
</section></p></article><article class="article intro"><header><p class="date"><span>October 25, 2022</span></p><h2><a href="/articles/2022-10-25/">App Review clarification, new harmful content rule and info about Matter and selling NFTs</a></h2></header><section class="content"><p>Apple has updated their <a href="https://developer.apple.com/app-store/review/guidelines/">App Store Review Guidelines</a> expanding more on how to get through App Review, adding a new rule about harmful content, and adding new information about apps that support Matter, and about using in-app purchases to sell NFTs and services related to NFTs.
<br><br></p>
<p><a href="https://developer.apple.com/news/?id=xk8d7p8c">Apple’s full summary can be found here</a>.
</br></br></p>
<p>The complete set of changes can be seen below:</p>
</section><p class="changes"><section class="apple">
<h3 data-sidenav id="before-you-submit">Before You Submit</h3>
<p>Make sure you:</p>
<ul class="disc top-level">
<li>Provide <span class="nowrap"><span class="insert">App Review</span></span><span class="insert"> with full access to your app. If your app includes account-based features, provide either </span>an active demo account <span class="delete">and login information</span><span class="insert">or fully-featured demo mode</span>, plus any other hardware or resources that might be needed to review your app (e.g. login credentials or a sample QR code)</li>
</ul>
<span id="1.1"></span><strong>1.1 Objectionable Content</strong>
<ul class="no-bullet margin-top-small">
<li id="1.1.4"><strong>1.1.4</strong> Overtly sexual or pornographic material, defined as “explicit descriptions or displays of sexual organs or activities intended to stimulate erotic rather than aesthetic or emotional feelings.” This includes “hookup” apps <span class="insert">and other apps </span>that may include pornography or be used to facilitate prostitution<span class="insert">, or human trafficking and exploitation</span>.</li>
<li id="1.1.7"><strong><span class="insert">1.1.7</span></strong><span class="insert"> Harmful concepts which capitalize or seek to profit on recent or current events, such as violent conflicts, terrorist attacks, and epidemics.</span></li>
</ul>
<span id="2.1"></span><strong>2.1 App Completeness</strong>
<p>Submissions to <span class="nowrap">App Review,</span> including apps you make available for pre-order, should be final versions with all necessary metadata and fully functional URLs included; placeholder text, empty websites, and other temporary content should be scrubbed before submission. Make sure your app has been tested on-device for bugs and stability before you submit it, and include demo account info (and turn on your back-end service!) if your app includes a login. If you <span class="insert">are unable to provide a demo account due to legal or security obligations, you may include a built-in demo mode in lieu of a demo account with prior approval by Apple. Ensure the demo mode exhibits your app’s full features and functionality. If you </span>offer in-app purchases in your app, make sure they are complete, up-to-date, and visible to the reviewer, or that you explain why not in your review notes. Please don’t treat <span class="nowrap">App Review</span> as a software testing service. We will reject incomplete app bundles and binaries that crash or exhibit obvious technical problems.</p>
<span id="2.5"></span><strong>2.5 Software Requirements</strong>
<ul class="no-bullet margin-top-small">
<li id="2.5.17"><strong><span class="insert">2.5.17</span></strong><span class="insert"> Apps that support Matter must use Apple’s support framework for Matter to initiate pairing. In addition, if you choose to use any Matter software component in your app other than the </span><span class="nowrap"><span class="insert">Matter SDK</span></span><span class="insert"> provided by Apple, the software component must be certified by the </span><a href="https://csa-iot.org"><span class="insert">Connectivity Standards Alliance</span><span class="loc-c"></span></a><span class="insert"> for the platform it runs on.</span></li>
<li id="2.5.18"><strong><span class="insert">2.5.18</span></strong><span class="insert"> Display advertising should be limited to your main app binary, and should not be included in extensions, App Clips, widgets, notifications, keyboards, watchOS apps, etc. Ads displayed in an app must be appropriate for the app’s age rating, allow the user to see all information used to target them for that ad (without requiring the user to leave the app), and may not engage in targeted or behavioral advertising based on sensitive user data such as health/medical data (e.g. from the HealthKit APIs), school and classroom data (e.g. from ClassKit), or from kids (e.g. from apps in the Kids Category), etc. Interstitial ads or ads that interrupt or block the user experience must clearly indicate that they are an ad, must not manipulate or trick users into tapping into them, and must provide easily accessible and visible close/skip buttons large enough for people to easily dismiss the ad.</span></li>
</ul>
<span id="3.1"></span><strong>3.1 Payments</strong>
<ul class="no-bullet margin-top-small">
<li data-sidenav="3.1.1 In-App Purchase" id="in-app-purchase"><span id="3.1.1"></span><strong>3.1.1 In-App Purchase:</strong>
<ul class="disc no-margin-top">
<li>If you want to unlock features or functionality within your app, (by way of example: subscriptions, in-game currencies, game levels, access to premium content, or unlocking a full version), you must use in-app purchase. Apps may not use their own mechanisms to unlock content or functionality, such as license keys, augmented reality markers, QR codes, <span class="insert">cryptocurrencies and cryptocurrency wallets, </span>etc. Apps and their metadata may not include buttons, external links, or other calls to action that direct customers to purchasing mechanisms other than in-app purchase, except as set forth in 3.1.3(a).</li>
<li><span class="insert">Apps may use in-app purchase to sell and sell services related to non-fungible tokens (NFTs), such as minting, listing, and transferring. Apps may allow users to view their own NFTs, provided that NFT ownership does not unlock features or functionality within the app. Apps may allow users to browse NFT collections owned by others, provided that the apps may not include buttons, external links, or other calls to action that direct customers to purchasing mechanisms other than in-app purchase.</span></li>
</ul>
</li>
<li data-sidenav="3.1.3(g) Advertising Management Apps" id="advertising-management-apps"><span id="3.1.3g"></span><strong><span class="insert">3.1.3(g) Advertising Management Apps:</span></strong><span class="insert"> Apps for the sole purpose of allowing advertisers (persons or companies that advertise a product, service, or event) to purchase and manage advertising campaigns across media types (television, outdoor, websites, apps, etc.) do not need to use in-app purchase. These apps are intended for campaign management purposes and do not display the advertisements themselves. Digital purchases for content that is experienced or consumed in an app, including buying advertisements to display in the same app (such as sales of “boosts” for posts in a social media app) must use in-app purchase.</span></li>
<li data-sidenav="3.1.5 Cryptocurrencies" id="cryptocurrencies"><span id="3.1.5"></span><strong>3.1.5 Cryptocurrencies:</strong>
<ul class="disc margin-top-small">
<li>(iii) Exchanges: Apps may facilitate transactions or transmissions of cryptocurrency on an approved exchange, provided they are offered <span class="delete">by the</span><span class="insert">only in countries or regions where the app has appropriate licensing and permissions to provide a cryptocurrency</span> exchange<span class="delete"> itself</span>.</li>
</ul>
</li>
<span class="delete">3.1.7 Advertising:</span><span class="delete"> Display advertising should be limited to your main app binary, and should not be included in extensions, </span><span class="delete">App Clips,</span><span class="delete"> widgets, notifications, keyboards, watchOS apps, etc. Ads displayed in an app must be appropriate for the app’s age rating, allow the user to see all information used to target them for that ad (without requiring the user to leave the app), and may not engage in targeted or behavioral advertising based on sensitive user data such as health/medical data (e.g. from the HealthKit APIs), school and classroom data (e.g. from ClassKit), or from kids (e.g. from apps in the Kids Category), etc. Interstitial ads or ads that interrupt or block the user experience must clearly indicate that they are an ad, must not manipulate or trick users into tapping into them, and must provide easily accessible and visible close/skip buttons large enough for people to easily dismiss the ad.</span>
</ul>
<span id="5.2"></span><strong>5.2 Intellectual Property</strong>
<ul class="no-bullet margin-top-small">
<li id="5.2.5"><strong>5.2.5 Apple Products:</strong> Don’t create an app that appears confusingly similar to an existing Apple product, interface (e.g. Finder), app (such as the <span class="nowrap">App Store,</span> <span class="nowrap">iTunes Store,</span> or Messages) or advertising theme. Apps and extensions, including third-party keyboards and Sticker packs, may not include Apple emoji. <span class="insert">Music from </span>iTunes <span class="delete">music</span><span class="insert">and </span><span class="nowrap"><span class="insert">Apple Music</span></span> previews may not be used for their entertainment value (e.g. as the background music to a photo collage or the soundtrack to a game) or in any other unauthorized manner. If <span class="insert">you provide music previews from iTunes or </span><span class="nowrap"><span class="insert">Apple Music,</span></span><span class="insert"> you must display a link to the corresponding music in iTunes or </span><span class="nowrap"><span class="insert">Apple Music.</span></span><span class="insert"> If </span>your app displays Activity rings, they should not visualize Move, Exercise, or Stand data in a way that resembles the Activity control. The <a href="https://developer.apple.com/design/human-interface-guidelines/patterns/workouts#activity-rings">Human Interface Guidelines<span class="loc-en-only"></span></a> have more information on how to use Activity rings. If your app displays Apple Weather data, it should follow the attribution requirements provided in the <a href="/weatherkit/get-started/index.html#attribution-requirements">WeatherKit documentation<span class="loc-apac"></span></a>.</li>
</ul>
</section></p></article><article class="article intro"><header><p class="date"><span>June 08, 2022</span></p><h2><a href="/articles/2022-06-06-updates-in-preparation-for-upcoming-os-releases/">Updates in preparation for upcoming OS releases</a></h2></header><section class="content"><p>Apple has updated their <a href="https://developer.apple.com/app-store/review/guidelines/">App Store Review Guidelines</a> in preparation of upcoming <span class="caps">OS</span> releases.
<br><br></p>
<p><a href="https://developer.apple.com/news/?id=npbbcwsx">Apple’s own summary can be found here</a>.
</br></br></p>
<p>The complete set of changes can be seen below:</p>
</section><p class="changes"><section class="apple">
<li data-sidenav="1.1 Objectionable Content" id="objectionable-content"><span id="1.1"></span><strong>1.1 Objectionable Content</strong>
<ul class="no-bullet margin-top-small">
<li id="1.1.4"><strong>1.1.4</strong> Overtly sexual or pornographic material, defined <span class="delete">by Webster’s Dictionary </span>as “explicit descriptions or displays of sexual organs or activities intended to stimulate erotic rather than aesthetic or emotional feelings.” This includes “hookup” apps that may include pornography or be used to facilitate prostitution.</li>
</ul>
</li>
<li data-sidenav="1.5 Developer Information" id="developer-information"><span id="1.5"></span><strong>1.5 Developer Information</strong>
<p>People need to know how to reach you with questions and support issues. Make sure your app and its Support URL include an easy way to contact you; this is particularly important for apps that may be used in the classroom. Failure to include accurate and up-to-date contact information not only frustrates customers, but may violate the law in some countries<span class="insert"> or regions</span>. Also ensure that Wallet passes include valid contact information from the issuer and are signed with a dedicated certificate assigned to the brand or trademark owner of the pass.</p>
</li>
<li data-sidenav="1.7 Reporting Criminal Activity"><span id="1.7"></span><strong>1.7 Reporting Criminal Activity</strong>
<p>Apps for reporting alleged criminal activity must involve local law enforcement, and can only be offered in countries <span class="insert">or regions </span>where such involvement is active.</p>
</li>
<li data-sidenav="2.5 Software Requirements" id="software-requirements"><span id="2.5"></span><strong>2.5 Software Requirements</strong>
<ul class="no-bullet margin-top-small">
<li id="2.5.4"><strong>2.5.4</strong> Multitasking apps may only use background services for their intended purposes: VoIP, audio playback, location, task completion, local notifications, etc.<span class="delete"> If your app uses location background mode, include a reminder that doing so may dramatically decrease battery life.</span></li>
</ul>
</li>
<li data-sidenav="3.1 Payments" id="payments"><span id="3.1"></span><strong>3.1 Payments</strong>
<ul class="no-bullet margin-top-small">
<ul class="disc margin-top-small">
<li>Auto-renewing subscription apps may offer a free trial period to customers by providing the relevant information set forth in <span class="nowrap">App Store Connect.</span> <a href="https://developer.apple.com/app-store/subscriptions/#providing-subscription-offers">Learn more about <span class="delete">Subscription Free Trials</span><span class="insert">providing subscription offers</span>.</a></li>
</ul>
</li>
</ul>
</li>
<li data-sidenav="4.2 Minimum Functionality" id="minimum-functionality"><span id="4.2"></span><strong>4.2 Minimum Functionality</strong>
<ul class="no-bullet margin-top-small">
<li id="4.2.3"><strong>4.2.3</strong>
<ul class="disc margin-top-small">
<li>(ii) <span class="delete">Make sure you include sufficient content in the binary for the</span><span class="insert">If your</span> app <span class="insert">needs to download additional resources in order </span>to function <span class="delete">at launch.</span>
<span class="delete">(iii) If your app needs to download additional resources in order to function </span>on initial launch, disclose the size of the download and prompt users before doing so.</li>
</ul>
</li>
</ul>
</li>
<li data-sidenav="4.4 Extensions" id="extensions"><span id="4.4"></span><strong>4.4 Extensions</strong>
<ul class="no-bullet margin-top-small">
<li id="4.4.3"><strong>4.4.3</strong> Stickers
<ul class="no-bullet margin-top-small">
<li><strong>(ii)</strong> Consider regional sensitivities, and do not make your sticker pack available in a country <span class="insert">or region </span>where it could be poorly received or violate local law.</li>
</ul>
</li>
</ul>
</li>
<li data-sidenav="4.7 HTML5 Games, Bots, etc." id="third-party-software"><span id="4.7"></span><strong>4.7 HTML5 Games, Bots, etc.</strong>
<ul class="no-bullet margin-top-small">
<li id="4.7.1"><strong>4.7.1</strong> Software offered under this rule must:
<ul class="disc margin-top-small">
<li>not provide access to real money gaming<span class="delete">, lotteries, or charitable donations</span>;</li>
</ul>
</li>
</ul>
</li>
<li data-sidenav="5.1.3 Health and Health Research" id="health-and-health-research"><span id="5.1.3"></span><strong>5.1.3 Health and Health Research</strong>
<ul class="no-bullet margin-top-small">
<li><strong>(i)</strong> Apps may not use or disclose to third parties data gathered in the health, fitness, and medical research context—including from the Clinical Health Records API, HealthKit API, Motion and Fitness, MovementDisorderAPIs, or health-related human subject research—for advertising, marketing, or other use-based data mining purposes other than improving health management, or for the purpose of health research, and then only with permission. Apps may, however, use a user’s health or fitness data to provide a benefit directly to that user (such as a reduced insurance premium), provided that the app is submitted by the entity providing the benefit, and the data is not <span class="delete">be </span>shared with a third party. You must disclose the specific health data that you are collecting from the device.</li>
</ul>
</li>
<li data-sidenav="5.2 Intellectual Property" id="intellectual-property"><span id="5.2"></span><strong>5.2 Intellectual Property</strong>
<ul class="no-bullet margin-top-small">
<li id="5.2.5"><strong>5.2.5 Apple Products:</strong> Don’t create an app that appears confusingly similar to an existing Apple product, interface (e.g. Finder), app (such as the <span class="nowrap">App Store,</span> <span class="nowrap">iTunes Store,</span> or Messages) or advertising theme. Apps and extensions, including third-party keyboards and Sticker packs, may not include Apple emoji. iTunes music previews may not be used for their entertainment value (e.g. as the background music to a photo collage or the soundtrack to a game) or in any other unauthorized manner. If your app displays Activity rings, they should not visualize Move, Exercise, or Stand data in a way that resembles the Activity control. The <a href="https://developer.apple.com/design/human-interface-guidelines/watchos/system-capabilities/health-and-fitness/#activity-rings">Human Interface Guidelines<span class="loc-en-only"></span></a> have more information on how to use Activity rings.<span class="insert"> If your app displays Apple Weather data, it should follow the attribution requirements provided in the </span><a href="/weatherkit/get-started/index.html#attribution-requirements"><span class="insert">WeatherKit documentation</span></a><span class="insert">.</span></li>
</ul>
</li>
<li data-sidenav="5.3 Gaming, Gambling, and Lotteries" id="gaming-gambling-and-lotteries"><span id="5.3"></span><strong>5.3 Gaming, Gambling, and Lotteries</strong>
<ul class="no-bullet margin-top-small">
<li id="5.3.3"><strong>5.3.3</strong> Apps may not use in-app purchase to purchase credit or currency for use in conjunction with real money gaming of any kind<span class="delete">, and may not enable people to purchase lottery or raffle tickets or initiate fund transfers in the app</span>.</li>
</ul>
</li>
<h3 data-sidenav id="after-you-submit">After You Submit</h3>
<p>Once you’ve submitted your app and metadata in <span class="nowrap">App Store Connect</span> and you’re in the review process, here are some things to keep in mind:</p>
<ul class="disc top-level">
<li><strong>Rejections</strong>: Our goal is to apply these guidelines fairly and consistently, but nobody’s perfect. If your app has been rejected and you have questions or would like to provide additional information, please use <span class="nowrap">App Store Connect</span> to communicate directly with the <span class="nowrap">App Review</span> team. This may help get your app on the store, and it can help us improve the <span class="nowrap">App Review</span> process or identify a need for clarity in our policies.<span class="delete"> If you still disagree with the outcome, or would like to suggest a change to the guideline itself, please </span><span class="delete">submit an appeal</span><span class="delete">.</span></li>
</ul>
</section></p></article><article class="article intro"><header><p class="date"><span>April 05, 2022</span></p><h2><a href="/articles/2022-04-05-update-on-reader-app-distribution/">Update on "reader" app distribution</a></h2></header><section class="content"><p>Apple has updated their <a href="https://developer.apple.com/app-store/review/guidelines/">App Store Review Guidelines</a> to now allow developers of “reader” apps to include an in-app link to their website for account creation and management purposes.
<br><br></p>
<p><a href="https://developer.apple.com/news/?id=grjqafts">Apple’s own summary can be found here</a>.
</br></br></p>
<p>The complete set of changes can be seen below:</p>
</section><p class="changes"><section class="apple">
<li data-sidenav="3.1 Payments" id="payments"><span id="3.1"></span><strong>3.1 Payments</strong>
<ul class="no-bullet margin-top-small">
<li data-sidenav="3.1.1 In-App Purchase" id="in-app-purchase"><span id="3.1.1"></span><strong>3.1.1 In-App Purchase:</strong>
<ul class="disc no-margin-top">
<li>If you want to unlock features or functionality within your app, (by way of example: subscriptions, in-game currencies, game levels, access to premium content, or unlocking a full version), you must use in-app purchase. Apps may not use their own mechanisms to unlock content or functionality, such as license keys, augmented reality markers, QR codes, etc. Apps and their metadata may not include buttons, external links, or other calls to action that direct customers to purchasing mechanisms other than in-app purchase<span class="insert">, except as set forth in 3.1.3(a)</span>.</li>
</ul>
</li>
<li data-sidenav="3.1.3 Other Purchase Methods" id="other-purchase-methods"><span id="3.1.3"></span><strong>3.1.3 Other Purchase Methods:</strong> The following apps may use purchase methods other than in-app purchase. Apps in this section cannot, within the app, encourage users to use a purchasing method other than in-app purchase<span class="insert">, except as set forth in 3</span>.<span class="insert">1.3(a).</span> Developers can send communications outside of the app to their user base about purchasing methods other than in-app purchase.</li>
<li data-sidenav="3.1.3(a) “Reader” Apps" id="reader-apps"><span id="3.1.3a"></span><strong>3.1.3(a) “Reader” Apps:</strong> Apps may allow a user to access previously purchased content or content subscriptions (specifically: magazines, newspapers, books, audio, music, and video). Reader apps may offer account creation for free tiers, and account management functionality for existing customers.<span class="insert"> Reader app developers may apply for the External Link Account Entitlement to provide an informational link in their app to a web site the developer owns or maintains responsibility for in order to create or manage an account. Learn more about the </span><a href="/support/reader-apps/" class="loc-en-only"><span class="insert">External Link Account Entitlement</span></a><span class="insert">.</span></li>
</ul>
</li>
<li data-sidenav="5.6 Developer Code of Conduct" id="code-of-conduct"><span id="5.6"></span><strong>5.6 Developer Code of Conduct</strong>
<p>Please treat everyone with respect, whether in your responses to <span class="nowrap">App Store</span> reviews, customer support requests, or when communicating with Apple, including your responses in <span class="delete">Resolution Center</span><span class="nowrap"><span class="insert">App Store Connect</span>.</span> Do not engage in harassment of any kind, discriminatory practices, intimidation, bullying, and don’t encourage others to engage in any of the above. Repeated manipulative or misleading behavior or other fraudulent conduct will lead to your removal from the Apple Developer Program.</p>
</li>
<h3 data-sidenav id="after-you-submit">After You Submit</h3>
<p>Once you’ve submitted your app and metadata in <span class="nowrap">App Store Connect</span> and you’re in the review process, here are some things to keep in mind:</p>
<ul class="disc top-level">
<li><strong>Rejections</strong>: Our goal is to apply these guidelines fairly and consistently, but nobody’s perfect. If your app has been rejected and you have questions or would like to provide additional information, please use<span class="delete"> the Resolution Center to communicate directly with the</span> <span class="nowrap">App <span class="insert">Store Connect</span></span><span class="insert"> to communicate directly with the </span><span class="nowrap"><span class="insert">App </span>Review</span> team. This may help get your app on the store, and it can help us improve the <span class="nowrap">App Review</span> process or identify a need for clarity in our policies. If you still disagree with the outcome, or would like to suggest a change to the guideline itself, please <a href="https://developer.apple.com/contact/app-store/?topic=appeal">submit an appeal</a>.</li>
<li><strong>Bug Fix Submissions</strong>: For apps that are already on the <span class="nowrap">App Store,</span> bug fixes will no longer be delayed over guideline violations except for those related to legal or safety issues. If your app has been rejected, and qualifies for this process, please use<span class="delete"> the Resolution Center to communicate directly with the</span> <span class="nowrap">App <span class="insert">Store Connect</span></span><span class="insert"> to communicate directly with the </span><span class="nowrap"><span class="insert">App </span>Review</span> team indicating that you would like to take advantage of this process and plan to address the issue in your next submission.</li>
</ul>
</section></p></article><article class="article intro"><header><p class="date"><span>October 25, 2021</span></p><h2><a href="/articles/2021-10-25-in-app-events-purchasing-and-user-info/">In-app events, changed purchasing rules and basic contact information requests</a></h2></header><section class="content"><p>Apple has updated their <a href="https://developer.apple.com/app-store/review/guidelines/">App Store Review Guidelines</a> with new info about in-app events, changes to rules about targeting individuals regarding purchasing methods other than in-app purchases and new info about requests for basic contact information.
<br><br></p>
<p><a href="https://developer.apple.com/news/?id=4m3f5hbw">Apple’s own summary can be found here</a>.
</br></br></p>
<p>The complete set of changes can be seen below:</p>
</section><p class="changes"><section class="apple">
<li data-sidenav="2.3 Accurate Metadata" id="accurate-metadata"><span id="2.3"></span><strong>2.3 Accurate Metadata</strong>
<ul class="no-bullet margin-top-small">
<li id="2.3.13"><strong><span class="insert">2.3.13</span></strong><span class="insert"> In-app events are timely events that happen within your app. To feature your event on the App Store, it must fall within an event type provided in App Store Connect. All event metadata must be accurate and pertain to the event itself, rather than the app more generally. Events must happen at the times and dates you select in App Store Connect, including across multiple storefronts. You may monetize your event so long as you follow the rules set forth in Section 3 on Business. And your event deep link must direct users to the proper destination within your app. Read </span><a href="/app-store/in-app-events/"><span class="insert">In-App Events</span></a><span class="insert"> for detailed guidance on acceptable event metadata and event deep links.</span></li>
</ul>
</li>
<li data-sidenav="3.1 Payments" id="payments"><span id="3.1"></span><strong>3.1 Payments</strong>
<ul class="no-bullet margin-top-small">
<li data-sidenav="3.1.3 Other Purchase Methods" id="other-purchase-methods"><span id="3.1.3"></span><strong>3.1.3 Other Purchase Methods:</strong> The following apps may use purchase methods other than in-app purchase. Apps in this section cannot, within the app, encourage users to use a purchasing method other than in-app purchase. Developers <span class="delete">cannot use information obtained within</span><span class="insert">can send communications outside of</span> the app to <span class="delete">target individual users outside of the app to use</span><span class="insert">their user base about</span> purchasing methods other than in-app<span class="delete"> purchase (such as sending an individual user an email about other purchasing methods after that individual signs up for an account within the app). Developers can send communications outside of the app to their user base about purchasing methods other than in-app</span> purchase.</li>
</ul>
</li>
<li data-sidenav="5.1 Privacy" id="privacy"><span id="5.1"></span><strong>5.1 Privacy</strong>
<ul class="no-bullet margin-top-small">
<li data-sidenav="5.1.1 Data Collection and Storage" id="data-collection-and-storage"><span id="5.1.1"></span><strong>5.1.1 Data Collection and Storage</strong>
<ul class="no-bullet margin-top-small">
<li><strong><span class="insert">(x) </span></strong><span class="insert">Apps may request basic contact information (such as name and email address) so long as the request is optional for the user, features and services are not conditional on providing the information, and it complies with all other provisions of these guidelines, including limitations on collecting information from kids.</span></li>
</ul>
</li>
</ul>
</li>
</section></p></article><article class="article intro"><header><p class="date"><span>June 07, 2021</span></p><h2><a href="/articles/2021-06-07-wwdc-2021/">WWDC 2021</a></h2></header><section class="content"><p>On the back of this year’s Worldwide Developers Conference, Apple has updated the <a href="https://developer.apple.com/app-store/review/guidelines/">App Store Review Guidelines</a> with <a href="https://developer.apple.com/news/?id=dovxb62h">clarifications of existing guidelines, new prohibitions regarding apps facilitating prostitution and reporting crime activity, and much more</a>.</br></br></p>
<p>The complete set of changes can be seen below:</p>
</section><p class="changes"><section class="apple">
<div class="section-content">
<div class="column-flex large-9 small-12 margin-bottom">
<h3 data-sidenav id="introduction">Introduction</h3>
<p>A few other points to keep in mind:</p>
<ul class="disc top-level">
<li>If you attempt to cheat the system (for example, by trying to trick the review process, steal user data, copy another developer’s work, manipulate ratings or <span class="nowrap">App Store</span> discovery) your apps will be removed from the store and you will be expelled from the <span class="insert">Apple </span>Developer Program.</li>
</ul>
</div>
</div>
</section>
<section class="apple">
<h3 data-sidenav id="safety"><span id="1"></span>1. Safety</h3>
<ul class="no-bullet">
<li data-sidenav="1.1 Objectionable Content" id="objectionable-content"><span id="1.1"></span><strong>1.1 Objectionable Content</strong>
<ul class="no-bullet margin-top-small">
<li id="1.1.4"><strong>1.1.4</strong> Overtly sexual or pornographic material, defined by Webster’s Dictionary as “explicit descriptions or displays of sexual organs or activities intended to stimulate erotic rather than aesthetic or emotional feelings.<span class="delete">"</span><span class="insert">” This includes “hookup” apps that may include pornography or be used to facilitate prostitution.</span></li>
</ul>
</li>
<li data-sidenav="1.2 User-Generated Content" id="user-generated-content"><span id="1.2"></span><strong>1.2 User <span class="insert">-</span>Generated Content</strong>
<ul class="no-bullet margin-top-small">
<li id="1.2.1"><strong><span class="insert">1.2.1 Creator Content</span></strong><br><span class="insert">Apps which feature content from a specific community of users called “creators” are a great opportunity if properly moderated. These apps present a singular, unified experience for customers to interact with various kinds of creator content. They offer tools and programs to help this community of non-developer creators to author, share, and monetize user-generated experiences. These experiences must not change the core features and functionality of the native app—rather, they add content to those structured experiences. These experiences are not native “apps” coded by developers—they are content within the app itself and are treated as user-generated content by App Review. Such creator content may include video, articles, audio, and even casual games. The </span><span class="nowrap"><span class="insert">App Store</span></span><span class="insert"> supports apps offering such user-generated content so long as they follow all Guidelines, including Guideline 1.2 for moderating user-generated content and Guideline 3.1.1 for payments and in-app purchases. Creator apps should share the age rating of the highest age-rated creator content available in the app, and communicate to users which content requires additional purchases.</span></li>
</ul>
</li>
<li data-sidenav="1.4 Physical Harm" id="physical-harm"><span id="1.4"></span><strong>1.4 Physical Harm</strong>
<p>If your app behaves in a way that risks physical harm, we may reject it. For example:</p>
<ul class="no-bullet margin-top-small">
<li id="1.4.3"><strong>1.4.3</strong> Apps that encourage consumption of tobacco and vape products, illegal drugs, or excessive amounts of alcohol are not permitted on the <span class="nowrap">App Store.</span> Apps that encourage minors to consume any of these substances will be rejected. Facilitating the sale of controlled substances (except for licensed pharmacies<span class="insert"> and licensed or otherwise legal cannabis dispensaries</span>), <span class="delete">marijuana, </span>or tobacco is not allowed.</li>
</ul>
</li>
<li data-sidenav="1.7 Reporting Criminal Activity"><span id="1.7"></span><strong><span class="insert">1.7 Reporting Criminal Activity</span></strong>
<p><span class="insert">Apps for reporting alleged criminal activity must involve local law enforcement, and can only be offered in countries where such involvement is active.</span></p>
</li>
</ul>
</section>
<section class="apple">
<h3 data-sidenav id="performance"><span id="2"></span>2. Performance</h3>
<ul class="no-bullet">
<li data-sidenav="2.2 Beta Testing" id="beta-testing"><span id="2.2"></span><strong>2.2 Beta Testing</strong>
<p>Demos, betas, and trial versions of your app don’t belong on the <span class="nowrap">App Store –</span> use TestFlight instead. Any app submitted for beta distribution via TestFlight should be intended for public distribution and should comply with the <span class="nowrap">App Review</span> Guidelines. Note, however, that apps using TestFlight cannot be distributed to testers in exchange for compensation of any kind, including as a reward for crowd-sourced funding. Significant updates to your beta build should be submitted to TestFlight App Review before being distributed to your testers. To learn more, visit the <a href="/testflight/">TestFlight Beta Testing</a><span class="insert"> page</span>.</p></li>
<li data-sidenav="2.3 Accurate Metadata" id="accurate-metadata"><span id="2.3"></span><strong>2.3 Accurate Metadata</strong>
<ul class="no-bullet margin-top-small">
<li id="2.3.1"><strong>2.3.1</strong> Don’t include any hidden, dormant, or undocumented features in your app; your app’s functionality should be clear to end users and<span class="insert"> App Review. All new features, functionality, and product changes must be described with specificity in the Notes for Review section of</span> <span class="nowrap">App <span class="delete">Review.</span><span class="delete"> All new features, functionality, and product changes must be described with specificity in the Notes for Review section of </span><span class="delete">App </span>Store Connect</span> (generic descriptions will be rejected) and accessible for review. Similarly, <span class="delete">you should</span><span class="insert">marketing your app in a misleading way, such as by promoting content or services that it does</span> not <span class="delete">market your app on the </span><span class="delete">App Store</span><span class="delete"> or offline as including content or services that it does not </span>actually offer (e.g. iOS-based virus and malware scanners)<span class="insert"> or promoting a false price, whether within or outside of the App Store, is grounds for removal of your app from the </span><span class="nowrap"><span class="insert">App Store</span></span><span class="insert"> and termination of your developer account</span>. Egregious or repeated behavior is grounds for removal from the <span class="insert">Apple </span>Developer Program. We work hard to make the <span class="nowrap">App Store</span> a trustworthy ecosystem and expect our app developers to follow suit; if you’re dishonest, we don’t want to do business with you.</li>
<li id="2.3.3"><strong>2.3.3</strong> Screenshots should show the app in use, and not merely the title art, login page, or splash screen. They may also include text and image overlays (e.g. to demonstrate input mechanisms, such as an animated touch point or <span class="nowrap">Apple Pencil)</span> and show extended functionality on device, such as Touch Bar.</li>
<li id="2.3.10"><strong>2.3.10</strong> Make sure your app is focused on the iOS, <span class="delete">Mac</span><span class="insert">iPadOS</span>, <span class="delete">Apple TV</span><span class="delete"> or </span><span class="delete">Apple Watch</span><span class="insert">macOS, tvOS or watchOS</span> experience, and don’t include names, icons, or imagery of other mobile platforms in your app or metadata, unless there is specific, approved interactive functionality. Make sure your app metadata is focused on the app itself and its experience. Don’t include irrelevant information<span class="delete">, including but not limited to information about Apple or the development process</span>.</li>
</ul>
</li>
<li data-sidenav="2.4 Hardware Compatibility" id="hardware-compatibility"><span id="2.4"></span><strong>2.4 Hardware Compatibility</strong>
<ul class="no-bullet margin-top-small">
<li id="2.4.4"><strong>2.4.4</strong> Apps should never suggest or require a restart of the device or modifications to system settings unrelated to the core functionality of the <span class="delete">application</span><span class="insert">app</span>. For example, don’t encourage users to turn off Wi-Fi, disable security features, etc.</li>
<li id="2.4.5"><strong>2.4.5</strong> Apps distributed via the <span class="nowrap">Mac App Store</span> have some additional requirements to keep in mind:
<ul class="no-bullet margin-top-small">
<li><strong>(ii)</strong> They must be packaged and submitted using technologies provided in Xcode; no third-party installers allowed. They must also be self-contained, single <span class="delete">application</span><span class="insert">app</span> installation bundles and cannot install code or resources in shared locations.</li>
<li><strong>(iii)</strong> They may not auto-launch or have other code run automatically at startup or login without consent nor spawn processes that continue to run without consent after a user has quit the app. They should not automatically add their icons to the Dock or leave shortcuts on the user desktop.</li>
</ul>
</li>
</ul>
</li>
<li data-sidenav="2.5 Software Requirements" id="software-requirements"><span id="2.5"></span><strong>2.5 Software Requirements</strong>
<ul class="no-bullet margin-top-small">
<li id="2.5.2"><strong>2.5.2</strong> Apps should be self-contained in their bundles, and may not read or write data outside the designated container area, nor may they download, install, or execute code which introduces or changes features or functionality of the app, including other apps. Educational apps designed to teach, develop, or allow students to test executable code may, in limited circumstances, download code provided that such code is not used for other purposes. Such apps must make the source code provided by the <span class="delete">Application</span><span class="insert">app</span> completely viewable and editable by the user.</li>
<li id="2.5.3"><strong>2.5.3</strong> Apps that transmit viruses, files, computer code, or programs that may harm or disrupt the normal operation of the operating system and/or hardware features, including Push Notifications and Game Center, will be rejected. Egregious violations and repeat behavior will result in removal from the <span class="insert">Apple </span>Developer Program.</li>
</ul>
</li>
</ul>
</section>
<section class="apple">
<h3 data-sidenav id="business"><span id="3"></span>3. Business</h3>
<p class="section-intro margin-bottom-small">If we find that you have attempted to manipulate reviews, inflate your chart rankings with paid, incentivized, filtered, or fake feedback, or engage with third-party services to do so on your behalf, we will take steps to preserve the integrity of the <span class="nowrap">App Store,</span> which may include expelling you from the <span class="insert">Apple </span>Developer Program.</p>
<ul class="no-bullet">
<li data-sidenav="3.1 Payments" id="payments"><span id="3.1"></span><strong>3.1 Payments</strong>
<ul class="no-bullet margin-top-small">
<li data-sidenav="3.1.1 In-App Purchase" id="in-app-purchase"><span id="3.1.1"></span><strong>3.1.1 In-App Purchase:</strong>
<ul class="disc no-margin-top">
<li><span class="delete">Gift</span><span class="insert">Digital gift</span> cards, certificates, vouchers, and coupons which can be redeemed for digital goods or services can only be sold in your app using in-app<span class="insert"> purchase. Physical gift cards that are sold within an app and then mailed to customers may use payment methods other than in-app</span> purchase.</li>
</ul>
</li>
<li id="permissible-uses"><span id="3.1.2a"></span><strong>3.1.2(a) Permissible uses:</strong>
<ul class="disc margin-top-small">
<li>Auto-renewing subscription apps may offer a free trial period to customers by providing the relevant information set forth in <span class="nowrap">App Store Connect.</span><span class="insert"> Learn more about Subscription Free Trials.</span></li>
<li>Apps that attempt to scam users will be removed from the <span class="nowrap">App Store.</span> This includes apps that attempt to trick users into purchasing a subscription under false pretenses or engage in bait-and-switch and scam practices<span class="insert">; these</span> will be removed from the <span class="nowrap">App Store</span> and you may be removed from the <span class="nowrap">Apple Developer</span> Program.<span class="delete"> Learn more about </span><span class="delete">Subscription Free Trials</span><span class="delete">.</span></li>
<li><span class="delete">Apps that offer</span><span class="insert">Cellular carrier apps may include</span> auto-renewing music and video subscriptions<span class="delete"> with prior approval by Apple may also be included</span> in pre-defined bundles with cellular data plans<span class="delete"> offered in</span><span class="insert">, with prior approval by Apple. Other auto-renewing subscriptions may also be included in pre-defined bundles with</span> cellular <span class="insert">data plans, with prior approval by Apple, if the cellular </span>carrier apps<span class="insert"> support in-app purchase for new users and the carrier provides a mechanism for customers to revert to in-app purchase upon termination of the customer’s bundled service. Such subscriptions cannot include access to or discounts on consumable items</span>.</li>
</ul>
</li>
<li data-sidenav="3.1.3 Other Purchase Methods" id="other-purchase-methods"><span id="3.1.3"></span><strong>3.1.3 Other Purchase Methods:</strong> The following apps may use purchase methods other than in-app purchase. Apps in this section cannot, <span class="delete">either </span>within the app<span class="delete"> or through communications sent to points of contact obtained from account registration within the app (like email or text)</span>, encourage users to use a purchasing method other than in-app<span class="insert"> purchase. Developers cannot use information obtained within the app to target individual users outside of the app to use purchasing methods other than in-app purchase (such as sending an individual user an email about other purchasing methods after that individual signs up for an account within the app). Developers can send communications outside of the app to their user base about purchasing methods other than in-app</span> purchase.</li>
<li data-sidenav="3.1.7 Advertising" id="advertising"><span id="3.1.7"></span><strong>3.1.7 Advertising:</strong> Display advertising should be limited to your main app <span class="delete">executable</span><span class="insert">binary</span>, and should not be included in extensions, <span class="nowrap">App Clips,</span> widgets, notifications, keyboards, watchOS apps, etc. Ads displayed in an app must be appropriate for the app’s age rating, allow the user to see all information used to target them for that ad (without requiring the user to leave the app), and may not engage in targeted or behavioral advertising based on sensitive user data such as health/medical data (e.g. from the HealthKit APIs), school and classroom data (e.g. from ClassKit), or from kids (e.g. from apps in the Kids Category), etc. Interstitial ads or ads that interrupt or block the user experience must clearly indicate that they are an ad, must not manipulate or trick users into tapping into them, and must provide easily accessible and visible close/skip buttons large enough for people to easily dismiss the ad.</li>
</ul>
</li>
<li data-sidenav="3.2 Other Business Model Issues" id="other-business-model-issues"><span id="3.2"></span><strong>3.2 Other Business Model Issues</strong>
<ul class="no-bullet margin-top-small">
<li data-sidenav="3.2.1 Acceptable" id="acceptable"><span id="3.2.1"></span><strong>3.2.1 Acceptable</strong>
<ul class="no-bullet margin-top-small">
<li><strong>(viii)</strong> Apps used for financial trading, investing, or money management should <span class="delete">come from</span><span class="insert">be submitted by</span> the financial institution performing such services.</li>
</ul>
</li>
</ul>
</li>
</ul>
</section>
<section class="apple">
<h3 data-sidenav id="design"><span id="4"></span>4. Design</h3>
<ul class="no-bullet">
<li data-sidenav="4.2 Minimum Functionality" id="minimum-functionality"><span id="4.2"></span><strong>4.2 Minimum Functionality</strong>
<p>Your app should include features, content, and UI that elevate it beyond a repackaged website. If your app is not particularly useful, unique, or “app-like,” it doesn’t belong on the <span class="nowrap">App Store.</span> If your App doesn’t provide some sort of lasting entertainment value<span class="insert"> or adequate utility</span>, it may not be accepted. Apps that are simply a song or movie should be submitted to the <span class="nowrap">iTunes Store.</span> Apps that are simply a book or game guide should be submitted to the <span class="nowrap">Apple Books Store.</span></p>
</li>
<li data-sidenav="4.3 Spam" id="spam"><span id="4.3"></span><strong>4.3 Spam</strong><p>Don’t create multiple Bundle IDs of the same app. If your app has different versions for specific locations, sports teams, universities, etc., consider submitting a single app and provide the variations using in-app purchase. Also avoid piling on to a category that is already saturated; the <span class="nowrap">App Store</span> has enough fart, burp, flashlight, fortune telling, dating, <span class="insert">drinking games, </span>and Kama Sutra apps, etc. already. We will reject these apps unless they provide a unique, high-quality experience. Spamming the store may lead to your removal from the <span class="insert">Apple </span>Developer Program.</p></li>
<li data-sidenav="4.4 Extensions" id="extensions"><span id="4.4"></span><strong>4.4 Extensions</strong>
<ul class="no-bullet margin-top-small">
<li id="4.4.3"><strong>4.4.3</strong> Stickers
<ul class="no-bullet margin-top-small">
<li><strong>(v)</strong> You must have all the necessary copyright, trademark, publicity rights, and permissions for the content in your stickers, and shouldn’t submit anything unless you’re authorized to do so. Keep in mind that you must be able to provide verifiable documentation upon request. Apps with sticker content you don’t have rights to use will be removed from the <span class="nowrap">App Store</span> and repeat offenders will be removed from the <span class="insert">Apple </span>Developer Program. If you believe your content has been infringed by another provider, <a href="https://www.apple.com/legal/internet-services/itunes/appstorenotices/#?lang=en">submit a claim here</a>.</li>
</ul>
</li>
</ul>
</li>
<li data-sidenav="4.5 Apple Sites and Services" id="apple-sites-and-services"><span id="4.5"></span><strong>4.5 Apple Sites and Services</strong>
<ul class="no-bullet margin-top-small">
<li id="4.5.3"><strong>4.5.3</strong> Do not use Apple Services to spam, phish, or send unsolicited messages to customers, including <span class="nowrap">Game Center,</span> Push Notifications, etc. Do not attempt to reverse lookup, trace, relate, associate, mine, harvest, or otherwise exploit Player IDs, aliases, or other information obtained through <span class="nowrap">Game Center,</span> or you will be removed from the <span class="insert">Apple </span>Developer Program.</li>
</ul>
</li>
<li data-sidenav="4.7 HTML5 Games, Bots, etc." id="third-party-software"><span id="4.7"></span><strong>4.7 HTML5 Games, Bots, etc.</strong>
<p>Apps may contain or run code that is not embedded in the binary (e.g. HTML5-based games, bots, etc.), as long as code distribution isn’t the main purpose of the app, the code is not offered in a store or store-like interface, and provided that the software <span class="delete">(</span><span class="insert">adheres to the additional rules that follow in 4.7.</span>1<span class="delete">) is</span><span class="insert"> and 4.7.2. These additional rules are important to preserve the experience that </span><span class="nowrap"><span class="insert">App Store</span></span><span class="insert"> customers expect, and to help ensure user safety.</span></p>
<ul class="no-bullet margin-top-small">
<li id="4.7.1"><strong><span class="insert">4.7.1</span></strong><span class="insert"> Software offered under this rule must:
</span><ul class="disc margin-top-small">
<li><span class="insert">be</span> free or purchased using in-app purchase;<span class="delete"> (2) </span></li>
<li>only <span class="delete">uses</span><span class="insert">use</span> capabilities available in a standard WebKit view (e.g. it must open and run natively in Safari without modifications or additional software); <span class="delete">your app must</span><span class="insert">and</span> use WebKit and JavaScript Core to run third-party software and should not attempt to extend or expose native platform APIs to third-party software;<span class="delete"> (3) is</span></li>
<li><span class="insert">be</span> offered by developers that have joined the <span class="nowrap">Apple Developer</span> Program and signed the <span class="nowrap">Apple Developer</span> Program License Agreement;<span class="delete"> (4) does </span></li>
<li>not provide access to real money gaming, lotteries, or charitable donations;<span class="delete"> (5) adheres</span></li>
<li><span class="insert">adhere</span> to the terms of these <span class="nowrap">App <span class="insert">Store</span></span> Review Guidelines (e.g. <span class="delete">does</span><span class="insert">do</span> not include objectionable content); and<span class="delete"> (6) does </span></li>
<li>not offer digital goods or services for sale.</li>
</ul>
</li>
<li id="4.7.2"><strong><span class="insert">4.7.2</span></strong> Upon request, you must provide an index of software and metadata available in your app. It must include <span class="nowrap">Apple Developer</span> Program Team IDs for the providers of the software along with a URL which App Review can use to confirm that the software complies with the requirements above.</li>
</ul>
</li>
</ul>
</section>
<section class="apple">
<h3 data-sidenav id="legal"><span id="5"></span>5. Legal</h3>
<ul class="no-bullet">
<li data-sidenav="5.1 Privacy" id="privacy"><span id="5.1"></span><strong>5.1 Privacy</strong>
<ul class="no-bullet margin-top-small">
<li data-sidenav="5.1.1 Data Collection and Storage" id="data-collection-and-storage"><span id="5.1.1"></span><strong>5.1.1 Data Collection and Storage</strong>
<ul class="no-bullet margin-top-small">
<li><strong>(v) Account Sign-In: </strong>If your app doesn’t include significant account-based features, let people use it without a login. <span class="insert">If your app supports account creation, you must also offer account deletion within the app. </span>Apps may not require users to enter personal information to function, except when directly relevant to the core functionality of the app or required by law. If your core app functionality is not related to a specific social network (e.g. Facebook, WeChat, Weibo, Twitter, etc.), you must provide access without a login or via another mechanism. Pulling basic profile information, sharing to the social network, or inviting friends to use the app are not considered core app functionality. The app must also include a mechanism to revoke social network credentials and disable data access between the app and social network from within the app. An app may not store credentials or tokens to social networks off of the device and may only use such credentials or tokens to directly connect to the social network from the app itself while the app is in use.</li>
<li><strong>(vi) </strong>Developers that use their apps to surreptitiously discover passwords or other private data will be removed from the <span class="nowrap"><span class="insert">Apple </span>Developer</span> Program.</li>
<li><strong>(ix) </strong>Apps that provide services in highly-regulated fields (such as banking and financial services, healthcare, gambling, <span class="insert">legal cannabis use, </span>and air travel) or that require sensitive user information should be submitted by a legal entity that provides the services, and not by an individual developer.<span class="insert"> Apps that facilitate the legal sale of cannabis must be geo-restricted to the corresponding legal jurisdiction.</span></li>
</ul>
</li>
</ul>
</li>
<li data-sidenav="5.3 Gaming, Gambling, and Lotteries" id="gaming-gambling-and-lotteries"><span id="5.3"></span><strong>5.3 Gaming, Gambling, and Lotteries</strong>
<p><span class="delete">Gambling</span><span class="insert">Gaming</span>, <span class="delete">gaming</span><span class="insert">gambling</span>, and lotteries can be tricky to manage and tend to be one of the most regulated offerings on the <span class="nowrap">App Store.</span> Only include this functionality if you’ve fully vetted your legal obligations everywhere you make your app available and are prepared for extra time during the review process. Some things to keep in mind:</p>
</li>
<li data-sidenav="5.5 Mobile Device Management" id="mobile-device-management"><span id="5.5"></span><strong>5.5 Mobile Device Management</strong>
<p>Mobile Device Management Apps that offer Mobile Device Management (MDM) services must request this capability from Apple. Such apps may only be offered by commercial enterprises<span class="delete"> (such as business organizations</span>, educational institutions, or government agencies<span class="delete">)</span>, and in limited cases, companies using MDM for parental control services or device security. You must make a clear declaration of what user data will be collected and how it will be used on an app screen prior to any user action to purchase or otherwise use the service. MDM apps must not violate any applicable laws. Apps offering MDM services may not sell, use, or disclose to third parties any data for any purpose, and must commit to this in their privacy policy. In limited cases, third-party analytics may be permitted provided that the services only collect or transmit data about the performance of the developer’s MDM app, and not any data about the user, the user’s device, or other apps used on that device. Apps offering configuration profiles must also adhere to these requirements. Apps that do not comply with this guideline will be removed from the <span class="nowrap">App Store</span> and you may be removed from the <span class="nowrap">Apple Developer Program.</span></p>
</li>
<li data-sidenav="5.6 Developer Code of Conduct" id="code-of-conduct"><span id="5.6"></span><strong>5.6 Developer Code of Conduct</strong>
<p>Please treat everyone with respect, whether in your responses to <span class="nowrap">App Store</span> reviews, customer support requests, or when communicating with Apple, including your responses in Resolution Center. Do not engage in harassment of any kind, discriminatory practices, intimidation, bullying, and don’t encourage others to engage in any of the above.<span class="insert"> Repeated manipulative or misleading behavior or other fraudulent conduct will lead to your removal from the Apple Developer Program.</span></p>
<p><span class="insert">Your Developer Program account will be terminated if you engage in activities or actions that are not in accordance with the Developer Code of Conduct. To restore your account, you may provide a written statement detailing the improvements you plan to make. If your plan is approved by Apple and we confirm the changes have been made, your account may be restored.</span></p>
<ul class="no-bullet margin-top-small">
<li id="5.6.2"><strong><span class="insert">5.6.2 Developer Identity</span></strong>
<p><span class="insert">Providing verifiable information to Apple and customers is critical to customer trust. Your representation of yourself, your business, and your offerings on the </span><span class="nowrap"><span class="insert">App Store</span></span><span class="insert"> must be accurate. The information you provide must be truthful, relevant, and up-to-date so that Apple and customers understand who they are engaging with and can contact you regarding any issues.</span></p>
</li>
<li id="5.6.3"><strong><span class="insert">5.6.3 Discovery Fraud</span></strong>
<p><span class="insert">Participating in the </span><span class="nowrap"><span class="insert">App Store</span></span><span class="insert"> requires integrity and a commitment to building and maintaining customer trust. Manipulating any element of the </span><span class="nowrap"><span class="insert">App Store</span></span><span class="insert"> customer experience such as charts, search reviews, or referrals to your app erodes customer trust and is not permitted.</span></p>
</li>
<li id="5.6.4"><strong><span class="insert">5.6.4 App Quality</span></strong>
<p><span class="insert">Customers expect the highest quality from the </span><span class="nowrap"><span class="insert">App Store,</span></span><span class="insert"> and maintaining high quality content, services, and experiences promotes customer trust. Indications that this expectation is not being met include excessive customer reports about concerns with your app, such as negative customer reviews, and excessive refund requests. Inability to maintain high quality may be a factor in deciding whether a developer is abiding by the Developer Code of Conduct.</span></p>
</li>
</ul>
</li>
</ul>
</section>
<section class="apple">
<h3 data-sidenav id="after-you-submit">After You Submit</h3>
<ul class="disc top-level">
<li><strong>Bug Fix Submissions</strong>: For apps that are already on the <span class="nowrap">App Store,</span> bug fixes will no longer be delayed over guideline violations except for those related to legal<span class="insert"> or safety</span> issues. If your app has been rejected, and qualifies for this process, please use the Resolution Center to communicate directly with the <span class="nowrap">App Review</span> team indicating that you would like to take advantage of this process and plan to address the issue in your next submission.</li>
</ul>
</section></p></article><article class="article intro"><header><p class="date"><span>February 02, 2021</span></p><h2><a href="/articles/2021-02-02-app-tracking-transparency-and-more/">Clarifications and App Tracking Transparency</a></h2></header><section class="content"><p>Apple has updated the <a href="https://developer.apple.com/app-store/review/guidelines/">App Store Review Guidelines</a> with <a href="https://developer.apple.com/news/?id=3ozbk628">support for new features in upcoming <span class="caps">OS</span> releases, e.g. App Tracking Transparency, better protection of customers, and more help to get your apps through the review process as smoothly as possible</a>.</br></br></p>
<p>The complete set of changes can be seen below:</p>
</section><p class="changes"><section class="apple">
<li data-sidenav="1.4 Physical Harm" id="physical-harm"><span id="1.4"></span><strong>1.4 Physical Harm</strong>
<p>If your app behaves in a way that risks physical harm, we may reject it. For example:</p>
<ul class="no-bullet margin-top-small">
<li id="1.4.3"><strong>1.4.3</strong> Apps that encourage consumption of tobacco and vape products, illegal drugs, or excessive amounts of alcohol are not permitted on the <span class="nowrap">App Store.</span> Apps that encourage minors to consume any of these substances will be rejected. Facilitating the sale of<span class="insert"> controlled substances (except for licensed pharmacies),</span> marijuana, <span class="insert">or </span>tobacco<span class="delete">, or controlled substances (except for licensed pharmacies) isn’t</span><span class="insert"> is not</span> allowed.</li>
</ul>
</li>
<ul class="no-bullet">
<li data-sidenav="2.3 Accurate Metadata" id="accurate-metadata"><span id="2.3"></span><strong>2.3 Accurate Metadata</strong>
<p>Customers should know what they’re getting when they download or buy your app, so make sure <span class="insert">all </span>your app<span class="insert"> metadata, including privacy information, your app</span> description, screenshots, and previews accurately reflect the app’s core experience and remember to keep them up-to-date with new versions.</p>
<ul class="no-bullet margin-top-small">
<li id="2.3.7"><strong>2.3.7</strong> Choose a unique app name, assign keywords that accurately describe your app, and don’t try to pack any of your metadata with trademarked terms, popular app names, pricing information, or other irrelevant phrases just to game the system. App names must be limited to 30 characters<span class="delete"> and</span><span class="insert">. Metadata such as app names, subtitles, screenshots, and previews</span> should not include prices, terms, or descriptions that are not <span class="delete">the name of the app</span><span class="insert">specific to the metadata type</span>. App subtitles are a great way to provide additional context for your app; they must follow our standard metadata rules and should not include inappropriate content, reference other apps, or make unverifiable product claims. Apple may modify inappropriate keywords at any time or take other appropriate steps to prevent abuse.</li>
</ul>
</li>
<li data-sidenav="2.4 Hardware Compatibility" id="hardware-compatibility"><span id="2.4"></span><strong>2.4 Hardware Compatibility</strong>
<ul class="no-bullet margin-top-small">
<li id="2.4.5"><strong>2.4.5</strong> Apps distributed via the <span class="nowrap">Mac App Store</span> have some additional requirements to keep in mind:
<ul class="no-bullet margin-top-small">
<li><strong>(viii)</strong> Apps should run on the currently shipping OS and may not use deprecated or optionally installed technologies (e.g. Java<span class="delete">, Rosetta</span>)</li>
</ul>
</li>
</ul>
</li>
</ul>
<ul class="no-bullet">
<li data-sidenav="3.1 Payments" id="payments"><span id="3.1"></span><strong>3.1 Payments</strong>
<ul class="no-bullet margin-top-small">
<li data-sidenav="3.1.1 In-App Purchase" id="in-app-purchase"><span id="3.1.1"></span><strong>3.1.1 In-App Purchase:</strong>
<ul class="disc no-margin-top">
<li>Apps may use in-app purchase currencies to enable customers to “tip” <span class="insert">the developer or </span>digital content providers in the app.</li>
<li>Any credits or in-game currencies purchased via in-app purchase may not expire, and you should make sure you have a restore mechanism for any restorable in-app purchases.</li>
<span class="delete">Remember to assign the correct purchasability type or your app will be rejected.</span>
<li><span class="insert">Gift cards, certificates, vouchers, and coupons which can be redeemed for digital goods or services can only be sold in your app using in-app purchase.</span></li>
</ul>
</li>
<li id="permissible-uses"><span id="3.1.2a"></span><strong>3.1.2(a) Permissible uses:</strong> If you offer an auto-renewing subscription, you must provide ongoing value to the customer, and the subscription period must last at least seven days and be available across all of the user’s devices. While the following list is not exhaustive, examples of appropriate subscriptions include: new game levels; episodic content; multiplayer support; apps that offer consistent, substantive updates; access to large collections of, or continually updated, media content; software as a service (“SAAS”); and cloud support. In addition:
<ul class="disc margin-top-small">
<li>Games offered in a streaming game service subscription <span class="insert">may offer a single subscription that is shared across third-party apps and services; however, they </span>must be downloaded directly from the <span class="nowrap">App Store,</span> must be designed to avoid duplicate payment by a subscriber, and should not disadvantage non-subscriber customers.</li>
</ul>
</li>
<li data-sidenav="3.1.3(c) Enterprise Services" id="enterprise-services"><span id="3.1.3c"></span><strong>3.1.3(c) Enterprise Services:</strong> If your app is only sold directly by you to organizations or groups for their employees or students (for example professional databases and classroom management tools), you may <span class="insert">allow enterprise users to access previously-purchased content or subscriptions. Consumer, single user, or family sales must </span>use<span class="delete"> purchase methods in addition to</span> in-app<span class="delete"> purchase to collect those payments. Consumer, single user, or family sales must use in-app</span> purchase.</li>
<li data-sidenav="3.1.3(d) Person-to-Person Services" id="person-to-person-services"><span id="3.1.3d"></span><strong>3.1.3(d) Person-to-Person <span class="delete">Experiences:</span><span class="insert">Services:</span></strong> If your app enables the purchase of realtime person-to-person <span class="delete">experiences</span><span class="insert">services</span> between two individuals (for example tutoring students, medical consultations, real estate tours, or fitness training), you may use purchase methods other than in-app purchase to collect those payments. One-to-few and one-to-many realtime <span class="delete">experiences</span><span class="insert">services</span> must use in-app purchase.</li>
</ul>
</li>
<li data-sidenav="3.2 Other Business Model Issues" id="other-business-model-issues"><span id="3.2"></span><strong>3.2 Other Business Model Issues</strong>
<p>The lists below are not exhaustive, and your submission may trigger a change or update to our policies, but here are some additional dos and don’ts to keep in mind:</p>
<ul class="no-bullet margin-top-small">
<li data-sidenav="3.2.1 Acceptable" id="acceptable"><span id="3.2.1"></span><strong>3.2.1 Acceptable</strong>
<ul class="no-bullet margin-top-small">
<li><strong>(vii)</strong> Apps may enable individual users to give a monetary gift to another individual without using in-app purchase, provided that (a) the gift is a completely optional choice by the giver, and (b) 100% of the funds go to the receiver of the gift. However, a gift that is connected to or associated at any point in time with receiving digital content or services must use in-app purchase.</li>
<li><strong>(viii)</strong> Apps used for financial trading, investing, or money management should come from the financial institution performing such services<span class="delete"> or must use a public API offered by the institution in compliance with its Terms & Conditions</span>.</li>
</ul>
</li>
<li data-sidenav="3.2.2 Unacceptable" id="unacceptable"><span id="3.2.2"></span><strong>3.2.2 Unacceptable</strong>
<ul class="no-bullet margin-top-small">
<li><strong>(ix)</strong> Apps <span class="insert">offering personal loans </span>must <span class="delete">not force users to rate the app, review the app, download other apps, or perform other similar actions in order to access functionality, content, or use of the app.</span>
<span class="delete">(x)</span><span class="delete"> Apps offering personal loans must </span>clearly and conspicuously disclose all loan terms, including but not limited to equivalent maximum Annual Percentage Rate (APR) and payment due date. Apps may not charge a maximum APR higher than 36%, including costs and fees, and may not require repayment in full in 60 days or less.</li>
</ul>
</li>
</ul>
</li>
</ul>
<li data-sidenav="4.2 Minimum Functionality" id="minimum-functionality"><span id="4.2"></span><strong>4.2 Minimum Functionality</strong>
<ul class="no-bullet margin-top-small">
<li id="4.2.3"><strong>4.2.3</strong>
<ul class="disc margin-top-small">
<li>(iii) If your app needs to download additional resources<span class="insert"> in order to function on initial launch</span>, disclose the size of the download and prompt users before doing so.</li>
</ul>
</li>
</ul>
</li>
<li data-sidenav="5.1 Privacy" id="privacy"><span id="5.1"></span><strong>5.1 Privacy</strong>
<ul class="no-bullet margin-top-small">
<li data-sidenav="5.1.1 Data Collection and Storage" id="data-collection-and-storage"><span id="5.1.1"></span><strong>5.1.1 Data Collection and Storage</strong>
<ul class="no-bullet margin-top-small">
<li><strong>(ix) </strong>Apps that provide services in highly-regulated fields (such as banking and financial services, healthcare, <span class="insert">gambling, </span>and air travel) or that require sensitive user information should be submitted by a legal entity that provides the services, and not by an individual developer.</li>
</ul>
</li>
<li data-sidenav="5.1.2 Data Use and Sharing" id="data-use-and-sharing"><span id="5.1.2"></span><strong>5.1.2 Data Use and Sharing</strong>
<ul class="no-bullet margin-top-small">
<li><strong>(i) </strong>Unless otherwise permitted by law, you may not use, transmit, or share someone’s personal data without first obtaining their permission. You must provide access to information about how and where the data will be used. Data collected from apps may only be shared with third parties to improve the app or serve advertising (in compliance with the <a href="/terms/">Apple Developer Program License Agreement</a>). <span class="insert">You must receive explicit permission from users via the App Tracking Transparency APIs to track their activity. Learn more about </span><a href="/app-store/user-privacy-and-data-use/"><span class="insert">tracking</span></a><span class="insert">. </span>Apps that share user data without user consent or otherwise complying with data privacy laws may be removed from sale and may result in your removal from the <span class="nowrap">Apple Developer Program.</span></li>
<li><strong>(vii) </strong>Apps using<span class="delete"> Apple Pay may only share user data acquired via</span> <span class="nowrap">Apple Pay</span> <span class="insert">may only share user data acquired via </span><span class="nowrap"><span class="insert">Apple Pay</span></span> with third parties to facilitate or improve delivery of goods and services.</li>
</ul>
</li>
</ul>
</li>
<h3 data-sidenav id="after-you-submit">After You Submit</h3>
<ul class="disc top-level">
<li><strong><span class="insert">Appeals</span></strong><span class="insert">: If you disagree with the outcome of your review, or would like to suggest a change to the guideline itself, please </span><a href="https://developer.apple.com/contact/app-store/?topic=appeal"><span class="insert">submit an appeal</span></a><span class="insert">. This may help get your app on the store, and it can help us improve the </span><span class="nowrap"><span class="insert">App Review</span></span><span class="insert"> process or identify a need for clarity in our policies.</span></li>
</ul>
</section></p></article><article class="article intro"><header><p class="date"><span>September 11, 2020</span></p><h2><a href="/articles/2020-09-11-streaming-game-services-changes/">New rules for streaming game services and more</a></h2></header><section class="content"><p>Apple has updated the <a href="https://developer.apple.com/app-store/review/guidelines/">App Store Review Guidelines</a> with changes to rules related to <a href="https://developer.apple.com/news/?id=xqk627qu">streaming game services, hidden functionality in apps, and more</a>.</br></br></p>
<p>Mainly, Apple now allows for streaming game services as long as the included games can be downloaded directly from the App Store. Apple has also clarified that so-called “Reader apps”, like Netflix, can offer account creation for free tiers, and they’ve now made it more clear that having hidden, dormant or undocumented features in apps are not allowed, an obvious reference to the Fortnite situation.</br></br></p>
<p>The complete changes can be seen below:</p>
</section><p class="changes"><section class="apple">
<li data-sidenav="2.3 Accurate Metadata" id="accurate-metadata"><span id="2.3"></span><strong>2.3 Accurate Metadata</strong>
<p>Customers should know what they’re getting when they download or buy your app, so make sure your app description, screenshots, and previews accurately reflect the app’s core experience and remember to keep them up-to-date with new versions.</p>
<ul class="no-bullet margin-top-small">
<li id="2.3.1"><strong>2.3.1</strong> Don’t include any hidden<span class="insert">, dormant,</span> or undocumented features in your app; your app’s functionality should be clear to end<span class="delete">-</span> users and <span class="nowrap">App Review.</span><span class="insert"> All new features, functionality, and product changes must be described with specificity in the Notes for Review section of </span><span class="nowrap"><span class="insert">App Store Connect</span></span><span class="insert"> (generic descriptions will be rejected) and accessible for review.</span> Similarly, you should not market your app on the <span class="nowrap">App Store</span> or offline as including content or services that it does not actually offer (e.g. iOS-based virus and malware scanners). Egregious or repeated behavior is grounds for removal from the Developer Program. We work hard to make the <span class="nowrap">App Store</span> a trustworthy ecosystem and expect our app developers to follow suit; if you’re dishonest, we don’t want to do business with you.</li>
<li id="2.3.7"><strong>2.3.7</strong> Choose a unique app name, assign keywords that accurately describe your app, and don’t try to pack any of your metadata with trademarked terms, popular app names, <span class="insert">pricing information, </span>or other irrelevant phrases just to game the system. App names must be limited to 30 characters and should not include prices, terms, or descriptions that are not the name of the app. App subtitles are a great way to provide additional context for your app; they must follow our standard metadata rules and should not include inappropriate content, reference other apps, or make unverifiable product claims. Apple may modify inappropriate keywords at any time or take other appropriate steps to prevent abuse.</li>
</ul>
</li>
<li data-sidenav="2.5 Software Requirements" id="software-requirements"><span id="2.5"></span><strong>2.5 Software Requirements</strong>
<ul class="no-bullet margin-top-small">
<li id="2.5.16"><strong><span class="insert">2.5.16</span></strong> <span class="nowrap"><span class="insert">App Clips,</span></span><span class="insert"> widgets, extensions, and notifications should be related to the content and functionality of your app. Additionally, all </span><span class="nowrap"><span class="insert">App Clip</span></span><span class="insert"> features and functionality must be included in the main app binary. </span><span class="nowrap"><span class="insert">App Clips</span></span><span class="insert"> cannot contain advertising.</span></li>
</ul>
</li>
<li data-sidenav="3.1 Payments" id="payments"><span id="3.1"></span><strong>3.1 Payments</strong>
<ul class="no-bullet margin-top-small">
<li id="permissible-uses"><span id="3.1.2a"></span><strong>3.1.2(a) Permissible uses:</strong> If you offer an auto-renewing subscription, you must provide ongoing value to the customer, and the subscription period must last at least seven days and be available across all of the user’s devices. While the following list is not exhaustive, examples of appropriate subscriptions include: new game levels; episodic content; multiplayer support; apps that offer consistent, substantive updates; access to large collections of, or continually updated, media content; software as a service (“SAAS”); and cloud support. In addition:
<ul class="disc margin-top-small">
<li>You may offer a single subscription that is shared across your own apps and<span class="delete"> services, but these subscriptions may not extend to third-party apps or</span> services. Games offered in a <span class="insert">streaming </span>game <span class="insert">service </span>subscription must be <span class="delete">owned or exclusively licensed by the developer</span><span class="insert">downloaded directly from the </span><span class="nowrap"><span class="insert">App Store,</span></span><span class="insert"> must be designed to avoid duplicate payment by a subscriber, and should not disadvantage non-subscriber customers.</span></li>
<li><span class="insert"> Subscriptions must work on all of the user’s devices where the app is available. Learn more about </span><a href="/documentation/storekit/in-app_purchase/offering_a_subscription_across_multiple_apps"><span class="insert">sharing a subscription across your apps</span></a><span class="insert">. </span></li>
<li><span class="insert">Apps must not force users to rate the app, review the app, download other apps, or other similar actions in order to access functionality, content, or use of the app.</span></li>
<li><span class="insert">As with all apps, those offering subscriptions should allow a user to get what they’ve paid for without performing additional tasks, such as posting on social media, uploading contacts, checking in to the app a certain number of times, etc. </span></li>
<li><span class="insert">Subscriptions may include consumable credits, gems, in-game currencies, etc., and you may offer subscriptions that include access to discounted consumable goods</span> (e.g. <span class="delete">not part of a game publishing platform). Each game must be downloaded directly from the </span><span class="delete">App Store,</span><span class="delete"> must be designed to avoid duplicate payment by a subscriber, and should not disadvantage non-subscriber customers.</span><span class="delete"> Subscriptions must work on all of the user’s devices where the app is available. Learn more about </span><span class="delete">sharing a subscription across your apps</span><span class="delete">. </span>
<span class="delete">Apps must not force users to rate the app, review the app, download other apps, or other similar actions in order to access functionality, content, or use of the app.</span>
<span class="delete">As with all apps, those offering subscriptions should allow a user to get what they’ve paid for without performing additional tasks, such as posting on social media, uploading contacts, checking in to the app a certain number of times, etc. </span>
<span class="delete">Subscriptions may include consumable credits, gems, in-game currencies, etc., and you may offer subscriptions that include access to discounted consumable goods (e.g. </span>a platinum membership that exposes gem-packs for a reduced price).</li>
<li><span class="insert">Apps that offer auto-renewing music and video subscriptions with prior approval by Apple may also be included in pre-defined bundles with cellular data plans offered in cellular carrier apps.</span></li>
</ul>
</li>
<li data-sidenav="3.1.3 Other Purchase Methods" id="other-purchase-methods"><span id="3.1.3"></span><strong><span class="insert">3.1.3 Other Purchase Methods:</span></strong><span class="insert"> The following apps may use purchase methods other than in-app purchase. Apps in this section cannot, either within the app or through communications sent to points of contact obtained from account registration within the app (like email or text), encourage users to use a purchasing method other than in-app purchase.</span></li>
<li data-sidenav="3.1.3(a) “Reader” Apps" id="reader-apps"><span id="3.1.3a"></span><strong>3.1.3(a) “Reader” Apps:</strong> Apps may allow a user to access previously purchased content or content subscriptions (specifically: magazines, newspapers, books, audio, music, <span class="insert">and </span>video<span class="insert">). Reader apps may offer account creation for free tiers</span>, <span class="delete">access to professional databases, VoIP, cloud storage, and approved services such as classroom</span><span class="insert">and account</span> management <span class="delete">apps), provided that you agree not to directly or indirectly target iOS users to use a purchasing method other than in-app purchase, and your general communications about other purchasing methods are not designed to discourage use of in-app purchase</span><span class="insert">functionality for existing customers</span>.</li>
<li data-sidenav="3.1.3(b) Multiplatform Services" id="multiplatform-services"><span id="3.1.3b"></span><strong>3.1.3(b) Multiplatform Services:</strong> Apps that operate across multiple platforms may allow users to access content, subscriptions, or features they have acquired in your app on other platforms or your web site, including consumable items in <span class="delete">multiplatform</span><span class="insert">multi-platform</span> games, provided those items are also available as in-app purchases within the app.<span class="delete"> You must not</span></li>
<li data-sidenav="3.1.3(c) Enterprise Services" id="enterprise-services"><span id="3.1.3c"></span><strong><span class="insert">3.1.3(c) Enterprise Services:</span></strong><span class="insert"> If your app is only sold</span> directly <span class="delete">or indirectly target iOS users to</span><span class="insert">by you to organizations or groups for their employees or students (for example professional databases and classroom management tools), you may</span> use <span class="delete">a purchasing method other than</span><span class="insert">purchase methods in addition to</span> in-app purchase<span class="insert"> to collect those payments. Consumer</span>, <span class="delete">and your general communications about other purchasing methods</span><span class="insert">single user, or family sales</span> must <span class="delete">not discourage </span>use<span class="delete"> of</span> in-app purchase.</li>
<li data-sidenav="3.1.3(d) Person-to-Person Experiences" id="person-to-person-experiences"><span id="3.1.3d"></span><strong><span class="insert">3.1.3(d) Person-to-Person Experiences:</span></strong><span class="insert"> If your app enables the purchase of realtime person-to-person experiences between two individuals (for example tutoring students, medical consultations, real estate tours, or fitness training), you may use purchase methods other than in-app purchase to collect those payments. One-to-few and one-to-many realtime experiences must use in-app purchase.</span></li>
<li data-sidenav="3.1.3(e) Goods and Services Outside of the App" id="goods-and-services-outside-of-the-app"><span id="3.1.3e"></span><strong><span class="insert">3.1.3(e) Goods and Services Outside of the App:</span></strong><span class="insert"> If your app enables people to purchase physical goods or services that will be consumed outside of the app, you must use purchase methods other than in-app purchase to collect those payments, such as </span><span class="nowrap"><span class="insert">Apple Pay</span></span><span class="insert"> or traditional credit card entry.</span></li>
<li data-sidenav="3.1.3(f) Free Stand-alone Apps" id="free-stand-alone-apps"><span id="3.1.3f"></span><strong><span class="insert">3.1.3(f) Free Stand-alone Apps:</span></strong>
<span class="insert"> Free apps acting as a stand-alone companion to a paid web based tool (eg. VOIP, Cloud Storage, Email Services, Web Hosting) do not need to use in-app purchase, provided there is no purchasing inside the app, or calls to action for purchase outside of the app.</span></li>
<li data-sidenav="3.1.5 Cryptocurrencies" id="cryptocurrencies"><span id="3.1.5"></span><strong>3.1.5<span class="delete">(a) Goods and Services Outside of the App:</span></strong>
<span class="delete"> If your app enables people to purchase goods or services that will be consumed outside of the app, you must use purchase methods other than in-app purchase to collect those payments, such as Apple Pay or traditional credit card entry.</span></li>
<li data-sidenav="3.1.5 Cryptocurrencies" id="cryptocurrencies"><strong><span class="delete">3.1.5(b)</span> Cryptocurrencies:</strong>
</li>
<li data-sidenav="3.1.7 Advertising" id="advertising"><span id="3.1.7"></span><strong>3.1.7 Advertising:</strong> <span class="insert">Display advertising should be limited to your main app executable, and should not be included in extensions, </span><span class="nowrap"><span class="insert">App Clips,</span></span><span class="insert"> widgets, notifications, keyboards, watchOS apps, etc. </span>Ads displayed in an app must be appropriate for the app’s age rating, allow the user to see all information used to target them for that ad (without requiring the user to leave the app), and may not engage in targeted or behavioral advertising based on sensitive user data such as health/medical data (e.g. from the HealthKit APIs), school and classroom data (e.g. from ClassKit), or from kids (e.g. from apps in the Kids Category), etc. Interstitial ads or ads that interrupt or block the user experience must clearly indicate that they are an ad, must not manipulate or trick users into tapping into them, and must provide easily accessible and visible close/skip buttons large enough for people to easily dismiss the ad.</li>
</ul>
</li>
<li data-sidenav="3.2 Other Business Model Issues" id="other-business-model-issues"><span id="3.2"></span><strong>3.2 Other Business Model Issues</strong>
<ul class="no-bullet margin-top-small">
<li data-sidenav="3.2.2 Unacceptable" id="unacceptable"><span id="3.2.2"></span><strong>3.2.2 Unacceptable</strong>
<ul class="no-bullet margin-top-small">
<li><strong>(vi)</strong> Apps should allow a user to get what they’ve paid for without performing additional tasks, such as posting on social media, uploading contacts, checking in to the app a certain number of times, etc. Apps should not require users to rate the app, review the app, watch videos, download other apps, tap on advertisements, <span class="insert">enable tracking, </span>or take other similar actions in order to access functionality, content, use the app, or receive monetary or other compensation, including but not limited to gift cards and codes.</li>
<li><strong><span class="insert">(x)</span></strong><span class="insert"> Apps offering personal loans must clearly and conspicuously disclose all loan terms, including but not limited to equivalent maximum Annual Percentage Rate (APR) and payment due date. Apps may not charge a maximum APR higher than 36%, including costs and fees, and may not require repayment in full in 60 days or less.</span></li>
</ul>
</li>
</ul>
</li>
<li data-sidenav="4.5 Apple Sites and Services" id="apple-sites-and-services"><span id="4.5"></span><strong>4.5 Apple Sites and Services</strong>
<ul class="no-bullet margin-top-small">
<li id="4.5.2"><strong>4.5.2</strong> Apple Music
<ul class="no-bullet margin-top-small">
<li><strong>(i)</strong> <span class="delete">The </span>MusicKit <span class="delete">APIs let customers access</span><span class="insert">on iOS lets users play </span><span class="nowrap"><span class="insert">Apple Music</span></span><span class="insert"> and</span> their <span class="delete">subscription while</span><span class="insert">local music library natively from your apps and games. When a user provides permission to their </span><span class="nowrap"><span class="insert">Apple Music</span></span><span class="insert"> account, your app can create playlists, add songs to their library, and play any of the millions of songs in the </span><span class="nowrap"><span class="insert">Apple Music</span></span><span class="insert"> catalog. Users must initiate the playback of an </span><span class="nowrap"><span class="insert">Apple Music</span></span><span class="insert"> stream and be able to navigate</span> using <span class="delete">your app. They are intended for simple music playback by Apple Music subscribers. Users must initiate the playback of an Apple Music stream and be able to navigate using </span>standard media controls such as “play,” “pause,” and “skip.” Moreover, your app may not require payment or indirectly monetize access to the <span class="nowrap">Apple Music</span> service (e.g. in-app purchase, advertising, requesting user info, etc.). Do not download, upload, or enable sharing of music files sourced from the MusicKit APIs, except as explicitly permitted in <a href="/musickit/">MusicKit</a> documentation. </li>
</ul>
</ul>
</li>
<li data-sidenav="4.9 Streaming games" id="streaming-games"><span id="4.9"></span><strong><span class="insert">4.9 Streaming games</span></strong>
<p><span class="insert">Streaming games are permitted so long as they adhere to all guidelines — for example, each game update must be submitted for review, developers must provide appropriate metadata for search, games must use in-app purchase to unlock features or functionality, etc. Of course, there is always the open Internet and web browser apps to reach all users outside of the </span><span class="nowrap"><span class="insert">App Store.</span></span></p>
<ul class="no-bullet margin-top-small">
<li id="4.9.1"><strong><span class="insert">4.9.1</span></strong><span class="insert"> Each streaming game must be submitted to the </span><span class="nowrap"><span class="insert">App Store</span></span><span class="insert"> as an individual app so that it has an </span><span class="nowrap"><span class="insert">App Store</span></span><span class="insert"> product page, appears in charts and search, has user ratings and review, can be managed with ScreenTime and other parental control apps, appears on the user’s device, etc.</span></li>
<li id="4.9.2"><strong><span class="insert">4.9.2</span></strong><span class="insert"> Streaming game services may offer a catalog app on the </span><span class="nowrap"><span class="insert">App Store</span></span><span class="insert"> to help users sign up for the service and find the games on the </span><span class="nowrap"><span class="insert">App Store,</span></span><span class="insert"> provided that the app adheres to all guidelines, including offering users the option to pay for a subscription with in-app purchase and use Sign in with Apple. All the games included in the catalog app must link to an individual </span><span class="nowrap"><span class="insert">App Store</span></span><span class="insert"> product page.</span></li>
</ul>
</li>
<li data-sidenav="5.1 Privacy" id="privacy"><span id="5.1"></span><strong>5.1 Privacy</strong>
<ul class="no-bullet margin-top-small">
<li data-sidenav="5.1.2 Data Use and Sharing" id="data-use-and-sharing"><span id="5.1.2"></span><strong>5.1.2 Data Use and Sharing</strong>
<ul class="no-bullet margin-top-small">
<li><strong>(vi) </strong>Data gathered from the HomeKit API, HealthKit, <span class="delete">Consumer</span><span class="insert">Clinical</span> Health Records API, MovementDisorder APIs, ClassKit or from depth and/or facial mapping tools (e.g. ARKit, Camera APIs, or Photo APIs) may not be used for marketing, advertising or use-based data mining, including by third parties. Learn more about best practices for implementing <a href="/documentation/callkit">CallKit</a>, <a href="/documentation/healthkit">HealthKit</a>, <a href="/documentation/classkit">ClassKit</a>, and <a href="/documentation/arkit">ARKit</a>.</li>
</ul>
</li>
</ul>
</li>
<h3 data-sidenav id="after-you-submit">After You Submit</h3>
<p>Once you’ve submitted your app and metadata in <span class="nowrap">App Store Connect</span> and you’re in the review process, here are some things to keep in mind:</p>
<ul class="disc top-level">
<li><strong>Rejections</strong>: Our goal is to apply these guidelines fairly and consistently, but nobody’s perfect. If your app has been rejected and you have questions or would like to provide additional information, please use the Resolution Center to communicate directly with the <span class="nowrap">App Review</span> team. This may help get your app on the store, and it can help us improve the <span class="nowrap">App Review</span> process or identify a need for clarity in our policies. If you still disagree with the outcome, <span class="insert">or would like to suggest a change to the guideline itself, </span>please <a href="/contact/app-store/?topic=appeal">submit an appeal</a>.</li>
<li><strong><span class="insert">Bug Fix Submissions</span></strong><span class="insert">: For apps that are already on the </span><span class="nowrap"><span class="insert">App Store,</span></span><span class="insert"> bug fixes will no longer be delayed over guideline violations except for those related to legal issues. If your app has been rejected, and qualifies for this process, please use the Resolution Center to communicate directly with the </span><span class="nowrap"><span class="insert">App Review</span></span><span class="insert"> team indicating that you would like to take advantage of this process and plan to address the issue in your next submission.</span></li>
</ul>
</section></p></article><article class="article intro"><header><p class="date"><span>March 04, 2020</span></p><h2><a href="/articles/2020-03-04-push-notifications-marketing-and-more/">Push Notifications for marketing purposes, a 'Sign in with Apple' clarification and more</a></h2></header><section class="content"><p>Apple has updated the <a href="https://developer.apple.com/app-store/review/guidelines/">App Store Review Guidelines</a> with changes to rules related to <a href="https://developer.apple.com/news/?id=03042020a">replies to reviews, spam, push notifications, <em>Sign in with Apple</em>, data collection and storage, mobile device management, and more</a>.</br></br></p>
<p>Specifically, Apple now allows for marketing Push Notifications if the user has opted in to these and the guidelines related to <em>Sign in with Apple</em> are now clearer, Apple having removed “exclusively”, which was used in a way that made it sound like you were only required to offer <em>Sign in with Apple</em> if you exclusively used third-party login systems, which is not the case.</br></br></p>
<p>The complete changes can be seen below:</p>
</section><p class="changes"><section class="apple">
<strong>1.1 Objectionable Content</strong>
<p>
Apps should not include content that is offensive, insensitive, upsetting,
intended to disgust, in exceptionally poor taste, or just plain creepy.
Examples of such content include:
</p>
<ul class="no-bullet margin-top-small">
<li id="1.1.1">
<strong>1.1.1</strong> Defamatory, discriminatory, or mean-spirited
content, including references or commentary about religion, race, sexual
orientation, gender, national/ethnic origin, or other targeted groups,
particularly if the app is likely to humiliate, intimidate, or
<span class="delete">place</span><span class="insert">harm</span> a
targeted individual or group<span class="delete"> in harm’s way</span>.
Professional political satirists and humorists are generally exempt from
this requirement.
</li>
<li>
<span class="delete"><strong>1.1.7</strong> App Store Reviews:</span>
</li>
<li>
<span class="delete"
>App Store customer reviews can be an integral part of the app
experience, so you should treat customers with respect when responding
to their comments. Keep your responses targeted to the user’s comments
and do not include personal information, spam, or marketing in your
response.
</span>
</li>
<li>
<span class="delete"
>Use the provided API to prompt users to review your app; this
functionality allows customers to provide an App Store rating and review
without the inconvenience of leaving your app, and we will disallow
custom review prompts.</span
>
</li>
</ul>
<strong>1.2 User Generated Content</strong>
<p>
Apps with user-generated content or services that end up being used
primarily for pornographic content,
<span class="insert">Chatroulette-style experiences, </span>objectification
of real people (e.g. “hot-or-not” voting), making physical threats, or
bullying do not belong on the App Store and may be removed without notice.
If your app includes user-generated content from a web-based service, it may
display incidental mature “NSFW” content, provided that the content is
hidden by default and only displayed when the user turns it on via your
website.
</p>
<strong>3.1 Payments</strong>
<ul class="no-bullet margin-top-small">
<li
data-sidenav="3.1.3(b) Multiplatform Services"
id="multiplatform-services"
>
<span id="3.1.3b"></span
><strong>3.1.3(b) Multiplatform Services:</strong> Apps that operate
across multiple platforms may allow users to access content,
subscriptions, or features they have acquired
<span class="delete">elsewhere</span
><span class="insert"
>in your app on other platforms or your web site</span
>, including consumable items in multiplatform games, provided those items
are also available as in-app purchases within the app. You must not
directly or indirectly target iOS users to use a purchasing method other
than in-app purchase, and your general communications about other
purchasing methods must not discourage use of in-app purchase.
</li>
</ul>
<strong>4.2 Minimum Functionality</strong>
<ul class="no-bullet margin-top-small">
<li id="4.2.3">
<strong>4.2.3</strong>
<ul class="disc margin-top-small">
<li>
(iii) If your app needs to download additional resources, disclose the
size of the download and prompt users before doing so.<span
class="delete"
>
Existing apps must comply with this guideline in any update
submitted after January 1, 2019.</span
>
</li>
</ul>
</li>
</ul>
<strong>4.3 Spam</strong>
<p>
Don’t create multiple Bundle IDs of the same app. If your app has
different versions for specific locations, sports teams, universities, etc.,
consider submitting a single app and provide the variations using in-app
purchase. Also avoid piling on to a category that is already saturated; the
App Store has enough fart, burp, flashlight,
<span class="insert">fortune telling, dating, </span>and Kama Sutra apps,
etc. already.
<span class="insert"
>We will reject these apps unless they provide a unique, high-quality
experience. </span
>Spamming the store may lead to your removal from the Developer Program.
</p>
<strong>4.5 Apple Sites and Services</strong>
<ul class="no-bullet margin-top-small">
<li id="4.5.4">
<strong>4.5.4</strong> Push Notifications must not be required for the app
to function, and should not be used
<span class="delete"
>for advertising, promotions, or direct marketing purposes or </span
>to send sensitive personal or confidential information.
<span class="insert"
>Push Notifications should not be used for promotions or direct
marketing purposes unless customers have explicitly opted in to receive
them via consent language displayed in your app’s UI, and you provide a
method in your app for a user to opt out from receiving such messages. </span
>Abuse of these services may result in revocation of your privileges.
</li>
</ul>
<strong>4.7 HTML5 Games, Bots, etc.</strong>
<p>
Apps may contain or run code that is not embedded in the binary (e.g.
HTML5-based games, bots, etc.), as long as code distribution isn’t the main
purpose of the app, the code is not offered in a store or store-like
interface, and provided that the software (1) is free or purchased using
in-app purchase; (2) only uses capabilities available in a standard WebKit
view (e.g. it must open and run natively in Safari without modifications or
additional software); your app must use WebKit and JavaScript Core to run
third-party software and should not attempt to extend or expose native
platform APIs to third-party software; (3) is offered by developers that
have joined the <span class="nowrap">Apple Developer</span> Program and
signed the <span class="nowrap">Apple Developer</span> Program License
Agreement; (4) does not provide access to real money gaming, lotteries, or
charitable donations; (5) adheres to the terms of these App Review
Guidelines (e.g. does not include objectionable content); and (6) does not
<span class="delete">support</span><span class="insert">offer</span> digital
<span class="delete">commerce</span
><span class="insert">goods or services for sale</span>. Upon request, you
must provide an index of software and metadata available in your app. It
must include <span class="nowrap">Apple Developer</span> Program Team IDs
for the providers of the software along with a URL which App Review can use
to confirm that the software complies with the requirements above.
</p>
<strong>4.8 Sign in with Apple</strong>
<p>
Apps that <span class="delete">exclusively </span>use a third-party or
social login service (such as Facebook Login, Google Sign-In, Sign in with
Twitter, Sign In with LinkedIn, Login with Amazon, or WeChat Login) to set
up or authenticate the user’s primary account with the app must also offer
Sign in with Apple as an equivalent option. A user’s primary account is the
account they establish with your app for the purposes of identifying
themselves, signing in, and accessing your features and associated services.
</p>
</section>
</p></article><article class="article intro"><header><p class="date"><span>September 14, 2019</span></p><h2><a href="/articles/2019-09-14-kids-apps-ads-analytics-and-sign-in-with-apple/">Third-party analytics, ads in kids apps and 'Sign in with Apple'</a></h2></header><section class="content"><p>Apple has updated the <a href="https://developer.apple.com/app-store/review/guidelines/">App Store Review Guidelines</a> with changes to rules regarding <a href="https://developer.apple.com/news/?id=091202019a">ads, data collection and privacy in kids apps</a>, and <a href="https://developer.apple.com/news/?id=09122019b">new rules about <em>Sign in with Apple</em></a>.<br/><br/></p>
<p>Specifically, it is now, in limited cases, permissible to show ads and include third-party analytics in kids apps and creators of kids apps must now comply with all applicable children’s privacy statutes. Newly submitted kids apps must follow these guidelines immediately, while existing apps will have until March 3, 2020 to be fully compliant. Regarding <em>Sign in with Apple</em>, the guidelines now state that any apps that use a third-party login service, e.g. Facebook or Google, must also offer <em>Sign in with Apple</em>.<br/><br/></p>
<p>The complete changes can be seen below:</p>
</section><p class="changes"><section class="apple">
<strong>1.3 Kids Category</strong>
<p>
<span class="insert">You must comply with applicable privacy laws around the world relating to the collection of data from children online. Be sure to review the </span><a href="#privacy"><span class="insert">Privacy section</span></a
><span class="insert"> of these guidelines for more information. In addition, Kids Category apps may not send personally identifiable information or device information to third parties. </span>Apps in the Kids Category <span class="delete">may</span><span class="insert">should</span> not include third-party <span class="insert">analytics or third-party </span>advertising<span class="delete"> or</span><span class="insert">. This provides a safer experience for kids. In limited cases, third-party</span> analytics<span class="insert"> may be permitted provided that the services do not collect or transmit the IDFA or any identifiable information about children (such as name, date of birth, email address), their location, or their devices</span>. <span class="delete">You should</span
><span class="insert">This includes any device, network, or other information that could be used directly or combined with other information to identify users and their devices. Third-party contextual advertising may</span> also <span class="delete">pay particular attention to privacy laws around the world relating to the collection of data from children online. Be sure to</span><span class="insert">be permitted in limited cases provided that the services have publicly documented practices and policies for Kids Category apps that include human</span> review <span class="delete">the </span><span class="delete">Privacy section</span><span class="delete"> of these guidelines for more information</span><span class="insert">of ad creatives for age appropriateness</span>.
</p>
<strong>4.2 Minimum Functionality</strong>
<p>
Your app should include features, content, and UI that elevate it beyond a repackaged website. If your app is not particularly useful, unique, or “app-like,” it doesn’t belong on the <span class="nowrap"><span class="insert">App Store.</span></span
><span class="insert"> If your </span>App<span class="insert"> doesn’t provide some sort of lasting entertainment value, it may not be accepted. Apps that are simply a song or movie should be submitted to the iTunes</span> Store.<span class="delete"> If your App doesn’t provide some sort of lasting entertainment value, it may not be accepted.</span> Apps that are simply a <span class="delete">song or movie</span><span class="insert">book or game guide</span> should be submitted to the <span class="delete">iTunes Store. Apps that are simply a book or game guide should be submitted to the </span>Apple Books Store.
</p>
<strong><span class="insert">4.8 Sign in with Apple</span></strong>
<p><span class="insert">Apps that exclusively use a third-party or social login service (such as Facebook Login, Google Sign-In, Sign in with Twitter, Sign In with LinkedIn, Login with Amazon, or WeChat Login) to set up or authenticate the user’s primary account with the app must also offer Sign in with Apple as an equivalent option. A user’s primary account is the account they establish with your app for the purposes of identifying themselves, signing in, and accessing your features and associated services.</span></p>
<p><span class="insert">Sign in with Apple is not required if: </span></p>
<ul class="disc margin-top-small">
<li><span class="insert">Your app exclusively uses your company’s own account setup and sign-in systems.</span></li>
<li><span class="insert">Your app is an education, enterprise, or business app that requires the user to sign in with an existing education or enterprise account.</span></li>
<li><span class="insert">Your app uses a government or industry-backed citizen identification system or electronic ID to authenticate users.</span></li>
<li><span class="insert">Your app is a client for a specific third-party service and users are required to sign in to their mail, social media, or other third-party account directly to access their content.</span></li>
</ul>
<strong>5.1 Privacy</strong>
<ul class="no-bullet margin-top-small">
<li data-sidenav="5.1.1 Data Collection and Storage" id="data-collection-and-storage">
<span id="5.1.1"></span><strong>5.1.1 Data Collection and Storage</strong>
<ul class="no-bullet margin-top-small">
<li>
<strong>(i) Privacy Policies: </strong>
<ul class="disc">
<li>Confirm that any<span class="insert"> third party with whom an app shares user data (in compliance with these Guidelines) — such as analytics tools, advertising networks and</span> third-party <span class="delete">with whom an app shares user data (in compliance with these Guidelines) — such as analytics tools, advertising networks and third-party </span>SDKs, as well as any parent, subsidiary or other related entities that will have access to user data — will provide the same or equal protection of user data as stated in the app’s privacy policy and required by these Guidelines.</li>
</ul>
</li>
</ul>
</li>
</ul>
<strong>5.1.4 Kids</strong>
<p>For many reasons, it is critical to use care when dealing with personal data from kids, and we encourage you to carefully review all the requirements for complying with laws like the Children’s Online Privacy Protection Act (“COPPA”), the European Union’s General Data Protection Regulation (“GDPR”), and any <span class="delete">international or local equivalents</span><span class="insert">other applicable regulations or laws</span>.</p>
<p>Apps may ask for birthdate and parental contact information only for the purpose of complying with these statutes, but must include some useful functionality or entertainment value regardless of a person’s age.</p>
<p>
Apps intended <span class="insert">primarily </span>for kids <span class="delete">may</span><span class="insert">should</span> not include third-party <span class="insert">analytics or third-party </span>advertising<span class="delete"> or</span><span class="insert">. This provides a safer experience for kids. In limited cases, third-party</span> analytics<span class="insert"> and third-party advertising may be permitted provided that the services adhere to the same terms set forth in </span><a href="#1.3"><span class="insert">Guideline 1.3</span></a
>.
</p>
<p>Moreover, apps in the Kids Category or those that collect, transmit, or have the capability to share personal information (e.g. name, address, email, location, photos, videos, drawings, the ability to chat, other personal data, or persistent identifiers used in combination with any of the above) from a minor must include a privacy policy and must comply with all applicable children’s privacy statutes. For the sake of clarity, the <a href="#kids-category">parental gate requirement</a> for the Kid’s Category is generally not the same as securing parental consent to collect personal data under these privacy statutes.<span class="delete"> Collecting and transmitting data to third parties from apps in</span></p>
<p>
<span class="insert">As a reminder, </span><a href="#2.3.8"><span class="insert">Guideline 2.3.8</span></a
><span class="insert"> requires that use of terms like “For Kids” and “For Children” in app metadata is reserved for</span> the Kids <span class="delete">category is</span><span class="insert">Category. Apps</span> not <span class="delete">allowed</span><span class="insert">in the Kids Category cannot include any terms in app name, subtitle, icon, screenshots or description that imply the main audience for the app is children</span>.
</p>
</section>
</p></article><article class="article intro"><header><p class="date"><span>June 06, 2019</span></p><h2><a href="/articles/2019-06-06-kids-privacy-no-gambling-vpn-changes-and-more/">Restrictions to tracking of data in VPN apps and apps for kids, ban of HTML5 apps supporting digital commerce, and more</a></h2></header><section class="content"><p>Apple has updated the <a href="https://developer.apple.com/app-store/review/guidelines/">App Store Review Guidelines</a> with some significant changes, primarily focusing on rules surrounding data collection. Here’s <a href="https://developer.apple.com/news/?id=06032019j">Apple’s own summary</a>:</p>
<ul>
<li><strong>Guidelines 1.3 and 5.1.4.</strong> In order to help keep kids’ data private, apps in the kids category and apps intended for kids cannot include third-party advertising or analytics software and may not transmit data to third parties. This guideline is now enforced for new apps. Existing apps must follow this guideline by September 3, 2019.</li>
<li><strong>Guideline 4.7.</strong> <span class="caps">HTML5</span> games distributed in apps may not provide access to real money gaming, lotteries, or charitable donations, and may not support digital commerce. This functionality is only appropriate for code that’s embedded in the binary and can be reviewed by Apple. This guideline is now enforced for new apps. Existing apps must follow this guideline by September 3, 2019.</li>
<li><strong>Guideline 5.4.</strong> Because <span class="caps">VPN</span> provides access to sensitive data, VPN apps may not sell, use, or disclose to third parties any data for any purpose, and must commit to this in their privacy policy. Certain types of apps — such as those for parental control, content blocking, and security — from approved providers may use the NEVPNManager API.</li>
<li><strong>Guideline 5.5. (New)</strong> Because <span class="caps">MDM</span> provides access to sensitive data, MDM apps must request the mobile device management capability, and may only be offered by commercial enterprises, such as business organizations, educational institutions, or government agencies, and, in limited cases, companies utilizing MDM for parental controls. MDM apps may not sell, use, or disclose to third parties any data for any purpose, and must commit to this in their privacy policy.</li>
<li><strong>Guideline 5.1.3(i).</strong> Apps may use a user’s health or fitness data to provide a benefit directly to that user, such as a reduced insurance premium, if the app is submitted by the entity providing the benefit and the data is not shared with a third party. The developer must also disclose to the user the specific health data collected from the device.</li>
<li><strong>Guideline 5.1.1(viii) (New).</strong> Apps that compile information from any source that is not directly from the user or without the user’s explicit consent, even public databases, are not permitted on the App Store.</li>
<li><strong>Guideline 5.1.1(ii).</strong> Apps must get consent for data collection, even if the data is considered anonymous at the time of or immediately following collection.</li>
<li><strong>Guideline 1.1.3.</strong> Apps may not facilitate purchase of ammunition.</li>
<li><strong>Guideline 4.2.7.</strong> Remote desktop clients now include game consoles owned by the user. Software appearing in the client must be fully executed on the host device.
Demo videos of app functionality that is geo-locked or otherwise restricted are not accepted. Developers must provide a fully functional app for review.</li>
</ul>
<p>The full changes can be seen below.</p>
</section><p class="changes"><section class="apple">
<div class="section-content">
<div class="row">
<div class="column large-10 large-centered medium-12 small-12 padding-bottom">
<h3 class="typography-subsection-headline">Introduction</h3>
<p>The guiding principle of the <span class="nowrap">App Store</span> is simple - we want to provide a safe experience for users to get apps and a great opportunity for all developers to be successful. <span class="insert">We do this by offering a highly curated </span><span class="nowrap"><span class="insert">App Store</span></span><span class="insert"> where every app is reviewed by experts and an editorial team helps users discover new apps every day. For everything else there is always the open Internet. If the </span><span class="nowrap"><span class="insert">App Store</span></span><span class="insert"> model and guidelines are not best for your app or business idea that’s okay, we provide Safari for a great web experience too.</span></p>
<p>On the following pages you will find <span class="insert">our latest </span>guidelines arranged into five clear sections: Safety, Performance, Business, Design, and Legal. <span class="insert">The </span><span class="nowrap"><span class="insert">App Store</span></span><span class="insert"> is always changing and improving to keep up with the needs of our customers and our products. Your apps should change and improve as well in order to stay on the </span><span class="nowrap"><span class="insert">App Store.</span></span></p>
<p>A few other points to keep in mind:</p>
<ul class="disc top-level">
<li>If you attempt to cheat the system (for example, by trying to trick the review process, steal user data, copy another developer’s work, <span class="delete">or </span>manipulate ratings<span class="insert"> or </span><span class="nowrap"><span class="insert">App Store</span></span><span class="insert"> discovery</span>) your apps will be removed from the store and you will be expelled from the Developer Program.</li>
<li><span class="insert">Some features and technologies that are not generally available to developers may be offered as an entitlement for limited use cases. For example, we offer entitlements for CarPlay Audio, HyperVisor, and Privileged File Operations. Review our documentation on developer.apple.com to learn more about entitlements.</span></li>
</ul>
</div>
</div>
</div>
</section>
<section class="apple">
<h3 class="typography-subsection-headline" id="before-you-submit">Before You Submit</h3>
<p>Make sure you:</p>
<ul class="disc top-level">
<li>Include detailed explanations of non-obvious features and in-app purchases in the App Review notes, including supporting documentation where appropriate.<span class="delete"> If we’re not able to access part of your app because it’s geo-locked or otherwise restricted, provide a link to a video of the functionality</span></li>
</ul>
</section>
<section class="apple" id="guidelines">
<strong>1.1 Objectionable Content</strong>
<p>Apps should not include content that is offensive, insensitive, upsetting, intended to disgust, <span class="delete">or </span>in exceptionally poor taste<span class="insert">, or just plain creepy</span>. Examples of such content include:</p>
<ul class="no-bullet margin-top-small">
<li id="1.1.3"><strong>1.1.3</strong> Depictions that encourage illegal or reckless use of weapons and dangerous objects, or facilitate the purchase of firearms<span class="insert"> or ammunition</span>.</li>
</ul>
</li>
<strong>1.3 Kids Category</strong>
<p>Apps in the Kids Category may not include <span class="delete">behavioral</span><span class="insert">third-party</span> advertising <span class="delete">(e</span><span class="insert">or analytics</span>.<span class="delete">g. the advertiser may not serve ads based on the user’s activity), and any contextual ads must be appropriate for young audiences.</span> You should also pay particular attention to privacy laws around the world relating to the collection of data from children online. Be sure to review the <a href="#privacy">Privacy section</a> of these guidelines for more information.</p>
<strong>1.4 Physical Harm</strong>
<p>If your app behaves in a way that risks physical harm, we may reject it. For example:</p>
<ul class="no-bullet margin-top-small">
<li id="1.4.3"><strong>1.4.3</strong> Apps that encourage consumption of tobacco<span class="insert"> and vape</span> products, illegal drugs, or excessive amounts of alcohol are not permitted on the <span class="nowrap">App Store.</span> Apps that encourage minors to consume any of these substances will be rejected. Facilitating the sale of marijuana, tobacco, or controlled substances (except for licensed pharmacies) isn’t allowed.</li>
<li id="1.4.5"><strong>1.4.5</strong> Apps should not urge customers to <span class="insert">participate in activities (like bets, challenges, etc.) or </span>use their devices in a way that <span class="delete">contradicts safety documentation for Apple hardware, risking damage to the device or</span><span class="insert">risks</span> physical harm to <span class="delete">people. For example, apps should not encourage placing the device under a mattress or pillow while charging or perform excessive write cycles to the solid state drive. Review </span><span class="delete">device documentation</span><span class="insert">themselves or others</span>.</li>
</ul>
</section>
<section class="apple">
<strong>2.3 Accurate Metadata</strong>
<ul class="no-bullet margin-top-small">
<li id="2.3.10"><strong>2.3.10</strong> Make sure your app is focused on the iOS, Mac, <span class="nowrap">Apple TV<span class="delete"> or </span></span><span class="insert"> or </span><span class="nowrap">Apple Watch</span> experience, and don’t include names, icons, or imagery of other mobile platforms in your app or metadata, unless there is specific, approved interactive functionality.<span class="insert"> Make sure your app metadata is focused on the app itself and its experience. Don’t include irrelevant information, including but not limited to information about Apple or the development process.</span></li>
</ul>
</li>
<strong>2.4 Hardware Compatibility</strong>
<ul class="no-bullet margin-top-small">
<li id="2.4.2"><strong>2.4.2</strong> Design your app to use power efficiently<span class="insert"> and be used in a way that does not risk damage to the device</span>. Apps should not rapidly drain battery, generate excessive heat, or put unnecessary strain on device resources. <span class="insert">For example, apps should not encourage placing the device under a mattress or pillow while charging or perform excessive write cycles to the solid state drive. </span>Apps, including any third <span class="insert">-</span>party advertisements displayed within them, may not run unrelated background processes, such as cryptocurrency mining.</li>
</ul>
<strong>2.5 Software Requirements</strong>
<ul class="no-bullet margin-top-small">
<li id="2.5.5"><strong>2.5.5</strong> <span class="delete">We will be reviewing on an</span><span class="insert">Apps must be fully functional on</span> IPv6<span class="delete"> network, so if your app isn’t compatible with the IPv6 addressing, it may fail during review</span><span class="insert">-only networks</span>.</li>
<li id="2.5.14"><strong>2.5.14 </strong> Apps must request explicit user consent and provide a clear visual <span class="insert">and/or audible </span>indication when recording, logging, or otherwise making a record of user activity. This includes any use of the device camera, microphone, <span class="insert">screen recordings, </span>or other user inputs.</li>
</ul>
</section>
<section class="apple">
<strong>3.1 Payments</strong>
<ul class="no-bullet margin-top-small">
<li id="permissible-uses"><span id="3.1.2a"></span><strong>3.1.2(a) Permissible uses:</strong>
<ul class="disc margin-top-small">
<li>Apps that attempt to <span class="insert">scam users will be removed from the </span><span class="nowrap"><span class="insert">App Store.</span></span><span class="insert"> This includes apps that attempt to </span>trick users into purchasing a subscription under false pretenses or engage in bait-and-switch <span class="insert">and scam </span>practices will be removed from the <span class="nowrap">App Store</span> and you may be removed from the <span class="nowrap">Apple Developer</span> Program. Learn more about <a href="/web/20190606000009/https://developer.apple.com/app-store/subscriptions/">Subscription Free Trials</a>.</li>
</ul>
</li>
</ul>
</li>
<strong>3.2 Other Business Model Issues</strong>
<ul class="no-bullet margin-top-small">
<li id="unacceptable"><span id="3.2.2"></span><strong>3.2.2 Unacceptable</strong>
<ul class="no-bullet margin-top-small">
<li><strong>(vi)</strong> Apps should allow a user to get what they’ve paid for without performing additional tasks, such as posting on social media, uploading contacts, checking in to the app a certain number of times, etc. Apps should not require users to rate the app, review the app, watch videos, download other apps, tap on advertisements, or take other similar actions in order to access functionality, content, use the app, or receive monetary or other compensation<span class="insert">, including but not limited to gift cards and codes</span>.</li>
</ul>
</li>
</ul>
</section>
<section class="apple">
<strong>4.2 Minimum Functionality</strong>
<p>Your app should include features, content, and UI that elevate it beyond a repackaged website. If your app is not particularly useful, unique, or “app-like,” it doesn’t belong on the <span class="nowrap">App Store.</span> If your App <span class="delete">doesn't</span><span class="insert">doesn’t</span> provide some sort of lasting entertainment value, <span class="delete">or is just plain creepy, </span>it may not be accepted. Apps that are simply a song or movie should be submitted to the iTunes Store. Apps that are simply a book or game guide should be submitted to the <span class="delete">iBooks</span><span class="insert">Apple Books</span> Store.</p>
<ul class="no-bullet margin-top-small">
<li id="4.2.7"><strong>4.2.7 Remote <span class="delete">Application Mirroring:</span><span class="insert">Desktop Clients:</span></strong>
<ul class="disc margin-top-small">
<li>(a) The <span class="insert">app must only connect to a user-owned </span>host device <span class="insert">that </span>is a personal computer <span class="insert">or dedicated game console </span>owned by the user, and both the host <span class="insert">device </span>and client must be connected on a local and LAN-based network.</li>
<li>(b) Any software or services appearing in the client are fully <span class="delete">rendered on the screen of</span><span class="insert">executed on</span> the host device, <span class="insert">rendered on the screen of the host device, </span>and may not use APIs or platform features beyond what is required to stream the Remote Desktop<span class="insert">.</span></li>
<li><span class="insert">(e) Thin clients for cloud-based apps are not appropriate for the </span><span class="nowrap"><span class="insert">App Store.</span></span></li>
</ul>
</li>
</ul>
</li>
<strong>4.3 Spam</strong><p>Don’t create multiple Bundle IDs of the same app. If your app has different versions for specific locations, sports teams, universities, etc., consider submitting a single app and provide the variations using in-app purchase. Also avoid piling on to a category that is already saturated; the <span class="nowrap">App Store</span> has enough fart, burp, flashlight, and Kama Sutra apps<span class="insert">, etc.</span> already. Spamming the store may lead to your removal from the Developer Program.</p>
<strong>4.7 HTML5 Games, Bots, etc. </strong><p>Apps may contain or run code that is not embedded in the binary (e.g. HTML5-based games, bots, etc.), as long as code distribution isn’t the main purpose of the app, the code is not offered in a store or store-like interface, and provided that the software (1) is free or purchased using in-app purchase; (2) only uses capabilities available in a standard WebKit view (e.g. it must open and run natively in Safari without modifications or additional software); your app must use WebKit and JavaScript Core to run third <span class="insert">-</span>party software and should not attempt to extend or expose native platform APIs to third <span class="insert">-</span>party software; (3) is offered by developers that have joined the <span class="nowrap">Apple Developer</span> Program and signed the <span class="nowrap">Apple Developer</span> Program License Agreement;<span class="delete"> and</span> (4) <span class="insert">does not provide access to real money gaming, lotteries, or charitable donations; (5) </span>adheres to the terms of these App Review Guidelines (e.g. does not include objectionable content)<span class="insert">; and (6) does not support digital commerce</span>. Upon request, you must provide an index of software and metadata available in your app. It must include <span class="nowrap">Apple Developer</span> Program Team IDs for the providers of the software along with a URL which App Review can use to confirm that the software complies with the requirements above.</p>
</ul>
</section>
<section class="apple">
<strong>5.1 Privacy</strong>
<ul class="no-bullet margin-top-small">
<li id="data-collection-and-storage"><span id="5.1.1"></span><strong>5.1.1 Data Collection and Storage</strong>
<ul class="no-bullet margin-top-small">
<li><strong>(ii) Permission </strong>Apps that collect user or usage data must secure user consent for the<span class="insert"> collection, even if such data is considered to be anonymous at the time of or immediately following</span> collection. Paid functionality must not be dependent on or require a user to grant access to this data. Apps must also provide the customer with an easily accessible and understandable way to withdraw consent. Ensure your purpose strings clearly and completely describe your use of the data. Apps that collect data for a legitimate interest without consent by relying on the terms of the European Union’s General Data Protection Regulation (“GDPR”) or similar statute must comply with all terms of that law. Learn more about <a href="https://web.archive.org/web/20190606000009/https://developer.apple.com/documentation/uikit/core_app/protecting_the_user_s_privacy">Requesting Permission</a>.</li>
<li><strong><span class="insert">(viii) </span></strong><span class="insert">Apps that compile personal information from any source that is not directly from the user or without the user’s explicit consent, even public databases, are not permitted on the </span><span class="nowrap"><span class="insert">App Store.</span></span></li>
</ul>
</li>
<li id="health-and-health-research"><span id="5.1.3"></span><strong>5.1.3 Health and Health Research</strong>
<p>Health, fitness, and medical data are especially sensitive and apps in this space have some additional rules to make sure customer privacy is protected:</p>
<ul class="no-bullet margin-top-small">
<li><strong>(i)</strong> Apps may not use or disclose to third parties data gathered in the health, fitness, and medical research context—including from the Clinical Health Records API, HealthKit API, Motion and Fitness, MovementDisorderAPIs, or health-related human subject research—for advertising, marketing, or other use-based data mining purposes other than improving health management, or for the purpose of health research, and then only with permission.<span class="insert"> Apps may, however, use a user’s health or fitness data to provide a benefit directly to that user (such as a reduced insurance premium), provided that the app is submitted by the entity providing the benefit, and the data is not be shared with a third party. You must disclose the specific health data that you are collecting from the device.</span></li>
</ul>
</li>
<li id="kids"><span id="5.1.4"></span><strong>5.1.4 Kids</strong>
<p><span class="insert">Apps intended for kids may not include third-party advertising or analytics.</span></p>
<p>Moreover, apps in the Kids Category or those that collect, transmit, or have the capability to share personal information (e.g. name, address, email, location, photos, videos, drawings, the ability to chat, other personal data, or persistent identifiers used in combination with any of the above) from a minor must include a privacy policy and must comply with all applicable children’s privacy statutes. For the sake of clarity, the <a href="#kids-category">parental gate requirement</a> for the Kid’s Category is generally not the same as securing parental consent to collect personal data under these privacy statutes.<span class="insert"> Collecting and transmitting data to third parties from apps in the Kids category is not allowed.</span></p>
</li>
</ul>
</li>
<strong>5.4 VPN Apps</strong>
<p>Apps offering VPN services must utilize the <a href="https://web.archive.org/web/20190606000009/https://developer.apple.com/documentation/networkextension/nevpnmanager">NEVPNManager API</a> and may only be offered by developers enrolled as an organization. You must make a clear declaration of what user data will be collected and how it will be used<span class="insert"> on an app screen prior to any user action to purchase or otherwise use the service</span>. <span class="insert">Apps offering </span>VPN <span class="insert">services may not sell, use, or disclose to third parties any data for any purpose, and must commit to this in their privacy policy. VPN </span>apps must not violate local laws, and if you choose to make your VPN app available in a territory that requires a VPN license, you must provide your license information in the App Review Notes field.<span class="insert"> Parental control, content blocking, and security apps, among others, from approved providers may also use the NEVPNManager API. Apps that do not comply with this guideline will be removed from the </span><span class="nowrap"><span class="insert">App Store</span></span><span class="insert"> and you may be removed from the </span><span class="nowrap"><span class="insert">Apple Developer</span></span><span class="insert"> Program.</span></p>
<strong>5.5 <span class="insert">Mobile Device Management</span></strong>
<p><span class="insert">Mobile Device Management Apps that offer Mobile Device Management (MDM) services must request this capability from Apple. Such apps may only be offered by commercial enterprises (such as business organizations, educational institutions, or government agencies), and in limited cases, companies using MDM for parental control services. You must make a clear declaration of what user data will be collected and how it will be used on an app screen prior to any user action to purchase or otherwise use the service. MDM apps must not violate local laws. Apps offering MDM services may not sell, use, or disclose to third parties any data for any purpose, and must commit to this in their privacy policy. Apps that do not comply with this guideline will be removed from the </span><span class="nowrap"><span class="insert">App Store</span></span><span class="insert"> and you may be removed from the </span><span class="nowrap"><span class="insert">Apple </span>Developer</span><span class="insert"> Program.</span></p>
</section>
</p></article><article class="article intro"><header><p class="date"><span>December 20, 2018</span></p><h2><a href="/articles/2018-12-20-gifting-in-app-purchases/">Gifting in-app purchases</a></h2></header><section class="content"><p>Apple has updated the <a href="https://developer.apple.com/app-store/review/guidelines/">App Store Review Guidelines</a>, adding some minor changes, the most important being a small change to now allow gifting in-app purchases:</p>
</section><p class="changes"><section class="apple">
<h3>Introduction</h3>
<p>The guiding principle of the App Store is simple - we want to provide a safe experience for users to get apps
and a great opportunity for all developers to be successful. On the following pages you will find guidelines
arranged into five clear sections: Safety, Performance, Business, Design, and Legal. A few other points to keep in
mind:</p>
<ul class="disc top-level">
<li class="margin-top">The App Store is a great way to reach hundreds of millions of people around the world. If you build an app that
you just want to show to family and friends, the App Store isn’t the best way to do that. Consider <span
class="insert">using Xcode to install your app on a device for free or use </span>Ad Hoc distribution <span
class="delete">or the Enterprise</span><span class="insert">available to Apple Developer</span> Program<span
class="insert"> members</span>. If you’re just getting started, learn more about the <a
href="/web/20181220202510/https://developer.apple.com/programs/">Apple Developer Program</a>.
</li>
</ul>
<strong>3.1 Payments</strong>
<ul class="no-bullet margin-top-small">
<li id="in-app-purchase"><strong>3.1.1 In-App Purchase:</strong>
<li class="margin-top">Apps <span class="delete">should not directly or indirectly</span><span
class="insert">may</span> enable gifting of<span class="insert"> items that are eligible
for</span> in-app purchase<span class="delete"> content, features, or consumable
items</span> to others.<span class="insert"> Such gifts may only be refunded to the original
purchaser and may not be exchanged.</span></li>
</li>
</ul>
</section></p></article><article class="article intro"><header><p class="date"><span>June 04, 2018</span></p><h2><a href="/articles/2018-06-04-wwdc2018/">Changes after WWDC 2018</a></h2></header><section class="content"><p>After the keynote of the World Wide Developers Conference 2018, Apple updated the <a href="https://developer.apple.com/app-store/review/guidelines/">App Store Review Guidelines</a> with a bunch of changes and new rules. It is clear that the theme of this update is user privacy and data protection. You can check out all the additions (marked with green) and removals (marked with red) below, but a few noteworthy changes include:</p>
<ul>
<li>Apps now must clearly describe new features and changes in the “What’s New” section of the App Store. Several of the large social network companies have been using a practice where they reuse a generic update text for every release and then enable new features remotely on a per-user basis. This appears to no longer be permitted.</li>
<li>Developers are now allowed to provide time based free trials for non-subscription apps.</li>
<li>Several new rules for apps dealing with cryptocurrencies. Apps are not allowed to mine coins, but in return cryptocurrencies no longer need to be “approved”.</li>
<li>New rules for apps and games with advertising. Users now must be able to see all information used to target an ad without leaving the app.</li>
<li>New rules for apps that enable Remote Desktop access.</li>
<li>Emojis are back! Section 4.5.6 says that it is ok to use Unicode characters that render as Apple emojis inside apps and app metadata.</li>
<li>All apps must include a link to their privacy policy in the App Store Connect metadata field and within the app</li>
<li>Apps must respect the user’s permission settings and not attempt to manipulate, trick, or force people to consent to unnecessary data access. For example, apps that include the ability to post photos to a social network must not also require microphone access before allowing the user to upload photos.</li>
<li>Apps that enable sign in using a 3<span class="ord">rd</span> party social network must also include a mechanism to revoke social network credentials and disable data access between the app and social network from within the app.</li>
<li>There is a new Developer Code of Conduct section.</li>
</ul>
<p>Check out all the changes yourself below.</p>
</section><p class="changes"><section class="apple">
<h3 class="typography-subsection-headline">Introduction</h3>
<p>The guiding principle of the App Store is simple - we want to provide a safe experience for users to get apps
and a great opportunity for all developers to be successful.
<span class="delete">We have updated the App Review Guidelines with that principle in mind. The</span>
<span class="insert">On the following pages you will find</span> guidelines
<span class="delete">themselves haven’t changed, but they are better organized and provide more context. On the following pages you
will find guidelines </span>arranged into five clear sections: Safety, Performance, Business, Design, and
Legal. A few other points to keep in mind:</p>
<ul class="disc top-level">
<li>
<span class="insert">You are responsible for making sure everything in your app complies with these guidelines, including ad networks,
analytics services, and third-party SDKs, so review and choose them carefully.</span>
</li>
</ul>
<p>We hope these
<span class="delete">new </span>guidelines help you sail through the App Review process, and that approvals and rejections
<span class="delete">are more</span>
<span class="insert">remain</span> consistent across the board. This is a living document; new apps presenting new questions may result
in new rules at any time. Perhaps your app will trigger this. We love this stuff too, and honor what you do.
<span class="delete">We're</span>
<span class="insert">We’re</span> really trying our best to create the best platform in the world for you to express your talents
and make a living, too.</p>
<strong>1.5 Developer Information</strong>
<p>People need to know how to reach you with questions and support issues. Make sure your
<span class="insert">app and its </span>Support URL
<span class="delete">includes</span>
<span class="insert">include</span> an easy way to
<span class="delete">reach</span>
<span class="insert">contact</span> you
<span class="insert">; this is particularly important for apps that may be used in the classroom</span>. Failure to include accurate
and up-to-date contact information not only frustrates customers, but may violate the law in some countries.
Also ensure that Wallet passes include valid contact information from the issuer and are signed with a dedicated
certificate assigned to the brand or trademark owner of the pass.</p>
<strong>
<span class="insert">1.6 Data Security</span>
</strong>
<p>
<span class="insert">Apps should implement appropriate security measures to ensure proper handling of user information collected pursuant
to the Apple Developer Program License Agreement and these Guidelines (see Guideline 5.1 for more information)
and prevent its unauthorized use, disclosure, or access by third parties.</span>
</p>
<strong>2.3 Accurate Metadata</strong>
<ul class="no-bullet margin-top-small">
<li>
<strong>2.3.6</strong> Answer the age rating questions in
<span class="nowrap">
<span class="delete">iTunes</span>
<span class="insert">App Store</span> Connect</span> honestly so that your app aligns properly with parental controls. If
your app is mis-rated, customers might be surprised by what they get, or it could trigger an inquiry from
government regulators.
<span class="insert"> If your app includes media that requires the display of content ratings or warnings (e.g. films, music, games,
etc.), you are responsible for complying with local requirements in each territory where your app is
available.
</span>
</li>
<li>
<strong>
<span class="insert">2.3.12</span>
</strong>
<span class="insert"> Apps must clearly describe new features and product changes in their “What’s New” text. Simple bug fixes,
security updates, and performance improvements may rely on a generic description, but more significant
changes must be listed in the notes.</span>
</li>
</ul>
<strong>2.4 Hardware Compatibility</strong>
<ul class="no-bullet margin-top-small">
<li>
<strong>2.4.2</strong> Design your app to use power efficiently. Apps should not rapidly drain battery, generate excessive
heat, or put unnecessary strain on device resources.
<span class="insert"> Apps, including any third party advertisements displayed within them, may not run unrelated background processes,
such as cryptocurrency mining.</span>
</li>
<li>
<strong>2.4.4</strong> Apps should never suggest or require a restart of the device
<span class="insert"> or modifications to system settings unrelated to the core functionality of the application. For example, don’t
encourage users to turn off Wi-Fi, disable security features, etc</span>.</li>
</ul>
<strong>2.5 Software Requirements</strong>
<ul class="no-bullet margin-top-small">
<li>
<strong>2.5.2</strong> Apps should be self-contained in their bundles, and may not read or write data outside the
designated container area, nor may they download, install, or execute code
<span class="insert"> which introduces or changes features or functionality of the app</span>, including other apps.</li>
<li>
<strong>2.5.11</strong> SiriKit
<span class="insert"> and Shortcuts</span>
<ul class="no-bullet margin-top-small">
<li>
<strong>(i)</strong> Apps integrating SiriKit
<span class="insert">and Shortcuts </span>should only sign up for intents they can handle without the support of an additional
app and that users would expect from the stated functionality. For example, if your app is a meal
planning app, you should not incorporate an intent to start a workout, even if the app shares integration
with a fitness app.</li>
<li>
<strong>(ii)</strong> Ensure that the vocabulary and phrases in your plist pertains to your app and the
<span class="delete">SiriKit</span>
<span class="insert">Siri</span> functionality of the intents the app has registered for. Aliases must relate directly
to your app or company name and should not be generic terms or include third party app names or services.</li>
<li>
<strong>(iii)</strong> Resolve the Siri request
<span class="insert">or Shortcut </span>in the most direct way possible and do not insert ads or other marketing between
the request and its fulfillment. Only
<span class="delete">present interstitial UI</span>
<span class="insert">request a disambiguation</span> when required to complete the task (e.g. asking the user to specify
a particular type of workout).</li>
</ul>
</li>
<li>
<strong>2.5.13 </strong> Apps using facial recognition for account authentication must use
<a href="https://developer.apple.com/documentation/localauthentication/">LocalAuthentication</a> (and not ARKit or other facial recognition technology)
<span class="insert"> where possible</span>, and must use an alternate authentication method for users under 13 years old.</li>
<li>
<strong>
<span class="insert">2.5.14 </span>
</strong>
<span class="insert"> Apps must request explicit user consent and provide a clear visual indication when recording, logging, or
otherwise making a record of user activity. This includes any use of the device camera, microphone, or
other user inputs.</span>
</li>
<li>
<strong>
<span class="insert">2.5.15 </span>
</strong>
<span class="insert"> Apps that enable users to view and select files should include items from the Files app and the user’s iCloud
documents.
</span>
</li>
</ul>
<strong>3.1 Payments</strong>
<ul class="no-bullet margin-top-small">
<li id="in-app-purchase">
<strong>3.1.1 In-App Purchase:</strong>
<ul class="disc no-margin-top">
<li>If you want to unlock features or functionality within your app, (by way of example: subscriptions, in-game
currencies, game levels, access to premium content, or unlocking a full version), you must use in-app
purchase. Apps may
<span class="insert">not </span>use
<span class="insert"> their own mechanisms to unlock content or functionality, such as license keys, augmented reality
markers, QR codes, etc. Apps and their metadata may not include buttons, external links, or other
calls to action that direct customers to purchasing mechanisms other than</span> in-app
<span class="delete"> purchase currencies to enable customers to “tip” digital content providers in the app. Apps and their
metadata may not include buttons, external links, or other calls to action that direct customers
to purchasing mechanisms other than in-app</span> purchase.</li>
<li>
<span class="insert">Apps may use in-app purchase currencies to enable customers to “tip” digital content providers in
the app.</span>
</li>
<li>
<span class="insert">Non-subscription apps may offer a free time-based trial period before presenting a full unlock option
by setting up a Non-Consumable IAP item at Price Tier 0 that follows the naming convention: “XX-day
Trial.” Prior to the start of the trial, your app must clearly identify its duration, the content
or services that will no longer be accessible when the trial ends, and any downstream charges
the user would need to pay for full functionality. Learn more about managing content access and
the duration of the trial period using </span>
<a href="https://developer.apple.com/library/archive/releasenotes/General/ValidateAppStoreReceipt/Introduction.html">
<span class="insert">Receipts</span>
</a>
<span class="insert"> and </span>
<a href="https://developer.apple.com/documentation/devicecheck">
<span class="insert">Device Check</span>
</a>
<span class="insert">.</span>
</li>
</ul>
</li>
<li id="permissible-uses">
<strong>3.1.2(a) Permissible uses:</strong>
<ul class="disc margin-top-small">
<span class="insert">Auto-renewing subscription apps may offer a free trial period to customers by providing the relevant
information set forth in App Store Connect. Apps that attempt to trick users into purchasing a subscription
under false pretenses or engage in bait-and-switch practices will be removed from the App Store and
you may be removed from the Apple Developer Program. Learn more about </span>
<a href="https://www.apple.com/app-store/subscriptions/">
<span class="insert">Subscription Free Trials</span>
</a>
<span class="insert">.</span>
</li>
</ul>
<li id="reader-apps">
<strong>3.1.3
<span class="insert">(a)</span> “Reader” Apps:</strong> Apps may allow a user to access previously purchased content or content subscriptions
(specifically: magazines, newspapers, books, audio, music, video, access to professional databases, VoIP, cloud storage,
and approved services such as
<span class="delete">educational</span>
<span class="insert">classroom management</span> apps
<span class="delete"> that manage student grades and schedules</span>),
<span class="delete">as well as</span>
<span class="insert">provided that you agree not to directly or indirectly target iOS users to use a purchasing method other than in-app
purchase, and your general communications about other purchasing methods are not designed to discourage use of
in-app purchase.</span>
</li>
<li id="multiplatform-services">
<strong>
<span class="insert">3.1.3(b) Multiplatform Services:</span>
</strong>
<span class="insert"> Apps that operate across multiple platforms may allow users to access content, subscriptions, or features they have
acquired elsewhere, including</span> consumable items in multi-platform games, provided
<span class="delete">that you agree not to directly or indirectly target iOS users to use a purchasing method other than</span>
<span class="insert">those items are also available as</span> in-app
<span class="insert">purchases within the app. You must not directly or indirectly target iOS users to use a purchasing method other than
in-app </span>purchase, and your general communications about other purchasing methods
<span class="delete">are</span>
<span class="insert">must</span> not
<span class="delete">designed to </span>discourage use of in-app purchase.</li>
<li id="hardware-specific-content">
<strong>3.1.4
<span class="delete">Content Codes:</span>
<span class="insert">Hardware-Specific Content:</span>
</strong>
<span class="delete">Apps may not use their own mechanisms to unlock content or functionality, such as license keys, augmented reality
markers, QR codes, etc. </span>In limited circumstances, such as when features are dependent upon specific hardware
to function, the app may unlock that functionality without using in-app purchase (e.g. an astronomy app that adds
features when synced with a telescope). App features that work in combination with an approved physical product (such
as a toy) on an
<em>optional</em> basis may unlock functionality without using in-app purchase, provided that an in-app purchase option
is available as well. You may not, however, require users to purchase unrelated products or engage in advertising
or marketing activities to unlock app functionality.</li>
<li id="goods-and-services">
<strong>3.1.5 (a)
<span class="delete">Physical </span>Goods and Services Outside of the App:</strong> If your app enables people to purchase goods
or services that will be consumed outside of the app, you must use purchase methods other than in-app purchase to
collect those payments, such as Apple Pay or traditional credit card entry.</li>
<li>
<strong>3.1.5 (b) Cryptocurrencies:</strong>
<ul class="disc margin-top-small">
<li>
<span class="insert">(i) Wallets:</span> Apps may facilitate
<span class="delete">transmission of approved </span>virtual
<span class="delete">currencies</span>
<span class="insert">currency storage, provided they are offered by developers enrolled as an organization.</span>
</li>
<li>
<span class="insert">(ii) Mining: Apps may not mine for cryptocurrencies unless the processing is performed off device</span>
(e.g.
<span class="delete">Bitcoin</span>
<span class="insert">cloud-based mining).</span>
</li>
<li>
<span class="insert">(iii) Exchanges: Apps may facilitate transactions or transmissions of cryptocurrency on an approved exchange
</span>,
<span class="delete">DogeCoin</span>
<span class="insert">provided they are offered by the exchange itself.</span>
</li>
<li>
<span class="insert">(iv</span>)
<span class="delete">provided that they do so in compliance with all state and federal laws for the territories in which the app
functions. </span>
<span class="insert">Initial Coin Offerings: </span>Apps facilitating Initial Coin Offerings (“ICOs”), cryptocurrency futures
trading, and other crypto-securities or quasi-securities trading must come from established banks, securities
firms, futures commission merchants (“FCM”), or other approved financial institutions and must comply with
all applicable law.</li>
<li>
<span class="insert">(v) Cryptocurrency apps may not offer currency for completing tasks, such as downloading other apps, encouraging
other users to download, posting to social networks, etc.</span>
</li>
</ul>
</li>
<li id="advertising">
<strong>
<span class="insert">3.1.7 Advertising:</span>
</strong>
<span class="insert"> Ads displayed in an app must be appropriate for the app’s age rating, allow the user to see all information used
to target them for that ad (without requiring the user to leave the app), and may not engage in targeted or behavioral
advertising based on sensitive user data such as health/medical data (e.g. from the HealthKit APIs), school and
classroom data (e.g. from ClassKit), or from kids (e.g. from apps in the Kids Category), etc. Interstitial ads
or ads that interrupt or block the user experience must clearly indicate that they are an ad, must not manipulate
or trick users into tapping into them, and must provide easily accessible and visible close/skip buttons large
enough for people to easily dismiss the ad.</span>
</li>
</ul>
</li>
<strong>3.2 Other Business Model Issues</strong>
<ul class="no-bullet margin-top-small">
<li id="unacceptable">
<strong>3.2.2 Unacceptable</strong>
<ul class="no-bullet margin-top-small">
<li>
<strong>
<span class="insert">(ix)</span>
</strong>
<span class="insert"> Apps must not force users to rate the app, review the app, download other apps, or perform other
similar actions in order to access functionality, content, or use of the app.</span>
</li>
</ul>
</li>
</ul>
<strong>4.2 Minimum Functionality</strong>
<ul class="no-bullet margin-top-small">
<li><strong>4.2.3</strong>
<ul class="disc margin-top-small">
<li><span class="insert">(i)</span> Your app should work on its own without requiring installation of another app to function.</li>
<li><span class="insert">(ii) Make sure you include sufficient content in the binary for the app to function at launch.</span></li>
<li><span class="insert">(iii) If your app needs to download additional resources, disclose the size of the download and prompt users before doing so. Existing apps must comply with this guideline in any update submitted after January 1, 2019.</span></li>
</ul>
</li>
<li><strong><span class="insert">4.2.7 Remote Application Mirroring:</span></strong><span class="insert"> If your remote desktop app acts as a mirror of specific software or services rather than a generic mirror of the host device, it must comply with the following:
</span>
<ul class="disc margin-top-small">
<li><span class="insert">(a) The host device is a personal computer owned by the user, and both the host and client must be connected on a local and LAN-based network.</span></li>
<li><span class="insert">(b) Any software or services appearing in the client are fully rendered on the screen of the host device, and may not use APIs or platform features beyond what is required to stream the Remote Desktop</span></li>
<li><span class="insert">(c) All account creation and management must be initiated from the host device.</span></li>
<li><span class="insert">(d) The UI appearing on the client does not resemble an iOS or App Store view, does not provide a store-like interface, or include the ability to browse, select, or purchase software not already owned or licensed by the user. For the sake of clarity, transactions taking place within mirrored software do not need to use in-app purchase, provided the transactions are processed on the host device.</span></li>
</ul>
</li>
</ul>
<strong>4.5 Apple Sites and Services</strong>
<ul class="no-bullet margin-top-small">
<li><strong>4.5.4</strong> Push Notifications must not be required for the app to function, and should not be used for advertising, promotions, or direct marketing purposes or to send sensitive personal or confidential information.<span class="insert"> Abuse of these services may result in revocation of your privileges.</span></li>
<li><strong><span class="insert">4.5.6</span></strong><span class="insert"> Apps may use Unicode characters that render as Apple emojis in their app and app metadata. Apple emojis may not be used on other platforms or embedded directly in your app binary.</span></li>
</ul>
<strong>4.7 HTML5 Games, Bots, etc. </strong>
<p>Apps may contain or run code that is not embedded in the binary (e.g. HTML5-based games, bots, etc.), as long as code distribution isn’t the main purpose of the app, the code is not offered in a store or store-like interface, and provided that the software (1) is free or purchased using in-app purchase; (2) only uses capabilities available in a standard WebKit view<span class="delete">; your app must use WebKit and JavaScript Core to run third party software and should not attempt to extend or expose native platform APIs to third party software; (3) is offered by developers that have joined the Apple Developer Program and signed the Apple Developer Program License Agreement; and (4) adheres to the terms of these App Review Guidelines</span> (e.g. <span class="insert">it must open and run natively in Safari without modifications or additional software); your app must use WebKit and JavaScript Core to run third party software and should not attempt to extend or expose native platform APIs to third party software; (3) is offered by developers that have joined the Apple Developer Program and signed the Apple Developer Program License Agreement; and (4) adheres to the terms of these App Review Guidelines (e.g. </span>does not include objectionable content). <span class="delete">You</span><span class="insert">Upon request, you</span> must provide an index of software and metadata available in your app<span class="delete"> upon request</span><span class="insert">. It must include Apple Developer Program Team IDs for the providers of the software along with a URL which App Review can use to confirm that the software complies with the requirements above</span>.</p></li>
<strong>5.1 Privacy</strong>
<ul class="no-bullet margin-top-small">
<li id="data-collection-and-storage"><strong>5.1.1 Data Collection and Storage</strong>
<ul class="no-bullet margin-top-small">
<li><strong>(i)<span class="insert"> Privacy Policies: </span></strong> <span class="insert">All apps must include a link to their privacy policy in the App Store Connect metadata field and within the app in an easily accessible manner. The privacy policy must clearly and explicitly:
</span><ul>
<li><span class="insert">Identify what data, if any, the app/service collects, how it collects that data, and all uses of that data.</span></li>
<li><span class="insert">Confirm that any third party with whom an app shares user data (in compliance with these Guidelines) — such as analytics tools, advertising networks and third party SDKs, as well as any parent, subsidiary or other related entities that will have access to user data — will provide the same or equal protection of user data as stated in the app’s privacy policy and required by these Guidelines.</span></li>
<li><span class="insert">Explain its data retention/deletion policies and describe how a user can revoke consent and/or request deletion of the user’s data.</span></li>
</ul>
</li>
<li><strong><span class="insert">(ii) Permission </span></strong>Apps that collect user or usage data must <span class="delete">have a privacy policy and </span>secure user consent for the collection. <span class="delete">This includes—but isn’t limited to—apps that implement HealthKit or other health/medical technologies</span><span class="insert">Paid functionality must not be dependent on or require a user to grant access to this data. Apps must also provide the customer with an easily accessible and understandable way to withdraw consent. Ensure your purpose strings clearly and completely describe your use of the data. Apps that collect data for a legitimate interest without consent by relying on the terms of the European Union’s General Data Protection Regulation (“GDPR”) or similar statute must comply with all terms of that law. Learn more about </span><a href="https://developer.apple.com/documentation/uikit/core_app/protecting_the_user_s_privacy"><span class="insert">Requesting Permission</span></a><span class="insert">.</span></li>
<li><strong><span class="insert">(iii) Data Minimization: </span></strong><span class="insert">Apps should only request access to data relevant to the core functionality of the app and should only collect and use data that is required to accomplish the relevant task. Where possible</span>, <span class="insert">use the out-of-process picker or a share sheet rather than requesting full access to protected resources like Photos or Contacts.</span></li>
<li><strong><span class="insert">(iv) Access </span></strong><span class="insert">Apps must respect the user’s permission settings and not attempt to manipulate, trick, or force people to consent to unnecessary data access. For example, </span>apps that <span class="delete">utilize ARKit</span><span class="insert">include the ability to post photos to a social network must not also require microphone access before allowing the user to upload photos. Where possible</span>, <span class="delete">Camera APIs</span><span class="insert">provide alternative solutions for users who don’t grant consent. For example</span>, <span class="delete">Photo APIs</span><span class="insert">if a user declines to share Location</span>, <span class="delete">or other software for depth of facial mapping</span><span class="insert">offer the ability to manually enter an address.</span></li>
<li><strong><span class="insert">(v) Account Sign-In: </span></strong><span class="insert">If your app doesn’t include significant account-based features, let people use it without a log-in. Apps may not require users to enter personal</span> information<span class="insert"> to function</span>, <span class="delete">HomeKit, Keyboard extensions, Apple Pay, Stickers and iMessage extensions, include a login, or access user data from the device</span><span class="insert">except when directly relevant to the core functionality of the app or required by law</span>. <span class="delete">Your</span><span class="insert">If your core</span> app <span class="delete">description should let people know what types of access</span><span class="insert">functionality is not related to a specific social network</span> (e.g. <span class="delete">location, contacts, calendar, etc.) are requested by your app, and what aspects of the app won’t work if the user doesn’t grant permission.</span>
<span class="delete">(ii)</span><span class="delete"> If your app doesn’t include significant account-based features, let people use it without a log-in. Apps may not require users to enter personal information to function, except when directly relevant to the core functionality of the app or required by law. If your core app functionality is not related to a specific social network (e.g. </span>Facebook, WeChat, Weibo, Twitter, etc.), you must provide access without a login or via another mechanism. Pulling basic profile information, sharing to the social network, or inviting friends to use the app are not considered core app functionality.<span class="insert"> The app must also include a mechanism to revoke social network credentials and disable data access between the app and social network from within the app. An app may not store credentials or tokens to social networks off of the device and may only use such credentials or tokens to directly connect to the social network from the app itself while the app is in use.</span></li>
<li><strong>(<span class="delete">iii</span><span class="insert">vi</span>) </strong> Developers that use their apps to surreptitiously discover passwords or other private data will be removed from the Developer Program.</li>
<li><strong>(<span class="delete">iv</span><span class="insert">vii</span>) </strong>SafariViewContoller must be used to visibly present information to users; the controller may not be hidden or obscured by other views or layers. Additionally, an app may not use SafariViewController to track users without their knowledge and consent.</li>
</ul>
</li>
<li id="data-use-and-sharing"><strong>5.1.2 Data Use and Sharing</strong>
<ul class="no-bullet margin-top-small">
<li><strong>(i) </strong><span class="insert">Unless otherwise permitted by law, you may not use, transmit, or share someone’s personal data without first obtaining their permission.</span> You <span class="insert">must provide access to information about how and where the data will be used. Data collected from apps </span>may <span class="insert">only be shared with third parties to improve the app or serve advertising (in compliance with the </span><a href="https://developer.apple.com/terms/"><span class="insert">Apple Developer Program License Agreement</span></a><span class="insert">.). Apps that share user data without user consent or otherwise complying with data privacy laws may be removed from sale and may result in your removal from the Apple Developer Program.</span></li>
<li><strong><span class="insert">(ii) </span></strong><span class="insert">Data collected for one purpose may </span>not<span class="insert"> be repurposed without further consent unless otherwise explicitly permitted by law. </span></li>
<li><strong><span class="insert">(iii) </span></strong><span class="insert">Apps should not attempt to surreptitiously build a user profile based on collected data and may not</span> attempt, facilitate, or encourage others to identify anonymous users or reconstruct user profiles based on data collected from <span class="delete">depth and</span><span class="insert">Apple-provided APIs or any data that you say has been collected in an “anonymized,” “aggregated,” or otherwise non-identifiable way.</span></li>
<li><strong><span class="insert">(iv) </span></strong><span class="insert">Do not use information from Contacts, Photos, or other APIs that access user data to build a contact database for your own use or for sale</span>/<span class="delete">or facial mapping tools</span><span class="insert">distribution to third parties, and don’t collect information about which other apps are installed on a user’s device for the purposes of analytics or advertising/marketing.</span></li>
<li><strong><span class="insert">(v) </span></strong><span class="insert">Do not contact people using information collected via a user’s Contacts or Photos, except at the explicit initiative of that user on an individualized basis; do not include a Select All option or default the selection of all contacts. You must provide the user with a clear description of how the message will appear to the recipient before sending it</span> (e.g. <span class="delete">ARKit, Camera APIs, or Photo APIs</span><span class="insert">What will the message say? Who will appear to be the sender?</span>)<span class="delete">, or data that you say has been collected in an “anonymized,” “aggregated,” or otherwise non-identifiable way</span>. <span class="delete">You may not use or transmit someone’s personal data without first obtaining their permission and providing access to information about how and where the data will be used.</span></li>
<li><strong>(<span class="delete">ii</span><span class="insert">vi</span>) </strong> Data <span class="delete">collected from apps may not be used or shared with third parties for purposes unrelated to improving the user experience or software</span><span class="insert">gathered from the HomeKit API, HealthKit, Consumer Health Records API, MovementDisorder APIs, ClassKit or from depth and</span>/<span class="delete">hardware performance connected to the app’s functionality, or to serve advertising in compliance with the </span><span class="delete">Apple Developer Program License Agreement</span><span class="delete">.</span>
<span class="delete">(iii)</span><span class="delete"> Data gathered from the HomeKit API or from depth and/</span>or facial mapping tools (e.g. ARKit, Camera APIs, or Photo APIs) may not be used for <span class="insert">marketing, </span>advertising or<span class="delete"> other</span> use-based data mining, including by third parties.<span class="insert"> Learn more about best practices for implementing </span><a href="https://developer.apple.com/documentation/callkit"><span class="insert">CallKit</span></a><span class="insert">, </span><a href="https://developer.apple.com/documentation/healthkit"><span class="insert">HealthKit</span></a><span class="insert">, </span><a href="https://developer.apple.com/documentation/classkit"><span class="insert">ClassKit</span></a><span class="insert">, and </span><a href="https://developer.apple.com/documentation/arkit"><span class="insert">ARKit</span></a><span class="insert">.</span></li>
<li><strong>(<span class="delete">iv</span><span class="insert">vii</span>) </strong> Apps using Apple Pay may only share user data acquired via Apple Pay with third parties to facilitate or improve delivery of goods and services.</li>
</ul>
</li>
<li id="kids"><strong>5.1.4 Kids</strong>
<p>For many reasons, it is critical to use care when dealing with personal data from kids, and we encourage you to carefully review all the requirements for complying with laws like the Children’s Online Privacy Protection Act (“COPPA”)<span class="insert">, the European Union’s General Data Protection Regulation (“GDPR”),</span> and any international<span class="insert"> or local</span> equivalents.</p>
</li>
</ul>
<strong>5.4 VPN Apps</strong>
<p>Apps offering VPN services must utilize the <a href="https://developer.apple.com/documentation/networkextension/nevpnmanager">NEVPNManager<span class="insert"> API</span></a> <span class="delete">API and</span><span class="insert">and may only be offered by developers enrolled as an organization. You</span> must make a clear declaration of what user data will be collected and how it will be used. VPN apps must not violate local laws, and if you choose to make your VPN app available in a territory that requires a VPN license, you must provide your license information in the App Review Notes field.</p>
<strong><span class="insert">5.5 Developer Code of Conduct</span></strong>
<p><span class="insert">Please treat everyone with respect, whether in your responses to App Store reviews, customer support requests, or when communicating with Apple, including your responses in Resolution Center. Do not engage in harassment of any kind, discriminatory practices, intimidation, bullying, and don’t encourage others to engage in any of the above.</span></p>
<p><span class="insert">Customer trust is the cornerstone of the App Store’s success. Apps should never prey on users or attempt to rip-off customers, trick them into making unwanted purchases, force them to share unnecessary data, raise prices in a tricky manner, charge for features or content that are not delivered, or engage in any other manipulative practices within or outside of the app.</span></p>
</section></p></article><article class="article intro"><header><p class="date"><span>December 21, 2017</span></p><h2><a href="/articles/2017-12-21-tba/">Crypto currencies and ICOs, template apps, loot boxes and more</a></h2></header><section class="content"><p>Wednesday the <a href="https://developer.apple.com/app-store/review/guidelines/">App Store Review Guidelines</a> was updated with quite a few changes. Besides some minor clarifications, new sections were introduced about:</p>
<ul>
<li>Crypto currencies and ICOs now have a dedicated section.</li>
<li>The ban on template apps is clarified so its now more clear exactly what kinds of apps are affected. <a href="https://techcrunch.com/2017/12/20/apple-revises-its-controversial-guidelines-on-template-based-apps/">Techcrunch spotted this change too</a>.</li>
<li>There is a few paragraphs on apps available for pre-order.</li>
<li>Details about what is allowed when offering so-called “loot boxes” in games.</li>
<li>Financial apps must come from the financial institutions performing the services or they should at least use public APIs.</li>
<li>A new section on <span class="caps">VPN</span> apps details some rules specific to this app type.</li>
</ul>
<p>Check out all the changes below.</p>
</section><p class="changes"><section class="apple">
<h3 class="typography-subsection-headline">Introduction</h3>
<p>We <span class="insert">strongly support all points of view being represented on the App Store, as long as the apps are respectful to users
with differing opinions and the quality of the app experience is great. We </span>will reject apps for any content
or behavior that we believe is over the line. What line, you ask? Well, as a Supreme Court Justice once said, “I'll
know it when I see it”. And we think that you will also know it when you cross it.</p>
<strong>2.1 App Completeness</strong>
<p>Submissions to App Review<span class="insert">, including apps you make available for pre-order,</span> should be final versions with all necessary metadata
and fully functional URLs included; placeholder text, empty websites, and other temporary content should be scrubbed
before submission. Make sure your app has been tested on-device for bugs and stability before you submit it,
and include demo account info (and turn on your back-end service!) if your app includes a login. If you offer
in-app purchases in your app, make sure they are complete, up-to-date, and visible to the reviewer, or that you
explain why not in your review notes. Please don’t treat App Review as a software testing service. We will reject
incomplete app bundles and binaries that crash or exhibit obvious technical problems.</p>
<strong>2.3 Accurate Metadata</strong>
<ul class="no-bullet margin-top-small">
<li>
<strong>2.3.2</strong> If your app includes in-app purchases, make sure your app description, screenshots, and previews
clearly indicate whether any featured items, levels, subscriptions, etc. require additional purchases. If
you decide to promote in-app purchases on the App Store, ensure that the in-app purchase Display Name, Screenshot
and Description are appropriate for a public audience
<span class="insert">, that you follow the guidance found in </span>
<a href="/app-store/promoting-in-app-purchases/">
<span class="insert">Promoting Your In-App Purchases</span>
</a>
<span class="insert">,</span> and that your app properly handles the
<a href="https://developer.apple.com/documentation/storekit/skpaymenttransactionobserver/2877502-paymentqueue">SKPaymentTransactionObserver method</a> so that customers can seamlessly complete the purchase when your
app launches.
</li>
<li>
<strong>
<span class="insert">2.3.11</span>
</strong>
<span class="insert"> Apps you submit for pre-order on the App Store must be complete and deliverable as submitted. Ensure that
the app you ultimately release is not materially different from what you advertise while the app is in
a pre-order state. If you make material changes to the app (e.g. change business models), you should
restart your pre-order sales.
</span>
</li>
</ul>
<strong>2.5 Software Requirements</strong>
<ul class="no-bullet margin-top-small">
<li>
<strong>2.5.1</strong> Apps may only use public APIs and must run on the currently shipping OS. Learn more about
<a href="https://developer.apple.com/documentation/">public APIs</a>. Keep your apps up-to-date and make sure you phase out any deprecated features, frameworks
or technologies that will no longer be supported in future versions of an OS.
<span class="insert">Apps should use APIs and frameworks for their intended purposes and indicate that integration in their app
description. For example, the HomeKit framework should provide home automation services; and HealthKit
should be used for health and fitness purposes and integrate with the Health app.</span>
</li>
</ul>
<strong>3.1 Payments</strong>
<ul class="no-bullet margin-top-small">
<li id="in-app-purchase">
<strong>3.1.1 In-App Purchase:</strong>
<ul class="disc no-margin-top"></ul>
<li>
<span class="insert">Apps offering “loot boxes” or other mechanisms that provide randomized virtual items for purchase must
disclose the odds of receiving each type of item to customers prior to purchase.</span>
</li>
<li id="permissible-uses">
<strong>3.1.2(a) Permissible uses:</strong>
<ul class="disc margin-top-small">
<li>You may offer a single subscription that is shared across your own apps
<span class="insert"> and services</span>, but these subscriptions may not extend to third party apps or services.
<span class="delete">Subscriptions</span>
<span class="insert">Games offered in a game subscription</span> must
<span class="delete">work on all of the user’s devices where the app is available. Learn more about </span>
<span class="delete">sharing a subscription across your apps</span>
<span class="delete">. </span>
<span class="delete">Apps must not force users to rate the app, review the app, download other apps, or other similar
actions in order to access functionality, content, or use of the app.</span>
<span class="delete">As with all apps, those offering subscriptions should allow a user to get what they’ve paid for
without performing additional tasks, such as posting on social media, uploading contacts,
checking in to the app a certain number of times, etc. </span>
<span class="delete">Subscriptions may not include consumable credits, gems, in-game currencies, etc., even when combined
with other offerings, but you may offer subscriptions that include access to discounted consumable
goods
</span>
<span class="insert">be owned or exclusively licensed by the developer</span> (e.g.
<span class="insert">not part of a game publishing platform). Each game must be downloaded directly from the App Store,
must be designed to avoid duplicate payment by a subscriber, and should not disadvantage
non-subscriber customers.</span>
</li>
<li>
<span class="insert"> Subscriptions must work on all of the user’s devices where the app is available. Learn more about
</span>
<a href="https://developer.apple.com/library/content/documentation/NetworkingInternet/Conceptual/StoreKitGuide/Chapters/Subscriptions.html">
<span class="insert">sharing a subscription across your apps</span>
</a>
<span class="insert">. </span>
</li>
<li>
<span class="insert">Apps must not force users to rate the app, review the app, download other apps, or other similar
actions in order to access functionality, content, or use of the app.</span>
</li>
<li>
<span class="insert">As with all apps, those offering subscriptions should allow a user to get what they’ve paid for
without performing additional tasks, such as posting on social media, uploading contacts,
checking in to the app a certain number of times, etc. </span>
</li>
<li>
<span class="insert">Subscriptions may include consumable credits, gems, in-game currencies, etc., and you may offer
subscriptions that include access to discounted consumable goods (e.g. </span>a platinum
membership that exposes gem-packs for a reduced price).</li>
</ul>
</li>
<li>
<strong>
<span class="insert">3.1.5 (b) Cryptocurrencies:</span>
</strong>
<p>Apps may facilitate transmission of approved virtual currencies (e.g. Bitcoin, DogeCoin) provided that
they do so in compliance with all state and federal laws for the territories in which the app functions.
<span class="insert"> Apps facilitating Initial Coin Offerings (“ICOs”), cryptocurrency futures trading, and other crypto-securities
or quasi-securities trading must come from established banks, securities firms, futures commission
merchants (“FCM”), or other approved financial institutions and must comply with all applicable law.</span></p>
</li>
</ul>
<strong>3.2 Other Business Model Issues</strong>
<ul class="no-bullet margin-top-small">
<li id="acceptable">
<strong>3.2.1 Acceptable</strong>
<ul class="no-bullet margin-top-small">
<li>
<strong>
<span class="insert">(viii)</span>
</strong>
<span class="insert"> Apps used for financial trading, investing, or money management should come from the financial
institution performing such services or must use a public API offered by the institution
in compliance with its Terms & Conditions.</span>
</li>
</ul>
</li>
<li id="unacceptable">
<strong>3.2.2 Unacceptable</strong>
<ul class="no-bullet margin-top-small">
<li>
<strong>(viii)</strong> Apps that facilitate binary options trading are not permitted on the App Store.
Consider a web app instead.
<span class="insert"> Apps that facilitate trading in contracts for difference (“CFDs”) or other derivatives (e.g.
FOREX) must be properly licensed in all jurisdictions where the service is available.</span>
</li>
</ul>
</li>
</ul>
<strong>4.2 Minimum Functionality</strong>
<ul class="no-bullet margin-top-small">
<li>
<strong>4.2.1</strong> Apps
<span class="insert">using ARKit </span>should
<span class="delete">use APIs and frameworks for their intended purposes and indicate that integration in their app description.
For example, the HomeKit framework should </span>provide
<span class="delete">home automation services; and HealthKit should be used for health and fitness purposes and integrate
with the Health app. Apps using ARKit should provide </span>rich and integrated augmented reality
experiences; merely dropping a model into an AR view or replaying animation is not enough.</li>
<li>
<strong>4.2.6</strong> Apps created from a commercialized template or app generation service will be rejected
<span class="insert"> unless they are submitted directly by the provider of the app’s content. These services should not submit
apps on behalf of their clients and should offer tools that let their clients create customized,
innovative apps that provide unique customer experiences. Another acceptable option for template
providers is to create a single binary to host all client content in an aggregated or “picker” model,
for example as a restaurant finder app with separate customized entries or pages for each client
restaurant, or as an event app with separate entries for each client event</span>.</li>
</ul>
<strong>4.4 Extensions</strong>
<ul class="no-bullet margin-top-small">
<li>
<strong>4.4.1</strong> Keyboard extensions have some additional rules.
<br>
<p>They must:</p>
<ul class="disc margin-top-small">
<li>
Remain functional without full network access and without requiring full access;
<span class="delete">Provide Number and Decimal keyboard types as described in the </span>
<span class="delete">App Extension Programming Guide</span>
<span class="delete">;</span>
</li>
</ul>
</li>
</ul>
<strong>
<span class="insert">5.4 VPN Apps</span>
</strong>
<p>
<span class="insert">Apps offering VPN services must utilize the </span>
<a href="https://developer.apple.com/documentation/networkextension/nevpnmanager">
<span class="insert">NEVPNManager</span>
</a>
<span class="insert"> API and must make a clear declaration of what user data will be collected and how it will be used. VPN apps
must not violate local laws, and if you choose to make your VPN app available in a territory that requires
a VPN license, you must provide your license information in the App Review Notes field.</span>
</p>
</ul>
</section></p></article></div></div></body></html>
Whois info of domain
Domain Name: ASRGH.COM
Registry Domain ID: 1898282252_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.rrpproxy.net
Registrar URL: http://www.key-systems.net
Updated Date: 2025-01-11T08:59:05Z
Creation Date: 2015-01-26T09:24:31Z
Registry Expiry Date: 2026-01-26T09:24:31Z
Registrar: Key-Systems GmbH
Registrar IANA ID: 269
Registrar Abuse Contact Email: [email protected]
Registrar Abuse Contact Phone: +49.68949396850
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Name Server: NS1.SIMPLY.COM
Name Server: NS2.SIMPLY.COM
Name Server: NS3.SIMPLY.COM
Name Server: NS4.SIMPLY.COM
DNSSEC: signedDelegation
DNSSEC DS Data: 10906 13 2 82A591EC4A28C4BE7943A56C8ACA69A6444FDA71B2F5DE1F59BFA37F3552AC9A
DNSSEC DS Data: 10906 13 4 647E235C462CDA8A0ABF35AEECE0D99CB065C5B8AB36EB63FAE24A6C829E47480ED9D303B7512EDFA1DF4E963EB883CE
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2025-05-13T06:39:55Z <<<
For more information on Whois status codes, please visit https://icann.org/epp
NOTICE: The expiration date displayed in this record is the date the
TERMS OF USE: You are not authorized to access or query our Whois
by the following terms of use: You agree that you may use this Data only
to: (1) allow, enable, or otherwise support the transmission of mass