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 states that users may configure and limit which GitHub repositories Devin can access, with permissions manageable through GitHub's App Settings before and after installation.
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 establishes that source code repository access is configurable by the user, placing responsibility for access scope management with the customer. The document references a GitHub Integration Guide for detailed permission and security information but does not enumerate specific permissions granted by default.
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, users control which repositories Devin may access via GitHub's App Settings, and can adjust these permissions at any time. The document directs users to the GitHub Integration Guide for specific permission details.
Cross-platform context
See how other platforms handle GitHub Integration Repository Access and Permissions 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 25 platforms.
"When setting up the GitHub integration, users can select which repositories Devin can access, with permissions adjustable through GitHub's App Settings during and post-installation.Excerpt from Windsurf's Security & Data Handling
(1) REGULATORY LANDSCAPE: Repository access configuration affects data minimization obligations under GDPR and analogous frameworks, as overly broad repository access could expose personal data or proprietary code beyond what is necessary for the service. The document does not enumerate default permissions, which limits the ability to assess regulatory exposure from this disclosure alone. (2) GOVERNANCE EXPOSURE: Medium. Organizations deploying the GitHub integration should conduct a repository access audit to ensure Devin is granted access only to repositories necessary for its function. Failure to scope access appropriately may result in broader data processing than intended. (3) JURISDICTION FLAGS: EU/EEA organizations should assess whether repository access configurations satisfy GDPR data minimization requirements. Organizations in regulated industries should review whether repository contents include personal or regulated data that would require additional controls. (4) CONTRACT AND VENDOR IMPLICATIONS: Procurement teams should review the GitHub Integration Guide referenced in this document to understand the full scope of default permissions requested by Devin. Security assessments should include a review of repository access scope as part of vendor onboarding. (5) COMPLIANCE CONSIDERATIONS: IT and security teams should document repository access configurations for Devin and establish a periodic review process. Access permissions should be revisited when repository contents change or when team membership is updated.
Full institutional analysis
Regulatory citations, enforcement risk, and due diligence action items.
Monitor: same-day alerts on the platforms you choose. Analyst: full institutional analysis.
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 provision establishes that source code repository access is configurable by the user, placing responsibility for access scope management with the customer. The document references a GitHub Integration Guide for detailed permission and security information but does not enumerate specific permissions granted by default.
Under this provision, users control which repositories Devin may access via GitHub's App Settings, and can adjust these permissions at any time. The document directs users to the GitHub Integration Guide for specific permission details.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Windsurf.