App Store Rejection 5.2: IP, Copyright, & Trademark Fixes

When an app faces App Store rejection 5.2, Apple's review team has identified content infringing on intellectual property rights. This rejection typically relates to copyright or trademark use. Understanding how to address these specific issues is essential for indie developers to avoid approval delays. This guide clarifies common intellectual property pitfalls and provides concrete steps for resolution.

Understanding App Store Guideline 5.2: Legal Issues

App Store Guideline 5.2 encompasses "Legal" compliance, ensuring apps adhere to applicable laws. Intellectual property rejections most often fall under Guideline 5.2.1. Apple's App Store Review Guidelines, Section 5.2.1, explicitly states: "apps should not include copyrighted content or trademarks without having the necessary rights or proof of permission." This rule applies to your app's name, icon, and all internal content, including images, audio, video, and code snippets.

Copyright Best Practices for Your App Assets

Copyright protects original works of authorship like images, text, music, and specific code. For indie developers, copyright violations frequently appear in marketing materials and in-app content. A common issue is using an image or sound effect from the web without verifying its license. Here are specific steps to ensure your app assets are compliant:

1. Source Licensed Assets: Use royalty-free stock photo sites, sound effect libraries, or Creative Commons (CC0) resources. Always read specific license terms. Some Creative Commons licenses require attribution, meaning you must credit the original creator, often in your app's "About" section or legal disclaimers.
2. Create Your Own: Creating all assets from scratch is the safest approach. This includes your app icon, screenshots, feature graphics, and any in-app imagery. If you hire a designer, ensure your contract explicitly grants you full ownership or an unlimited license for the created assets. Utilize tools like the LaunchShots App Icon Generator or Feature Graphic Maker to build unique assets.
3. Check Open-Source Licenses: When incorporating open-source code libraries or frameworks, always review their licenses. Permissive licenses like MIT or Apache are generally safe, but others, such as GPL, may require you to open-source your entire app.
4. Document Everything: Maintain clear records of all licenses, permissions, and purchase receipts for any third-party assets. If Apple requests proof during the review, these documents will be ready for submission.

Consider a habit tracker app that uses custom icons for different habits. If you download these icons from a free library, verify the license permits commercial use without attribution, or provide proper attribution if required. If you include motivational quotes, confirm they are in the public domain or you have specific permission. Using a brand logo, such as Nike or Starbucks, in your habit examples without permission, even for illustrative purposes, constitutes a 5.2.1 violation.

Navigating Trademarks: Brands, Logos, and Names

Trademarks protect brand names, logos, slogans, and other identifiers that distinguish the source of goods or services. Unlike copyright, which protects the work itself, trademark safeguards the *identity* associated with that work. Common trademark pitfalls for indie developers include:

• Using Brand Names or Logos: Incorporating names like "Netflix" or "Spotify," or their logos, without explicit written permission is a trademark infringement. This also applies to popular fictional characters (e.g., "Mario," "Batman") if they are strongly associated with a specific brand.
• Similar App Names: Naming your app with a close resemblance to an existing popular app or brand can result in a 5.2.1 rejection, as it may confuse users about your app's origin.
• Keywords and Promotional Text: Using trademarked terms in your App Store Connect keywords or promotional text to attract traffic can also be deemed an infringement.

Before app submission, conduct a trademark search. For US-based trademarks, check the USPTO Trademark Search. For international trademarks, the WIPO Global Brand Database is a starting point. These searches are not legal advice, but they identify obvious conflicts. App Store Connect fields most affected by trademark issues include your App Name (up to 30 characters), Subtitle (up to 30 characters), and Keywords (up to 100 characters).

Securing Proper Licensing and Permissions

If you need to use third-party intellectual property, obtaining proper licensing or direct permission is the only safe approach.

How to Obtain and Document Permissions:

1. Contact the Rights Holder: Reach out directly to the company or individual owning the intellectual property. Clearly state how you intend to use their content, including the duration and specific context.
2. Formal Agreements: Always secure permission in writing. While a simple email exchange might suffice for minor uses, a formal license agreement is best for significant IP. This agreement should detail the scope of use, any limitations, and whether the license is exclusive or non-exclusive.
3. Proof for App Review: If you anticipate a potential IP issue or have secured specific licenses, you can proactively provide documentation to Apple. During submission in App Store Connect, use the "Notes for App Review" field to briefly explain your use of third-party IP and confirm you have permission. Should the review team request further proof after a rejection, you will upload the documents directly as an attachment in your resolution center communication.

A clear, verifiable record of your rights is the best defense against a 5.2.1 rejection.

FAQ

Can I use popular character names if my app isn't a game?

Generally, no. Even if your app isn't a game, using character names like "Harry Potter" or "Mickey Mouse" (or their associated imagery) without explicit permission is a trademark and copyright violation. These characters are protected intellectual property, regardless of your app's category.

What if I cite the source? Is that enough?

For copyrighted material, simply citing the source is usually not enough to avoid infringement. Attribution is often required by certain open licenses (like some Creative Commons licenses), but it does not grant you permission to use fully copyrighted material. You need a license or direct permission from the rights holder.

How do I prove I own my assets?

You prove ownership by showing original source files, design sketches, purchase receipts for stock assets, or contracts with designers explicitly stating you own the work. For assets created using LaunchShots, the fact that you generated them from scratch using the free tools makes them your original work.

Does 5.2.1 apply to my app's *content* or just the app itself?

Guideline 5.2.1 applies to both. It covers your app's name, icon, screenshots, and promotional text in the App Store listing, as well as all content, features, and assets within the app itself (images, sounds, videos, text, code).

I used a font from Google Fonts. Is that okay?

Yes, fonts from Google Fonts are generally safe for commercial use, as they typically use licenses like the Open Font License (OFL) or Apache License 2.0. These licenses permit embedding and using the fonts in your apps. However, it's always good practice to quickly check the specific license for any font you download.

Your Next Step: Audit Your App's IP Footprint

Review every asset in your app: your app icon, screenshots, feature graphics, in-app images, sounds, music, and all text in your description and promotional materials. For each, confirm that you either own it or have explicit permission to use it. If there is any doubt, replace the asset with something original or properly licensed. Use the free screenshot editor at LaunchShots to design and generate compliant marketing screenshots, ensuring your visual assets are original.