# Guideline 3.1.3(a) - Reader Apps: Incorrectly Claiming Reader App Status

**Guideline:** 3.1.3 · **Store:** Apple App Store · **Severity:** high · **Fix difficulty:** hard · **Typical turnaround:** 1-3 days

Canonical URL: https://appstorereject.com/rejections/apple/3/guideline-313a-reader-apps-incorrectly-claiming-reader-app-status

## Description

Apple is rejecting your app because it claims to be a 'reader' app to justify not using In-App Purchase for content access, but it does not qualify under Apple's reader app definition. Reader apps are a specific exception that allows apps providing access to previously purchased content -- such as magazines, newspapers, books, audio, music, and video -- to not offer IAP as a purchase mechanism within the app. To qualify as a reader app, the app must: (1) provide access to content that users have already purchased or subscribed to outside the app, (2) not offer in-app purchasing for that content, (3) fall within the defined content categories (magazines, newspapers, books, audio, music, video), and (4) be approved through Apple's reader app entitlement process. Common disqualifications: SaaS tools claiming reader status because users 'read' their data, productivity apps claiming reader status for document access, educational platforms claiming reader status for course content, and apps that create or produce content (not just consume it). The reader app exception is narrow and content-consumption focused.

## Common variations

- App does not meet criteria for reader app provision
- App content does not fall within reader app categories
- SaaS or productivity app incorrectly claims reader app status
- App creates content rather than providing access to purchased content

## Example rejection email

```
Guideline 3.1.3(a) - Business - Payments - Reader Apps

We found that your app claims reader app status, but the app does not meet the criteria for the reader app provision. Specifically, your app provides access to SaaS functionality and productivity tools rather than previously purchased content in the defined reader app categories (magazines, newspapers, books, audio, music, video).

Reader apps provide access to content that users have previously purchased or subscribed to, limited to the specific content categories defined in the guidelines.

Next Steps:
Please revise the app to either implement in-app purchase for accessing premium content and features, or provide documentation demonstrating that the app qualifies as a reader app.
```

## Resolution steps

## Quick Assessment
- **Risk level:** High
- **Resolution path:** Fix & Resubmit (implement IAP) or Appeal (if genuinely a reader app)
- **Typical turnaround:** 1-3 days

## The Fix

### If you ARE a legitimate reader app:
1. **Apply for the reader app entitlement** -- Contact Apple through the developer portal to request reader app classification. Provide documentation of your content catalog and external purchase mechanism.
2. **Ensure compliance with reader app rules** -- No in-app purchase buttons, no links to external purchase pages within the app (unless you have the External Purchase Link entitlement), no calls to action directing users to buy content.
3. **Document your case** -- In Review Notes, explain what content categories you serve, how users purchase content externally, and how the app provides consumption-only access.

### If you are NOT a legitimate reader app:
1. **Implement IAP** -- Add StoreKit In-App Purchase for all digital content and features accessed within the app.
2. **Remove reader app claims** -- Remove any references to reader app status from your app metadata and Review Notes.
3. **Consider hybrid approach** -- You can offer IAP within the app while also honoring purchases made on your website through account-based entitlements.

## Prevention
- Only claim reader app status if your app genuinely fits the defined categories
- SaaS, productivity, and educational platforms are not reader apps
- When in doubt, implement IAP as the primary purchase mechanism

## Appeal guidance

Appeal if your app genuinely provides access to previously purchased content in qualifying categories and the reviewer may have misunderstood the app's function. Provide detailed documentation of how users purchase content externally and how the app provides read-only access. Otherwise, implement IAP.

## Before / after examples

**Before:** Project management SaaS app claims reader app status because users 'read' their project boards and documents, avoiding IAP for premium tier access
**After:** App implements IAP for premium tier; users can also access premium features via their web subscription through account authentication, but IAP is offered as a purchase option within the app
**Why it works:** Reader apps are limited to specific content consumption categories. SaaS and productivity tools do not qualify.

## Common questions

**Can you appeal a 3.1.3 rejection?**

Appeal if your app genuinely provides access to previously purchased content in qualifying categories and the reviewer may have misunderstood the app's function. Provide detailed documentation of how users purchase content externally and how the app provides read-only access. Otherwise, implement IAP.

**How long does this typically take to fix?**

Typical turnaround is 1-3 days (difficulty: hard). After resubmission, most re-reviews complete within 24-48 hours.

---
*Machine-readable source: https://api.appstorereject.com/api/rejections/detail?slug=guideline-313a-reader-apps-incorrectly-claiming-reader-app-status*