The first major update of the App Store Review Guidelines in 2017! Modified/newly added content accounts for 23%!

Recently, Apple made the first major update to the App Store Review Guidelines in 2017! Compared with the previous version, the modified/newly added content accounts for 23%! Not only does it involve App names, subtitles , in-app purchases, backup App icons, SiriKit, APIs, subscriptions, etc., Apple has also made new regulations on abandoned apps, medical apps, replying to user reviews, and "rewarding" digital content providers.

In order to help everyone quickly get the latest updates of the latest review guidelines, Xiaoqi has sorted out and summarized the main changes and additions.

About App Name:

App names must be limited to 30 characters. (This regulation has not yet been implemented, and the iTC backend App name can still be entered with 50 characters.)

About the subtitle:

App subtitles are a great way to provide additional descriptions for your app; they must follow our standard metadata rules and should not include inappropriate content, reference other apps, or make unverifiable product claims.

About abandoned apps:

If your app no ​​longer functions as intended or you no longer maintain and operate it , it will be removed from the App Store.

About replying to user reviews in the App Store:

Do not include personal information, spam, or engage in marketing in your response. Use the provided API to prompt users to rate your app.

About Medical App:

Apps must clearly disclose data and methods to support accuracy claims related to health measurements. If the accuracy and methods of the App cannot be verified, we will reject your App. Apps should remind users to consult a doctor in addition to using the App and before making medical decisions.

About in-app purchases:

If you decide to promote in-app purchases on the App Store, make sure the name and description of the IAP display are written for public users and that your app correctly handles the payment API so that customers can complete the purchase seamlessly when your app launches.

About API

Only public APIs are used and must be compatible with the latest released system.

About SiriKit

Aliases must be related to your app or company name and should not be generic terms or include the names of third-party applications or services.

About Subscription:

The subscription period must last at least 7 days and be available on all of the user's devices.

About Reader App

Apps should allow users to access previously purchased content or content subscriptions and consumable items in multi-platform games , as long as you agree not to directly or indirectly direct iOS users to use purchase methods other than IAP and the general information about other purchase methods is not intended to discourage the use of IAP.

About Binary Options Trading

Binary options trading apps are not allowed to be uploaded to the App Store.

About Alternative App Icons

Apps can display customized icons, provided that each change is initiated by the user and the app includes a setting to restore the original icon. All icon versions must be relevant to the content of the app.

About third-party software

Apps may include or run code provided by third-party developers (such as HTML5-based games) as long as the code is not provided in a store or store-like interface and as long as the software is free or purchased using in-app purchase…

For more information, please refer to the translated and edited full text of the App Store Review Guidelines (Note: modified/newly added parts are shown in red font)

The latest App Store review guidelines for 2017

Introduction

Apps are changing the world, enriching people’s lives, and providing developers like you with unprecedented opportunities to innovate. As a result, the App Store has grown into an exciting and vibrant ecosystem that serves millions of developers and over a billion users. Whether you're a new developer or a large team of experienced programmers , we welcome you to develop apps for the App Store and want to help you understand our guidelines to ensure your apps are quickly reviewed.

The guiding principles of the App Store are simple – we want to provide a safer and more reliable experience for users when acquiring apps, and give all developers an opportunity to succeed with apps. We have updated our App Review Guidelines to reflect this principle. The core content of the new guide has not changed, but it is more organized and contains more context for easier understanding. On the following pages, you'll find these guidelines clearly divided into five sections: Security, Performance, Business, Design, and Legal. In addition, please keep the following points in mind:

We found that many children download a large number of various apps. While parental controls are effective in protecting children, you must also do your part. So you know, we are keeping an eye on these children at all times.

The App Store is a great place where hundreds of millions of people from all over the world gather. If you're developing an app just to show off to family and friends, the App Store isn't the best place to do it. Release using a test certificate or an enterprise version. If you're just getting started, learn more about the Apple Developer Program.

If we believe any content or behavior in an app goes beyond acceptable limits, we will reject the app. You might ask, what is this acceptable range? To paraphrase a Supreme Court Justice: “I know it when I see it.” And, we believe that you yourself will realize when you go beyond this range.

If you attempt to game the system (for example, by attempting to game the review process, steal user data, copy other developers’ work, or manipulate ratings), we will remove your app from the store and remove you from the Developer Program.

We hope these new guidelines help you navigate the App Review process and make approval and rejection criteria more consistent overall. This is a living document; we may develop new rules at any time if new apps raise new issues. Maybe your app will help set new rules. We love app development as well and respect what you do. We are doing our best to create the best platform in the world for you to showcase your talents and get rewards.

Table of contents

Before you submit – Pre-review checklist

1. Security

1.1 Objectionable Content

1.2 User-Generated Content

1.3 Children Category

1.4 Personal Injury

1.5 Developer Information

2. Performance

2.1 App Completion

2.2 Beta App

2.3 Accurate metadata

2.4 Hardware Compatibility

2.5 Software Requirements

3. Business

3.1 Payment

3.1.1 In-App Purchases

3.1.2 Subscription

3.1.3 Content-based “Reader” App

3.1.4 Content Code

3.1.5 Physical Goods and Services Outside of Apps

3.1.6 Apple Pay

3.2 Other business model issues

3.2.1 Acceptable

3.2.2 Unacceptable

4. Design

4.1 Plagiarists

4.2 Minimum functional requirements

4.3 Spam Apps

4.4 Extended Functionality

4.5 Apple Sites and Services

5. Legal

5.1 Privacy

5.1.1 Data Collection and Storage

5.1.2 Data Use and Sharing

5.1.3 Health and health research

5.1.4 Children

5.1.5 Location Services

5.2 Intellectual Property

5.3 Games, gambling and lotteries

After you submit – what to expect

Before you submit

