Skip to content
Lifestyle & Learning

Complete Guide to App Review Information: Preparing Your App Store Submission

In this article

App review information refers to the required metadata, contact details, test credentials, and operational notes that developers must provide to platform review teams—such as Apple App Store Connect and Google Play Console—to evaluate and approve an application before publication. Complete app review information ensures app store evaluators can thoroughly inspect all features, verify compliance, and approve the submission without unnecessary delays or rejections.

What Is App Review Information?

When submitting an iOS, iPadOS, macOS, or Android application to major app marketplaces, submission portals require specific background configuration details categorized as App Review Information (or App Access and Content declarations). Platform operators like Apple and Google deploy human reviewers and automated scanners to inspect every submitted build.

Reviewers must be able to launch the app, log into restricted features, test in-app purchases, verify data collection declarations, and contact the development team if technical or compliance issues arise during testing. If an app relies on accounts, hardware connections, specialized location triggers, or subscription models, supplying complete app review information provides evaluators with direct access to these features.

Failing to provide complete testing details is one of the most common reasons for app rejection. Under Apple’s App Store Review Guidelines (specifically Guideline 2.1 regarding App Completeness), a submission will be paused or rejected immediately if reviewers cannot access core functionality or lack clear instructions on how to evaluate the app.

Core Components of App Review Information on Apple App Store Connect

In Apple’s App Store Connect, the App Review Information section is located on the app version preparation page. Apple requires specific metadata fields before you can submit a new app or version update for review.

App Store Connect Submission Metadata Structure:

  • Contact Information
    • First & Last Name
    • Phone Number (with Country Code)
    • Email Address
  • Access Information (Sign-In Credentials)
    • User Name / Test Login
    • Password
    • Two-Factor Authentication (2FA) Bypass Notes
  • Review Notes
    • Configuration Instructions
    • Backend / Sandbox Details
    • Special Hardware Requirements
  • Attachments
    • Demo Videos (.mp4, .mov)
    • Technical Documentation (.pdf)

1. Contact Information

Apple requires valid contact details for the person responsible for handling review inquiries. This includes:

  • First and Last Name: The direct representative or lead engineer managing the build.
  • Phone Number: A functional telephone number including international country codes (e.g., +1 for the US/Canada). Apple app reviewers occasionally call developers directly if a critical issue or clarification is required during live testing.
  • Email Address: An active inbox monitored by the deployment team. Review status changes, rejection notifications, and technical inquiries are sent directly to this address.

2. Sign-In Credentials (Access Information)

If your app requires user registration, login credentials, social sign-in, or biometric access to reach its core features, you must check the "Sign-in required" box and provide functional test account details.

  • Demo User Name & Password: Provide dedicated, active credentials created specifically for the app review team. Avoid using live personal accounts or temporary credentials that expire mid-review.
  • Two-Factor Authentication (2FA) Bypasses: If your application enforces 2FA or SMS verification upon login, you must supply a static verification code (e.g., configuring 123456 for the review account) or disable 2FA entirely for the reviewer's IP range/test account.
  • Account State & Test Data: Ensure the test account contains pre-populated sample data (e.g., active orders, saved items, chat histories, or profile data) so reviewers can test interface elements immediately without encountering empty states.

3. Notes for the Reviewer

The Notes field (up to 4,000 characters) is one of the most vital sections in App Store Connect. Use this space to explain complex workflows, backend setup requirements, or hidden functionality.

Key items to include in reviewer notes:

  • Sandbox Environment Toggles: Clarify whether the app automatically connects to a staging/sandbox server or if the reviewer must perform a specific gesture (e.g., triple-tapping a logo) to switch environments.
  • In-App Purchase (IAP) Testing: Detail how to reach in-app purchase triggers and confirm that test purchases can be completed using StoreKit test environments without charging actual payment methods.
  • Hardware Dependencies: If the app requires external hardware (such as a Bluetooth health monitor, smart home hub, or OBD-II scanner), explain how the app behaves when hardware is disconnected or provide a simulated demo mode.
  • Location-Based Services: If features depend on specific GPS coordinates, provide instructions or mock coordinates so reviewers located in regional review centers can trigger location-based UI elements.

4. Review Attachments

App Store Connect allows developers to upload supplementary files (such as PDF documentation or video files) to demonstrate functionality. If your app interacts with specialized hardware, requires an enterprise server connection, or relies on complex physical interactions, attaching a brief video demonstrating the app running in a real-world setting helps reviewers verify compliance without requiring physical hardware shipments.

Gamma.app Review: Best AI Presentation Tool for Enterprises?
Gamma.app Review: Best AI Presentation Tool for Enterprises?

Google Play Console App Content & Access Requirements

Google Play Console handles review information through its App Content (Policy > App content) and Store Listing settings. Rather than a single metadata box, Google requires structured declarations across multiple policy categories before publishing apps to the Google Play Store.

