Developer Program Policies – Chrome Developers

Caution

Important: As of 06/12/2018, inline initiation is deprecated. For more information, read our Chromium Blog post and Migration FAQ. Branding Guidelines | Rating Guidelines | Program Policies | User Data FAQ | Developer Agreement

The developer program policies listed below bring an important function in maintaining a positive experience for everyone using Chrome Web Store. These policies apply to the entire exploiter know of your application/extension/theme, unless differently noted. Please be mindful that these policies pertain to your software, content, and digital materials created for use in connection with Google Chrome and distributed via the Chrome Web Store, including applications, extensions, and themes, arsenic well as any ads bundled or made available through the product. These policies have the same mean as in the Google Chrome Web Store Developer Agreement. There are extra choice guidelines that apply to Chrome Apps and Chrome Extensions. Be certain to check back from time to time, as these policies may change .

# Content policies

Our message policies apply to your Product ‘s message, including any ads it shows to users and any user-generated content it hosts or links to. Further, they apply to any contented from your developer account that is publicly displayed in Chrome Web Store, including your developer diagnose and the landing page of your listed developer web site. Products that include content that may not be desirable for all ages should be marked “ Mature ” on the Developer Dashboard .

# Sexually explicit material

We do n’t allow contentedness that contains nakedness, graphic sex acts, sexually explicit fabric, or contentedness that drives dealings to commercial pornography sites. We besides do n’t allow content that promotes incest, bestiality, necrophilia, or non-consensual sexual acts. Google has a zero-tolerance policy against child pornography. If we become mindful of content with child pornography, we will report it to the appropriate authorities and delete the Google Accounts of those involved with the distribution. Content which contains non-sexual nakedness – such as aesthetic, educational, scientific, or cultural nakedness – is by and large allowed, but may impact the visibility of your product .

# Violent or bullying behavior

Depictions of complimentary violence are not allowed. Products should not contain materials that threaten, harass, or bully early users. For example, Products should not contain :

  • Content which makes a specific threat of serious harm against an individual person or a defined group of people.
  • Content whose predominant purpose is to single out another person for abuse, malicious attack, or ridicule. Content that results in the unwanted sexualization of a person, including malicious claims about a person’s sexual activities, sexual orientation, or gender identity.
  • A series of posts/comments/photos that, taken together, clearly have the primary intention of harassment, even if each individual piece of content is not severe.

# Hate speech

We do n’t allow contented advocating against or inciting hatred towards groups of people based on their subspecies or cultural origin, religion, disability, sex, age, seasoned status, nationality, sexual orientation, gender, gender identity, or any other characteristic that is associated with systematic discrimination or marginalization. additionally, the visibility of your merchandise may be impacted if it contains broadly hateful content not covered by the above definition .

# Violent extremism

We remove contentedness that recruits, fundraises, or promotes violence on behalf of extremist groups defined by the US State Department and other external organizations. violent extremism is defined as the function of violence and determent in the pursuit of political aims or goals outside of social norms .

# Impersonation or deceptive behavior

Do n’t pretend to be person else, and do n’t represent that your product is authorized by, endorsed by, or produced by another company or organization, if that is not the case. Developers should not divert users or provide links to any early locate that mimics the Chrome Web Store or passes itself off as the Chrome Web Store. Your intersection and its exploiter experience besides must not mimic functionality or warnings from a exploiter ‘s manoeuver system or browser. Any changes to device settings must be made with the drug user ‘s cognition and accept and be easily reversible by the drug user. We do not allow products that deceive or misinform users, including in the contentedness, title, description, or screenshots.

Do n’t misrepresent the functionality of your intersection or include non-obvious functionality that does n’t serve the basal function of the intersection. Descriptions of your product must immediately state the functionality sol that users have a clear agreement of the product they are adding. For case, products should not contain :

  • Claimed functionalities that are not possible to implement ( e.g. “ Who has viewed your social media account ” ) or which are not directly provided by the extension ( e.g. charge converters which entirely link to other file conversion services )
  • Any metadata that misrepresents the reference ‘s or developer ‘s current status or performance on the Chrome Web Store ( e.g. “ Editor ‘s Choice ” or “ Number One ” ) .

If your product has a blank description field or is missing an icon or screenshots, it will be rejected. If any of your merchandise ‘s content, title, icon, description, or screenshots contains false or misinform information, we may remove it .

The Chrome Web Store features products that align with our standards, values, and that we believe will produce valuable drug user experiences. certain products that do n’t meet these standards, but which do not explicitly violate CWS policies – such as VPN extensions and Video Downloaders – may be restricted from being featured in the store, but will however be available to users. For case, the pursue products are presently not featured in the CWS shop :

  • Religious or political content
  • VPNs
  • Video Downloaders
  • Anti-Virus tools
  • Content deemed not family friendly
  • Bots
  • Cryptocurrency
  • Non-production builds
  • Prohibited products
  • Gambling content
  • Extensions whose developers have questionable reputations, such as historically misleading or malicious extensions.

# Intellectual property

Do n’t infringe on the intellectual property rights of others, including patent, brand, barter secret, copyright, and other proprietary rights. We will respond to clear notices of alleged copyright misdemeanor. For more information or to file a DMCA request, use this tool. additionally, the visibility of your product may be impacted if we believe it potentially infringes on cerebral property rights .

# Illegal activities

Keep it legal. Do n’t engage in or promote illegitimate activities in your intersection, such as rape, illegal sexual activity exploit, or the sale of prescription drugs without a prescription drug. We will remove contentedness which promotes, glorifies, or encourages dangerous or illegal bodily process that may result in physical harm to those involved. We do n’t allow capacity or services that facilitate on-line gambling, including but not limit to online casinos, sports bet, lotteries, or games of skill that offer prizes of cash or other value .

# Regulated goods and services

We do not allow the facilitation of the sale of regulate Products or services. Regulated goods include pharmaceuticals, alcohol, tobacco, fireworks, weapons, gamble, or health/medical devices .

# Malicious products

Do n’t transmit viruses, worms, defects, Trojan horses, malware, or any other products of a destructive nature. We do n’t allow subject that harms or interferes with the operation of the networks, servers, or other infrastructure of Google or any third-parties. Spyware, malicious scripts, and phishing scams are besides prohibited in the Chrome Web Store .

# Code readability requirements

Developers must not obfuscate code or conceal functionality of their extension. This besides applies to any external code or resource fetched by the extension package. Minification is allowed, including the postdate forms :

  • Removal of whitespace, newlines, code comments, and block delimiters
  • Shortening of variable and function names
  • Collapsing files together

# Two step verification

To ensure the security of CWS accounts, two step confirmation is required for all developer accounts prior to publishing an extension or updating an existing elongation. Developers can activate two footstep verification for their Google Accounts hera. More information on Google ‘s two step confirmation features can be found here .

# Additional requirements for Manifest V3

Extensions using Manifest V3 must meet extra requirements related to the propagation ‘s code. specifically, the fully functionality of an extension must be well discernible from its submitted code. This means that the logic of how each annex operates should be self contained. The extension may reference and load data and other information sources that are external to the annex, but these external resources must not contain any logic. Some common violations include :

  • Including a

Leave a Reply

Your email address will not be published.