To help you get your app approved as smoothly as possible, please review the following list of common mistakes that may delay the review process or lead to your app being rejected. These are not a substitute for the guidelines or a guarantee of app approval, but making sure you check off every item on this list is a good start. If your app no ​​longer functions as expected or you no longer maintain and operate it, it will be removed from the App Store. Learn more about App Store improvements.

Please ensure that:

Test whether the app crashes or has errors

Ensure all app information and metadata are complete and correct

Update your contact information so that App Review can get in touch with you if needed.

Provide a valid demo account and login information, as well as any other hardware or resources required to review the app (e.g., sample QR codes)

Enable the background service so that it is active and available during the audit period

Include detailed descriptions of non-obvious features and IAP in your App Review notes, including supporting documentation where applicable. If we cannot access parts of the app due to region locks or other restrictions, please provide a link to a video of the functionality in question

Check that your app follows relevant guidelines in other documents, such as:

Development Guide

App Programming Guide

(Application Programming Guide)

App Extension Programming Guide

(App Extension Programming Guide)

iOS Data Storage Guidelines

(iOS Data Storage Terms)

macOS File System Documentation

(Mac OS X File Systems documentation)

Safari Extensions Development Guide

(Safari Extension Development Guide)

iTunes Connect Developer Guide

(iTunes Connect Developer Guide)

Design Guide

iOS Human Interface Guidelines

(iOS Human Interface Guidelines)

macOS Human Interface Guidelines

(Mac OS Human Interface Guidelines)

tvOS Human Interface Guidelines

(tvOS Human Interface Guidelines)

watchOS Human Interface Guidelines

(watchOS Human Interface Guidelines)

Brand and Marketing Guidelines

App Store Marketing Guidelines

(App Store Marketing Guidelines)

Apple Pay Identity Guidelines

(Apple Pay logo guide)

Add to Apple Wallet Guidelines

(Guide to joining Apple Wallet)

Guidelines for Using Apple Trademarks and Copyrights

(Terms of Use of Apple Trademarks and Copyrights)

1. Security

When users install apps from the App Store, they expect a safe experience: apps that do not contain objectionable or offensive content, that will not damage their devices, or that will cause physical harm during use. We've listed the main safety concerns below. If you intend to intimidate or attack others, your app is not suitable for the App Store.

1.1 Objectionable Content

Apps should not contain content that is offensive, insensitive, disturbing, objectionable, or vulgar. Examples of this type of content include:

1.1.1 Defamatory or malicious content, including references or comments about religion, race, sexual orientation, gender, or other targeted groups, particularly when the App is likely to cause harm to a specific individual or group. Professional political satire and humor writers are generally exempt from this requirement.

1.1.2 Realistic depictions of the killing, maiming, torture or abuse of humans or animals, or content that encourages violence. In the game, "enemies" cannot be limited to specific races, cultures, real governments or corporations, or any other real-world entities.

1.1.3 Depictions that encourage the illegal or irresponsible use of weapons and dangerous items, or that promote the purchase of arms.

1.1.4 Excessively pornographic content (Merriam-Webster defines pornography as explicit descriptions or displays of sexual organs or sexual activity intended to stimulate sexual pleasure rather than to bring aesthetic value or to arouse emotion).

1.1.5 Incendiary religious commentary or false or misleading references to religious texts.

1.1.6 False information and features that include inaccurate device data or features used for pranks/jokes, such as fake location trackers. Even if an app is specified as “for entertainment purposes only”, it cannot violate this principle. Apps that support anonymous or prank calls or SMS/MMS will be rejected.

1.1.7 App Store Reviews:

App Store user reviews can be an integral part of your app experience, so you should treat your users respectfully when responding to their reviews. Keep your responses targeted to the user's comments and don't include personal information, spam, or marketing in your responses.

Use the provided API to prompt users to review your app; this feature allows users to provide an App Store rating and score without leaving your app . We will not allow custom review prompts.

1.2 User-Generated Content

For apps that contain user-generated content, there are specific challenges that need to be addressed, such as intellectual property infringement and anonymous bullying. To prevent abuse, apps that include user-generated content or social networking services must meet the following conditions:

Use appropriate methods to filter objectionable content to prevent it from being published in the App

Develop a mechanism to report offensive content and respond promptly when issues arise

If a user posts offensive content, he or she may be disqualified from using the service.

Publish contact information so users can contact you

Apps that contain user-generated content or services that ultimately serve the primary purpose of pornography, objectifying a real person (such as a "hot or not" vote), making physical threats, or bullying are not appropriate for the App Store and may be removed without notice. Apps that include user-generated content from web-based services may display incidental “NSFW” content, provided that the content is hidden by default and only displayed when the user turns it on through your website.

1.3 Children Category

The Kids Category helps users easily find apps suitable for children. If you want to participate in the Kids Category, you should focus on creating a great experience tailored for younger users. These apps may not provide out-of-app links, purchasing opportunities, or other content that may be disruptive to children unless they are kept in a designated area with parental controls. Keep in mind that as long as customers want your app to qualify for the Kids Category, your app will need to continue to meet those guidelines in subsequent updates; this is true even if you decide to deselect this category. Learn more about Parental Controls.

Apps in the Kids Category may not display behavioral advertising (for example, advertisers may not serve ads based on a user’s activity within the app), and all content ads must be appropriate for children. You should also pay special attention to privacy laws around the world regarding the online collection of data from children. Please be sure to review the "Privacy" section of these guidelines for more information.

1.4 Personal Injury

We may reject an app if it behaves in a way that could cause physical harm. For example:

1.4.1 Medical apps may face more stringent scrutiny if they may provide erroneous data or information, or be used to diagnose or treat patients.