1. App Access Declarations

Under Google Play policy, developers must explicitly state whether parts of the app are restricted based on credentials, geo-location, network settings, or membership fees.

  • All Functionality Available Without Restrictions: Selected only if every screen and feature can be accessed without logging in or configuring specific settings.
  • Restricted Access: If any screen requires authentication, developers must add explicit access instructions inside Google Play Console, including username, password, pin codes, and step-by-step instructions for entering restricted areas.

2. Data Safety & Privacy Policy Links

Google requires developers to complete a comprehensive Data Safety form detailing what user data is collected, shared, and encrypted. Developers must provide a valid, publicly accessible URL pointing to their privacy policy. The privacy policy must explicitly disclose data handling practices, third-party SDK usage, and account deletion procedures.

3. Financial, Government, and Health Declarations

Apps operating in sensitive domains must submit specialized credentials and background documentation:

  • Financial Services: Proof of licensing, regulatory registration, or authorization to offer credit, banking, or investment services.
  • Government Entities: Official authorization letters on government letterhead if an app represents or delivers public agency services.
  • Health & Medical Features: Clear documentation validating health data collection compliance and regulatory classification (where applicable).

Comparison: Apple App Store Connect vs. Google Play Console Review Requirements

The structural requirements for providing app review information differ significantly between Apple's and Google's developer ecosystems:

Requirement Category Apple App Store Connect Google Play Console
Primary Location App Version Page -> App Review Information App Content (Policy > App Content) & Main Store Listing
Test Credentials Format Single Username/Password pair with text Notes field Structured "App Access" rules with custom credential sets
Contact Info Rules First/Last Name, Phone Number, Email on every submission Developer Contact Email on Store Listing; Account Owner info in console
Video Attachments Supported directly in review metadata upload Supported via external links (e.g., YouTube) in declarations
Privacy Disclosures App Privacy Details (Nutrition Labels) on store page Data Safety Form & mandatory Privacy Policy URL
Rejection Appeal Channel App Store Review Board / Resolution Center Play Console Policy Appeals & Support Ticket System

Common Reasons for Rejection Related to Review Information

Submitting incomplete or inaccurate app review information is a primary driver of app approval delays. Understanding where review submissions fail allows teams to audit their metadata prior to release.

Common Submission Failure Points:

  1. Inaccessible Test Credentials (2FA blocked, expired accounts)
  2. Broken URLs (Privacy Policy, Support URL returning 404/500 errors)
  3. Missing Hardware/Environment Instructions
  4. Undeclared Data Collection or Incomplete Privacy Labels

1. Inaccessible or Expired Test Credentials

Reviewers test thousands of builds daily. If a reviewer attempts to log in using the supplied test account and encounters an "Invalid Password," "Account Locked," or an unhandled 2FA prompt, the review is immediately halted, and the app is rejected under performance guidelines.

  • Prevention: Test the review credentials on a clean installation of the production/release build immediately before clicking "Submit for Review." Ensure the staging server or database holding the test account is persistent and publicly reachable.

2. Broken Support or Privacy URLs

App store policies mandate that all public support links and privacy policy URLs submitted in review metadata must be live and accessible. If an automated web crawler or human reviewer encounters a 404 Not Found or 500 Internal Server Error on your privacy policy link, submission processing stops.

  • Prevention: Host privacy policies on stable, high-availability content distribution networks (CDNs) and avoid using temporary landing pages or local staging links (localhost or internal VPN paths).

3. Unexplained External Dependencies or Hardware Requirements

If an app opens to a blank screen or an infinite loading spinner because it cannot connect to a physical IoT device, local server, or custom accessory, reviewers will reject the app as incomplete.

  • Prevention: Explicitly state hardware prerequisites in the Review Notes. Provide a video demonstration link showing the application connected to the physical device, and include a offline/demo mode in the build so reviewers can interact with the user interface without physical hardware present.

4. Mismatch Between Review Information and App Behavior

If your reviewer notes state that an app does not collect user location, but the binary contains background location framework permissions (NSLocationAlwaysUsageDescription or Android location permissions), app reviewers will issue a query asking for clarification.

  • Prevention: Align your technical configuration, privacy labels, and reviewer notes prior to uploading your final archive.

Step-by-Step Checklist for Preparing Your App Review Information

Before submitting your next release candidate, run through this verification checklist to minimize approval friction.

Phase 1: Contact & Operational Verification

  • Verify that the listed contact name, phone number (with country code), and email address are monitored by someone available during the 24–48 hour review window.
  • Confirm that external backend servers, staging APIs, and databases supporting the build are online and fully accessible from international IP ranges (including Apple and Google review locations in the US, Europe, and Asia).

Phase 2: Account & Access Configuration

  • Create a dedicated test account with realistic sample data.
  • Verify that 2FA/SMS verification is bypassed or disabled for the test account credentials provided.
  • If the app features tiered roles (e.g., Admin, Buyer, Seller), provide login credentials for each distinct user role in the Review Notes.

