1. The Impersonation policy in Google's own words. Google Play's Impersonation policy (https://support.google.com/googleplay/android-developer/answer/9888374) has two operative sentences: "We don't allow apps that mislead users by impersonating someone else (for example, another developer, company, entity) or another app." and "Don't imply that your app is related to or authorized by someone that it isn't." The scope sentence that decides most take-downs follows immediately: "Be careful not to use app icons, descriptions, titles, or in-app elements that could mislead users about your app's relationship to someone else or another app." The policy summary adds that you "must not coordinate with others to mislead users." There is no declaration form and no warning that cures a violation - the compliant state is honest metadata, not a disclosure you file afterwards.
2. Google's own example list is the best predictor of enforcement. Four buckets are enumerated: (a) developer names that falsely imply an official relationship with Google; (b) icons and titles that falsely imply a relationship with another company / developer / entity - e.g. using a national emblem to look government-affiliated, or copying a business's logo to look like its official app; (c) titles and icons "so similar to those of existing products or services that users may be misled" - e.g. borrowing a popular cryptocurrency site's logo, or a famous TV show's character and title to look affiliated; (d) apps that falsely claim to be the official app of an established entity - "Titles like 'Justin Bieber Official' are not allowed without the necessary permissions or rights." Apps that breach the Android Brand Guidelines fall here too.
3. Where "copycat" lives now. The standalone "Copycat apps" bullet was folded into Impersonation, and the operative test is bucket (c) above: is your title, icon or UI so close to an existing product that a user is misled about who made it, or into thinking it is the same product? Copying a competitor's functionality is not, by itself, impersonation; copying the identity (name, icon, developer name, screenshots, in-app branding) until users cannot tell the apps apart is - and it can be enforced against the lookalike even when your app is the original, because Google acts on the misleading listing, not on who shipped first.
4. The Misrepresentation policy is the other half. Google Play's Misrepresentation policy (https://support.google.com/googleplay/android-developer/answer/9888689) forbids apps or developer accounts that "impersonate any person or organization, or that misrepresent or conceal their ownership or primary purpose", and those "that engage in coordinated activity to mislead users. This includes ... apps or developer accounts that misrepresent or conceal their country of origin and that direct content at users in another country." It also forbids coordinating with "other apps, sites, developers, or other accounts to conceal or misrepresent developer or app identity or other material details, where app content relates to politics, social issues or matters of public concern." Its Key Considerations double as a self-audit: represent developer name, organisation and contact information accurately; don't conceal the app's primary purpose; make the title, icon and description honestly represent functionality; be truthful about country of origin and location in the developer profile.
5. Metadata rules compound the risk. The Metadata policy (https://support.google.com/googleplay/android-developer/answer/9898842) bans misleading, irrelevant or excessive metadata. Concretely: app titles must be 30 characters or less; no emojis, emoticons or repeated special characters in the title, icon or developer name; avoid ALL CAPS unless it is part of your brand name; no misleading symbols (a fake new-message dot, or download/install icons when the app does not download); and no text or images implying store performance or ranking ('#1', 'Best of Play 20XX', 'Editor's choice', award icons), price or promotional info ('10% off', 'free for limited time'), or Google Play programs. A title like "X Official" or a lookalike icon violates both policies at once, which is why these cases are usually removed rather than warned.
6. What is not impersonation - the reporting split. An Impersonation FAQs article (https://support.google.com/googleplay/android-developer/answer/16341334) draws the line: the Impersonation policy governs how developers display apps and whether users are misled about an app's connection to someone else; if you believe an app is using content you own, that is a copyright or trademark matter, not impersonation. If you hold the rights, file the copyright / trademark form; if you do not own or are not asserting IP rights but users are being misled, report it as impersonation. Google warns that filing under the wrong form delays or blocks processing.
7. Enforcement and the practical path. Misrepresentation and Impersonation breaches are normally enforced against the listing or the account - removal, rejection, or a repeat-offender strike that can lead to account termination - not a warning you can ignore. If your app is removed, appeal through Play Console; if you are the victim, flag the offending app for review via the store's reporting flow (and use the copyright / trademark forms when you hold the rights).
8. Pre-release identity checklist. Before you ship, confirm: the developer name and profile match your real legal entity and country; the title is 30 characters or fewer with no emojis, ALL CAPS, ranking or promo text; the icon borrows no other brand's logo, national emblem, or a confusably similar competitor mark; no 'Official' / '破解' / '加速' style prefix you are not licensed to use; the description matches what the app actually does; you claim no affiliation with Google, Apple or any company without written authorisation; multiple apps under one account do not reuse copy-pasted metadata that blurs them together; and if you do have a brand relationship, you hold the written permission to say so.