Apps must clearly disclose data and methods to support accuracy claims related to health measurements. If the accuracy and methods of the App cannot be verified, we will reject your App. For example, apps that use only on-device sensors to take x-rays, measure blood pressure, temperature, blood sugar levels, or blood oxygen levels are not allowed.

The app should remind users to consult a doctor before using the app and making medical decisions .

If your medical app has been approved by regulatory authorities, please submit a link to the relevant documents along with your app.

1.4.2 Medication dosage calculators must come from pharmaceutical manufacturers, hospitals, universities, health insurance companies, or other entities approved by the FDA or its international counterparts. Because of the potential for harm to patients, we need to ensure that the app will be supported and updated over a long period of time.

1.4.3 Apps may not encourage illegal drug use or excessive alcohol intake; or encourage minors to purchase drugs, alcohol, or tobacco; or facilitate the sale of marijuana.

1.4.4 The App may only display DUI checkpoints published by relevant law enforcement agencies and may not encourage DUI and other reckless behavior including speeding.

1.4.5 Apps may not cause customers to use their devices in a manner that is inconsistent with Apple hardware security documentation or in a manner that could cause harm to the device or to persons. For example, apps may not encourage users to place their devices under mattresses and pillows while charging. Consult your device documentation.

1.5 Developer Information

Users need to know how to contact you with questions and support issues. Please ensure that your support URL includes easy-to-use contact information. Failure to provide accurate, up-to-date contact information may not only irritate your customers, but may also violate laws in some countries. Also, make sure to include valid contact details of the card issuer in your Wallet credentials, as well as a dedicated certificate assigned to the brand or trademark owner of the credential.

2. Performance

2.1 App Completion

Apps submitted for review should be final and should contain all required metadata and fully functional URLs; placeholder text, blank websites, and other temporary content should be removed prior to submission. Before submitting your app, be sure to test it on a device for bugs and stability, and if your app requires a login, provide demo account information (and turn on your background service!). If you offer in-app purchases in your app, make sure that they are visible to the reviewer and that they are complete and up to date. If not, explain why not in the review notes. Please do not consider App Review as a software testing service. We will reject incomplete app bundles and binaries that crash or have obvious technical issues.

2.2 Beta App

Demos, betas, and trials of your app are not appropriate for the App Store – use TestFlight instead. All apps submitted for test distribution through TestFlight should be intended for public release and should follow the App Review Guidelines. Please note that apps using TestFlight may not be distributed to testers in exchange for compensation of any kind, including as a reward for crowdfunding funds. Significant updates to your beta app should be submitted to the TestFlight App Review team before being distributed to your testers. To learn more, visit TestFlight Beta Testing.

2.3 Accurate metadata

Customers should know what they're getting when they download or purchase your app, so make sure your app's description, screenshots, and previews accurately reflect your app's core experience, and remember to update them frequently to stay current with new releases.

2.3.1 Do not include undocumented or hidden features in your app; app functionality should be clearly visible to both end users and the App Review team. Egregious or repeated behavior may result in removal from the Apple Developer Program. We work hard to make the App Store a trustworthy ecosystem and expect the same from our app developers; if you're not honest, we won't do business with you.

2.3.2 If your app includes in-app purchases, please ensure that the app description, screenshots, and previews clearly indicate whether there are featured items, levels, subscriptions, etc. that require separate purchase. If you decide to promote in-app purchases on the App Store, make sure the name and description of the IAP display are written for public users and that your app correctly handles the payment API so that customers can seamlessly complete the purchase when your app launches.

2.3.3 Screenshots should show the use of the app, not just the title cover, login page, or initial screen. They can also display text and extended features of the device, such as the Touch Bar.

2.3.4 Preview is a good way to let customers know the appearance and functions of the app. To ensure that customers understand the experience they will have in your app, the preview might only use a video screen captured from your app. Stickers and iMessage extensions bring the user experience to life in the Messages app. You can also add narration along with the video, or add text descriptions to help explain anything that can't be explained through the video alone.

2.3.5 Please select the most appropriate category for your app and refer to the App Store Category Definitions if you need help. We may change the category of the app if the selected category is far from the actual situation.

2.3.6 Please answer the age rating questions honestly in iTunes Connect so that your app is rated consistently with the parental controls. If an app is incorrectly rated, customers may be surprised when they receive the app, or it may prompt an investigation by government regulators.

2.3.7 Please choose a unique app name and specify keywords that accurately describe the app. Do not try to trick the system by packaging any metadata with trademarked terms, names of popular apps, or other irrelevant phrases. App names must be limited to 30 characters and may not contain words or descriptions that are not part of the app name. App subtitles are a great way to provide additional descriptions 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.

2.3.8 Metadata should be appropriate for all audiences, so make sure your icons, screenshots, and previews remain at a 4+ age rating; this should be done even if your app is rated higher. For example, if your app is a game that contains violence, don't choose images that include gruesome deaths or guns aimed at specific characters. The use of the terms “For Kids” and “For Children” in the App Name is reserved for the Kids Category. It is important to ensure that metadata, including app name and icon (small icon, large icon, Apple Watch app, etc.), are similar to each other to avoid confusion.

2.3.9 You are responsible for ensuring that you have the right to use all materials in the App icons, screenshots, and previews, and should display fictitious account information rather than real personal data.

2.3.10 Ensure that your app focuses on the iOS, Mac, Apple TV, or Apple Watch experience and does not include names, icons, or images of other mobile platforms in your app or metadata unless there is specific approved interactive functionality.

2.4 Hardware Compatibility

2.4.1 To ensure that users can make full use of your App, iPhone App should be able to run on iPad as much as possible. We encourage you to consider developing a universal app so that your customers can use it on all their devices. Learn more about Universal App.

2.4.2 Make the App save energy through design. Apps should not quickly drain battery power, generate excessive heat, or place unnecessary strain on device resources.

