If your app was rejected on Google Play under a policy, the fix depends on which policy Google cited, so read the exact one in the Policy Center first. Two of the most common and most confusing are Impersonation, which is triggered when your app name, icon, or claims make it look like another brand, developer, or app, and Intellectual Property, which covers using someone else's copyrighted content, trademark, or brand assets without rights. For impersonation, remove the misleading branding and any implied affiliation. For an intellectual property or copyright rejection, remove the infringing content or provide proof of your rights. Both can be appealed, and if the rejection came from a third-party complaint, you generally resolve it with the complainant or through a counter notification.
Short answer
A Google Play policy rejection names a specific policy, and the right fix follows from that name rather than from guesswork. Per Google's Impersonation policy, apps must not mislead users by impersonating another developer, company, or app, or imply an affiliation they do not have, so the fix is to change the name, icon, or claims that create that impression. Per Google's Intellectual Property policy, apps must not infringe trademark or copyright, so the fix is to remove the content or show you are licensed to use it. If you hold the rights, contact the Google Play team before resubmitting, and appeal through the Policy Center if you believe the rejection is wrong.
Read the exact policy Google cited
The first step is to find the precise policy Google named, because impersonation, intellectual property, deceptive behavior, and permissions each have different fixes and the rejection message tells you which one applies. Open the Policy Center in Play Console and the rejection email, and note the exact policy title and the app version it applies to. A rejection is not a vague verdict; it points at one policy, and fixing the wrong thing wastes a review cycle.
Reading carefully also tells you whether the issue is something you control directly, like your listing text or icon, or whether it stems from a third party, like a copyright complaint from a rights holder. That distinction changes your path: a direct policy catch is fixed by editing your app or listing and resubmitting, while a complaint-driven removal is usually resolved by addressing the complaint itself. So before touching anything, confirm the named policy and whether it originates from Google's review or from an outside claim.
Impersonation rejections
An impersonation rejection means something about your app suggests it is, or is endorsed by, someone it is not. Per Google's policy, this includes an app name or icon that mimics a well-known brand or another app, a developer name that copies someone else's, or claims and imagery that imply your app is related to or authorized by a company when it is not. It does not require bad intent; a lookalike icon or a title that borrows a famous name is enough to trigger it.
The fix is to remove every element that creates the false impression. Rename the app so it does not echo another brand, replace an icon or graphics that resemble someone else's, and delete text that suggests an affiliation, partnership, or authorization you do not have. If your app is a fan project or works with a brand, make its independent status explicit rather than implied. And if you genuinely are authorized to represent the brand, that becomes an evidence question: be ready to show Google the permission, because the policy is about misleading users, not about naming a brand you are licensed to use.
Intellectual property and copyright rejections
An intellectual property rejection means your app uses content or marks that belong to someone else without the right to use them. Per Google, this covers copyright, trademark, patent, and trade secret, so it includes copyrighted images, characters, music, video, or code, and brand names or logos protected as trademarks. Importantly, modifying copyrighted content does not make it yours, so a redrawn character or an edited clip can still infringe.
You have two ways to clear it, and which one applies depends on the facts. If you do not hold the rights, remove the infringing content and any brand assets you are not licensed to use, then resubmit the clean version. If you do hold the rights, through ownership, a license, or written permission, gather that evidence, because Google may require proof that you are authorized to use the material. Google advises that if you have documentation proving authorization, you contact the Play team in advance of submission so the app is not rejected for an intellectual property violation in the first place.
When the rejection came from a third-party complaint
Some intellectual property removals are not Google spotting a problem but a rights holder filing a complaint, and these follow a different resolution path. When a copyright or trademark owner reports your app, Google acts on that notice, so the fastest resolution is usually to address the complaint itself: remove the disputed content, or if you believe the claim is mistaken or you are licensed, respond through the process Google provides.
For copyright specifically, there is a counter notification path if you believe the material was removed in error, and for a dispute the practical route is often to resolve it directly with the complainant, who can withdraw the claim. This is different from a metadata or permissions rejection you can fix alone, because a third party is involved. Recognizing that a complaint drove the removal keeps you from resubmitting an unchanged app and instead points you at either taking the content down or settling the underlying rights question.
Common policy rejections at a glance
Matching the named policy to its fix keeps you from guessing. The table below maps the common ones.
| Rejection policy | What it means | First fix |
|---|---|---|
| Impersonation | Name, icon, or claims mimic another brand or app | Remove misleading branding and implied affiliation |
| Intellectual property | Uses others' copyright or trademark without rights | Remove content or provide proof of authorization |
| Copyright complaint | A rights holder reported your app | Address the complaint or file a counter notification |
| Deceptive behavior | Misleading functionality or claims | Make the app match what the listing promises |
Read the middle column first: identifying which impression or content triggered the rejection is what tells you which fix to apply.
How to appeal a Google Play rejection
If you believe a rejection is wrong, or you have fixed the issue, you appeal through the channel in the rejection notice and the Policy Center, and the quality of the appeal matters. State plainly what the app does, identify the cited policy, and explain either why it does not apply or exactly what you changed to comply. For an impersonation or intellectual property claim where you are authorized, attach the evidence of your rights, since that is what the reviewer needs to overturn the decision.
Keep the appeal specific and honest rather than a general request to reconsider. If you were at fault, say what you corrected; if you believe the reviewer misread the app, point to the precise feature or listing element and explain it. Because enforcement generally allows a limited number of appeals per action, make the first one complete, with the fix or the proof included, rather than sending a thin message and hoping for a follow-up.
Fix checklist
Working through these steps clears most policy rejections. The checklist below covers them.
| Step | Action | Done? |
|---|---|---|
| Identify the policy | Read the exact policy in the Policy Center | [ ] |
| Determine the source | Google review or a third-party complaint | [ ] |
| Fix impersonation | Remove lookalike names, icons, and false affiliation | [ ] |
| Fix IP issues | Remove infringing content or gather proof of rights | [ ] |
| Prepare evidence | Attach authorization documents if you hold rights | [ ] |
| Appeal or resubmit | Submit a specific appeal or the corrected app | [ ] |
The step teams skip most is determining the source, because a complaint-driven removal is not solved by the same edit-and-resubmit loop as a direct policy catch.
After you fix: resubmit safely
Once you have made the change, resubmit deliberately rather than reflexively. Confirm the misleading branding is gone or the infringing content is removed across the app and the store listing, including screenshots and the description, since the rejection can cite listing assets as well as the app itself. If you are relying on a right you hold, make sure the authorization documentation is ready to attach, because resubmitting without it invites the same rejection.
Do not resubmit an unchanged app in the hope of a different reviewer, as that tends to confirm the violation rather than clear it. If your rejection was intellectual property based and you are licensed, follow Google's advice to contact the Play team in advance, so your resubmission arrives with the context that prevents a repeat rejection. A deliberate resubmission with the fix and any proof in place is what turns a rejection into an approval.
Where a scan fits
Policy rejections split into two kinds, and it is worth being clear about which a tool can help with. Impersonation and intellectual property rejections are branding and rights matters that a code scanner cannot resolve for you, so those come down to your listing, your content, and your documentation.
For the technical side of Play policy, a scanner like PTKD.com analyzes your build and flags issues that map to policy risk, such as flagged third-party code, over-broad permissions, and data handling that conflicts with your Data safety form, by severity and mapped to OWASP MASVS. To be clear about the boundary: PTKD does not clear an impersonation or copyright rejection, which are legal and branding questions. It helps with the security and permissions policies that are about your code.
What to take away
- A Google Play policy rejection names a specific policy, so read the Policy Center first and fix what it actually cites rather than guessing.
- Impersonation means your name, icon, or claims make the app look like another brand, developer, or app, so remove the misleading branding and any implied affiliation.
- An intellectual property or copyright rejection means the app uses protected content or marks without rights, so remove them or provide proof you are licensed, remembering that modifying copyrighted content still infringes.
- If a third-party complaint drove the removal, resolve it with the complainant or file a counter notification rather than resubmitting unchanged.
- Appeal specifically with your fix or your proof attached, contact the Play team in advance if you hold IP rights, and use a tool like PTKD.com for the technical policy issues in your code.
