AppStore latest review guidelines 2017

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 first-time developer or a large team of experienced programmers , we welcome you to create apps for the App Store and want to help you understand our guidelines to ensure your apps make it through the review process quickly.

The guiding principles of the App Store are simple: we want to provide a safer and more reliable experience for users to acquire apps, and give all developers an opportunity to succeed with their 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:

Many children download a large number of apps from us. While parental controls are effective in protecting children, you must also do your part. You know, we are always keeping an eye on these children.

The App Store is a great way to share apps with hundreds of millions of people around the world. If you're developing apps just to distribute to friends and family, then the App Store isn't the best place to go. At this time, you can consider using Ad Hoc distribution or joining the Enter pr ise Program. If you’re new to app development, learn more about the Apple Developer Program.

If we believe any content or behavior in an app falls outside acceptable boundaries, 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 trying 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. Safety

1.1 Objectionable Content

1.2 User-Generated Content

1.3 Children Category

1.4 Personal Injury

1.5 Developer Information

1. performance

2.1 App Completion

2.2 Beta Testing

2.3 Accurate metadata

2.4 Hardware Compatibility

2.5 Software Requirements

1. 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

1. design

4.1 Plagiarists

4.2 Minimum functional requirements

4.3 Duplicate App

4.4 Extension

4.5 Apple Sites and Services

4.6 Alternative App Icons

4.7 Third-Party Software

1. law

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 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 works as expected or you are no longer actively supporting 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 your 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 IAPs (in-app purchases) 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 GuideApp Extension Programming GuideiOS Data Storage GuidelinesmacOS File System DocumentationSafari Extensions Development GuideiTunes Connect Developer GuideDesign Guidelines

iOS Human Interface GuidelinesmacOS Human Interface Guidelines tvOS Human Interface Guidelines watchOS Human Interface GuidelinesBranding and Marketing Guidelines

App Store Marketing GuidelinesApple Pay Identity GuidelinesAdd to Apple Wallet GuidelinesGuidelines for Using 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 do not damage users' devices, and that do not cause physical harm when used. We've listed the main safety concerns below. If you intend to intimidate or attack others, your app is not appropriate 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 Graphic 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 promote the purchase of arms.

