Type codeium.com/privacy-policy into a browser in August 2026 and you get a 301 redirect to windsurf.com/privacy-policy, which returns a 308 redirect to cognition.com/legal/privacy-policy. Two hops, three company names, one policy at the end of it.
That's why searching for "the Windsurf privacy policy" turns up so little. There isn't one. There's a Cognition AI, Inc policy last updated March 9, 2026, and it governs a product that was called Codeium, then Windsurf, and is now Devin Desktop.
TL;DR
The Windsurf and Codeium privacy policies both redirect to Cognition's. The current policy's default is that your code may be used for training, and the opt-out is only available on paid plans. Free tier users have no opt-out to click. On Teams, only an admin can flip it. Enterprise gets a written no-training commitment.
The redirect chain, verified
We checked these directly on 2026-08-26 rather than trusting a summary:
$ curl -sS -o /dev/null -w "%{http_code} -> %{redirect_url}\n" \
https://codeium.com/privacy-policy
301 -> https://windsurf.com/privacy-policy
$ curl -sS -o /dev/null -w "%{http_code} -> %{redirect_url}\n" \
https://windsurf.com/privacy-policy
308 -> https://cognition.com/legal/privacy-policy
The rest of the domain moved the same way. windsurf.com itself returns a 308 to devin.ai/desktop, and windsurf.com/security returns a 308 to docs.devin.ai/admin/security. A 308 is a permanent redirect that preserves the request method, which is the server's way of saying this isn't a temporary detour during a migration.
Why this matters more than a broken bookmark. Plenty of people evaluated this tool by reading Codeium's privacy policy, deciding it was acceptable, and moving on. That document is not the one that governs their account now. Nothing about the redirect tells you the terms changed, and in at least one respect that matters, they did.
What the current policy actually says
Cognition's privacy policy names Cognition AI, Inc as the controller and defines User Content as "any personal information collected when you use our Services, including personal information that may be provided in the input, file uploads, feedback or output."
Your prompts are input. Your code is file uploads and input. The model's suggestions are output. All of it is User Content.
The policy then lists, among its uses of that data, "using User Content to train, fine tune and improve the models that power our Services."
Cognition's security documentation is blunter about the default:
By default, we may use your data for model training purposes to improve and enhance the Services.
That is a different posture from an opt-in, and it is the single most important line on the page for anyone who pasted a client's codebase into the editor last year.
Who can opt out, and who can't
This is where the plan you're on stops being a billing detail.
| Plan | Can you opt out of training? | Who does it |
|---|---|---|
| Free | No opt-out available | n/a |
| Paid individual | Yes, Data Controls settings page | You |
| Teams | Yes | Administrator only |
| Enterprise | Not applicable, no training without written consent | Governed by agreement |
Cognition's docs state it plainly: "If you're on a paid plan, you can opt out at any time on the Data Controls settings page." The condition is doing real work in that sentence. If you're on the free tier, there's no setting to change.
The free tier is where the vibe-coded apps live. Founders prototyping in Windsurf are overwhelmingly on the free plan, and the free plan is precisely the one with no training opt-out. If you built something on a free account with real API keys in the repo, assume the contents of those files were eligible for training under the default. Rotating those keys is cheap. Finding out later that they weren't rotated isn't.
Opting out does more than stop training. Cognition's docs say that after you opt out, "your data will not be used for training and Zero Data Retention will be enabled with our model providers." Zero Data Retention is the setting that stops the upstream model vendor from holding your prompts, which is a separate exposure from Cognition's own training. One toggle, two effects.
The Teams caveat catches people. "On the Teams plan, only an administrator can exercise the opt-out." If you're an engineer on a team account and you flip through your own settings looking for Data Controls, you won't find a working switch. Ask your admin.
Enterprise is a different document
Enterprise customers get the commitment most security reviews are actually asking for: Cognition "will never train on your data without your express prior written consent." Cognition also holds SOC 2 Type II certification.
Check which entity your contract names. This product has been operated by Codeium, then Windsurf, then Cognition, and the corporate transaction in 2025 was messy enough that it made the tech press. If your DPA is more than a year old, the entity named on it may not be the entity processing your data today. That's a question for your legal team, not a settings page.
What to do this week
The bigger pattern
Windsurf is the clearest example of something worth watching generally: the privacy policy you evaluated is not a fixed object. It can be replaced by a redirect to a different company's document, with a different default, without anyone emailing you.
The controls that survive an acquisition are the ones on your side of the connection. An ignore file keeps a directory out of context no matter who owns the inference servers. A rotated key is rotated regardless of what a policy says about retention. A secret that was never committed can't be in anyone's training set.
We see the other side of this constantly in scans: apps deployed with live keys sitting in files that an AI editor had full read access to for months. The policy question and the exposure question look separate until you realise they're the same file.
Where is the Windsurf (Codeium) privacy policy?
It does not exist as a separate document anymore. As of August 2026, codeium.com/privacy-policy returns a 301 to windsurf.com/privacy-policy, which returns a 308 to cognition.com/legal/privacy-policy. The policy that governs your Windsurf usage is Cognition AI, Inc's, last updated March 9, 2026.
Does Windsurf train on my code?
By default, yes. Cognition's security documentation states: "By default, we may use your data for model training purposes to improve and enhance the Services." You have to opt out, and only paid plans can. On the free tier there is no opt-out to click.
How do I opt out of training in Windsurf?
Paid plans opt out on the Data Controls settings page. Cognition's docs say the opt-out also switches on Zero Data Retention with its model providers, so the change covers more than training. On the Teams plan only an administrator can do it, so an individual developer on a team account cannot opt themselves out.
Is my company's code safe on Windsurf Enterprise?
Enterprise has the strongest written commitment: Cognition states it will never train on Enterprise data without express prior written consent. Cognition also holds SOC 2 Type II. Because the corporate entity changed twice since 2024, have your legal team confirm which entity your current agreement names before relying on an older DPA.
Does the old Codeium privacy policy still apply to me?
No. The document it lived at is gone, replaced by a redirect. If you agreed to Codeium's terms in 2023 or 2024 and never revisited them, the policy governing your account today is a different document from a different company with a different training default. That is worth an actual read rather than an assumption.
Check What Your Editor Could See
CheckYourVibe scans your deployed app for exposed API keys, leaked credentials, and misconfigured endpoints. If a secret sat in a repo while an AI editor had read access, it's worth knowing whether it's still live.