Get the weekly 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. No account.
The document advises users to store credentials such as passwords, API keys, and cookies through the Secrets feature in Settings rather than sharing them directly in prompts or sessions.
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 places responsibility on users to manage credential security by directing them to a specific product feature. The document frames this as advisory guidance rather than a platform-enforced restriction, meaning users who share credentials outside the Secrets feature do so outside the recommended security perimeter.
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 →The document advises that credentials, API keys, and authentication tokens shared with Devin should be stored using the Secrets feature in account Settings. The guidance is advisory, and the document does not describe what security controls apply to credentials shared outside this mechanism.
Cross-platform context
See how other platforms handle Secrets and Credential Handling Recommendation and similar clauses.
Compare across platforms →Monitoring
Windsurf has changed this document before.
Receive same-day alerts, structured change summaries, and monitoring for up to 20 platforms.
"You may need to provide Devin with credentials and keys such as passwords, API keys, cookies or other for authentication. In all cases we advise users to leverage our Secrets feature under the Settings page to share and store those credentials securely.Excerpt from Windsurf's Security & Data Handling
(1) REGULATORY LANDSCAPE: Improper handling of credentials and API keys may implicate security breach notification requirements under state laws and GDPR in the event of a security incident. The document's advisory framing does not create an enforceable contractual obligation on Cognition to prevent credential mishandling if users do not follow the guidance. (2) GOVERNANCE EXPOSURE: Medium. Organizations deploying Devin for software engineering workflows may expose production credentials if employees share secrets outside the designated Secrets feature. Internal security policies should address how credentials are shared with AI agents. (3) JURISDICTION FLAGS: Organizations subject to PCI DSS, SOC 2, or HIPAA should assess whether credential handling practices for AI integrations satisfy their applicable security requirements, particularly regarding secrets management for production systems. (4) CONTRACT AND VENDOR IMPLICATIONS: Enterprise agreements should address the security obligations Cognition assumes for credentials stored through the Secrets feature, including encryption standards, access controls, and breach notification procedures. The document does not describe the security architecture of the Secrets feature in detail. (5) COMPLIANCE CONSIDERATIONS: Security teams should establish internal guidelines prohibiting the direct sharing of production credentials in Devin prompts and mandate use of the Secrets feature or equivalent secrets management tools. Periodic audits of credential exposure in session logs or Feedback Data may be warranted.
This provision places responsibility on users to manage credential security by directing them to a specific product feature. The document frames this as advisory guidance rather than a platform-enforced restriction, meaning users who share credentials outside the Secrets feature do so outside the recommended security perimeter.
The document advises that credentials, API keys, and authentication tokens shared with Devin should be stored using the Secrets feature in account Settings. The guidance is advisory, and the document does not describe what security controls apply to credentials shared outside this mechanism.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Windsurf.