Understanding mobile app names and Developer Account names

Edited

Overview

This article explains why your mobile app name should match your Apple Developer Account or Google Developer Account name when possible, and what to prepare if Apple or Google requests proof of ownership, permission, or copyright rights during app review.


How it works

Apple and Google review mobile apps before they are approved for the App Store or Google Play Store. During review, they may compare your app name, Developer Account name, app metadata, and app content to confirm that you have the right to publish the app and use the content.

Choosing a mobile app name

When completing your mobile app specs form, choose a mobile app name that clearly represents your organization and content. When possible, use a name that matches or closely aligns with the name on your Apple Developer Account or Google Developer Account.

If the mobile app name is different from the Developer Account name, Apple or Google may request proof that the app, content, and Developer Account belong to the same organization or are being used with proper permission. Preparing documentation before the app is submitted can help you respond quickly if Apple or Google asks for proof of ownership, licensing, or affiliation.

As the app owner, you are responsible for making sure you have the necessary intellectual property rights to distribute your app through Apple or Google. If you need help understanding which parts of your iOS and Android mobile app are provided by Lightcast and which parts are provided by your organization, contact Customer Support.

When to prepare a proof of ownership or permission letter

A proof of ownership or permission letter may be needed if your mobile app name is different from your Developer Account name.

The letter should explain the relationship between:

  • Your organization

  • Your Apple Developer Account or Google Developer Account name

  • Your mobile app name

  • The content included in the app

The letter should include:

  • Your name or company name

  • The Apple Developer Account name or Google Developer Account name

  • The mobile app name

  • A clear explanation of how the Developer Account name and app name are connected

  • Details explaining your affiliation with the business, organization, or app

  • Relevant signatures and dates

If you need a permission letter template, contact Customer Support.

For Android mobile apps

Google allows documentation to be submitted in advance through the Provide advance notice form. Use this form when your Android mobile app name is different from your Google Developer Account name and you want to send documentation to Google before app review or before a rejection occurs.

For full steps, see Submit documentation to Google in advance below.

For iOS mobile apps

Apple does not currently provide the same advance documentation process that Google provides. If Apple requests proof during app review, respond through App Store Connect and attach your permission letter, license agreement, or other proof of rights.

For full steps, see Submit documentation if Apple or Google requests proof below.

When to prepare a license agreement

Prepare a license agreement or other proof of rights if the app includes content, graphics, branding, or other materials that your organization did not create.

If the app includes content produced by you or your organization, explain that the content was produced by you or your team and that you own the rights to use it in the app.

A permission or affiliation letter explains the relationship between your Developer Account name and your mobile app name. A license agreement or proof of rights may be needed to show that you are allowed to use specific content, graphics, branding, or other materials in the app.


Instructions

Use the steps below only if you need to submit proof of ownership, permission, licensing, or affiliation to Google or Apple.

Submit documentation to Google in advance

Step 1

Prepare a permission letter, license agreement, or other proof of rights before the app is submitted.

The documentation should show that you are authorized to use the app name, content, graphics, and related metadata.

Step 2

Submit the documentation to Google through the Provide advance notice form.

Step 3

Complete the form with the requested app and account details.

You may be asked to provide:

  • First name

  • Last name

  • Email address

  • Application package name

Step 4

Attach your permission letter, license agreement, or other proof of rights.

Google may accept documentation such as:

  • An agreement between both parties stating your authorization to use the content

  • A declaration, authorization letter, or contract signed by both parties

  • A licensing or distribution agreement signed by both parties

Google may not accept screenshots, emails, or other non-verifiable correspondence as proof of permission.

Step 5

After submitting the documentation, save any confirmation details from Google.

If Google later rejects the app or requests proof, use those details when responding to Google.

Submit documentation if Apple or Google requests proof

Use this section if Apple or Google asks for proof during app review. Follow the Apple steps for iOS mobile apps and the Google steps for Android mobile apps.

If Apple rejects your app

If Apple rejects the app because of a name, copyright, brand, permission, or intellectual property concern, review the reason listed in App Store Connect and follow the steps below.

Step 1

Log in to your App Store Connect account.

Step 2

Click Apps in the top menu.

Step 3

Find the app that was rejected.

If the app tile shows View App Review Issues & Messages, click that link to open the app review issues.

Step 4

Open the rejected app version.

If the app has both an iOS version and a tvOS version, select the platform that Apple rejected.

The rejected version may show a status such as Rejected, Metadata Rejected, or something similar.

Step 5

Click View Submission in the red box that says This item requires your attention.

This opens Apple’s app review message.

Step 6

Review Apple’s rejection message carefully so you can respond with the correct documentation.

Step 7

Click Reply to App Review.

