Guideline 5.2.1 – Legal – Intellectual Property: how to fix the App Store rejection

What Guideline 5.2.1 actually means

Guideline 5.2 starts with a simple rule: only include content you created or have a license to use. It also notes that laws differ between countries and regions. Section 5.2.1 ("Generally") then says: "Don't use protected third-party material such as trademarks, copyrighted works, or patented ideas in your app without permission…"

Three separate parts of 5.2.1 can each trigger a rejection:

• Protected material without permission: brand names, logos, characters, photos, music, fonts and artwork owned by someone else.
• Misleading or copycat representations: names, metadata or a developer name that suggest you are someone you are not.
• The right submitter: apps "should be submitted by the person or legal entity that owns or has licensed the intellectual property" (5.2.1). This is the part behind the seller-name rejections that agencies run into.

App Review checks everything a customer sees: name, subtitle, keywords, description, icon, screenshots, previews, in-app purchase names, the home-screen name and the app's content. Apple's App Review page says that apps featuring third-party trademarks or copyrighted content must provide authorization, and names marketing that uses imagery of celebrities, sports, movies or music as examples.

Related rules: 5.2.2 (third-party sites and services), 5.2.3 (audio/video downloading), 5.2.4 (no implied Apple endorsement), 5.2.5 (Apple products) and Guideline 4.1 Copycats. Guideline 4.1(c) bars another developer's icon, brand or product name in your icon or name without approval.

This is practical release advice, not legal advice. For license negotiations, disputes with a rights holder or questions about whether a term is protected, talk to an IP attorney.

Common reasons apps get rejected under 5.2.1

The message usually names the brand or rights holder. It sometimes names a territory and often includes a screenshot. Typical triggers:

Two misconceptions lead to repeat rejections. First, "free to download" does not mean "free to use". Assets from free sites are still copyrighted, and you must be able to show the license. Second, AI-generated art is not automatically safe. An icon that resembles a famous character or a tournament's branding can be flagged just like the original.

Rejected or stuck? Talk to an App Specialist – for free.

Book a free consultation call: we look at your rejection or setup, explain the fastest way forward and tell you honestly whether you need us. Prefer to hand it off? Book our AI-powered + human-powered service and we take care of it.

Free consultation call Book our service →

How to fix a Guideline 5.2.1 rejection step by step

1. Pin down what was flagged. In App Store Connect, open your app's App Review section and read the full message and any attached screenshots. Note the brand, rights holder, territory and asset types it mentions.
2. Audit every surface. Search all metadata in every localization for the brand and its variants. Then check the icon, screenshot sets, previews, in-app purchase names, and the strings and images inside the app. A forgotten German subtitle gets the same rejection.
3. Choose a path for each item: prove your rights, remove or replace the content, rebrand, or exclude territories. You can combine these.
4. If you hold the rights, assemble evidence. Useful documents include a signed license agreement, a permission letter on the rights holder's letterhead that names your app and your legal entity, a trademark registration in your name, and license receipts for stock images, fonts or music. Apple doesn't publish a fixed list. Merge the documents into one PDF, highlight the relevant clauses and add an English summary if needed.
5. Upload it where App Review looks. On your app's version page, scroll to App Review Information, add the PDF as an attachment and use Notes (up to 4,000 bytes) to explain which document covers which asset. Apple's App Review page recommends exactly this for authorization documents. fastlane deliver can upload the file with app_review_attachment_file. You can also attach files to your reply in the App Review section.
6. Check the Content Rights declaration. Under App Information, the Content Rights setting asks whether your app contains, shows or accesses third-party content. If it does, you must hold the necessary rights in every country or region where the app is available.
7. If you don't hold the rights, remove the content. Change the name and subtitle under App Information. Remove the brand from keywords and the description, and replace the icon, screenshots and previews with original artwork. In Xcode, update the target's Display Name (CFBundleDisplayName) and the localized InfoPlist.strings or InfoPlist.xcstrings entries.
8. Rebrand when the brand is the product. Pick a new name, run a trademark search and check that the name isn't already taken on the App Store (2 to 30 characters). The bundle ID isn't shown to customers and can't be changed after you upload a build, so leave it as it is.
9. Exclude territories if the objection is regional. Go to Pricing and Availability, then App Availability, and remove the affected countries or regions. Rejection messages about regional trademark objections have offered this option, but it doesn't help with content you aren't licensed to use anywhere.
10. Resubmit correctly. If you only changed metadata, Apple lets you resubmit the same build. If the app's content or display name changed, upload a new build with a higher CFBundleVersion.

