Provision record
Windsurf · Security at Cognition · View original document ↗

Branch protections recommended before Devin merges changes

Medium confidence Common · 272 of 343 platforms

Key Facts · in the document’s own words

What does Windsurf recommend enabling to ensure checks are enforced before Devin can merge any changes?
“enabling branch protections to ensure checks are enforced before Devin can merge any changes, and any practices currently adopted in your organization to review engineers' work.”
Version CA-V-007341, captured Oct. 4, 2026 · live source ↗
Our reading, not the document’s words
Windsurf recommends enabling branch protections to ensure checks are enforced before Devin can merge any changes.
Stay ahead of the changes
Track Windsurf and hear on the next check after its terms change. We check daily where we can, and show you where we can't.
Share 𝕏 Share in Share 🔒 PDF
ⓘ

This analysis describes what Windsurf's agreement states, permits, or reserves. It does not constitute a legal determination about enforceability. Regulatory applicability and practical outcomes may vary by jurisdiction, enforcement context, and individual circumstances. Read our methodology

ConductAtlas Analysis

Why it matters (compliance & governance perspective)

Generated by a model from the captured document; not read by a person

This clause establishes that Windsurf does not enforce branch protections by default but places responsibility on the customer to implement this safeguard before Devin can merge code.

⚠

Interpretive note: The excerpt is presented as a recommendation, not a binding obligation. The primary proposition is the branch-protection recommendation; the secondary proposition about adopting existing engineering review practices was omitted from the canonical claim.

Recent Activity

This document changed recently

High Jul 6, 2026

The updated terms establish a default permission for Windsurf to use customer data for model training to improve services. Previously, the company required explicit opt-in before any training use. Paid plan users can now opt out at any time through the Data Controls settings page, after which their data will not be used for training and Zero Data Retention will be enabled with model providers. Enterprise customers must provide express prior written consent before any training use occurs. Teams plan users cannot opt out individually; only administrators can exercise this right.

View change record →

Consumer impact (what this means for users)

Generated by a model from the captured document; not read by a person

Readers are responsible for enabling branch protections if they want to ensure checks are enforced before Devin merges changes; Windsurf only recommends this, it does not require or configure it.

How other platforms handle this

Kling AI

We kindly request you do not disclose certain Data, such as passwords, credit card numbers, PINs or other confidential data during your use of our Services.

Credit Karma

You may not use our Services in any manner that infringes the rights of any third party.

Teladoc

If you disable or delete cookies, or if you are running third-party software that intercepts or deletes cookies, please note that some parts or functionality of our Websites may not work properly.

See all platforms with this clause type →
▸ View Original Clause Language DOCUMENT RECORD
"
enabling branch protections to ensure checks are enforced before Devin can merge any changes, and any practices currently adopted in your organization to review engineers' work.

Excerpt from Windsurf's Security at Cognition

Provision details

Document information
Document
Security at Cognition
Entity
Windsurf
Tracking information
First captured by ConductAtlas
May 11, 2026
Text quoted from version
CA-V-007341, captured Oct. 4, 2026
Record ID
CA-P-061049
Document ID
CA-D-000783
Evidence Provenance
Source URL
Wayback Machine
Archived bytes SHA-256 (version CA-V-007341)
05edda171cc1c200c61b6089b90d27db45537319bc10f5fd8fdfa1a5caaa27fe
Analysis generated
July 9, 2026 07:22 UTC
Methodology
Evidence
✓ Excerpt found in version CA-V-007341, captured Oct. 4, 2026 (checked Oct. 5, 2026)
Citation Record
Entity: Windsurf
Document: Security at Cognition
Record ID: CA-P-061049
Version: CA-V-007341
Captured: 2026-10-04 00:59:06 UTC
SHA-256: 05edda171cc1c200…
URL: https://conductatlas.com/platform/windsurf/security-at-cognition/provision/CA-P-061049/branch-protections-recommended-before-devin-merges-changes/
Accessed: Nov. 16, 2026
Permanent archival reference. Stable identifier suitable for legal filings, compliance documentation, and research citation.
Classification
Categories

Other risks in this policy

Get the weekly coverage letter

Companies change their terms without announcing it. We capture governance documents, compare each new version with the last, and publish what changed, with the source text behind it. One email a week on what we found and what we could not reach.

Frequently Asked Questions

What does Windsurf's Branch protections recommended before Devin merges changes clause do?

This clause establishes that Windsurf does not enforce branch protections by default but places responsibility on the customer to implement this safeguard before Devin can merge code.

How does this clause affect you?

Readers are responsible for enabling branch protections if they want to ensure checks are enforced before Devin merges changes; Windsurf only recommends this, it does not require or configure it.

How many platforms have this type of clause?

ConductAtlas has identified this type of provision across 272 platforms. See the full comparison.

Is ConductAtlas affiliated with Windsurf?

No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Windsurf.