1.1.4 Excessively pornographic content (Merriam-Webster defines pornography as sexually explicit descriptions or displays of sexual organs or activities intended to stimulate sexual pleasure rather than 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, including 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”, this principle cannot be violated. Apps that support anonymous or prank calls or SMS/MMS will be rejected.

1.1.7 App Store Reviews:

App Store customer reviews are an integral part of the app experience; therefore, you should be respectful when responding to customer reviews. Additionally, your response should directly address the topic of the customer review and should not include personal information, spam, or marketing advertisements in your response.

Prompt users to review your app using our API: This convenience feature lets customers leave ratings and reviews directly on the App Store without leaving your app; scheduled review prompts are not allowed.

1.2 User-Generated Content

For apps that include 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 could be disruptive to children unless they are kept in a designated area with parental controls. Keep in mind that once customers deem your app to meet the Kids Category requirements, your app will need to continue to meet those guidelines in subsequent updates, 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

If an app behaves in a way that could cause physical harm, we may reject it. For example:

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

Apps must clearly disclose the data and methods used to support the accuracy of the health measurements claimed. If the accuracy or methods cannot be verified, we will reject the app. For example, if an app claims to be able to take X-rays, measure blood pressure, temperature, blood sugar concentration, or blood oxygen content using only the sensors on the device, the app will be rejected.

Apps should remind users that in addition to using the app, they should consult a doctor before making medical decisions.

If your medical app has received regulatory approval, please submit a link to the relevant documentation along with your app.

1.4.2 Medication dosage calculators must be from a pharmaceutical manufacturer, hospital, university, health insurance company, or other entity 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 Any app that encourages the use of tobacco products, illegal drugs, or excessive alcohol consumption is not permitted on the App Store. Apps that encourage minors to ingest any of the above substances will be rejected. Facilitating the sale of marijuana, tobacco or controlled substances (except at an authorized pharmacy) is also not allowed.

1.4.4 Apps 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 violates Apple hardware safety documentation or in a manner that could cause harm to the device or to persons. For example, apps should not encourage placing a device under a mattress or pillow while charging or subjecting it to excessive write cycles to a solid-state drive. 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 necessary metadata and fully functional URLs; placeholder text, blank websites, and other temporary content should be cleared before submission. Before submitting your app, be sure to test it on a device for bugs and stability; if your app requires a login, provide demo account information (and turn on your backend service!). If you offer in-app purchases in your app, make sure they are visible to the reviewer and 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 Testing

Demos, betas, and trials of your app are not suitable 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. Major updates to your beta app should be submitted to the TestFlight App Review team before being distributed to your testers. For more information, 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 aren't honest, we won't do business with you.

2.3.2 If your app includes in-app purchases, make sure your 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 you write publicly readable IAP display names and descriptions, and ensure that your app properly handles the Purchase Intent API so that customers can seamlessly complete their purchases once your app is available.

2.3.3 Screenshots should show the app in action, not just the title cover, login page, or splash screen. Screenshots can also include text descriptions and showcase extended features on the device, such as the Touch Bar.

2.3.4 Previews are a great way to let customers know what your app will look like and do. To ensure that customers understand the experience they will have in the app, previews can only use video screen captures from the app. Stickers and iMessage extensions bring the user experience to 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 in iTunes Connect honestly 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, specify keywords that accurately describe the app, and 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 include prices, words, or descriptions that are not part of the app name. Your app subtitle is a great place to provide detailed background information about your app; it must follow our standard metadata rules and may not include inappropriate content, mention other apps, or make unsubstantiated product claims. Apple may modify inappropriate keywords at any time.

2.3.8 Metadata should be appropriate for all audiences, so make sure your app and in-app purchases' associated icons, screenshots, and previews maintain an age rating of 4+, 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. Only apps in the "kids category" can use terms like "suitable for toddlers" and "suitable for kids" in their names. 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 your 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 imagery from 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 take full advantage of your app, iPhone apps should run on iPad whenever possible. We encourage you to consider developing a universal app so that your customers can use it on all their devices. Learn more about the 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 app 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 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 must not request escalation to root privileges or use setuid attributes.

(vi) These apps may not display a license screen at 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 currently released 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 bundle.

2.5 Software Requirements

2.5.1 Apps may only use public APIs and must run on currently released OS. Learn more about the public API. Keep your app up to date, making sure to phase out any outdated 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. Only in special cases, apps for teaching, developing, or testing executable code may download the provided code, but such code may not be used for other purposes. Such apps must open the source code provided by the app so that customers can fully view and edit the source code.

2.5.3 Apps will be rejected if they transmit viruses, files, computer code, or programs that could negatively impact or disrupt the normal operation of the operating system and/or hardware functionality, including Push Notifications and Game Center. Repeated or egregious violations may result in a developer being removed from the Apple Developer Program.

2.5.4 Multitasking apps are only allowed to use background services when achieving their intended purpose: 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 over IPv6 networks. 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 Apps that create an alternative desktop/home screen environment or simulate a multi-app widget experience will be rejected.

2.5.9 Apps that alter or disable the functionality of standard switches, such as volume up/down and ring/silent switches, or that alter or disable other native user interface elements or behaviors will be rejected. For example, apps should not block links to other apps or features that users expect to function in a certain way. Learn more about how to properly handle links.

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

2.5.11 SiriKit

(i) Apps that integrate SiriKit should only register intents that they can handle without support from other apps and that match 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. Nicknames must be directly related to your app or company name and may not use generic terms or include third-party app names 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. An interstitial user interface MAY be displayed only when necessary to complete the associated task (for example, to allow the user to specify a specific type of workout).

2.5.12 Apps that use CallKit or include an SMS Fraud Extension should only block phone numbers that have been confirmed to be used to send spam. Apps with call, SMS, or MMS blocking features or spam identification features must clearly identify these features in their marketing text and explain the criteria for inclusion in blocking and spam lists. The data obtained through these tools may not be used for any other purpose not directly related to operating or improving your app or extension (for example, the data may not be used, shared, or sold for purposes such as tracking or creating user profiles).

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 your app works, or if in-app purchases aren't self-explanatory, there will be review delays and your app may be rejected. Although 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 are attempting to manipulate reviews to improve rankings through payment, incentives, filter or falsified feedback, or asking a third-party service to do so on your behalf, we will take appropriate action to protect the integrity of the App Store. Action taken 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 offer in-app purchase currency for customers to “tip” 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 game currency purchased through IAP 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 their category on the App Store, apps may 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, they must provide ongoing value to customers, last at least seven days, and be accessible on all of the user’s devices. The following is not an exhaustive list, but examples of appropriate subscriptions include: new game levels; serialized content; multiplayer support; apps that provide ongoing substantial 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 of the user's devices on which the app can be used. Learn more about sharing subscriptions between your apps.

Apps should 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 paying. How many instalments are there per month? How much cloud storage capacity is required? Which specific services can be accessed? Also, be sure to clearly state the relevant requirements, which are 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) and consumable items in multi-platform games, provided that you agree not to directly or indirectly direct iOS users to use non-IAP mechanisms for purchase and do not intentionally discourage users from using IAP in your general communications about other purchase methods.

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 using IAP, provided that an IAP option is also provided. You may not require users to unlock app features by purchasing unrelated products or engaging in advertising or marketing activities.