2.4.3 For Apple TV apps, ensure that users do not need to use hardware input other than the Siri Remote or third-party game controllers, but you are free to provide enhanced functionality for use when other peripherals are connected. If a game controller is required for the user, be sure to clearly indicate this in the metadata so that users know they will need an additional device to play the game.

2.4.4 Apps may not suggest or require restarting a device.

2.4.5 For apps distributed through the Mac App Store, there are a few additional requirements that you need to keep in mind:

(i) These apps must be properly sandboxed and follow the macOS File System Documentation. Additionally, these apps should only use the appropriate macOS APIs to modify user data stored by other apps (such as bookmarks, Address Book, or Calendar entries).

(ii) These apps must be packaged and submitted using the technology provided in Xcode; third-party installers are not allowed. Additionally, these apps must be single, self-contained application installation packages and cannot install code or resources in shared locations.

(iii) These apps may not automatically launch or contain other code that runs automatically when launched, may not log in without consent, or may not spawn a large number of processes that continue to run without consent after the user exits the app. These apps may not automatically add icons to the Dock or leave shortcuts on the user's desktop.

(iv) These apps may not download or install separate apps, kexts, additional code, or resources to add functionality or materially alter the apps we see during our review process.

(v) These apps may not request to escalate to root privileges or use setuid attributes.

(vi) These apps may not display a licensing screen upon launch, require use of a license key, or implement their own copy protection measures.

(vii) These apps must use the Mac App Store to distribute updates; no other update mechanisms are allowed.

(viii) These apps should run on the currently shipped OS and should not use disabled or optional technologies (e.g. Java, Rosetta).

(ix) These apps must include all language and localization support within a single app package.

2.5 Software Requirements

2.5.1 App can only use public APIs. And it must be compatible with the latest released system. Learn more about the public API. Keep your app up to date and ensure you phase out obsolete features, frameworks, or technologies that will no longer be supported in future OS versions.

2.5.2 Apps should be self-contained within their packages and may not read or write data outside the scope of their designated container, nor download, install, or execute code, including other apps. Apps designed to teach, develop, or test executable code may download code in limited circumstances, provided that such code is not used for other purposes. Such apps must use source code provided by the application, which can be fully viewed and edited by the user.

2.5.3 If the App transmits viruses, files, computer codes, or programs that may negatively impact or disrupt the normal operation of the operating system and/or hardware functions (including push notifications and Game Center), the App will be rejected. Egregious or repeated violations may result in removal from the Apple Developer Program.

2.5.4 Multitasking apps are only allowed to use background services to achieve their intended purposes: VoIP, audio playback, geolocation, task completion records, local notifications, etc. If your app uses location-based background mode, remind users that doing so can significantly reduce battery life.

2.5.5 We will conduct the audit on an IPv6 network. If your app is not compatible with IPv6 addressing, it may not pass review.

2.5.6 If your app browses the web, it must use the corresponding WebKit framework and WebKit JavaScript .

2.5.7 Video streaming content longer than 10 minutes over cellular networks must use HTTP Live Streaming and include a baseline 192 kbps HTTP Live Stream.

2.5.8 If an app creates an alternative desktop/home screen environment or simulates a multi-app widget experience, the app will be rejected.

2.5.9 Apps that change the functionality of standard switches (such as volume up/down and ring/silent switches) or change other native user interface elements or behaviors will be rejected. For example, apps should not block links to other apps or other functionality that users expect to work in a certain way. Learn more about handling links correctly.

2.5.10 Apps may not be submitted that contain blank ad banners or test ads.

2.5.11SiriKit

(i) Apps that integrate SiriKit should only register intents that they can handle without support from other apps and that are consistent with the user’s expectations of the described functionality. For example, if your app is a meal planning app, you should not incorporate an intent to start a workout, even if your app shares integration with a fitness app.

(ii) Ensure that the words and phrases in the plist match the SiriKit capabilities of your app and the intents it registers. Aliases must be related to your app or company name and should not be generic terms or include the names of third-party applications or services.

(iii) interpret Siri requests in the most direct manner possible, without inserting any advertising or other marketing messages between the request and its fulfillment. Interstitial UI may be displayed only when necessary to complete the associated task (for example, to allow the user to specify a specific type of workout).

3. Business

There are many ways to monetize your app on the App Store. If your business model isn’t obvious, be sure to explain it in its metadata and App Review notes. If we don't understand how an app works, or if in-app purchases aren't immediately obvious, there will be review delays and your app may be rejected. While you decide the price, we won't distribute apps and in-app purchases that are clearly priced too high. We will reject apps that attempt to deceive users with unreasonably high prices.

If we discover that you have attempted to manipulate reviews to improve rankings through payment, incentives, filter or fake feedback, or ask a third-party service to do so on your behalf, we will take appropriate action to preserve the integrity of the App Store, which may include removal from the Apple Developer Program.

3.1 Payment

3.1.1 In-App Purchases:

If you want to unlock features or functionality within the app (such as subscriptions, in-game currency, game levels, access to premium content, or unlocking the full version, etc.), you must use in-app purchase. Apps can use in-app purchase currency to help users "pay" digital content providers within the app. Apps may not contain buttons, external links, or other calls to action that direct customers to make purchases using non-IAP mechanisms.

All credits and in-game currency purchased through IAP must be usable within the app and must not expire, and you should ensure that a recovery mechanism is designed for all restorable In-App Purchases.

Please be sure to specify the correct purchasable type, otherwise your app will be rejected.

Apps may not directly or indirectly give away IAP content, functionality, or consumables to others.

Apps distributed through the Mac App Store can host plug-ins or extensions based on non-App Store mechanisms.

3.1.2 Subscriptions: Regardless of the category on the App Store, apps can offer auto-renewing in-app purchase subscriptions. When integrating auto-renewable subscriptions into your app, be sure to follow the guidelines below.

