The good news: This is NOT a content violation. Guideline 2.1 means Apple's reviewers could not complete the review — they didn't understand what the app does, couldn't log in to test it, and had no context for the claims content. They are not saying the app breaks any rules.
The real issue: ClaimIt submitted with empty App Review Notes. For an app that (a) uses AI, (b) collects health diagnoses, (c) shows legal claim amounts, and (d) has a subscription paywall — Apple reviewers had no idea what they were looking at. This causes an automatic "more info needed" rejection every time.
The fix: Two parallel tracks. Track A: Write comprehensive App Review Notes (copy-paste text is provided below). Track B: Make 4 specific in-app changes Apple explicitly flagged — account deletion, subscription display, purpose strings, and screenshots. Both tracks must be complete before resubmission.
A
Track A — App Review Notes (7 Required Items)
Apple asked for all 7 of these in the Notes field of App Review Information in App Store Connect. Ready-to-paste text is provided after the action cards.
💡
How to submit: In App Store Connect → Your App → App Review Information → Notes. Paste all 7 items. This alone may be enough to get approved on resubmission, provided the Track B app changes are also in place.
1. Screen Recording — Capture full user flow on a physical device
Record on a real iPhone (not simulator) running the latest iOS. Must show: app launch, onboarding questionnaire, account registration, account deletion, subscription purchase flow, and the claims results dashboard.
BlockingApple RequiredProduct
Start: Launch app from home screen cold (no background state)
Onboarding: Walk through all 7 questionnaire steps, select several options to show interactivity
Registration: Create a new account (email + password). Show the verification step if there is one.
Login: Log out then log back in to demonstrate the login flow
Account Deletion: Navigate to Settings → Account → Delete Account. Show the confirmation dialog. This is the most scrutinized flow.
Subscription: Navigate to the paywall. Show all three tiers (monthly $9.99 / annual $59.99 / lifetime $149.99). Tap "Subscribe" on one tier to show the native Apple payment sheet (do not need to complete purchase).
Results Dashboard: Show the claims results screen, tap into a claim card, show the tracking tab
Notifications prompt: If the app requests notification permission, include that moment in the recording
Format: Under 10 minutes, screen mirroring to Mac then QuickTime works well. Upload as MP4 to App Store Connect attachments.
2. Device Testing Matrix — List every device and OS tested
Apple wants to know the app was tested on real hardware before submission. List at minimum 3 device models across 2 OS versions.
Apple RequiredProduct / QA
Minimum required: iPhone 15 Pro Max (iOS 18.x) — latest flagship
Minimum required: iPhone 14 (iOS 17.x) — one OS version behind
Recommended: iPhone SE 3rd gen (iOS 17.x) — smallest screen, tests layout on compact form factor
Recommended: iPhone 13 mini if available — also compact form factor
Not required but helpful: iPad if the app supports it
Use TestFlight to distribute builds to testers on these devices before submission. Apple explicitly mentions TestFlight as the expected testing path.
3. App Description — Purpose, audience, problem, value
Clear plain-English description written for an Apple reviewer who has never heard of ClaimIt. Avoid legal jargon. Emphasize the informational nature of the app.
Apple RequiredContent
4. Demo Account Credentials — Reviewer must be able to log in immediately
Create a permanent demo account with premium features unlocked. Do not use a time-limited trial. The reviewer should see the full paid experience without needing to purchase anything.
BlockingApple RequiredDev
Create account: demo@claimit.app / ClaimIt2025! (or similar memorable credentials)
Pre-populate this account with a completed questionnaire profile (select several diagnoses, products, tech platforms to show non-empty results)
Grant this account premium subscription access server-side (bypass RevenueCat for this specific account)
Pre-load the account with sample matched claims in the results screen so reviewers see the value immediately
Make sure the account has scan history showing at least one completed weekly scan
Include in App Review Notes: username, password, and a note saying "premium features are pre-enabled on this account"
5. External Services List — Every third-party platform the app touches
Apple wants to know what external services power the app. This is especially important because ClaimIt uses an AI API. Be transparent and specific.
Apple RequiredContent
Anthropic Claude API — AI language model used to match user profiles to active legal claims and power the AI advisor feature. No user data is permanently stored by Anthropic. Queries are sent only during weekly scans.
RevenueCat — Manages in-app subscription state, purchase validation, and entitlement tracking for the three subscription tiers.
Stripe — Payment infrastructure (used server-side for any web-initiated transactions).
PostgreSQL database (self-hosted / managed cloud) — Stores encrypted user profiles, scan history, and matched claims.
Bull Queue / Node.js backend — Powers the scheduled weekly scan job that runs every Sunday at 2am.
If using any analytics (Mixpanel, Amplitude, etc.) — list these too, as they affect ATT requirements.
6. Regional Availability — Confirm US-only or explain state differences
ClaimIt is US-focused and some claims are state-specific. Apple needs a clear statement about regional differences.
Apple RequiredContent
State that the app is designed for and targeted at U.S. residents only
Note that some claim categories are state-specific (e.g., TikTok BIPA applies to Illinois residents only) — these are clearly labeled with state requirements within the app interface
The app functions consistently across all U.S. states. State-specific eligibility filters are applied automatically based on the user's profile answers, not device location.
The app does not request or use device location data to determine state eligibility
7. Regulated Industry Documentation — Legal / financial space disclaimer
This is the most sensitive point for ClaimIt. Apple may classify the app as being in the legal or financial services sector. Must proactively address this with a clear disclaimer and explanation.
BlockingApple RequiredLegal
Key statement to include: "ClaimIt is not a law firm, does not provide legal advice, and does not represent users in any legal proceedings. The app provides informational content about publicly known class action settlements, government benefit programs, and consumer rights opportunities."
Source clarity: "All claim information is sourced from publicly available court records, government databases, and news sources. Settlement amounts shown are estimates based on reported ranges — actual payouts depend on individual circumstances and the outcome of each case."
Health data disclaimer: "Health-related questions in the onboarding questionnaire are used solely to match users to relevant settlement categories. This information is not medical advice. ClaimIt does not integrate with Apple HealthKit."
No credentials needed — ClaimIt is an informational app, not a licensed legal or financial service. Make this explicit so Apple doesn't think credentials are missing.
Make sure a "Not Legal Advice" disclaimer is visible in-app (in the claims results screen and profile section)
B
Track B — In-App Changes (4 Technical Requirements)
Apple mentioned these as "common issues" — but for ClaimIt they are required fixes, not optional suggestions. Apps with accounts, subscriptions, and sensitive permissions must implement all four.
🚨
These are blocking issues. Even with perfect App Review Notes, Apple will reject again if these are not in the app. Implement all four before resubmitting.
B1. In-App Account Deletion — Hard requirement for all apps with accounts
Since mid-2023, Apple mandates that any app allowing account creation must also allow users to delete their account from within the app itself. This is non-negotiable and will cause rejection on every submission until implemented.
Blocking — Will Reject WithoutDev
Where to put it: Settings → Account → Delete Account. Must be in the app, not a link to a website.
Flow required:
User taps "Delete Account"
Show a warning screen: "This will permanently delete your profile, scan history, and all saved claims. This cannot be undone."
Require confirmation — either a text field where they type "DELETE" or a second confirmation button
Cancel active subscriptions via RevenueCat before deleting (or inform user their subscription remains active in App Store until they cancel)
Delete all personal data from database (GDPR / CCPA compliance also requires this)
Sign user out and return to onboarding screen
Backend: Create a DELETE /api/users/:id endpoint that hard-deletes: user record, all diagnoses/products/profile data, scan history, matched claims. Log the deletion event for compliance.
Apple Guideline reference: App Store Review Guideline 5.1.1 — Data Collection and Storage
The paywall screen must display specific required information. Missing any element causes rejection. The current paywall likely shows pricing but may be missing required legal text and links.
Blocking — Will Reject WithoutDevProduct
Subscription title: Each tier must have a clear name — e.g., "ClaimIt Monthly", "ClaimIt Annual", "ClaimIt Lifetime"
Duration: Must explicitly state the billing period — "per month", "per year", "one-time"
Price: Must show exact price: "$9.99 / month", "$59.99 / year", "$149.99 one-time"
Auto-renewal disclosure (exact language Apple expects): "Subscriptions automatically renew unless auto-renew is turned off at least 24 hours before the end of the current period. Your account will be charged for renewal within 24 hours prior to the end of the current period."
Cancellation info: "Manage or cancel your subscription in your iPhone Settings → [Your Name] → Subscriptions."
Links (tappable):
Terms of Use / Terms of Service — must be a real URL
Privacy Policy — must be a real URL
Free trial language (if offering one): Must state exact trial length and what happens after
Placement: All of the above must be visible on the paywall screen itself — not buried in a separate page the user has to navigate to
Every permission the app requests must have a purpose string in Info.plist that clearly explains what the data is used for, with a specific example. Vague strings like "To improve your experience" are rejected.
DevWill Reject If Vague
Push Notifications (NSUserNotificationUsageDescription): "ClaimIt uses notifications to alert you when our weekly scan finds new class action settlements or government benefits that match your profile. You can control notification frequency in the app settings."
Face ID / Touch ID (NSFaceIDUsageDescription) — if used for login: "ClaimIt uses Face ID to let you log in securely without typing your password, protecting your financial and health profile data."
Camera (NSCameraUsageDescription) — only add if used for document upload: "ClaimIt uses the camera to let you photograph documents (such as medical records or receipts) that support your claim applications."
Photo Library (NSPhotoLibraryUsageDescription) — only if used: "ClaimIt accesses your photo library to let you attach supporting documents to your claim profiles."
Location — Do NOT request location. ClaimIt determines state-specific eligibility through questionnaire answers, not GPS. If location is currently requested anywhere, remove it.
Contacts — Do NOT request contacts. Not needed for ClaimIt's functionality.
HealthKit — Do NOT request HealthKit. ClaimIt collects health information through its own questionnaire, not HealthKit. Requesting this would trigger extensive additional review.
Only include NSUsageDescription keys for permissions ClaimIt actually uses. Unused keys with strings cause unnecessary permission prompts and look suspicious to reviewers.
B4. App Store Screenshots — Must show real in-app UI, not marketing art
Guideline 2.3.3 means screenshots cannot be illustrations, mockups, or title cards. They must be actual screen captures from the running app. Apple reviewers check this.
Apple RequiredProductContent
Screenshot 1 — Intro / Hero: The onboarding intro screen ("Find Every Claim You're Owed") — this IS an actual app screen, so it qualifies
Screenshot 2 — Questionnaire: One of the questionnaire steps (e.g., Health Diagnoses with chips selected in amber) — shows the core input flow
Screenshot 3 — Results: The claims results screen showing 3+ matched claims with amber payout badges — the most valuable screen to show
Screenshot 4 — Dashboard: The main dashboard with the 5-tab layout and a populated overview card
Screenshot 5 — Claim Detail: A bottom-sheet claim detail showing the full claim description, eligibility checklist, and "Start Filing" CTA
Screenshot 6 — Subscription: The paywall screen — shows the value prop and pricing clearly
Sizes required: 6.9" (iPhone 16 Pro Max) and 6.5" (iPhone 11 Pro Max). Use Xcode Simulator or a physical device to capture.
What NOT to include: Marketing illustrations, text-only cards, the Apple logo, or screenshots of other apps
You can add text overlays on screenshots (e.g. "Match your profile to 38 active claims") as long as the underlying screenshot is real app UI
C
Track C — Proactive Fixes (Prevent Round 3)
Apple didn't explicitly call these out, but they will if the reviewer goes deeper. Fix them now to avoid a second round of rejections.
C1. "Not Legal Advice" Disclaimer — Visible in the app, not just the privacy policy
ClaimIt sits in a regulated-adjacent space. Apple reviewers who see dollar amounts next to cancer diagnoses will ask "is this a law firm?" The answer needs to be prominent in the UI.
LegalProduct
Results screen: Add a small info bar below the results banner: "ClaimIt provides informational summaries only. Payout amounts are estimates and not guaranteed. This is not legal advice."
High-value claim cards: Add a "Consult a lawyer before filing" note on any claim with payout > $10,000
Settings / About: Add a "Legal Disclaimer" section with the full disclaimer text
Onboarding health step: Add a subtitle: "This information helps match you to relevant settlements. We do not store or share your health data with third parties."
C2. Privacy Policy & Terms of Service — Must be live public URLs before submission
Apple requires a publicly accessible privacy policy URL entered in App Store Connect. The ToS must also be accessible. Both must cover data types ClaimIt collects, especially health information.
BlockingLegal
Data collected: Must explicitly list — email, name, health condition data, product usage history, financial account history. Be specific.
Health data section: ClaimIt collects sensitive health information (cancer diagnoses, medical device history, etc.). This MUST have a dedicated section explaining: what's collected, why, how it's stored (encrypted), who can access it (nobody external), and how to delete it.
AI processing: Explain that profile data is processed by Anthropic's Claude API for claims matching. Clarify that Anthropic does not retain this data beyond the API call.
Third-party services: List RevenueCat, Stripe, and any analytics platforms.
Data retention: State how long data is kept and what happens on account deletion.
CCPA / California rights: Required for US users — right to know, right to delete, right to opt-out of sale (ClaimIt doesn't sell data, but must state this).
Contact info: Privacy policy must include a way to contact ClaimIt about data requests.
Publish at:claimit.app/privacy and claimit.app/terms before submitting
C3. TestFlight Beta — Run through TestFlight before submitting
Apple explicitly calls out TestFlight as the expected pre-submission testing path. Running a TestFlight beta also demonstrates due diligence. It takes 1-2 days to process the build.
Dev
Submit the build to TestFlight first (separate from App Store submission). The TestFlight review is faster and less strict.
Run through all critical flows on the TestFlight build on a physical device: registration, deletion, subscription, questionnaire, results.
Fix any crashes or layout issues discovered.
In the App Review Notes, you can mention: "This build was tested on TestFlight across [X] devices before submission." It signals to reviewers that you follow Apple's recommended process.
C4. App Tracking Transparency (ATT) — Required if using analytics or ad networks
If ClaimIt uses any analytics platform that tracks users across apps (Mixpanel, Amplitude, Firebase Analytics), ATT prompt is required. Failure to include it when needed causes rejection under Guideline 5.1.1.
DevLegal
If ClaimIt has NO analytics or advertising SDK: No ATT prompt needed. Confirm this in App Review Notes: "ClaimIt does not use any advertising networks or cross-app tracking SDKs. No ATT prompt is presented."
If ClaimIt uses Mixpanel, Firebase, or similar: Must implement ATTrackingManager.requestTrackingAuthorization and add NSUserTrackingUsageDescription to Info.plist.
Purpose string for ATT:"ClaimIt uses analytics to understand how users navigate the app so we can improve the claims discovery experience. No data is shared with advertisers."
Include the ATT prompt flow in the screen recording if it's used.
C5. AI Feature Disclosure — Apple is increasingly scrutinizing AI apps
Apple has not yet issued a formal guideline on AI disclosure, but reviewers flag AI apps with generic boilerplate. Proactively label AI-generated content and be transparent about what Claude does.
ProductContent
Add a small label on AI-generated content (e.g., the AI Advisor responses): "Generated by AI — review before acting"
In app settings/about: "ClaimIt uses Anthropic's Claude AI to analyze your profile and identify relevant claim opportunities."
In App Review Notes, explain the AI's role clearly: "AI is used to match user profiles to a curated database of active legal claims. AI-generated text is clearly labeled within the app and does not constitute legal advice."
B4. Replace App Store screenshots with real in-app captures
Product
0.5 day
Likely — Apple checks 2.3.3 on review
P2
C1. Add "Not Legal Advice" disclaimer text to results screen and claim cards
Dev + Product
2 hours
Preemptive — prevents round 3 rejection
P2
C3. TestFlight beta on physical devices before submitting
Dev + QA
1 day (testing)
Apple recommends strongly — prevents crash issues
P3
C4. Determine ATT requirement and implement or explicitly confirm not needed
Dev
2 hours
Conditional — only if analytics SDK present
P3
C5. Add AI disclosure labels in app and in App Review Notes
Dev + Product
2 hours
Preemptive — Apple scrutinizing AI apps more
E
Ready-to-Submit: App Review Notes
Copy the text below into App Store Connect → App Review Information → Notes. Fill in the bracketed fields before pasting.
📋
Where to paste: App Store Connect → Select your app → App Review Information (in the left sidebar) → Notes field. The screen recording goes in the Attachments section on the same page.
App Review Notes — All 7 Required Items
=== ClaimIt — App Review Notes ===
Thank you for reviewing ClaimIt. We want to provide full transparency about the app to make your review as smooth as possible.
--- 1. DEMO ACCOUNT CREDENTIALS ---
Username: demo@claimit.app
Password: ClaimIt2025!
This account has premium subscription access pre-enabled and a completed profile with matched claims pre-loaded so you can immediately see the app's core value. No purchase is required to access any feature with this account.
--- 2. DEVICE TESTING ---
The app was tested on the following physical devices before submission:
- iPhone 15 Pro Max running iOS 18.x
- iPhone 14 running iOS 17.x
- iPhone SE 3rd Generation running iOS 17.x
A TestFlight beta build was distributed and tested before this App Store submission.
--- 3. APP PURPOSE & TARGET AUDIENCE ---
ClaimIt is a personal financial discovery app that helps everyday Americans find money they are owed but don't know about. This includes active class action settlements, government benefit programs, product recalls, and consumer rights claims.
Target audience: US adults 18 and older, particularly people in underserved communities who lack access to legal and financial advisory services.
Problem it solves: Billions of dollars in class action settlements go unclaimed every year because most Americans don't know they qualify. Finding these opportunities typically requires legal knowledge or expensive advisors. ClaimIt automates this discovery process.
Value it provides: Users complete a profile questionnaire covering their health history, products used, vehicles owned, apps used, and other factors. ClaimIt's AI matches their profile against a database of 38+ active claim categories and notifies them weekly when new matches are found.
--- 4. HOW TO ACCESS MAIN FEATURES ---
Step 1: Log in with the demo credentials above (or register a new account with any email address).
Step 2: The app will present the 7-step onboarding questionnaire. On the demo account, this has already been completed — tap "Skip" or navigate directly to the dashboard.
Step 3: The Dashboard shows matched claims organized into tabs: Overview, Benefits & Grants, Found Money, Prescriptions, and Paid Research.
Step 4: Tap any claim card to open the detail bottom sheet showing full eligibility requirements, estimated payout, and action steps.
Step 5: The weekly scan runs automatically every Sunday. On the demo account, a completed scan result is pre-loaded.
Step 6: To view subscription options, tap the "Upgrade" banner or navigate to Settings → Subscription. Note: The demo account already has premium access enabled.
Step 7: To test account deletion, navigate to Settings → Account → Delete Account. This flow permanently removes all user data. Please do not delete the demo account as it is shared for review purposes. Feel free to create and delete a new test account instead.
--- 5. EXTERNAL SERVICES & PLATFORMS ---
- Anthropic Claude API: AI language model used to match user profiles to active legal claims and power the AI Advisor feature. User profile data is sent to the API for matching purposes only and is not stored by Anthropic beyond the processing of each request.
- RevenueCat: Manages in-app subscription state, entitlement tracking, and purchase validation for the three subscription tiers ($9.99/month, $59.99/year, $149.99 lifetime).
- Stripe: Payment infrastructure for any web-initiated transactions (server-side only, not used directly in the iOS app).
- Secure cloud database (PostgreSQL): Stores encrypted user profiles, scan history, and matched claim data.
- Node.js backend API: Powers the weekly claims scan job and serves all app data.
- [List any analytics platform here, e.g., "Mixpanel: Used for anonymized app usage analytics."]
--- 6. REGIONAL AVAILABILITY ---
ClaimIt is designed for and targeted at US residents only. The app and all claim categories are US-specific.
Some claim categories have state-specific eligibility requirements (for example, the TikTok BIPA privacy claim applies only to Illinois residents). These state requirements are clearly labeled within the app interface. The app determines state eligibility through questionnaire answers — no device location data is requested or used.
The app functions consistently across all US regions and all supported iOS versions.
--- 7. REGULATED INDUSTRY INFORMATION ---
ClaimIt is not a law firm and does not provide legal advice or legal services. The app provides informational content about publicly known class action settlements, government benefit programs, and consumer rights opportunities.
All claim information is sourced from publicly available court records, government databases, legal news publications, and official settlement administrator websites.
Settlement payout amounts shown in the app are estimates based on publicly reported ranges. Actual payouts depend on individual circumstances and the outcome of each case. This is clearly disclosed within the app with the label "Not Legal Advice" displayed prominently on results screens.
The app collects health-related information (such as medical diagnoses) through its questionnaire solely to match users to relevant settlement categories. This is not medical advice. ClaimIt does not integrate with Apple HealthKit. All collected data is encrypted at rest and in transit.
ClaimIt does not require any special licenses or credentials to operate, as it provides informational discovery services only — not legal representation, legal advice, or medical advice.
Privacy Policy: [https://claimit.app/privacy]
Terms of Service: [https://claimit.app/terms]
--- ADDITIONAL NOTES ---
- The app does not request access to Contacts, Camera, Location, or HealthKit.
- Push notifications are used solely to alert users when new claim matches are found during the weekly scan. The purpose string clearly explains this use.
- [If applicable: "ClaimIt does not use any advertising networks or cross-app tracking SDKs. No ATT prompt is presented."]
- AI-generated content within the app is clearly labeled as such. The AI does not make legal determinations — it categorizes and surfaces publicly available information.
Please don't hesitate to reach out if additional information would be helpful. We are committed to making ClaimIt a great experience on the App Store.
F
Pre-Submission Checklist — Don't Submit Until All Are Checked
In-App Changes
Account deletion flow implemented in Settings — deletes all user data server-side
Subscription screen shows: tier names, prices, durations, auto-renewal text, cancellation instructions, ToU link, Privacy link
All NSUsageDescriptions audited — vague ones rewritten, unused keys removed
"Not Legal Advice" disclaimer visible on results screen and high-value claim cards
AI-generated content labeled within the app where applicable
ATT prompt implemented (if using analytics SDK) or explicitly not implemented (if no tracking)
App Store Connect — App Information
Privacy Policy URL entered and URL is publicly accessible
App description written (App Store listing) — mentions AI, claims discovery, US-only
All 6 App Store screenshots replaced with real in-app captures (not marketing art)
Age rating correctly set (likely 17+ due to health/legal content)
App Review Information Section
Notes field filled with all 7 required items (use the copy-paste text above)
Demo account credentials included in notes (username + password)
Screen recording uploaded as attachment (MP4, recorded on physical device)