Adam Frankel
General Counsel · Technology & AI
15+ years as General Counsel to technology, cloud & AI companies
Privacy Policy by Mozilla
The Mozilla Privacy Policy is a general, organisation-wide privacy statement that explains how Mozilla collects, uses, shares, and protects personal data across its products and services. It is an official policy from Mozilla, a globally trusted open-source organisation, providing authoritative guidance for lawful data handling, transparency, and user privacy.
[company name] Privacy Policy
[date of last update]
Your privacy is an important factor that [company name] (that's us) considers in the development of each of our products and services. We are committed to being transparent and open. This [company name] Privacy Policy [link to privacy policy] explains generally how we receive information about you, and what we do with that information once we have it. You can also read our product privacy notices and FAQs to get more detail with respect to each of our products and services.
What do we mean by "personal information?"
For us, "personal information" means information which either directly identifies you (like your name, email address, or billing information) or can be reasonably linked or combined to identify you (like an account identification number or IP address). We’ll always tell you what personal information we’re collecting from you. See each product’s Privacy Notice for specific details.
Any information that falls outside of this is "non-personal information."
If we store your personal information with information that is non-personal, we will consider the combination as personal information. If we remove all personal information from a set of data then the remaining is non-personal information.
How do we learn information about you?
We learn information about you when:
you give it to us directly (e.g., when you choose to send us crash reports);
we collect it automatically through our products and services (e.g., when your Firefox browser checks with us to see if it is up to date);
someone else tells us information about you (e.g., when Thunderbird works with your email providers to set up your account); or
when we try and understand more about you based on information you've given to us (e.g., when we use your IP address to customize language for some of our services).
What do we do with your information once we have it?
When you give us information, we will use it in the ways for which you've given us permission. Generally, we use your information to help us provide and improve our products and services for you.
For users in the EU, EEA, Switzerland, and California: see here for more information.
When do we share your information with others?
When we have asked and received your permission to share it.
For processing or providing products and services to you, but only if those entities receiving your information are contractually obligated to handle the data in ways that are approved by [company name].
When we are fulfilling our mission of being open. We sometimes release information to make our products better and foster an open web, but when we do so, we will remove your personal information and try to disclose it in a way that minimizes the risk of you being re-identified.
This is a preview. The full template is free on GitLaw.
About this template
What is this template?
This is a high-level privacy framework that defines the boundary between personal and non-personal information. It contains specific sections for automatic browser-based data collection and mandatory breach notification procedures. It is not a detailed cookie policy or a specific data processing agreement.
When should you use it?
Use this when launching a suite of software products where a general umbrella policy is needed alongside individual product notices. Use a Website Terms of Use instead if the document should focus on site behavior rather than data handling.
What's inside
| Clause | Name | What it does |
|---|---|---|
| What do we mean by "personal information?" | What do we mean by personal information? | Defines personal information as data that directly identifies a person, including name, email address, billing information, account ID, or IP address. |
| How do we learn information about you? | How do we learn information about you? | Lists four data collection methods: direct submission, automatic collection through products, third-party provision, and inferring details from existing information. |
| When do we share your information with others? | When do we share your information with others? | Permits data sharing with vendors who are contractually obligated to handle data in approved ways or when necessary to prevent harm. |
| How do we store and protect your personal information? | How do we store and protect your personal information? | Obliges the company to notify users of security breaches and limits data retention to the period necessary for the original collection purpose. |
| What if we change this privacy policy or any of our privacy notices? | What if we change this privacy policy? | States that continued use of services after an effective date constitutes acceptance of substantive updates announced via blogs or forums. |
Who it's for
- a technology provider collecting crash reports and IP addresses from product users
- a software company needing a modular policy that refers to specific product privacy notices
- an organization operating in the EU, Switzerland, or California requiring high-level data transparency
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.
Jurisdiction
European Union
Switzerland
California (US)
Document info
HTML document. Document created on Wed Dec 10th, 2025. Last updated on Wed Dec 10th, 2025.
This document is public
Licensed under CC BY-SA 4.0 (Attribution-ShareAlike).
Come to agreements faster
Write, review, negotiate, and manage legal contracts
Related documents
US
Firefox OS Privacy Notice by Mozilla
This privacy notice explains how an operating system handles user data related to updates, location services, and device activation. It outlines user options for disabling data sharing for app usage and search engine analytics directly within device settings.
Updated 13 Aug 2026
US
Security Policies Github Sirt Description Rfc 2350 (GitHub)
This document provides a standardized description of a Computer Security Incident Response Team (CSIRT) following the RFC 2350 protocol. It details contact methods, the team's mission and authority, and specific procedures for handling security incidents.
Updated 13 Aug 2026
US
Security Policies Coordinated Disclosure Of Security Vulnerabilities (GitHub)
This policy establishes a framework for security researchers to find and report vulnerabilities in a company's software. It introduces a bug bounty program that offers financial rewards for coordinated disclosure and provides links to specific legal safe harbor terms.
Updated 13 Aug 2026
US
Firefox Relay Privacy Notice by Mozilla
This privacy notice outlines how an email alias service handles user data, including the processing of email messages and account information. It details data collection for Firefox Accounts, interaction logs, and technical device data while clarifying that email content is not read or stored.
Updated 13 Aug 2026
European Union
Content Moderation Practices by Mozilla
This document outlines how an organization manages content moderation for user-generated text, images, and software applications. It specifies the human-led review process for reports of illegal or policy-violating content and the subsequent appeals procedure for both reporters and account holders.
Updated 13 Aug 2026
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.
1
Open
Pick a template and open it. Nothing to download, and no credit card to start.
Free to open
2
Edit with AI
Describe your situation in chat and the agent adapts the wording, clause by clause.
Tracked changes you can review
3
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.
Adam Frankel
General Counsel · Technology & AI
15+ years as General Counsel to technology, cloud & AI companies
Juliana Calil
Principal Counsel · Technology & Entertainment
20+ years in-house at Google, Intel, Disney and Looker
Adam Wardel
General Counsel, Data Privacy Officer & AI Advisor
12+ years leading legal & privacy for SaaS and AI companies
John Hoffman
Associate Director, Corporate Counsel · Life Sciences & Technology
20+ years in corporate counsel, incl. senior counsel at Certara
Richard Nohe
General Counsel · Telecom, Cloud & Data Centers
20+ years in-house, regional General Counsel at BT across 30+ countries
Joe Al-Khayat
General Counsel · Technology & High-Growth Companies
Cross-jurisdictional M&A and SaaS contracting across the UK, US & Australia
Joshua Woo
Technology, AI & Privacy Counsel · APAC
Former Goldman Sachs Executive Director for AI, cybersecurity & privacy in APAC
Sahil Verma
International Business & Investment Lawyer
13+ years in business law, investment law & dispute resolution
Matthew Willis
CRO & General Counsel · SaaS
Former President of the ACC's 2,200-attorney Chicago Chapter · JD + Kellogg MBA
Mayowa Ogunrinola
Legal Consultant · Fintech & AI Compliance
Regulatory strategy, AI governance & data protection for fintech and AI
Steven J. Shanker
Partner and Chair of Corporate and Employment Law
25+ years as a corporate & employment attorney in New York
Rebecca Babbage
Legal Counsel · Financial Services, Corporate & Governance
UK-qualified solicitor working in-house with regulated entities in financial services
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.