3.1.2(a) Permitted Uses: If you offer auto-renewing subscriptions, you must provide ongoing value to your customers. The following is not an exhaustive list, but examples of appropriate subscriptions include: new game levels; serialized content; multiplayer support; apps that provide substantial ongoing updates; access to large collections of media content or ongoing updates; software as a service (SAAS); and cloud service support. also:

Subscriptions are available along with à la carte services. For example, you can offer subscriptions to your entire movie library, as well as individual movie purchases or rentals.

You may offer a single subscription that is shared across your own apps, but such subscriptions may not extend to third-party apps or services. The subscription must apply to all user devices on which the App can be used. Learn more about sharing subscriptions between your apps.

Apps may not force users to rate or review the app, download other apps, or perform other similar actions before they can access the app’s features, content, or use the app.

As with all apps, subscription services should allow users to directly access the items they paid for without having to perform additional tasks such as posting on social media , uploading contacts, or checking in a certain number of times within the app.

Subscriptions may not include consumable credits, in-game currency, etc., even when combined with other services, but you may offer subscriptions that include discounted benefits on consumable items, such as a premium membership that includes discounted gem packs.

If you are changing an existing app to a subscription-based business model, you may not remove key features that existing users have already paid for. For example, after introducing a subscription model for new customers, customers who have purchased a "full game unlock" should continue to have access to the full version of the game.

3.1.2(b) Upgrades and Downgrades: Users should have a seamless upgrade/downgrade experience and should not inadvertently subscribe to multiple versions of the same content. Review best practices for managing subscription upgrade and downgrade options.

3.1.2(c) Subscription Information: Before asking customers to subscribe, you should clearly describe the specific benefits after payment. How many issues are there per month? How big is the cloud storage capacity? Which of your services can be accessed? Also, be sure to clearly state the relevant requirements, namely those described in the "Agreements, Tax, and Banking" section of Schedule 2 of your agreement.

3.1.3 “Reader” Apps: Apps should allow users 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 educational apps for managing student grades and class schedules), as well as consumable items in multi-platform games, so long as you agree not to directly or indirectly direct iOS users to purchase methods other than IAP and the general information about other purchase methods is not intended to discourage the use of IAP.

3.1.4 Content Codes: Apps may not use their own mechanisms to unlock content or functionality, such as license keys, augmented reality markers, QR codes, etc. In a few rare cases, such as when functionality depends on specific hardware capabilities, an app can unlock that functionality without using in-app purchase (for example, an astronomy app that adds functionality after syncing with a telescope). Optional App Features for use with approved physical products (such as toys) can unlock specific functionality without IAP, provided an IAP option is also provided. You may not require users to purchase unrelated products or participate in advertising or marketing activities in order to unlock app features.

3.1.5 Physical Goods and Services Outside the App: If your app allows users to purchase goods or services that will be used outside the app, you must use a purchase method other than IAP to collect payment, such as Apple Pay or a traditional credit card entry. Apps can support the circulation of approved virtual currencies (such as Bitcoin and Dogecoin), provided that the above practices must comply with state and federal laws in areas where the app can be used normally.

3.1.6 Apple Pay: If your app uses Apple Pay, it must provide users with all basic purchase information before selling any goods or services, and must properly use Apple Pay branding and user interface elements. For specific requirements, please refer to the "Apple Pay Identity Guidelines" and "Human Interface Guidelines." Apps that use Apple Pay to provide recurring payment services must disclose at least the following information:

The length of the renewal period; unless canceled, the renewal will continue

What services are provided in each cycle?

The actual amount that will be charged to the customer

How to cancel

3.2 Other business model issues

The list below is not exhaustive, and your app submission may result in changes or updates to our policies, but here are some additional dos and don’ts to keep in mind:

3.2.1 Acceptable

(i) Display your other apps within your app for purchase or promotional purposes, as long as your app does more than simply list other apps.

(ii) Display or recommend third-party apps designed for approved specific needs (such as health management, aviation, and accessibility). Your app should provide ongoing editorial content so that it doesn't seem like just a decoration.

(iii) Access to specific approved rental content (e.g., movies , TV shows, music, books) is prohibited after the rental period ends; all other content services must not have an expiration date.

(iv) Wallet credentials can be used to make or receive payments, transmit transactions, or provide identity verification (e.g. movie tickets, coupons, and VIP credentials). If the Wallet credentials are used for other purposes, your App may be rejected and your Wallet credentials may be revoked.

(v) Insurance apps must be provided free of charge, must comply with the relevant laws of the region where the app is released, and may not use IAP.

(vi) Approved nonprofit organizations may raise funds directly in their own apps or in third-party apps, provided that the fundraising activities offered comply with the App Review Guidelines and support Apple Pay . The application must disclose how the funds will be used, comply with state or local laws, and provide appropriate tax receipts to donors. Provide additional information to application review upon request. Nonprofit platforms that connect donors and other nonprofits must ensure that every app listed on a nonprofit has gone through the nonprofit’s approval process. Learn more - About approval to become a nonprofit organization.

3.2.2 Unacceptable

(i) Create an interface similar to the App Store for displaying third-party apps, extensions, or plug-ins, or use it as a collection of popular apps.

(ii) monetize built-in functionality provided by the hardware or operating system (such as push notifications, camera, or gyroscope) or Apple services (such as access to Apple Music or iCloud storage).

(iii) Apps that artificially increase the number of ad impressions or ad click-throughs, and apps that are primarily designed to display ads.

(iv) Approved non-profit organizations may collect funds for charities and fundraisers within the App. Apps that seek to raise funds for these purposes must be free on the App Store and may only raise funds outside of the app, such as through Safari or text messages.

(v) Forcibly restrict the user base of the App, such as limiting it to specific regions or operators.

