The document states that the Slack integration is limited to processing only data explicitly provided in Slack threads where Devin is tagged, with no access to broader Slack instance data.
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 provision defines the data minimization scope of the Slack integration, limiting Devin's data access to thread-specific interactions. This disclosure is operationally relevant for organizations concerned about Devin accessing broader Slack workspace data.
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 →Under this provision, the Slack integration processes only data explicitly shared in @Devin-tagged threads and does not access or store other Slack workspace data. Users retain control over what data enters the Devin processing scope by managing what is shared within those threads.
Cross-platform context
See how other platforms handle Slack Integration Data Minimization Disclosure and similar clauses.
Compare across platforms →"In Slack, Devin doesn't read, process or store any data in your Slack instance other than the information provided when @Devin is tagged, initially prompted and when any additional information is provided within the Slack thread while the session is ongoing.Excerpt from Windsurf's Security & Data Handling
(1) REGULATORY LANDSCAPE: This provision is relevant to GDPR data minimization and purpose limitation principles, as it defines the scope of processing within the Slack integration.
Enforcement risk, jurisdiction flags, contract triggers, and due diligence action items.
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 provision defines the data minimization scope of the Slack integration, limiting Devin's data access to thread-specific interactions. This disclosure is operationally relevant for organizations concerned about Devin accessing broader Slack workspace data.
Under this provision, the Slack integration processes only data explicitly shared in @Devin-tagged threads and does not access or store other Slack workspace data. Users retain control over what data enters the Devin processing scope by managing what is shared within those threads.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Windsurf.