3.1.5 Physical Goods and Services Outside the App: If your app allows users to purchase goods or services to 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 cancelled, 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 a standalone app.

(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 nonprofits may run fundraising campaigns within their own apps or third-party apps, provided those fundraising campaigns comply with all App Review Guidelines and provide support for Apple Pay. Such apps must disclose the intended use of funds, comply with all necessary local and federal government laws, and ensure that appropriate tax receipts are provided to donors. Additional information should be provided to the App Review team upon request. Nonprofit platforms that introduce donors to other nonprofits must ensure that every nonprofit listed in the app has gone through the nonprofit approval process. Learn more about becoming an approved 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 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 whose primary design purpose is to display advertisements.

(iv) raise funds for charities and fundraisers within the app, unless you are an approved non-profit organization or have obtained permission pursuant to 3.2.1 (vi) above. Apps seeking 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 SMS.

(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 require users to rate or review the app, watch videos, download other apps, click on ads, or perform other similar actions before accessing the app’s features, content, or use the app, or before accepting cash or other compensation.

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

(viii) Apps that facilitate binary options trading are not permitted on the App Store. Please consider using the web app.

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 apps that are approved for distribution on the App Store must meet the following minimum standards. Also remember that even after your app is approved, you should update it to ensure that it works properly and continues to attract new and existing customers. Apps that cease to function or whose experience degrades 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 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 your app doesn't have any useful value, isn't innovative, 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 just 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 purposes 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 directory apps, apps should not be used solely for marketing materials, advertisements, web clippings, content aggregation, or collection of links.

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 additional app functionality in order to be approved.

4.2.6 Apps created using commercial templates or app generation services will be rejected.

4.3 Duplicate App

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 different 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 is available.

4.4.1 Keyboard extensions are subject to additional rules.

They must:

Provide keyboard input function (such as character input);

If your keyboard contains images or emojis, follow the sticker guidelines;

Provides a method to switch to the next keyboard;

Can be used without an Internet connection and without requiring full access permissions;

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.2 Safari Extension must run on the latest version of Safari on macOS. 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 contains sticker extensions or you create separate sticker packs, the 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 would be unacceptable or would violate local law.

(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 such information for ranking.

4.5.2 Apple Music

(i) The MusicKit API enables customers to access their subscriptions while using your app. They are designed to provide an easy and simple music playback experience for Apple Music subscribers. Users must be able to initiate Apple Music streaming and navigate through the music content using standard media controls such as Play, Pause, and Skip. Additionally, your app may not require users to pay or use indirect monetization methods to gain access to the Apple Music service (e.g., in-app purchases, advertising, requests for use of user information, etc.). Do not download, upload, or share music files derived from the MusicKit API unless explicitly allowed in the MusicKit documentation.

(ii) Use of the MusicKit API does not replace the licenses you may need for deeper or more complex music integrations. 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 holder directly to obtain permission (such as synchronization or adaptation rights) and assets. Cover artwork and other metadata may only be used in connection with music playback or playlists (including App Store screenshots demonstrating app functionality) and may not be used for any marketing or advertising purposes without the express authorization of the copyright 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 such access in the purpose string. Any data collected may not be shared with third parties or used for any purpose other than to support or improve the app experience. This data may not be used to identify users or devices, or for advertising targeting purposes.

4.5.3 You may not use Apple services (including Game Center or push notifications, etc.) 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. Otherwise, you will be removed from the Apple Developer Program.

4.5.4 Apps may not require push notifications, and may not use push notifications 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 within the app or to any third party.

4.6 Alternative App Icons

Apps may use custom icons to convey specific information (such as expressing favorites for a sports team), provided that each change is initiated by the user and the app includes a setting to revert to the original icon. All icon variations must be relevant to the content of your app, and changes should be consistent across all system assets so that icons displayed in places like Settings and Notifications match the new Springboard icon. This feature should not be used for dynamic, automatic, or continuous changes, such as to reflect updated weather information and calendar notifications.

4.7 Third-Party Software

Apps may include or run code provided by third-party developers (such as HTML5-based games), provided that such code is not available in a store or store-like interface and the software (1) is free or available for purchase through in-app purchase; (2) uses only functionality provided by standard WebKit views; your app must use WebKit and JavaScript Core to run the third-party software and must not attempt to extend or disclose native platform APIs to third-party software; (3) is provided by a developer who has joined the Apple Developer Program and signed the Apple Developer Program License Agreement; and (4) complies with the terms of the various App Review Guidelines (e.g., does not contain objectionable content; uses IAP to unlock features and functionality). You must provide index information about third-party software and metadata included in your app when requested.

5. Legal

As long as your app is available to users in a certain region, it must comply with all legal requirements of that region (if you are 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 the app collects user information or usage data, it must have a privacy policy and obtain user consent before collecting any 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 contain login information; or apps that access user data on the device. The app description should indicate what types of content the app requests access to (e.g., location, contacts, and calendars) and explain what features of the app will not work properly if the user does not grant permission.

(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 the app developed by the 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 a SafariViewController to prominently display information to the user; the controller must not be hidden or obscured by other views or layers. In addition, 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, assist or encourage others to identify or reconstruct user profiles based on data that you claim to have collected in an “anonymous,” “aggregate,” or other non-identifiable manner. The user's personal data may not be used or transferred unless the user's permission is first obtained and relevant information about how and where the data is used is provided.

(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 the App’s 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, "Activity and Fitness," or human subjects research in the health field) for the purpose of improving health management or health research, with permission, and may not use it for advertising or other data mining based on usage.

(ii) Apps may not write false or inaccurate 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 obtained from 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 Location 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 the reason 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 authorization; nor may you include false, plagiarized, or misleading representations, names, or metadata in your app package or developer name. The app submitter should be an individual or legal entity that owns or is authorized to use the intellectual property and other relevant rights, and should be responsible for providing any services in the app.

5.2.2 Third-Party Sites/Services: If your app uses, accesses, monetizes, or displays content from third-party services, make sure you have specific permission to do so under the terms of use for 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 (e.g., 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 your app accesses these services. 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). Apps and extensions (including third-party keyboards and sticker packs) may not include Apple emoji. iTunes Music Preview Content may not be used for its entertainment value (such as as background music for a photo collage or as a soundtrack 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

Gambling, games, 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 indicate that Apple is not a sponsor or involved in the activity in any way.

5.3.3 Apps may not purchase points or currency through IAP for use in any kind of real money gaming; may not sell lottery or raffle tickets to users; or may not transfer funds within the app.

5.3.4 Apps that offer real money gaming (e.g. sports betting, poker, casino games, horse racing) or lotteries must obtain the necessary licenses and approvals in the regions where the app is used and may only be released in those regions, and such apps must be available free of charge on 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

Once you submit your app and metadata in iTunes Connect, you'll immediately enter the review process. Keep the following in mind:

Timeline: The App Review team will review your app as quickly as possible, and we’re always working to reduce review times. Learn more about App Review.

Status Updates: The current status of your app will be reflected in iTunes Connect, so please pay attention here.

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 your app to be released on a future date, it won't appear on the App Store until that date, even if it's approved by the App Review team. 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 has been rejected and you have questions or want to provide additional information, please use the Resolution Center to communicate directly with the App Review team. This helps your app get included in the store, and also helps us improve the App Review process and identify areas that need clarification in our policies. If you are still not satisfied with the outcome, please submit an appeal.