(vi) Apps should allow users to directly obtain paid items without having to perform additional tasks, such as posting on social media, uploading contact lists, or checking in a certain number of times within the app. Apps may not force users to rate or review the app, watch videos , download other apps, click on ads , or perform other similar actions before they can access the app’s features, content, or use the app, or receive bonuses or other compensation.

(vii) Artificially manipulate a user’s visibility, status, or ranking on other services unless permitted by the terms and conditions of that service.

(viii) Apps for binary options trading are not allowed on the App Store. Consider using a web application instead.

4. Design

Apple customers value products that are simple, elegant, innovative, and easy to use, and that's what we want to see on the App Store. You can come up with any great design you want, but to be approved for distribution on the App Store, your app must meet the following minimum standards. Also remember that even after your app is approved, you should update it to ensure it functions properly and continues to attract new and existing customers. Apps that stop functioning or degrade in user experience may be removed from the App Store at any time.

4.1 Plagiarists

Please come up with your own ideas. We know you have great ideas, so make them a reality. Please do not simply copy popular apps on the App Store, or just slightly modify the name or UI of other apps and use them for your own purposes. Not only does doing so risk triggering claims of intellectual property infringement, it also makes it more difficult to navigate the App Store and is unfair to your fellow developers.

4.2 Minimum functional requirements

An app should contain functionality, content, and UI, not just a repackaged website. If the app has no practical value, is uninspired, or doesn't really feel like an app, then it doesn't belong in the App Store. If the app doesn't provide lasting entertainment value or is simply creepy, it won't be approved. If your app is just a song or a movie, you should submit it to the iTunes Store. If your app is simply a book or game guide, you should submit it to the iBooks Store.

4.2.1 Apps should use APIs and frameworks to achieve their intended purpose and describe the integration details in the App description. For example, the HomeKit framework should provide home automation services, while HealthKit should be used for health and fitness purposes and integrated into the Health app.

4.2.2 Except for those Apps that fall into specific categories, Apps should not be used solely for marketing materials, advertisements, web clippings, content aggregation or link collections.

4.2.3 The App should be able to work independently without installing other Apps.

4.2.4 Apple Watch apps that resemble watch faces may be confusing because users may assume that these apps work with various device features such as swipe, notifications, and third-party widgets. It's a good idea to use creative ways of representing time as an app interface (for example, a tide clock for surfers), but if your app looks too much like a watch face, we may reject it.

4.2.5 Apps that are primarily used as iCloud and iCloud Drive file managers need to include other app functionality in order to be approved.

4.3 Spam Apps

Please do not create multiple package IDs for the same app. If your app has different versions for specific locations, sports teams, universities, etc., consider submitting a single app and offering in-app purchases to provide the differentiated functionality. Also, avoid developing in categories that are already overcrowded with similar apps; the App Store already has too many apps that simulate fart and burp sounds, as well as flashlight and Kama Sutra apps. Developers who upload a large number of similar versions of apps will be removed from the Apple Developer Program.

4.4 Extended Functionality

Apps that host or include extensions must follow the App Extension Programming Guide or Safari Extensions Development Guide and, where applicable, include a range of features such as help screens and settings interfaces. You should clearly and accurately disclose in your App's marketing copy what Extended Functionality you offer.

4.4.1 Keyboard extensions need to follow some additional rules.

They must:

Provide keyboard input function (such as character input);

Provides a method to switch to the next keyboard;

Can be used even without an Internet connection:

Provide numeric and decimal keyboard types as described in the App Extension Programming Guide;

User activity data is collected only for the purpose of improving the performance of its keyboard extension functionality on iOS devices.

They must not:

Contains marketing, advertising, or in-app purchases;

Launch an app other than Settings; or

Use keyboard keys for other behaviors, such as holding down the Return key to launch the camera, etc.

4.4.2Safari Extension must be run on the latest version of Safari on OS X. They must not interfere with system and Safari UI elements, and must not contain malicious or misleading content or code. Violation of this rule will result in expulsion from the Apple Developer Program. Safari Extensions should not require access to more websites than necessary to function properly.

4.4.3 Emoticon stickers

Stickers are a great way to make Messages more dynamic and interesting, allowing people to express themselves in more clever, fun, and meaningful ways. Whether your app includes an emoji sticker extension or you create a separate emoji sticker pack, its content must not offend users, create a negative experience, or violate relevant laws.

(i) Generally, content that is not suitable for distribution on the App Store is not suitable for inclusion in stickers.

(ii) Consider regional sensitivities and do not make your sticker packs available in countries where this is unacceptable or would violate local laws.

(iii) If the meaning of your sticker is not clear, please include a clear explanation in the review notes to avoid delays in the review process.

(iv) Make sure your stickers are relevant beyond your friends and family; they should not be specific to individual activities, groups, or relationships.

(v) You must hold all necessary copyrights, trademarks, publicity rights and authorization licenses for the content in the emoticon stickers, and may not submit any unauthorized content. Remember that you must be able to provide verifiable documentation upon request. If your app contains emoji sticker content that you do not have the rights to use, the app will be removed from the App Store, and repeat infringers will be removed from the Developer Program. If you believe your content has been infringed by another provider, please submit a claim here.

4.5 Apple Sites and Services

4.5.1 Apps may use approved Apple RSS feeds, such as the iTunes Store RSS feed, but may not scrape any information from Apple sites (such as Apple.com, iTunes Store, App Store, iTunes Connect, Developer Portal, etc.) or use this information for ranking.

(i) While using your App, customers may access their subscriptions through the Apple Music API. Their purpose is to provide simple music playback functionality for Apple Music users. Users must grant Apple Music permission to play and be able to use standard media controls (such as Play, Pause, and Skip) to play; in addition, your app may not require users to gain access to the Apple Music service through payment or indirect monetization methods (such as in-app purchases, advertising, requiring user information, etc.). Do not download, upload, or enable sharing of MusicKit API music files unless explicitly permitted in the MusicKit documentation.

