“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
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.
You may not use our Services in any manner that infringes the rights of any third party.
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.
"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 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.
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 272 platforms. See the full comparison.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Windsurf.