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 policy permitting Windsurf to use customer data for model training purposes to improve services. Previously, the company required explicit opt-in before any training use. Under the revised policy, data training occurs automatically for free and paid users unless they affirmatively opt out through the Data Controls settings page. Once disabled, the terms state your data will not be used for training and Zero Data Retention will be enabled with model providers. Enterprise customers operate under a different standard, requiring express prior written consent before any training use occurs.
View change record →The updated document establishes explicit commitments about how Windsurf protects data and manages security. The terms state that all data transmission is encrypted in transit and at rest, that access to production systems is restricted to a small number of employees or contractors based on business roles, and that production systems are monitored via logging, error handling, and monitoring dashboards. The document discloses that Windsurf obtained SOC 2 Type II certification as of March 2024 and that all employees and contractors are required to use multi-factor authentication and receive annual security training. These disclosures describe organizational practices rather than establishing new user-facing rights or obligations.
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.
You will comply with Service-specific notices if applicable, such as any warnings not to input sensitive or confidential information.
Please take steps to secure your access credentials such as login name and password, and do not share them with anyone.
Monitoring
Windsurf has changed this document before.
Receive same-day alerts, structured change summaries, and monitoring for up to 25 platforms.
"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 Windsurf Security & Data Handling
Compliance Governance Intelligence
Need to monitor specific governance provisions?
Compliance includes provision-level monitoring, governance timelines, regulatory mapping, and audit-ready analysis.
Built from archived source documents, structured governance mappings, and historical version tracking.
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 285 platforms. See the full comparison.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Windsurf.