“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.”
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
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.
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 →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
Please note that any changes you make to your account profile must be in accordance with our App Use Standards.
NVIDIA AI Workbench is licensed for use under Section 1.1.1 and Section 1.1.2.2, and not licensed for use under Section 1.1.2.1.
Send bulk emails, meaning commercial or marketing emails directed to a number of individuals with the same content, through Mailchimp Inbox.
"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
Get the research letter
Companies change their terms quietly. We read every version and catch what actually changed. One email a week on the changes that matter and what they mean.
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.
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.
ConductAtlas has identified this type of provision across 274 platforms. See the full comparison.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Windsurf.