10+ Google Chrome Web Store applications/extensions developer program policies

10+ Google Chrome Web Store applications/extensions developer program policies


10+ Google Chrome Web Store applications/extensions developer program policies
10+ Google Chrome Web Store applications/extensions developer program policies

Brief on Chrome Web Store Developer Program Policies


  • Contents
  • Content Policies
  • Security Vulnerabilities
  • Deceptive Installation Tactics
  • Spam Placement in the Store
  • User Data Privacy
  • Ads in Chrome Apps Extensions
  • Extensions Quality Guidelines
  • Chrome Apps Quality Guidelines
  • Accepting Payment from Users
  • Policy Enforcement

Developer program policies


Branding guidelines Evaluation Guides | Program procedures Frequently asked questions about user data Agreement with developers

The developer program criteria listed below play an important role in providing a positive experience for anyone using the Chrome Web Store. These policies apply to the entire application/extension user experience unless otherwise noted.

Please be aware that these policies are related to your application/extension, hereinafter referred to as the "App", as well as to all the declarations grouped or made available through the App. Please note that these policies have the meaning set out in the Google Chrome Web Store Developer Agreement. Keep in mind that there are also additional quality guidelines that apply to Chrome apps and extensions. Since these policies may vary, check from time to time.



Chrome Web Store Content policies


Our content policies apply to product content, to any advertising you show to users, and to any user-generated content that you host or connect to. In addition, they apply to any content in your developer account that is publicly displayed in the Chrome Web Store, including your developer name and the landing page of your listed development website. Products that contain inappropriate content for all ages must be marked as "mature" in the developer dashboard.

Sexually explicit material:

Content that includes nudity, graphic sexual activity, or sexually explicit material is not allowed. In addition, we do not allow content that drives traffic to commercial porn sites. Google has a zero-tolerance policy toward child pornography. If we are aware of child pornography content, we report it to the competent authorities and delete the Google accounts of those associated with the distribution.
Violent or threatening behavior:

Descriptions of unwanted violence are not allowed. Applications should not contain materials that intimidate, harass or intimidate other users.

Hate speech:
We do not allow content to discuss against groups of people based on their race or ethnic origin, religion, disability, gender, age, veteran status, or sexual orientation/gender identity.

Deception or fraudulent behavior:

Don't act like anyone else and don't represent that your app is authorized by another company or organization or not. The products or ads contained in them must not imitate activities or warnings from the user's operating system or browser. Products must not contain false or misleading information, including content, title, logo, description, or screenshots. Here are some specific checks you can perform to ensure that your item complies with our policies:
The specs should specify the functionality of the app so that users can understand the extension they are adding.

The screenshots should show the functionality of the extension in action.

Developers should not redirect users or provide links to other sites that mimic the Chrome Web Store or pass as the Chrome Web Store. Do not misrepresent the functionality of your app or add explicit non-functionality to the main purpose of the app without explicit notification to the user. If your item contains an empty description field or an icon or screenshot is missing, it will be rejected. If any of the content, title, icon, description, or screenshots of your article contain false or misleading information, we may remove it.

Intellectual property:

Do not infringe on third-party intellectual property rights, including patents, trademarks, trade secrets, copyrights, and other property rights. We will respond to explicit notices of alleged copyright infringement. For more information or to submit a DMCA request, use this tool.
Illegal activities:
Keep it legal. Do not engage in illegal activities in the product, such as selling drugs without a prescription.

Gamble:

We do not allow content or services that facilitate online gambling, including online casinos, sports betting, lotteries, or specialized games that offer money or other value.

Harmful products:

Do not transmit viruses, worms, defects, Trojan horses, malware, or other destructive objects. We do not allow content that could damage or interfere with the operation of networks, servers, or other infrastructures of Google or third parties. Spyware, malicious scripts, and password phishing are also prohibited in the Chrome Web Store.

Code readability requirements:

Developers should not obscure the code or hide the functionality of their extension. The same goes for any external code or resource received through an extension packet. Minimization is allowed,

including the following modules:

Eliminating whitespace, newlines, code comments, and block delimiters
Reduction of the names of variables and functions
Compress the files
Prohibited products:

We do not allow products or services to:
Facilitate unauthorized access to website content, for example by avoiding paywalls or access restrictions
Encourage, facilitate or enable unauthorized access, download, or streaming of copyrighted content or media
My cryptocurrency.


Chrome Web Store Security vulnerability

If your item is linked to a security vulnerability that could be compromised by another application, service, browser or system, we may remove your item from the Chrome Web Store and take other measures to protect users. If so, you may be contacted regarding the corrective steps necessary to restore the item.

Chrome Web Store Fraudulent installation strategies

Extensions must be sold responsibly. Extensions that use or exploit fraudulent installation strategies are removed from the Chrome Web Store.

Spam and positioning in the store
Developers are important partners in maintaining a rich user experience in the Chrome Web Store.

Repetitive content: We don't allow any developer or its affiliates to post multiple extensions that provide fake experiences or functionality in the Chrome Web Store.