Never submit edited or unverifiable documents. Guideline 5.6 warns that misleading or fraudulent conduct can get you removed from the Apple Developer Program.

Fan apps, companion apps and referential use

Most grey areas come down to one question: are you describing compatibility with a brand, or borrowing it as your identity?

Fan apps and unofficial guides

Labeling an app "Unofficial" rarely helps. If the app depends on a franchise's name, characters or artwork, App Review expects authorization. Get a license or written permission, or turn the app into a generic tool, for example a "match tracker" instead of an app named after a league. Some publishers have published fan content policies. Read them closely, because many exclude standalone apps or commercial use.

Companion apps for products and services

For services, Guideline 5.2.2 requires the service's terms of use to specifically permit your use, and you must provide authorization on request. Have the API or partner terms, or a written partnership confirmation, ready to attach. Hardware companion apps for brands you don't work with get the "marketed to control external hardware" rejection. Apps built on reverse-engineered protocols or scraped content are the hardest to defend.

Referential mentions and real people

Saying in the description that your app "works with" a product is different from putting that product in your name or icon. Keep mentions factual, with no logos and nothing that implies a partnership. Real people's names, photos and voices are protected by publicity or personality rights in many countries, so celebrity-themed apps need written consent as well as photo licenses.

Using Apple trademarks and product images correctly

Apple's App Store marketing guidelines and guidelines for using Apple trademarks set clear rules:

• Names: use Apple product names only in a referential phrase. "App Name for iPhone" or "works with Apple Watch" is fine, "iPhone App Name" is not. Apple trademarks may not be part of your product name.
• Apple logo: don't use the standalone Apple logo or use it in place of the word "Apple".
• Device images: use Apple product images as they are. Don't add reflections, crop, tilt, flip or animate them, and don't place copy on top of the device.
• Endorsement: 5.2.4 prohibits implying that Apple is the source of your app or endorses it, so avoid wording like "Apple-approved".
• Look-alikes and Apple content: 5.2.5 rejects apps that look confusingly similar to Apple products or apps. Apps and extensions, including keyboards and sticker packs, may not include Apple emoji, and iTunes or Apple Music previews may not be used for their entertainment value.

If your screenshots are the problem, see our Guideline 2.3.3 screenshots guide.

Agency and client apps: the seller name problem

"The seller and company names associated with your app do not reflect the name … in the app or its metadata" is also filed under 5.2.1, but it needs a different fix. In messages developers have shared, Apple asks for the app to be published under a seller name that reflects the brand, and asks agencies to have the client add them to the client's own developer account. A permission letter alone usually doesn't solve it. What works:

1. The client enrolls in the Apple Developer Program as an organization. That requires a legal entity and a D-U-N-S Number, and the organization's legal name becomes the seller name. Apple doesn't accept DBAs or trade names.
2. The client invites you under Users and Access, as Admin or as App Manager with access to Certificates, Identifiers & Profiles.
3. You create the app record in the client's account. For an existing app, check whether it qualifies for Apple's app transfer process.
4. Your CI/CD pipeline switches to the client's team ID, certificates, provisioning profiles and an App Store Connect API key created in the client's account.

Publishing your own brand as an individual? The seller name is your personal legal name, so make the link verifiable. Set the Copyright field on the version page to the actual rights owner, publish a support site and privacy policy that name you as the operator, and add a trademark registration in your name if you have one. Enrolling as an organization under the legal entity that owns the brand removes the mismatch completely. Our Guideline 2.3 metadata guide covers related naming conflicts.

Responding to App Review and appealing

In App Store Connect, select the app, click the unresolved issues link at the top, click Resolve next to the submission, then Reply to App Review. Use Attach File for documents.

