Terms of Use

These terms cover the use of MV3 Extension Dev Hub — what you may do with the writing and the code samples, and what the site does and does not promise about them. They are written to be read once and understood, because a documentation site whose terms are unreadable has failed at its own subject.

By using the site you accept these terms. If you do not, the appropriate response is not to use it.

Licence for the written content

The articles, explanations, diagrams and page structure are made available under the Creative Commons Attribution 4.0 International licence. In practice that means you may:

• Share the material in any medium or format.
• Adapt it — remix, transform and build upon it — for any purpose, including commercially.

The one condition is attribution: credit MV3 Extension Dev Hub, link back to the page you used, and indicate whether you changed anything. You may not apply legal or technological measures that restrict others from doing anything the licence permits.

Attribution should be recognisable to a reader. Naming the site and linking to the specific page is sufficient; a bare link with no context, or a credit buried where readers will not see it, is not.

Licence for the code samples

Code samples — anything inside a code block, including manifest fragments, JavaScript, shell commands and configuration — are dedicated to the public domain under CC0 1.0. You may copy them into your own projects, proprietary or open source, without attribution and without any obligation.

This split is intentional. Prose benefits from attribution because it carries authorship; a five-line snippet showing how to register a listener does not, and requiring credit for it would make the samples less useful than they are meant to be. If you are unsure whether something is prose or a sample, the code block is the boundary.

What the site does not warrant

The content is provided as is, without warranty of any kind, express or implied, including but not limited to warranties of merchantability, fitness for a particular purpose and non-infringement. Specifically:

• Browser behaviour changes. Extension APIs, permission policies, store review requirements and browser version numbers move. A page accurate when written can be wrong by the time you read it, and the modified date on each page is the only claim made about currency.
• Samples are illustrative. Code is written to demonstrate a technique clearly, not to be dropped unmodified into production. Error handling, logging, telemetry and edge cases are frequently simplified or omitted, and where they are, the surrounding prose usually says so.
• Store outcomes are not guaranteed. Pages describe how review processes work in practice and what reviewers commonly ask for. No page can promise that a particular extension will be accepted; the stores decide, and their criteria change.
• No advice relationship. Reading the site does not create a professional or advisory relationship, and nothing here is legal advice — including the descriptions of licensing and store policy, which are a developer’s account of how these processes work rather than a lawyer’s.

In no event will the site or its authors be liable for any claim, damages or other liability arising from the use of the content, whether in an action of contract, tort or otherwise.

You are responsible for testing anything you take from here against your own extension, in the browsers you support, before you ship it to users.

Acceptable use

You may read, copy, adapt and redistribute the content within the licences above. The things that are not acceptable are the ordinary ones:

• Do not attack the site. Denial-of-service traffic, attempts to gain unauthorised access, or probing the host for vulnerabilities are not permitted.
• Do not scrape abusively. Automated fetching at a rate that degrades the site for other readers is not acceptable. Reasonable crawling that respects robots.txt is fine, and the full sitemap is published to make it unnecessary to guess at URLs.
• Do not misrepresent the source. Republishing content in a way that implies it was written by someone else, or that the site endorses a product it does not, goes beyond what the licence permits.
• Do not present adapted content as unmodified. If you change the substance of an article, say so, particularly where a change makes technical guidance different from what was published here.

Trademarks

Chrome, Firefox, Safari, Edge and their logos are trademarks of their respective owners. This site is independent and is not affiliated with, endorsed by or sponsored by Google, Mozilla, Apple, Microsoft or any browser vendor.

Product names are used descriptively — to say which browser a behaviour applies to — and that descriptive use does not transfer any rights in the marks. The Creative Commons licence covers the content of this site; it does not grant any licence to any third party’s trademarks.

Links to other sites

Pages link to vendor documentation, specifications, package registries and other external resources. Those sites are outside our control, and a link is not an endorsement of the linked site, its content, its terms or its privacy practices. External resources can move or disappear, and a broken external link is a defect worth reporting rather than a change in these terms.

Availability

The site is provided on a best-effort basis. There is no service level commitment, no guarantee of uptime and no guarantee that any particular URL will remain available indefinitely. Where a page is removed or merged, a redirect will be used if one is practical, but permanence is not promised.

Content may be corrected, expanded, restructured or withdrawn at any time. Because the site is published from a version-controlled repository, previous versions of a page are part of that history even when they are no longer the version served.

Privacy

How the site handles information is described separately in the privacy policy, which forms part of these terms by reference. The short version: no accounts, no analytics, no advertising and no tracking cookies.

Corrections and contributions

Technical documentation goes out of date, and a correction is more valuable than a complaint. If a page describes an API that has changed, a limit that has moved or a review requirement that no longer holds, the contact address on the site is the place to send it — a version number and a link to the vendor’s own documentation makes a correction quick to verify and quick to apply.

Sending a correction does not transfer any rights beyond what is needed to publish it: if a suggestion is incorporated, the resulting text is published under the same Creative Commons licence as the rest of the prose. Corrections are applied to the live page and the modified date is updated, so a page that has been corrected says so through its own metadata.

Severability

If any provision of these terms is held to be unenforceable, that provision is limited or removed to the minimum extent necessary and the remaining provisions continue in effect. In particular, an unenforceable limitation of liability does not affect the licences granted above, which stand on their own.

Changes to these terms

These terms may be updated. The modified date at the top of the page changes when they are, and continued use of the site after a change constitutes acceptance of the updated version. Changes that affect the licences above — the terms under which you may already have used the content — will not be applied retroactively: material you obtained under the previous licence remains under it.

Summary

Prose is Creative Commons Attribution 4.0; code samples are CC0 and free to take without credit. Everything is provided without warranty, browser behaviour changes faster than documentation does, and you should test before you ship. Browser names belong to their owners, and the site is not affiliated with any of them.