7 Total
0 High severity
6 Medium severity
1 Low severity
Summary

This is Windsurf's security and privacy disclosure covering how the company handles code data, model inference, subprocessors, and deployment options for its AI code assistant products. For individual users on cloud plans, logs containing code snippets and user interaction trajectories may be retained unless the user manually enables zero-data retention mode from their profile page; for Teams and Enterprise plans, zero-data retention applies by default. The document also discloses that multiple AI inference providers including OpenAI, Anthropic, Google Vertex, xAI, and Fireworks receive code data, each under zero-data retention agreements, while Bing API receives query data derived from code without such an agreement.

Technical / Legal Breakdown

This document is Windsurf's security and privacy disclosure page (last updated March 11, 2025), governing data flows, subprocessor relationships, deployment architectures, and compliance posture for an AI-powered code assistant platform serving individual developers and enterprise customers. The document states that for individual cloud plans without zero-data retention mode enabled, logs that may contain code snippets and user trajectories could be stored, while teams and enterprise plans apply zero-data retention by default; the policy discloses that OpenAI, Anthropic, Google Cloud Vertex, xAI, and Fireworks each receive code data for inference with zero-data retention agreements in place, while Bing API receives text potentially derived from code data without a zero-data retention agreement. The document identifies a notable operational distinction for individual users: zero-data retention is opt-in rather than default, meaning code snippets and usage trajectories may be retained and accessible to internal analytics tools including Retool, Raindrop, Metabase, and Tableau unless the user actively enables the mode; the document also discloses that OpenAI and Anthropic models may be leveraged independent of user model selection for background tasks such as summarization. The document references SOC 2 Type II certification, FedRAMP High accreditation, and HIPAA compliance posture with optional Business Associate Agreements, engaging frameworks relevant to federal procurement, healthcare data handling, and enterprise data residency requirements. Compliance teams should note that the Bing API integration for web search lacks a zero-data retention agreement and requires explicit Team or Enterprise administrator enablement, and that individual user data protections are materially weaker than enterprise defaults absent active opt-in to zero-data retention mode.

Institutional Analysis

Institutional analysis available with Compliance

Regulatory exposure by statute, material risk assessment, vendor due diligence action items, and enforcement precedent. Available on Compliance.

Start Compliance free trial

1 important change detected

3 versions captured · Last updated: May 2026

What changed Windsurf updated its Security & Data Handling policy on May 16, 2026 to disclose two practices involving data exposure. The policy now states that Windsurf uses Raindrop, a third-party service, to view usage analytics and aggregate statistics, and that users not using Zero-data retention mode may have their logs exposed for debugging purposes. Previously, this disclosure was not present in the policy.
Why this matters The updated policy now explicitly states that Windsurf uses Raindrop to view usage analytics and aggregate statistics, and that debug logs may be exposed for users not on zero-data retention mode. Previously these practices were not disclosed in the policy. The policy establishes that Zero-data retention mode provides more restricted log access, while standard users operate under different log exposure terms. You can switch to Zero-data retention mode to limit debug log exposure.
View full change record →

Recent Provision Changes Jun 2, 2026

Added (2)
Account Deletion and Zero-Data Retention Medium

New provision explicitly addresses account deletion and data retention practices, clarifying that zero-data retention applies by default for enterprise/team plans.

Subprocessor Code Data Access Disclosure Medium

New provision adds plan-dependent disclosure of subprocessors and introduces Google Cloud Platform as a subprocessor with conditional code data storage.

Removed (3)
Internal Tool Access to Code Logs Without Zero-Data Retention

Removal of transparency about internal tool access (Slack, Google Workspace, Retool) and debugging data discussions suggests either consolidation into other provisions or de-emphasis of internal data handling disclosures.

HIPAA Compliance and Business Associate Agreement Availability

Removal of explicit HIPAA compliance and BAA availability statements removes transparency about healthcare data handling and regulatory compliance options.

Subprocessor Disclosure and Data Exposure Scope

Removal of Oracle Cloud from subprocessor list and restructuring of subprocessor disclosure format; Oracle Cloud's code data access capability is no longer explicitly disclosed.

Modified (3)
Model Use Independent of User Selection

Provision was renamed from 'AI Model Use Independent of User Selection' to 'Model Use Independent of User Selection' with identical content.

Code Ownership and Attribution Filtering

Changed detection methodology from 'line-by-line fuzzy matching algorithm of hashes' to 'Jaccardian edit-distance' and added explicit statement about sanitizing training data.

Real-Time and Ahead-of-Time Personalization Data Collection

Severity was downgraded from 'medium' to 'low' while content remained identical.

2 provisions unchanged.

View full change record →
Medium — 6 provisions
Low — 1 provision

Monitoring

Windsurf has updated this document before.

Monitor includes same-day alerts, structured change summaries, and monitoring for up to 25 platforms.

Start Monitor free trial Or create a free account →

Compliance Governance Intelligence

Need provision-level monitoring and regulatory mapping?

Compliance includes governance timelines, compliance memos, audit-ready analysis, and full provision tracking.

Start Compliance free trial

Cross-platform context

See how other platforms handle Account Deletion and Zero-Data Retention and similar clauses.

Compare across platforms →

Mapped Governance Frameworks

CCPA/CPRA
California, USA
View official text ↗
Connecticut Data Privacy Act Amendments
US-CT
View official text ↗
FTC Act Section 5
United States Federal
View official text ↗
GDPR
European Union
View official text ↗
Indiana Consumer Data Protection Act
US-IN
View official text ↗
Kentucky Consumer Data Protection Act
US-KY
View official text ↗
Universal Opt-Out Mechanism Expansion 2026
US
View official text ↗
Archival ProvenanceSource & Archival Record
Last Captured June 2, 2026 20:42 UTC
Capture Method Automated scheduled archival capture
Document ID CA-D-000783
Version ID CA-V-003348
SHA-256 bcb9b134abe873978bb3d42f93e1a7d30bb231d67d58d1373f714dd1c17cf18b
✓ Snapshot stored ✓ Text extracted ✓ Change verified ✓ Hash verified

Governance Monitoring

Monitor governance changes across the platforms you rely on.

Structured alerts for policy changes, governance events, and provision updates across 318+ platforms.

Create free account Compare plans