• If you fixed it, list every change by surface and localization.
• If you hold the rights, map each document to the asset it covers, and include the territories and license term.
• If you think the rejection is wrong (a generic term, your own registered mark, purely referential use), explain why and attach evidence.

If that doesn't resolve it, you can book a 30-minute Meet with App Review consultation, or file an appeal with the App Review Board. Apple allows one appeal per rejected submission, asks for specific reasons and expects you to answer any open information requests first. Apple's bug-fix option, which approves an update and lets you address other issues in the next submission, excludes legal and safety concerns. That means IP issues usually have to be fixed in the current submission.

Rights holders can also file claims through Apple's intellectual property dispute forms. According to that page, Apple usually contacts the developer of the disputed app about the claim and asks the developer to work with the claimant directly. If a claim reaches you, involve counsel. The same page has an App Store dispute form and an App Name Dispute form you can use if someone copies your brand or uses your trademark as an app name.

How to prevent 5.2.1 rejections next time

• Clear the name early. Search USPTO, EUIPO and WIPO's Global Brand Database, and search the App Store in every launch market, before you design the icon.
• Keep an asset register in the repo. List every third-party image, font, sound and data source with its origin and license, so you can put together your App Review PDF in minutes.
• Lint metadata in CI. If you keep fastlane metadata in metadata/<locale>/, scan name.txt, subtitle.txt, keywords.txt and description.txt against a brand denylist and fail the build on a match. Check CFBundleDisplayName too.
• Use AI-assisted asset checks with human sign-off. Automation can spot logos, faces and brand text in screenshots. Whether a use is licensed still needs a human decision.
• Publish from the right account before the first submission, not after the rejection.

Want a second pair of eyes? appsubmitter.io combines AI-powered metadata and screenshot checks with App Specialists who help you structure your rights documentation and your reply to App Review. This is not legal advice. Book a free consultation call or book the iOS submission service.

Template: how to reply to App Review

Adapt this template to your situation. Keep it factual, short and specific – and only claim what you have actually changed.

Hello App Review Team,

Thank you for reviewing [App Name] (version [x.y], build [n]) and for the details regarding Guideline 5.2.1.

[Option A – we hold the rights]
We are authorized to use [protected content] in our app and its metadata. We have attached the following to the App Review Information section and to this reply:
- [License agreement between [Rights Holder] and [Our Legal Entity], dated [date], clause [x]]
- [Permission letter signed by [Name, Title] at [Rights Holder]]
The license covers [app name, icon, screenshots, in-app content] in [territories] until [expiry date or "no expiry"]. The rights holder can confirm this at [contact name, email].

[Option B – we removed the content]
We have removed all references to [brand/content]:
- App name and subtitle changed from "[old name]" to "[new name]" in all [n] localizations
- [Brand] removed from keywords and description
- Icon, screenshots and previews replaced with original artwork
- In-app: [describe change] in build [n]
[Optional: We also removed [countries or regions] from availability.]

Please let us know if you need anything else to continue the review.

Best regards,
[Your Name]
[Role], [Legal Entity Name]

Checklist before you resubmit

• Name, subtitle, keywords and description contain no third-party brand you lack written permission for, in every localization.
• Icon, screenshots, previews and in-app images show no third-party logos, characters or real people without a license.
• The Xcode Display Name and localized InfoPlist entries match the new app name.
• Every third-party asset is listed with its source and license proof.
• Rights documents are merged into one labeled PDF and attached in App Review Information, with Notes explaining which document covers what.
• The Content Rights declaration under App Information is answered correctly for third-party content.
• The seller name reflects the brand, or the app is published from the brand owner's developer account.
• The Copyright field names the actual rights owner.
• Apple trademarks appear only referentially, with no Apple logo or altered device images.
• Third-party APIs, services and hardware integrations are covered by terms or permission you can attach.
• A new build is selected if in-app content changed; the same build is reused only for metadata-only fixes.

Frequently asked questions

Official source: App Store Review Guidelines – 5.2 Intellectual Property. Store policies change regularly – always check the current version. This guide is independent advice and not affiliated with Apple or Google.