Websites & Communications Terms of Use by Mozilla
The Mozilla Websites & Communications Terms of Use set the rules for using Mozilla’s websites, social channels, newsletters, and related services, covering content licensing, submissions, accounts, acceptable use, and liability limits. As an official Mozilla policy document, it provides authoritative, trusted guidance on rights, responsibilities, and permitted use across Mozilla’s online ecosystem.
Websites & Communications Terms of Use
[effective date]
Terms of Use
Introduction
Please read the terms of this entire document (“Terms”) carefully because it explains your rights and responsibilities when you visit any of [company name]’s websites (“Websites”), or related feeds, social media, newsletters, source code repositories, and emails (together with Websites, these are collectively referred to as “Communications”). By accessing or signing up to receive Communications, you agree to be bound by these Terms.
Our Websites include multiple domains such as [example domains]. You may also recognize our Websites by nicknames such as [example nicknames]. Some of our Websites connect you with links, apps or add-ons that are provided by other parties and are subject to separate Terms.
Account Registration
Some Websites require you to register for an account in order to access additional features of a Website or another [company name] service. If applicable, additional terms will be presented to you. You are responsible for all activities under your account.
Some Websites allow you to create a username during registration. Your use of a username must comply with our Acceptable Use Policy.
Content Licensing
Our Communications include content such as articles, images, photographs, comments, software code, audio and video clips, and other materials (collectively, “Content”). Content is authored by [company name], contributors to [company name] projects, and other sources.
Content authored by [company name] is generally made available for public sharing and reuse through open licenses such as Creative Commons (for expressive material) or the [company name] Public License (for software code). In most cases we ask [company name] contributors to release Content under open licenses.
Some Content in our Communications is acquired from sources that prohibit further use of their Content without advance permission. Where possible, the Content or Website footer will display a notice with the applicable license. You agree to abide by such notices. Note the following specifics:
Some Content expressly indicates that the author does not intend for an open license to apply. You should contact the author or author’s agent for permission to use such Content. Questions on [company name] authored content can be sent to: [email address].
Some Content contains trademarks, trade dress, logos and brand assets of [company name] and other parties (“Trademarks”). Except for a few limited circumstances, Trademarks cannot be used without advance written permission of the owner of the Trademark. Learn more on [company name] trademarks.
Software used by our Websites is licensed under the MPL or similarly permissive open source licenses. For more information on the specific license, please see the applicable source code or GitHub repository.
Content Submissions
You may contribute Content when interacting with our Communications, including but not limited to commenting on an article, blogging, contributing code, or contributing graphics or written material (each a “Submission”). Unless your Submission is made under a separate agreement with [company name], in which case that agreement will govern, then
For Submissions to [company name]'s open source projects:
This is a preview. The full template is free on GitLaw.
5.0 out of 5 on Google
Read reviewsAs seen in
About this template
What is this template?
This document is a combined website terms of service and communications policy that specifically addresses open-source project contributions. It contains a distinct section for submissions to open source projects versus general submissions and includes a specific liability cap of [amount and currency]. It is not a standalone software license agreement like the MPL.
When should you use it?
Use this template when operating a community-driven website where users contribute code or expressive content under open-source frameworks. Use a standard Terms of Business instead if the primary purpose is the direct commercial sale of goods or services.
What's inside
| Clause | Name | What it does |
|---|---|---|
| 2 | Account Registration | Requires users to comply with an Acceptable Use Policy when creating usernames for additional Website features. |
| 3 | Content Licensing | Applies open licenses like Creative Commons or the Mozilla Public License to content authored by the company. |
| 4 | Content Submissions | Grants the company a royalty-free, worldwide, sublicensable license to use user-contributed graphics, code, or written material. |
| 7 | Notice of Claimed Infringement | Directs users to a specific URL for reporting copyright or trademark infringement claims. |
| 8 | Term; Termination | Permits the company to terminate access if users create legal exposure or if providing Communications is no longer commercially viable. |
| 10 | Limitation of Liability | Caps the collective liability of the company and Indemnified Parties at a specific [amount and currency]. |
| 12 | Miscellaneous | Subjects all claims to the exclusive jurisdiction of the courts in a specified [county name, state name]. |
Who it's for
- an organization hosting open source project repositories and related community newsletters
- a website operator requiring broad licenses for user-submitted code and expressive content
- a digital publisher managing multiple domains and social media feeds under a unified policy
How long it runs and how it's signed
Law it's drafted under
California note
This version is drafted for California. US contract and employment rules vary by state, so it will not transfer cleanly elsewhere. Tell GitLaw where the parties are and it adjusts the draft.
Frequently asked questions
A template isn't binding on its own - like any contract, it becomes binding once it's properly completed and signed. Templates in our curated library are professionally drafted for US or UK law; review any template before you sign it.
Yes. Chat with GitLaw to edit any section, or make changes directly in the editor.
Yes, read about team plans here.
Describe what you need in the chat and GitLaw will draft it for you.
Templates in our curated library are professionally drafted for US or UK law. The wider library comes from the GitLaw community and public sources - a solid starting point, but check any template fits your situation before you rely on it.
Mostly US and UK law. Some templates use general commercial terms that work across jurisdictions, and many note which law they're written for.
It depends on the situation. Templates work well for routine business agreements. For anything involving significant money, complex IP, employment, or areas you're unsure about, it's worth getting professional advice before you sign. GitLaw provides templates and tools, not legal advice.
Open any template in GitLaw and describe the change you want in the chat — 'make clause 4 mutual' or 'add a 30-day notice period', for example. GitLaw drafts the revised language and shows it as a suggested edit. You accept, reject, or keep editing from there.
Yes. Upload a Word, PDF, or Markdown file and GitLaw will open it in the editor. You can review, edit, or chat with GitLaw about it the same way you would with any template from the library.
Trusted by 5,000+ businesses
From template to signed, in one place
Every template opens in an editor with an AI agent alongside it.
Open
Pick a template and open it. Nothing to download, and no credit card to start.
Free to open
Edit with AI
Describe your situation in chat and the agent adapts the wording, clause by clause.
Tracked changes you can review
Send and sign
Share it for negotiation, then collect signatures without leaving GitLaw.
eSign included
Built for your legal work,
with practicing lawyers
Trained on 5,500+ clauses and specialist areas of law. Built with a standards committee of independent lawyers.
As seen in
Ready to get started?
No sales calls, no credit card. Just chat with GitLaw.
GitLaw provides templates and tools, not legal advice. Templates are a starting point, not a substitute for advice on your situation - for anything significant, speak to a qualified lawyer.