Guideline 5.2.3

Guideline 5.2.3 - Legal: Unauthorized Third-Party Content Access

High RiskHardTypical Fix: 3-7 days1 Report
Also known as:The app provides access to third-party streaming content without demonstrating proper licensing agreements.Your app appears to circumvent or provide unauthorized access to copyrighted audio/video content from third-party services.The app contains functionality that may infringe on third-party intellectual property rights through unauthorized content streaming or catalog access.We found that your app accesses third-party media services in a way that may violate content licensing agreements.The app provides features that allow users to access copyrighted content without proper authorization from content owners.

Our Take

Apple is concerned that your app accesses third-party audio/video content without proper licensing agreements. This rejection typically occurs when apps aggregate content from streaming services, provide unofficial access to platforms like YouTube/Spotify, or scrape media catalogs without authorization.


The language suggests this may be an automated detection based on app functionality patterns or API usage. The root cause is usually one of three issues: (1) your app directly streams copyrighted content without licenses, (2) you're using unofficial APIs to access third-party services, or (3) your app description or functionality suggests unauthorized content access even if you're operating legally.


The fastest path to approval is providing clear documentation of your content licensing agreements or modifying your app to remove any unauthorized access patterns while preserving your core business model.

Resolution Guide

01

Document Your Legal Rights

Upload licensing agreements, API terms of service, or content distribution agreements to the App Review Information section in App Store Connect. Include any partnership agreements with content providers.

02

Remove Unauthorized Access (If Applicable)

If your app uses unofficial APIs, web scraping, or circumvents platform restrictions to access content, remove these features and implement only authorized access methods.

03

Clarify Your Content Sources

In your reviewer notes, explicitly explain where your content comes from: user-generated, licensed catalogs, public APIs, or your own original content. Be specific about which third-party services you integrate with.

04

Update App Description and Metadata

Remove any language that suggests unauthorized access to premium content or ability to bypass paid services. Focus on your app's unique value proposition rather than content aggregation.

05

Provide Technical Documentation

Include screenshots or technical explanations showing how your app respects content ownership, implements proper attribution, and uses only authorized APIs or content sources.


Prevention

  • Always secure proper licensing before accessing third-party content
  • Use only official APIs and respect rate limits and terms of service
  • Clearly document your content sources and legal compliance in reviewer notes
  • Avoid marketing language that suggests unauthorized access to premium content
  • Example Rejection Email

    From:Apple App Review Team
    Subject:Guideline 5.2.3 - Legal: Unauthorized Third-Party Content
    From Apple Guideline 5.2.3 - Legal Issue Description The app contains content or features that may violate the rights of one or more third parties. Specifically, the app provides potentially unauthorized access to third-party audio or video streaming, catalogs, and discovery services. The app and its contents should not infringe upon the rights of another party. In the event the app infringes another party's rights, you are responsible for any liability to Apple because of a claim. Next Steps To resolve this issue, please attach documentary evidence in the App Review Information section in App Store Connect evidencing that you have all necessary rights or permissions to the third-party audio or video streaming, catalogs, and discovery services in the app. Once we have reviewed your documentation and confirmed its validity, we will proceed with the review of the app.

    Consider Appealing

    Use this approach if you have proper licensing or only use authorized content. Tone: Professional and documentation-heavy. Structure: (1) Acknowledge the concern about third-party rights, (2) Provide detailed explanation of your legal content sources and licensing, (3) Attach comprehensive documentation, (4) Clarify any misunderstanding about your app's functionality, (5) Request specific feedback if documentation is insufficient. Push back only with strong legal documentation. Avoid: Arguing about what other apps do, minimizing copyright concerns, or claiming fair use without legal backing. Key phrases: 'properly licensed content', 'authorized API access', 'comprehensive documentation attached', 'respect intellectual property rights'.

    Generate Appeal

    Before & After

    Before — Rejected

    App streams music from various platforms without showing explicit licensing agreements to Apple.

    After — Approved

    App includes detailed licensing documentation and only streams from authorized content libraries with proper attribution.

    What changed: Clear documentation demonstrates legal compliance and authorized access to third-party content.

    Before — Rejected

    App uses web scraping to aggregate video content from multiple streaming services.

    After — Approved

    App only displays user-uploaded content or integrates with official APIs that permit such usage.

    What changed: Removes unauthorized content access and replaces with properly licensed or user-generated content.

    Before — Rejected

    App description mentions 'access any streaming service' without clarifying legal basis.

    After — Approved

    App description specifies 'integrates with partnered content providers' and lists authorized sources.

    What changed: Marketing language now accurately represents legal content sourcing rather than suggesting unauthorized access.

    Community Solutions · 0

    Sign in to share your solution.

    More Guideline 5 (Legal) rejections

    View all Guideline 5 rejections