Add submission restriction list

LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2019 Flow-Launcher
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

README.md

@@ -37,14 +37,30 @@ Looking for a list of currently available plugins in Flow? Visit [here](https://
    ```
 5. For `IcoPath`, use a CDN provider for global accessibility. [jsdelivr.com](https://www.jsdelivr.com/) for example as shown above, works well with GitHub repositories.
 6. It is a requirement to set up a GitHub Actions workflow for automated build and release. Follow the guide [here](https://www.flowlauncher.com/docs/#/py-setup-project?id=_1-add-github-workflow) and use [this](https://github.com/Flow-Launcher/Flow.Launcher.Plugin.HelloWorldPython/blob/main/.github/workflows/Publish%20Release.yml) as an example.
-7. Submit a pull request.
-8. The plugin will be available in Flow after the pull request is approved by the Flow Launcher Team.
+7. It is a requirement that your plugin conforms with the [Plugin Store policy](#plugin-store-policy).
+8. Submit a pull request.
+9. The plugin will be available in Flow after the pull request is approved by the Flow Launcher Team.
 
-Flow downloads the plugins manifest file from various CDN providers, which means the availability of your new plugin depends on when these providers sync their updated files. This syncing process can take several days—sometimes up to a week—across all providers. During this period, you may see intermittent updates for your plugin in the manifest, as the provider chosen for retrieval is selected randomly based on the fastest fetch speed.
+Flow downloads the manifest (plugins.json) file from various CDN providers, which means the availability of your new plugin depends on when these providers sync their updated files. This syncing process can take several days and sometimes up to a week across all providers. During this period, you may see intermittent updates for your plugin in the manifest, as the provider chosen for retrieval is selected randomly based on the fastest fetch speed.
 
-Every three hours the *CI* in this repository will check for new updates from plugins and automatically update them to the latest version. 
+While the plugin has not yet appeared in the store, you and your users can manually install it using `pm install <url/local path>`.
 
-Plugin submissions that could potentially harm the computer or contains malicious code will not be accepted.
+## Plugin updates
+
+Every three hours the *CI* in this repository will check for new updates from plugins and automatically update them to the latest version.
+
+## Plugin Store policy
+
+Plugins that facilitate or contain any of the following will not be allowed:
+- Malicious code
+- Piracy
+- Deceptive use
+- Inappropriate content
+- Illegal activities
+- Impersonation
+- Abuse
+- Fraud
+- Spam
 
 ## Plugin Store