Keyword spam: Extensions with misleading, poorly formatted, inexplicable, irrelevant, excessive, or inappropriate metadata are not allowed, including but not limited to description, developer name, title, logo, screenshots, and promotional images. Developers should provide a clear and well-written explanation. We also do not allow testimonials from distributed or anonymous users in the app description.

User ratings, reviews, and installations: Developers shouldn't attempt to change the placement of any extensions in the Chrome Web Store. These include, by way of example, the installation of classifications, reviews, or classifications of products through illegal means such as downloads, fraudulent or promotional reviews, and classifications.

Activity: Do not publish an extension for the sole purpose of installing or launching another app, theme, web page, or extension.

Abuse of notification: associated extensions or improper use of notifications by sending spam, advertisements, promotions, phishing attempts, or unwanted messages that could damage the user's browsing experience are not allowed.

Message Spam: We do not allow extensions to send messages on behalf of the user without the user having the ability to verify the content and intended recipients.

In addition to these requirements, all extensions must comply with Google's webmaster quality guidelines.

Privacy of user data

You must be transparent about how you manage user data, including how you collect, use,   and share data (e.g. information provided by a user or about a user or product or the use of a Chrome browser). Disclosure of data should be limited. This policy establishes the minimum privacy requirements for user data of the Chrome Web Store; You or your product must comply with applicable laws.



Personal or sensitive user data

Privacy policy and secure publication


If your product retains your personal or sensitive user data (including personally identifiable information, financial and payment information, health information, authentication information, website content and resources, form data, web browsing functionality, content provided by a user, and personal information), your product must:

Extension quality guidelines


The extension should have a single purpose that is narrow and easy to understand. Do not create extensions or download local executable files to accept unrelated feature packs such as the email notifier and news headline aggregator. If the two features are clearly separate, they should be placed in two separate extensions and users should be able to install and uninstall them separately. For example, functionality that displays product ratings and reviews, but places ads on web pages, doesn't have to be grouped into one extension. Likewise, toolbars that provide a wide range of functionality or service access points are provided as separate extensions so that users can select the desired services. Please see this FAQ for more information.

As of July 1, 2017, extensions must use the designated Chrome API for any changes to the user's existing settings, including the settings replacement API (which includes the API for the home page, the search provider, and the default startup page) and URL. Replaces (API for managing bookmarks, the history page, and the new tab).

Chrome app quality guidelines


To ensure an exceptional user experience, the Chrome apps provided through the Chrome Web Store must follow the additional quality guidelines listed below. The guidelines in this section apply only to Chrome apps.

Packaged app:

Take advantage of the platform's features and don't surround existing websites or start a web page without providing additional features.
Identify the offline status and clearly report the status to the user.
Automatically restore without loss of Internet connectivity and restart normal functionality when connectivity is restored without the user having to restart the app.
Packaged and hosted applications should not:

Requires a local executable instead of the Chrome runtime.
Provide a web view of a website you don't own or manage.
Dynamically download or run scripts outside a sandbox environment, such as Webview or Sandboxed Iframe.
Abuse of notifications through spamming, advertising, any promotions, phishing attempts or sending unwanted messages in general.


Ads in Chrome apps and extensions


Advertisements for the purpose of content review and compliance with the Developer Rules are considered part of the product. Therefore, we want to remind you that all of the above content policies apply. Advertisements that conflict with the content rating or extension of your apps also violate our Developer Terms. Be careful of using ads that don't violate the Chrome Web Store Developer Terms.

Accept payments from customers


If you collect sensitive personal information through your product for sale, you must meet these requirements:

All personal credit card information and other sensitive information must be securely collected, stored, and transmitted in accordance with privacy and data security laws and payment card industry regulations.
Misleading customers should be avoided. For example, clearly and honestly describe the products or services you are selling and clearly publish your conditions of sale (including any refund and return policies).

If the user has to pay for the product to get the basic functionality, it is necessary to clarify in the description that the user sees when choosing whether to install it or not.
You must clearly identify that you are a seller of products or services, not Google.
Regardless of the payment method, it is not possible to process prohibited payment transactions for Google Checkout under the Google Checkout Vendor Terms of Service. This includes any illegal transaction or the sale or exchange of illegal or prohibited goods or services, including prohibited products specified in the Google Checkout Content Policy.https://developer.chrome.com/webstore/deceptive_installation_tactics


More Tips:














Comments

  1. Great Share. Thanks for this. I loved it.
    Also, I created one website on Sofa Reviews. So if you want to purchase some sofa, or looking for new sofas, then here is the link to my website ClickHere for more information related to Sofas.

    ReplyDelete
  2. This article is awesome. meanwhile I have also written one article on Monitors and technology. So if you want to check it out then you can Click here for more information related to Monitors

    ReplyDelete

Post a Comment

Most Useful Articles

How to Make Blogger BlogSpot Layout As Responsive Template

How to Show Blogger Widgets in Mobile View with Simple Steps

How to Create Internal Links within The Post in Blogger

How to Display Blogger Posts in Grid View with Thumbnails

How to Get Back A Hacked Facebook Account and Secure within 10 Steps

Blogger Login Google Account: How to Create a New Google Account(Gmail)