Phase 3: Metadata & Compliance Audit

  • Test all public-facing URLs (Privacy Policy, Terms of Service, Support Page) in an incognito web browser to ensure no authentication or paywalls block public access.
  • Clear away internal debug UI elements unless they are specifically instructed for reviewer usage in the Review Notes.
  • Draft concise, actionable Review Notes explaining non-obvious features, sandbox payment procedures, or hardware requirements.
  • If required, attach an MP4/MOV screen recording demonstrating complex features or physical device integrations.

How to Handle App Rejections and Review Communications

When an app is rejected due to missing or inadequate review information, both Apple and Google provide dedicated communication channels within their developer portals.

Resolving Rejections in Apple App Store Connect (Resolution Center)

When Apple issues a rejection, the details appear in the App Store Connect Resolution Center.

  1. Read the Specific Guideline Citation: Apple explicitly cites the guideline violated (e.g., Guideline 2.1 - Performance - App Completeness or Guideline 5.1.1 - Legal - Privacy).
  2. Provide Missing Details Directly in the Resolution Center: If the rejection is purely due to missing credentials, clear instructions, or an unhandled login state, reply directly to the reviewer in the Resolution Center with updated credentials or operational steps.
  3. Resubmit the Build (If Required): If the issue required code changes (such as fixing a crash on launch or updating binary permissions), upload a new build version, update the App Review Information fields, and submit the new build for review.

Detailed information regarding guidelines, submission workflows, and appeal channels can be reviewed on the official Apple Developer App Store Review page and the App Store Connect Help Portal.

Resolving Rejections in Google Play Console

Google Play issues rejection alerts via email and through the Policy Status tab in Google Play Console.

  1. Review the Violation Details: Google provides text descriptions and screenshots highlighting policy non-compliance (such as missing App Access declarations or broken links).
  2. Update App Content Declarations: Go to Policy > App Content in Google Play Console, update the relevant declaration forms (such as App Access or Data Safety), and save the changes.
  3. Submit an Update or Appeal: If you believe the decision was made in error or if you have updated your app access credentials, submit an appeal or release an updated build through the Production or Testing tracks.

To review detailed policy requirements and access management guidelines, visit the Google Play Console Help Center.

Frequently Asked Questions

What should I put in the "Notes for Reviewer" field if my app is simple?

If your app does not require a login, external hardware, or complex environment settings, you can keep the reviewer notes concise. State that no login is required, all features are accessible upon launch, and briefly summarize the core function of the app. If your build uses standard sandbox environments for testing in-app purchases, mention that in-app purchases can be tested using standard sandbox test accounts.

How do I handle Two-Factor Authentication (2FA) for app reviewers?

App reviewers cannot complete dynamic SMS or authenticator-app 2FA challenges during automated or manual testing. To bypass this, configure a static OTP (One-Time Password) code for the specific test phone number or email address assigned to the reviewer account (e.g., hardcoding 123456 for reviewer@example.com in your staging backend). Alternatively, disable 2FA entirely for the demo credentials during the review period.

Do I need to update App Review Information for every app release?

You do not need to re-enter contact information or test credentials for every app release if they remain unchanged. App Store Connect and Google Play Console retain your previously submitted review details across updates. However, you must update the information whenever test account passwords change, new restricted features are introduced, or new hardware dependencies are added to the application.

Will app store reviewers make real financial transactions when testing my app?

No, reviewers will not use real credit cards or spend real money during app evaluations. For apps utilizing Apple StoreKit or Google Play Billing, reviewers execute test purchases using platform sandbox environments. If your app processes payments through third-party gateways (like Stripe, PayPal, or Square), you must provide test/sandbox credit card numbers and instructions in the Review Notes so reviewers can complete checkout flows without incurring actual charges.

Can I submit a video demonstration instead of giving reviewers access to my app?

A video demonstration cannot replace physical access to the application binary. Reviewers must interact with the live build to evaluate performance, UI responsiveness, and security compliance. However, providing a video link or file attachment alongside your live test credentials is allowed—and encouraged—if your app requires proprietary physical hardware, specialized location triggers, or enterprise infrastructure that cannot be duplicated easily in a testing lab.

Recommended Next Steps

To streamline your deployment workflow and minimize approval turnaround times:

  1. Establish a Dedicated Review Account Infrastructure: Build persistent, isolated staging accounts specifically dedicated to app store testing that are never deleted or modified during automated database cleanups.
  2. Audit Privacy Disclosures Early: Ensure that your app review information, privacy policy disclosures, and actual SDK telemetry match completely prior to initiating submission.
  3. Keep Credentials Updated: Immediately after updating staging passwords or API keys, update the App Review Information fields in App Store Connect and Google Play Console before triggering a release candidate build.