Free Data Breaches & Incident Management Templates

Data Breaches & Incident Management: 14 free templates to browse without an account, then edit with an AI agent and e-sign in GitLaw.

These documents address internal data handling and external responses to security events. The collection includes a Data breach notification policy for UK GDPR compliance and an RFC 2350 CSIRT description for security incident response teams. General privacy requirements are handled here, but specific employment-related data handling should be sought in Human Resources.

  • 14 templates
  • Free to edit with AI
  • No account needed to browse

Community library

Everything else in this category, uploaded by the GitLaw community. Read any of it free - check it fits your situation before you rely on it.

US
Business Associate Agreement by Common Paper
This document is a Business Associate Agreement (BAA) designed to ensure compliance with the Health Insurance Portability and Accountability Act (HIPAA) regulations concerning Protected Health Information (PHI). It outlines the specific obligations of a Provider (acting as a Business Associate or Subcontractor) and a Company (acting as a Business Associate or Covered Entity) regarding the use, disclosure, and safeguarding of PHI. The agreement incorporates standard terms and allows for customization through a key terms cover page.
Updated 17 Oct 2025
Content Removal Policies Github Private Information Removal Policy (GitHub)
This document outlines GitHub's policy and process for removing private, high-risk information, such as exposed access credentials or sensitive personal data, from its repositories. It details what qualifies as "private information" and guides users on how to submit a removal request, including the necessary information and the steps GitHub will take. The policy also clarifies what types of content are not covered by this specific removal process.
Updated 17 Oct 2025
US
Security Policies Github Sirt Description Rfc 2350 (GitHub)
This document describes the GitHub Security Incident Response Team (SIRT), outlining its mission to protect GitHub's platform and user data by maintaining confidentiality, integrity, and availability. It provides essential contact information, details the team's operational policies, and explains the scope of its incident response and proactive security activities. The document also guides users and customers on how to report vulnerabilities and access support.
Updated 17 Oct 2025
Security Index by Basecamp
This document provides an overview of the security measures implemented by a service provider to protect user data. It details practices such as data encryption in transit and at rest, redundancy for systems, physical security of servers, regular infrastructure updates, and protection of billing information. The document emphasizes the company's commitment to data security and its long history in business.
Updated 17 Oct 2025

Browse other categories

Data Governance
463 documents
Cybersecurity
314 documents

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

Nexus logoMlabs logoTechstars logo

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.

5.0 out of 5 on Google

Read reviews

As seen in

Law360
Artificial Lawyer
Insider
Axios Pro
San Francisco Business Times
Built In
Startups Magazine
Business Reporter
Tech.eu

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.