Step 8

Enter your reply to Apple.

Your reply should explain that you have the rights to use the app name, content, graphics, and related metadata.

Step 9

Click Attach File and attach your permission letter, license agreement, or other proof of rights.

Step 10

Click Reply to submit your response to Apple.

Step 11

After Apple approves your documentation, contact Customer Support and let them know Apple accepted your documentation.

This is important because Lightcast’s developers need to know when the iOS mobile app can be resubmitted.

If Google rejects your app

If Google rejects the app because of a copyright, name, brand, permission, impersonation, or intellectual property concern, review the reason listed in the rejection email or in the Google Play Console.

Step 1

Log in to the Google Play Console.

Step 2

Find and open the rejected app.

You may see the app marked as Draft with an App rejected update status.

Step 3

Click on Go to Policy status.

Step 4

You may see the rejection listed under Policy issues. Click the arrow to open the policy issue details.

Step 5

Google may show where the issue was found, such as the app icon, app name, store listing, graphics, or other app content.

Step 6

Review Google’s How to fix section.

Google may direct you to submit an appeal and provide documentation that you are authorized to use the content in your app.

Step 7

Click Submit an appeal.

You may see this option in the rejection email from Google or inside the policy issue details in Google Play Console.

Step 8

Select the reason for appealing.

If you have documentation to provide, select I have additional documentation to provide.

Google may direct you to use the Provide advance notice form if your documentation can be submitted there.

Step 9

If the appeal form does not allow you to attach documentation, submit your documentation through the Provide advance notice form.

Then complete the appeal and explain that documentation has been submitted to Google for review.

Step 10

Submit the appeal.

Google notes that it may take up to 7 days to receive a response, but it may occasionally take longer.

Step 11

After Google approves your claim, contact Customer Support and let them know Google accepted your documentation.

This is important because Lightcast’s developers need to know when the Android mobile app can be resubmitted.


FAQs

Why should the mobile app name match the Developer Account name?

Matching the mobile app name to the Apple Developer Account or Google Developer Account name can help Apple or Google confirm that the account owner has the right to publish the app and its content.

If the names do not match, Apple or Google may request additional documentation before approving the app.


Can the mobile app name be different from the Developer Account name?

Yes. However, Apple or Google may ask for proof that you have the right to use the app name, brand, content, graphics, and related metadata.

This does not always mean the app cannot be approved. It means you may need to provide documentation that explains the relationship between the app name and the Developer Account name.


Can the iOS mobile app and Apple TV app use the same app name?

Yes. The iOS mobile app and Apple TV app can use the same app name if both apps are bundled together in the same Apple Developer Account.

Lightcast must have access to your Apple Developer Account so both apps can be developed and submitted with the same app name.


How does Lightcast get access to the Apple Developer Account?

Lightcast must be invited to your Apple Developer Account as an Admin.

For full setup instructions, see How to create an Apple Developer Account for your Apple TV or iOS mobile app.


Should proof of ownership be prepared in advance?

Only if the Developer Account name differs from the app name. Preparing this documentation in advance can help prevent delays if Apple or Google requests proof during the app review process.

You do not need to submit the documentation unless Apple or Google rejects the app or asks for it.


Can documentation be submitted to Google before the app is reviewed?

Yes. If your Android mobile app name is different from your Google Developer Account name, or if Google may need proof that you have the right to use the app name, content, graphics, or related metadata, you can submit documentation to Google in advance through the Provide advance notice form.

This can help reduce delays if Google requests proof during app review.


Can documentation be submitted to Apple before the app is reviewed?

Apple does not currently provide the same advance documentation process that Google provides. If Apple requests proof during app review, respond through App Store Connect and attach your permission letter, license agreement, or other proof of rights.


What documentation may Apple or Google request if the app name and Developer Account name are different?

Apple or Google may request documentation that confirms the relationship between your organization, your Developer Account, your app name, and the content in the app.

This may include a permission letter, license agreement, proof of ownership, or other documentation that shows you have the right to publish the app and content.


What should be provided if the app contains licensed content?

If your app contains content that was not produced by your organization, be prepared to provide license agreements or written permission showing that you have the right to use the content in your app.


What should be provided if the app contains original content?

If your app contains content produced by you or your organization, explain to Apple or Google that the content was produced by you or your team and that you own the rights to use it in the app.


What should happen after Apple or Google approves the copyright or permission claim?

After Apple or Google approves your claim, contact Customer Support and let them know your documentation was accepted.

Lightcast’s developers need this information so they can continue with the mobile app submission process.


Additional related resources

Was this article helpful?

Sorry about that! Care to tell us more?

Thanks for the feedback!

There was an issue submitting your feedback
Please check your connection and try again.