Apple App Store policies, explained.
Apple cited a rule. Let's find out what it means for your app. Browse by guideline number, or search the wording in your rejection.
117 policy guides for iPhone and iPad. Lettered clauses and examples are explained within their policy pages.
Safety
- App Store 1.1 rejection: Objectionable contentApple flagged your content, but "objectionable" doesn't tell you which screen needs work. Guideline 1.1 covers several different problems, from discriminatory material to misleading features.Apple App Store
- App Store 1.1.1 rejection: Discrimination and targeted abuseYour app may describe itself as a joke or a community, but Apple reviews what people can actually read and do.Apple App Store
- App Store 1.1.2 rejection: Violent contentA violence rejection can concern the material itself, even if you've selected an adult age rating. Apple's 1.1.2 addresses realistic depictions of severe harm and content that encourages violence.Apple App Store
- App Store 1.1.3 rejection: Weapons and dangerous objectsApple's concern may be what your app enables, rather than whether a weapon appears on screen. Guideline 1.1.3 covers encouragement of illegal or reckless weapon use and features that help people buy firearms or ammunition.Apple App Store
- App Store 1.1.4 rejection: Sexual content and exploitationAn adult-only setting doesn't resolve every sexual-content rejection. Under 1.1.4, Apple prohibits pornographic material and apps used for prostitution, trafficking, or sexual exploitation.Apple App Store
- App Store 1.1.5 rejection: Religious commentary and quotationsApple has questioned the content in your app, and changing its age rating may not address the issue.Apple App Store
- App Store 1.1.6 rejection: False features and prank communicationsCalling a feature "for entertainment" doesn't settle a 1.1.6 rejection. Apple applies this rule to false information, fabricated device readings, and deceptive functionality.Apple App Store
- App Store 1.1.7 rejection: Exploiting sensitive eventsYour app may mention a current event for a legitimate reason. Apple's 1.1.7 targets harmful concepts that exploit or profit from events such as violent conflicts, terrorist attacks, and epidemics.Apple App Store
- App Store 1.2 rejection: User-generated content and moderationYou've added a report button, but Apple still asks about moderation. Guideline 1.2 covers the whole process: filtering objectionable posts, receiving and responding to reports, blocking abusive users, and giving people a way to contact you.Apple App Store
- App Store 1.2.1 rejection: Creator contentYour creators make the content, but you're still responsible for what the app distributes. Apple treats creator experiences under 1.2.1 as user-generated content within a consistent app experience.Apple App Store
- App Store 1.3 rejection: Kids CategoryYou've built an app for children, and Apple is checking more than its content. Guideline 1.3 covers links, purchases, outside distractions, advertising, and data collection in Kids Category apps.Apple App Store
- App Store 1.4 rejection: Physical harmApple is questioning whether following your app could hurt someone. Guideline 1.4 brings together medical claims, dosage tools, substance-related features, road-safety information, and dangerous activities.Apple App Store
- App Store 1.4.1 rejection: Medical claims and measurementsApple has asked how your health feature works. Under 1.4.1, measurement claims need a disclosed method and support for their accuracy.Apple App Store
- App Store 1.4.2 rejection: Drug dosage calculatorsA correct-looking calculation isn't the only issue in a dosage-app rejection. Apple's 1.4.2 limits who can provide these tools: specified healthcare organizations and other approved entities, or apps with the relevant regulatory approval.Apple App Store
- App Store 1.4.3 rejection: Tobacco, drugs, and alcoholYour app may have an age gate, but Apple also reviews what it encourages or sells. Guideline 1.4.3 addresses promotion of tobacco, vaping, illegal drugs, excessive drinking, and use of these substances by minors.Apple App Store
- App Store 1.4.4 rejection: DUI checkpoints and road safetyApple's 1.4.4 makes the source of a checkpoint important. An app may display DUI checkpoints published by law enforcement; a crowd-submitted marker doesn't automatically meet that condition.Apple App Store
- App Store 1.4.5 rejection: Dangerous challenges and device useA challenge can be optional and still raise a 1.4.5 concern. Apple applies this rule when the app urges someone to take part in activities or use a device in ways that could harm them or other people.Apple App Store
- App Store 1.5 rejection: Developer contact informationYour app can work perfectly and still leave users with no way to reach you. Apple's 1.5 requires an easy contact route in the app and at its Support URL.Apple App Store
- App Store 1.6 rejection: Data securityApple has raised a security concern, and a privacy-policy edit won't fix an exposed account or data flow.Apple App Store
- App Store 1.7 rejection: Reporting criminal activityA community reporting feature can trigger 1.7 even if you don't describe the app as a police service.Apple App Store
Performance
- App Store 2.1 rejection: App completenessApple couldn't finish reviewing your app. A 2.1 rejection can mean a crash, an incomplete screen, missing information, or a purchase the reviewer couldn't reach.Apple App Store
- App Store 2.2 rejection: Beta apps and TestFlightYour app may be ready for feedback before it's ready for the public store. Apple's 2.2 directs demos and beta versions to TestFlight.Apple App Store
- App Store 2.3 rejection: Accurate store metadataApple found a mismatch between the app and what you say about it. Under 2.3, metadata means the information around the app: its description, images, previews, privacy answers, and other store fields.Apple App Store
- App Store 2.3.1 rejection: Hidden features and misleading claimsYour app may behave differently for the reviewer than it does for customers. Guideline 2.3.1 requires Apple to see and understand the features being submitted.Apple App Store
- App Store 2.3.2 rejection: Showing which features cost extraA screenshot can make a paid feature look included with the download. Apple's 2.3.2 requires the listing and previews to make extra purchases clear.Apple App Store
- App Store 2.3.3 rejection: App screenshotsYou've uploaded polished artwork, but Apple wants to see the app. Guideline 2.3.3 says screenshots should demonstrate actual use, rather than consisting only of a title image, login page, or splash screen.Apple App Store
- App Store 2.3.4 rejection: App preview videosYour preview may explain the idea well but still show something other than the app. Under 2.3.4, Apple requires app previews to use captures of the app itself.Apple App Store
- App Store 2.3.5 rejection: Choosing the app categoryApple thinks your app is in the wrong category. Guideline 2.3.5 asks you to choose the category that best describes the product, using Apple's category definitions.Apple App Store
- App Store 2.3.6 rejection: Accurate age ratingsYou may have rated your own content accurately while overlooking what users or a linked service can add.Apple App Store
- App Store 2.3.7 rejection: App names, subtitles, and keywordsApple has flagged the words around your app, not necessarily its code. Guideline 2.3.7 requires a distinctive name and accurate, relevant metadata.Apple App Store
- App Store 2.3.8 rejection: Public-facing icons and imagesYour app's age rating doesn't set the audience for its store images. Apple's 2.3.8 requires public metadata, including app and purchase icons, screenshots, and previews, to be suitable for a 4+ audience.Apple App Store
- App Store 2.3.9 rejection: Rights and privacy in store assetsA screenshot can be technically accurate and still expose someone else's information or use artwork without permission.Apple App Store
- App Store 2.3.10 rejection: Other platforms in an App Store listingYou may have reused a screenshot from another release, and Apple noticed. Guideline 2.3.10 asks the app and its metadata to focus on the Apple-platform experience.Apple App Store
- App Store 2.3.11 rejection: Pre-order promisesA pre-order is a promise about the app people will receive. Apple's 2.3.11 requires a complete, deliverable submission and an eventual release that isn't materially different from what you advertised.Apple App Store
- App Store 2.3.12 rejection: What's New release notes"Bug fixes and improvements" can be accurate, but it doesn't describe a new payment model or a major feature.Apple App Store
- App Store 2.3.13 rejection: In-app eventsApple may be questioning the event card even when the app itself works. Guideline 2.3.13 requires an eligible event, accurate event-specific metadata, correct timing, and a deep link that reaches the event inside the app.Apple App Store
- App Store 2.4 rejection: Hardware compatibilityThe reviewer may be using a device you didn't test. Apple's 2.4 groups several hardware concerns together, so start with the exact subrule, device model, and operating-system version in the notice.Apple App Store
- App Store 2.4.1 rejection: iPhone apps on iPadYour iPhone build can be reviewed on an iPad. Under 2.4.1, Apple says iPhone apps should run on iPad whenever possible.Apple App Store
- App Store 2.4.2 rejection: Battery, heat, and background workloadThe app can appear responsive while doing unnecessary work in the background. Guideline 2.4.2 addresses rapid battery drain, excessive heat, damaging resource use, and unrelated background processes, including cryptocurrency mining.Apple App Store
- App Store 2.4.4 rejection: Unnecessary device or system changesA troubleshooting prompt can itself be the problem Apple flags. Under 2.4.4, apps shouldn't require or suggest device restarts or system-setting changes unrelated to their core functionality.Apple App Store
- App Store 2.5 rejection: Software requirementsThe app works on your phone, but Apple has flagged how it uses the system. Guideline 2.5 covers technical requirements that can come from your code or a library bundled with it.Apple App Store
- App Store 2.5.1 rejection: Public APIs and intended framework useYou may not have added the rejected API yourself. Under 2.5.1, the app and its dependencies need to use public APIs, support the current operating system, and use frameworks for their intended purpose.Apple App Store
- App Store 2.5.2 rejection: Downloaded code and app containersDownloading content and downloading a new feature aren't the same review question. Apple's 2.5.2 requires apps to stay within their designated storage area and restricts downloading or executing code that introduces or changes functionality.Apple App Store
- App Store 2.5.3 rejection: Harmful code and system disruptionApple has identified behavior that could harm the device or interfere with system services. Under 2.5.3, responsibility includes code and files your app transmits, even when a third-party component introduced them.Apple App Store
- App Store 2.5.4 rejection: Background modesA background mode may have been added to keep the app alive, but Apple expects it to serve its documented purpose.Apple App Store
- App Store 2.5.5 rejection: IPv6-only networksYour home Wi-Fi test can pass while Apple's network test fails. Guideline 2.5.5 requires the app to work on IPv6-only networks, so the problem may be an address or networking library rather than a broken server.Apple App Store
- App Store 2.5.6 rejection: WebKit and alternative browser enginesAn embedded browser can bring its own review requirements. Under 2.5.6, apps browsing the web generally need the appropriate WebKit technologies.Apple App Store
- App Store 2.5.8 rejection: Replacement home screensYour app may present a launcher-style interface, but Apple distinguishes an app's own screen from a replacement system environment.Apple App Store
- App Store 2.5.9 rejection: System buttons and expected behaviorA custom interaction can surprise users in ways Apple doesn't allow. Guideline 2.5.9 addresses changes to standard switches and native behavior, including volume controls, silent-mode controls, and expected links to other apps.Apple App Store
- App Store 2.5.11 rejection: SiriKit and ShortcutsA Shortcut may run correctly but still ask Siri to do something your app doesn't actually provide. Guideline 2.5.11 covers the actions you register, the words used to invoke them, and what happens before the task completes.Apple App Store
- App Store 2.5.12 rejection: Call and message spam blockingApple wants to know why a number is blocked and what happens to the information your app sees. Guideline 2.5.12 limits blocking to confirmed spam and requires clear disclosure of the feature and list criteria.Apple App Store
- App Store 2.5.13 rejection: Facial recognition for authenticationUsing the camera to recognize a face isn't automatically an acceptable replacement for system authentication.Apple App Store
- App Store 2.5.14 rejection: Recording consent and indicatorsA permission granted earlier doesn't necessarily tell someone that recording is happening now. Apple's 2.5.14 requires explicit consent and a clear visual or audible indication when the app records or logs user activity.Apple App Store
- App Store 2.5.15 rejection: Files and iCloud document accessYour custom picker may show your own storage but leave out documents people keep on the device or in iCloud.Apple App Store
- App Store 2.5.16 rejection: Widgets, extensions, and App ClipsA widget or notification is part of the app's experience, even when it appears outside the app. Under 2.5.16, those surfaces need to relate to the app's content and functionality.Apple App Store
- App Store 2.5.17 rejection: Matter pairing and certificationA Matter device may pair in your tests while the integration still misses Apple's requirements. Guideline 2.5.17 requires Apple's Matter support framework to initiate pairing and sets certification conditions for other Matter software components.Apple App Store
- App Store 2.5.18 rejection: Advertising placement and controlsYour ad provider supplies the creative, but Apple reviews it as part of your app. Guideline 2.5.18 covers where ads appear, their suitability, targeting information, dismissal controls, and reporting.Apple App Store
Business
- App Store 3.1 rejection: PaymentsA payment rejection starts with what the customer is buying. Apple's 3.1 separates digital access, subscriptions, physical goods, and specific exceptions.Apple App Store
- App Store 3.1.1 rejection: In-app purchases and digital accessIf a payment gives someone a digital feature inside the app, Apple generally expects in-app purchase.Apple App Store
- App Store 3.1.2 rejection: SubscriptionsA subscription rejection can concern the offer itself, how plans interact, or what the paywall tells people.Apple App Store
- App Store 3.1.3 rejection: Other purchase methodsHaving a website checkout doesn't tell you whether your app can use it. Guideline 3.1.3 describes particular kinds of purchases and services that can qualify for another payment route.Apple App Store
- App Store 3.1.4 rejection: Hardware-specific paid featuresA hardware purchase can justify some access without in-app purchase, but only under the conditions in 3.1.4.Apple App Store
- App Store 3.1.5 rejection: Cryptocurrency servicesA crypto rejection can concern who operates the service, where it's licensed, or what the phone does.Apple App Store
- App Store 3.2 rejection: Other business modelsApple's concern may be how your product operates rather than whether checkout succeeds. Guideline 3.2 groups allowed arrangements and prohibited practices, with conditions that depend on the service and its operator.Apple App Store
- App Store 3.2.1 rejection: Conditionally allowed business modelsApple may allow your business model but still require evidence that its conditions are met. Guideline 3.2.1 covers several unrelated arrangements.Apple App Store
- App Store 3.2.2 rejection: Prohibited business practicesA 3.2.2 rejection can point to very different problems. The clause in parentheses identifies the one Apple means.Apple App Store
Design
- App Store 4.1 rejection: Copycats and impersonationYou've built your own app, but Apple sees a copy of someone else's. Guideline 4.1 concerns the product's identity and experience, including copied interfaces, impersonation, and unauthorized branding.Apple App Store
- App Store 4.2 rejection: Minimum functionalityYou've built an app, and Apple says it doesn't do enough. Before adding features, check whether the reviewer reached the experience you intended.Apple App Store
- App Store 4.2.1 rejection: ARKit experiencesApple cited 4.2.1 because the augmented reality feature may do too little. This rule is specifically about ARKit experiences, rather than the whole of minimum functionality under 4.2.Apple App Store
- App Store 4.2.2 rejection: Marketing apps and collections of linksYour app may contain a lot of pages without giving someone much to do. Guideline 4.2.2 rejects apps whose main purpose is marketing material, ads, web clippings, aggregated content, or links, with an exception for catalogs.Apple App Store
- App Store 4.2.3 rejection: Independent operation and first-launch downloadsApple may be blocked before reaching your app's useful part. Guideline 4.2.3 separates dependence on another installed app from the way you obtain initial resources.Apple App Store
- App Store 4.2.6 rejection: Templates and app-generation servicesUsing an app-building tool doesn't by itself explain a 4.2.6 rejection. Apple's rule focuses on who submits template-based apps and whether they provide a customized, useful experience.Apple App Store
- App Store 4.2.7 rejection: Remote desktop clientsA remote-desktop rejection can turn on where the software runs and who owns the host. Guideline 4.2.7 sets conditions for clients mirroring specific software or services.Apple App Store
- App Store 4.3 rejection: Spam and repetitive appsA 4.3 rejection can concern multiple versions of your own app or an experience Apple considers too similar to what's already available.Apple App Store
- App Store 4.4 rejection: App extensionsThe main app may pass your checks while an extension creates the rejection. Guideline 4.4 requires extensions to follow the relevant Apple programming guidance, be accurately described, and avoid marketing, advertising, or in-app purchases inside the extension.Apple App Store
- App Store 4.4.1 rejection: Keyboard extensionsYour keyboard has to remain a usable keyboard even when someone declines broader access. Guideline 4.4.1 requires typing functionality, a way to switch to the next keyboard, and operation without full network or full-access permission.Apple App Store
- App Store 4.4.2 rejection: Safari extensionsA Safari extension can work on one page while asking for access to far more sites than it needs. Guideline 4.4.2 requires current Safari compatibility, appropriate website access, and respect for Safari and system interface behavior.Apple App Store
- App Store 4.5 rejection: Apple servicesAn Apple API being available doesn't permit every use of the data it returns. Guideline 4.5 groups requirements for several Apple services, with separate rules for content, identifiers, notifications, and artwork.Apple App Store
- App Store 4.5.1 rejection: Scraping Apple sitesA publicly visible Apple page isn't automatically an allowed data feed. Guideline 4.5.1 allows approved Apple RSS feeds but prohibits scraping Apple sites and creating rankings from the scraped information.Apple App Store
- App Store 4.5.2 rejection: Apple MusicMusicKit provides access to a service, but it doesn't grant every music right or every use of someone's library.Apple App Store
- App Store 4.5.3 rejection: Unsolicited messages through Apple servicesA system notification or Game Center feature isn't a shortcut to contacting people who haven't asked for it.Apple App Store
- App Store 4.5.4 rejection: Push notification consentA person can allow notifications without agreeing to every promotional message. Under 4.5.4, the app must work without push permission, avoid sensitive or confidential information in pushes, and obtain explicit in-app consent for promotional notifications.Apple App Store
- App Store 4.5.5 rejection: Game Center player identifiersA Player ID can be useful to your integration without being appropriate to display or share. Apple's 4.5.5 limits Game Center IDs to uses allowed by its terms and says not to expose them in the app or to third parties.Apple App Store
- App Store 4.5.6 rejection: Apple emoji artworkTyping an emoji and bundling Apple's emoji image are different uses. Under 4.5.6, Unicode characters can render as Apple emoji in your app and metadata.Apple App Store
- App Store 4.7 rejection: Mini apps, hosted software, and emulatorsYour app can be rejected because of software it hosts, even when that software isn't included in the original download.Apple App Store
- App Store 4.7.1 rejection: Moderation, privacy, and payments in hosted softwareA mini app doesn't inherit a policy exemption from its host. Under 4.7.1, hosted software must follow privacy and payment rules and provide the required filtering, reporting, timely responses, and user blocking.Apple App Store
- App Store 4.7.2 rejection: Native API access from hosted softwareA JavaScript bridge can give hosted software access to native capabilities. Apple's 4.7.2 requires prior permission before the app exposes native platform APIs or technologies to software offered under 4.7.Apple App Store
- App Store 4.7.3 rejection: Consent for sharing with hosted softwareA person granting access to your host app hasn't necessarily agreed to share it with every mini app.Apple App Store
- App Store 4.7.4 rejection: Hosted software indexes and universal linksApple needs a way to find the software your app offers, including items loaded after installation. Guideline 4.7.4 requires an index with metadata and universal links leading to all the offered software.Apple App Store
- App Store 4.7.5 rejection: Age restrictions for hosted softwareA single age rating for the host doesn't settle access to every item inside it. Under 4.7.5, users need to identify software exceeding that rating, and underage access must be restricted using declared or verified age.Apple App Store
- App Store 4.8 rejection: Login servicesYou've added Google login, and Apple asks for another sign-in option. Guideline 4.8 doesn't apply to every app with an account.Apple App Store
- App Store 4.9 rejection: Apple Pay purchase informationThe Apple Pay sheet can't explain an offer that the app never makes clear. Guideline 4.9 requires material purchase information before the sale and correct use of Apple's branding and interface elements.Apple App Store
- App Store 4.10 rejection: Charging for built-in capabilitiesYou can build a paid product using device features, but Apple's 4.10 prohibits monetizing the built-in capability itself.Apple App Store
Legal
- App Store 5.1 rejection: PrivacyApple's privacy rules cover what the app does with information, not only the privacy policy on your website.Apple App Store
- App Store 5.1.1 rejection: Data collection, permissions, and account deletionApple's 5.1.1 covers enough different things that the number alone isn't a diagnosis. Look for the Roman numeral and the reviewer's description.Apple App Store
- App Store 5.1.2 rejection: Data use, sharing, and trackingA privacy policy can describe sharing without giving the person the choice Apple requires. Guideline 5.1.2 covers permission, onward use, profiling, and data from sensitive APIs.Apple App Store
- App Store 5.1.3 rejection: Health data and researchHealth permissions can be configured correctly while the data is still used in a prohibited way. Apple's 5.1.3 adds restrictions on health-data use, storage, accuracy, and research consent.Apple App Store
- App Store 5.1.4 rejection: Children's privacyA parental gate doesn't automatically provide consent to collect a child's information. Apple's 5.1.4 covers children's data, while 1.3 adds Kids Category requirements.Apple App Store
- App Store 5.1.5 rejection: Location dataApple may be asking why your app needs location at all. Under 5.1.5, location must directly relate to the app's features, with an explanation and consent before collection, transfer, or use.Apple App Store
- App Store 5.2 rejection: Intellectual propertyApple wants to know whether you have the right to distribute what your app uses. Guideline 5.2 covers content you create or properly license, with more specific rules for brands, services, media downloads, and Apple materials.Apple App Store
- App Store 5.2.1 rejection: Permission to use third-party materialA logo supplied by a client can still need evidence of authorization. Guideline 5.2.1 requires permission for protected third-party material and an accurate app and developer identity.Apple App Store
- App Store 5.2.2 rejection: Third-party service authorizationAn integration can work technically while falling outside the service's permitted uses. Under 5.2.2, the service's terms must specifically allow your access or use, and Apple can ask for authorization.Apple App Store
- App Store 5.2.3 rejection: Media downloading and conversionA download button can trigger a rights rejection even when the media is easy to play in a browser. Under 5.2.3, downloading or converting third-party media needs explicit authorization from the source.Apple App Store
- App Store 5.2.4 rejection: Claims of Apple endorsementA badge or phrase can imply an endorsement you didn't intend. Guideline 5.2.4 limits claims that Apple supplies the app or endorses its quality or functionality.Apple App Store
- App Store 5.2.5 rejection: Apple designs, media, and attributionApple's design and content rules extend beyond the app icon. Guideline 5.2.5 covers confusingly similar products, certain media uses, Activity-ring presentation, and Weather attribution.Apple App Store
- App Store 5.3 rejection: Gambling, contests, and lotteriesCalling a feature a game or giveaway doesn't settle how Apple treats it. Guideline 5.3 separates contest sponsorship and rules from real-money gaming and licensing.Apple App Store
- App Store 5.3.1 rejection: Contest and sweepstakes sponsorshipApple may be asking who is responsible for the promotion. Under 5.3.1, sweepstakes and contests must be sponsored by the app's developer.Apple App Store
- App Store 5.3.2 rejection: Official contest rulesA link to a promotion on your website may leave the reviewer without the rules inside the app. Guideline 5.3.2 requires the official rules to be presented in-app and to make clear that Apple has no sponsorship or involvement.Apple App Store
- App Store 5.3.3 rejection: In-app purchases and real-money gamingA credit pack doesn't avoid a gambling-payment restriction. Under 5.3.3, in-app purchase can't be used to buy credit or currency for real-money gaming.Apple App Store
- App Store 5.3.4 rejection: Real-money gaming and lottery accessYour license may cover one place while the app lets people play from another. Guideline 5.3.4 requires the necessary licensing, geographic restrictions to permitted locations, and a free App Store download for real-money gaming and lottery apps.Apple App Store
- App Store 5.4 rejection: VPN appsA working VPN connection is only part of Apple's review. Guideline 5.4 covers the developer's organization, the networking API, disclosure before use, strict data handling, and local licensing.Apple App Store
- App Store 5.5 rejection: Mobile device managementDevice-management access needs approval and an eligible provider. Under 5.5, MDM capability must be requested from Apple and is limited to specified organizations, with narrow additional cases for parental control or security.Apple App Store
- App Store 5.6 rejection: Developer conductA conduct notice can concern behavior outside the app as well as its screens. Guideline 5.6 covers dealings with customers and Apple, misleading purchases, unnecessary data demands, and other manipulative practices.Apple App Store
- App Store 5.6.1 rejection: Review prompts and customer repliesA request for a rating is part of the reviewed experience. Guideline 5.6.1 requires Apple's provided review API and prohibits custom review prompts.Apple App Store
- App Store 5.6.2 rejection: Accurate developer identityApple needs to know who provides the app, and so do your users. Guideline 5.6.2 requires accurate, relevant, current information about the developer, business, and offering.Apple App Store
- App Store 5.6.3 rejection: Manipulating discovery and reviewsA promotion agency's actions can still become a problem for your app. Under 5.6.3, manipulating discovery or customer signals on the App Store is prohibited.Apple App Store
- App Store 5.6.4 rejection: Ongoing app qualityApproval isn't the end of maintaining the experience people paid for. Guideline 5.6.4 connects ongoing quality with developer conduct, including excessive customer complaints and refund requests.Apple App Store