(ii) Use of the MusicKit APIs does not replace a license you may have for deeper or more complex music collections. For example, if you want your app to play a specific song at a specific moment, or create an audio or video file that can be shared on social media, you will need to contact the copyright owner directly to obtain their permission (for example, synchronization or adaptation rights) and assets. Cover art and other metadata may only be used for music playback or playlists (including App Store screenshots demonstrating app functionality) and may not be used in any marketing or advertising without specific authorization from the rights holder. When integrating the Apple Music service into your app, be sure to follow the Apple Music Identity Guidelines.

(iii) Apps that access Apple Music user data (such as playlists and favorites) must clearly disclose this access in the purpose field. Any data collected may not be shared with third parties except to support or improve the App experience. This data may not be used to identify users or devices, or to target advertising.

4.5.3 You may not use Apple services (including Game Center or push notifications) to send spam, conduct phishing, or send unsolicited messages to customers. You may not attempt to locate, track, correlate, mine, harvest or exploit player IDs, aliases or other information obtained through Game Center. If you do this, you will be removed from the Apple Developer Program.

4.5.4 Apps cannot require push notifications, and cannot use this feature for advertising, promotional or direct marketing purposes, or to send sensitive personal or confidential information.

4.5.5 Game Center Player IDs may only be used in ways approved by the Game Center team and may not be displayed in the App or to any third party.

4.6 Backup App Icons

Apps can display customized icons, for example, to reflect sports team preferences, provided that each change is initiated by the user and the app includes a setting to restore the original icons. All icon versions must be relevant to the app's content, and all system resource changes should be consistent so that icons displayed in settings, notifications, etc. match the new springboard icons. This feature is not intended for dynamic, automatic or serial changes, such as reflecting the latest weather information, calendar notifications, etc.

4.7 Third-Party Software

Apps may include or run code provided by third-party developers (such as HTML5-based games) as long as the code is not provided in a store or store-like interface and as long as the software (1) is free or purchased using in-app purchase and (2) uses only functionality available in the standard WebKit view; your app must use WebKit and JavaScript Core to run the third-party software and should not attempt to extend or expose native platform APIs to the third-party software; (3) is provided by a developer that has joined the Apple Developer Program and signed the Apple Developer Program License Agreement; and (4) complies with the terms of these App Review Guidelines (e.g., does not include objectionable content; uses IAP to unlock features and functionality). You must provide an index of your app’s third-party software and available metadata upon request.

5. Legal

Once your app is made available to users in a particular region, it must comply with all legal requirements of that region (if you're not sure, contact a lawyer). We know this stuff is complicated, but it's your responsibility to understand all local laws and ensure your app meets all legal requirements, not just the guidelines listed below. Of course, if the App instigates, promotes or encourages criminal behavior or obviously irresponsible behavior, it will be rejected.

5.1 Privacy

In the Apple ecosystem, protecting user privacy is always the top priority. You will exercise care when processing personal data to ensure that you comply with applicable laws and the terms of the Apple Developer Program License Agreement, and meet the expectations of your customers. In particular:

5.1.1 Data Collection and Storage

(i) If an App collects user information or usage data, it must include a privacy policy and obtain the user’s consent before collecting such information. This includes (but is not limited to) apps that implement HealthKit or other health/medical technologies, HomeKit, keyboard extensions, Apple Pay, stickers, and iMessage extensions; apps that include login information; or apps that access user data on the device (e.g., location, contacts, calendar, etc.).

(ii) If your app does not contain significant account-based functionality, allow users to use it without logging in. Apps should not require users to provide personal information in order to function properly, unless the personal information is directly related to the core functionality of the App or is required by law. If your core app functionality is not related to a specific social network (such as Facebook, WeChat , Weibo, or Twitter, etc.), you must provide access without login or other similar mechanisms. Retrieving basic profile information, sharing to social networks, or inviting friends to use the App are not considered core App functions.

(iii) If an app developed by a developer attempts to secretly collect user passwords or other user private data, the developer will be removed from the Apple Developer Program.

(iv) You must use SafariViewController to display information to the user in a prominent position; the controller must not be hidden or obscured by other views or layers. Additionally, apps may not privately use SafariViewController to track users without the user's knowledge and consent.

5.1.2 Data Use and Sharing

(i) You may not attempt, facilitate or encourage others to reconstruct personal information about users based on data you claim to have collected in an “anonymous,” “statistical,” or other non-identifiable manner. You may not use or transfer a user's personal data without first obtaining the user's permission and providing relevant information about how and where the data is used.

(ii) Data collected by the App may only be used or shared with third parties to improve the user experience or software/hardware performance related to App functionality, or for advertising purposes in accordance with the Apple Developer Program License Agreement.

(iii) Data collected from the HomeKit API may not be used for advertising or other usage-based data mining.

(iv) Apps using Apple Pay may only share user data obtained through Apple Pay with third parties to facilitate or improve the delivery of goods or services.

5.1.3 Health and health research

Health, fitness, and medical data are particularly sensitive, and apps covering these areas must meet additional rules and ensure that customer privacy is protected:

(i) Apps may only use or disclose to third parties data collected in the context of health, fitness, and medical research (including data collected from the HealthKit API, "Motion and Fitness," or human subjects research in the health field) for the purpose of improving health management or health research, with approval, and may not be used for advertising or other data mining based on usage.

(ii) Apps may not write false or erroneous data to HealthKit or any other medical research/health management app, and may not store personal health information in iCloud.

(iii) Apps that conduct human research in the health field must obtain informed consent from the participants. If minors are involved, informed consent must be provided by their parents or guardians. The informed consent form must include the following: (a) the nature, purpose, and duration of the research; (b) the specific procedures, risks, and benefits to participants; (c) information about confidentiality and data handling (including sharing of information with third parties); (d) a contact person to answer participants’ questions; and (e) the withdrawal process.

(iv) Apps used to conduct human research in the health field must be approved by an independent ethics review committee. Evidence of such approval must be provided upon request.

5.1.4 Children

For a number of reasons, you must be careful when processing children’s personal data. We recommend that you carefully review all requirements to comply with relevant laws, such as the Children's Online Privacy Protection Act ("COPPA") and other internationally applicable equivalent laws.

Apps may only request users’ date of birth or parental contact information to comply with applicable child privacy laws, but must provide some useful functionality or entertainment value for users of all ages.

In addition, apps in the "Children's Category" and apps that collect personal information from minors (such as name, address, email, location, photos, videos, drawings, chat capabilities, other personal data, or combine persistent identifiers with any of the above information), transmit such information, or have the ability to share such information must comply with applicable children's privacy protection laws and must have a privacy policy. For clarity, parental control requirements for “child categories” are generally not the same as obtaining parental consent to collect personal data under these privacy regulations.

5.1.5 Positioning Services

You may use location services in your app only if they are directly related to the functionality and services provided by your app. Location-based APIs may not be used to provide emergency services, autonomously control cars , aircraft, and other devices (except for small devices such as lightweight drones and toys), remotely control car anti-theft systems, etc. Always provide notification and obtain user consent before collecting, transmitting or using location data. If your app uses background location services, be sure to explain why in your app; refer to the Human Interface Guidelines for best practices.

5.2 Intellectual Property

Please ensure that your app contains only content that you created or have a license to use. If you cross the line and use content without permission, your app may be removed. Of course, this also means that if someone else plagiarizes your work, their app may also be removed. If you believe your intellectual property has been infringed by another developer on the App Store, please submit a claim through the web form. Laws vary from country to country, but be sure to avoid these common mistakes:

5.2.1 General: You may not use protected third-party materials (such as trademarks, copyrighted works, patented designs) in your App without permission, or include false, plagiarized, or misleading representations, names, metadata , or developer names in your App bundle. The application should be submitted by an individual or relevant legal person who owns or has obtained a license for the intellectual property or other relevant rights and is responsible for providing any services provided by the application.

5.2.2 Third-Party Sites/Services: If your App uses, accesses, monetizes, or displays content from third-party services, please make sure you obtain specific permission to perform such operations under the terms of use of that service. If requested, relevant authorization must be provided.

5.2.3 Audio/Video Downloads: Apps may not facilitate illegal file sharing or provide the ability to save, convert, or download media assets from third-party sources (such as Apple Music, YouTube , SoundCloud, Vimeo) without explicit authorization from those sources. Streaming video/audio content may also violate the terms of use, so be sure to check before accessing these services in your app. If there is a corresponding request, relevant manuscripts must be provided.

5.2.4 Apple Endorsement: You may not mislead or imply that Apple is the source or provider of the App, or that Apple in any way endorses its quality or functionality. If your app is selected as an Editors' Choice, Apple will automatically display the corresponding badge.

5.2.5 Apple Products: You may not create apps that are similar or confusingly similar to existing Apple products, interfaces (such as Finder), apps (such as App Store, iTunes Store, or "Messages"), or advertising themes. Do not misspell the names of Apple products (such as GPS for iPhone, iTunz). iTunes Music Preview Content may not be used for its entertainment value (such as as background music for a photo collage or as voiceover for a game) or in any other unauthorized manner. If your app displays Activity rings, do not modify the look and feel of the rings or the data they represent. The Human Interface Guidelines contain more information about how to use your Activity rings.

5.3 Games, gambling and lotteries

Games, gambling, and lotteries are difficult to regulate and are one of the most regulated app categories on the App Store. This feature should only be included after you have fully verified the legal requirements of all countries where your app will be released, and the review process for this feature will take longer to prepare. Here are some things to keep in mind:

5.3.1 Sweepstakes and competitions must be sponsored by the App developer.

5.3.2 The official rules for sweepstakes, contests, and raffles must be stated in the App and must clearly state that Apple is not a sponsor and is not involved in the activity in any way.

5.3.3App shall not purchase points or currency through IAP for any kind of real currency games; it shall not sell lottery tickets or lottery tickets to users; it shall not transfer funds within the App.

5.3.4 Apps that provide real currency games (such as sports betting, poker, *** games, horse racing) or lottery must obtain the necessary licenses and approvals in the areas where the app is used and can only be published in these areas. Such apps must be available for free in the App Store. Illegal gambling aids , including card counters, are not allowed on the App Store. Lottery apps must have rewards, odds, and prizes.

After Submission

After submitting the app and metadata in iTunes Connect, you will enter the audit process. Keep the following in mind:

Schedule: The App Review team will check your app as soon as possible, and we have been working to reduce review time. Learn more about App Review.

Status update: The current status of the app will be reflected in iTunes Connect, so please pay more attention to this place.

Expedited Request: If you have serious time constraints, you can request an expedited review. Please only request an expedited review if you truly need one, so that other developers' expedited requests are not affected. If we find that you are abusing this system we may reject your application from now on.

Release Date: If you set a future release date, the app will not appear on the App Store even if you have approved the App Review team before this day arrives. Please note that it may take up to 24 hours for your app to appear in all selected stores.

No: Our goal is to follow these guidelines fairly and consistently, but no one is perfect. If your app is rejected but you have questions or would like to provide additional information, please use the Solution Center to communicate directly with the App Review team. This can help your app appear in the store, it can also help us improve the App Review process, and find out what needs to be clarified in our policies. If you are still not satisfied with the outcome, please submit an appeal.