If your Netlify account is registered to you@yourcompany.com and the thing deployed on it is your side project, two new paragraphs in Netlify's terms are about you. They were published on November 4, 2026 and take effect on December 4, 2026.
One lets the company that owns your email domain see the account. The other lets it end up owning it.
TL;DR
From December 4, 2026, an organization that verifies it controls your account email's domain can see that your Netlify account exists, its plan, and your public sites' names, URLs and last deploy dates. If that organization also has a Netlify subscription, your account can be moved into its account after notice, users' form submissions and request logs included, unless you change the email first. Check which email your account uses today. Private sites aren't listed, and privacy@netlify.com opts you out of being shown.
What changed on November 4
Netlify's changelog entry announced a new Self-Serve Subscription Agreement, Privacy Statement and Acceptable Use Policy, effective December 4, 2026. The changelog's own summary is short and reassuring. The agreement itself (it's served as a PDF, "Last Updated: November 4, 2026") is worth reading at the clause level, because a couple of the qualifiers only appear there.
One date caveat from the agreement: changes take effect 30 days after notice, or when you accept them, if earlier. If you sign up today, they apply to you today.
Section 6.6: what a verified organization sees
An organization "may ask Netlify to verify its ownership or control" of a domain. If it does, and your account email is on that domain, the agreement says Netlify may disclose:
the existence of Customer's account, its plan type, and information about the sites under that account that are publicly accessible on the Services, such as their site names, URLs, and when they were last deployed.
Note the "such as". In the agreement, names, URLs and deploy dates are examples, not a closed list. Netlify's Privacy Statement describes the same three fields as what it will show, and says each verified organization "must agree to limit its use of this information to administering and securing its use of the Netlify Services."
Now the qualifier the changelog leaves out. The changelog says Netlify never shows your name, email address or username this way. The agreement says it won't disclose them:
other than as they may appear in any account names, site names, or URLs
So if your team is called "Jane Doe's team" and your side project lives at janedoe-invoicing.netlify.app, your name is in the listing, because it's part of the name.
Section 2.1: when the account moves
This is the clause with teeth:
If the domain of the email address associated with Customer's account is owned or controlled by an organization that has or later enters into a subscription agreement with Netlify, Customer's account may be consolidated into that organization's account after notice to Customer. If Customer does not change the email address associated with the account within the period stated in such notice, the account, including its Customer Content, will be controlled by that organization.
Three things in there are easy to miss.
The notice period isn't specified. Not in the agreement, the changelog or the Privacy Statement. It's whatever the notice says.
"Customer Content" isn't just your code. The agreement defines it as including "data that end users submit to Customer's sites and applications hosted on the Services, logs of requests that end users make to those sites and applications," and AI inputs and outputs. If your side project takes sign-ups through a Netlify form, those submissions are part of what moves.
Verification is described in the summaries, not in 2.1. Netlify's changelog and Privacy Statement describe consolidation as following a verified domain. The text of 2.1 turns only on the domain being "owned or controlled" by an organization with a subscription. We'd read it as Netlify describes it, but it's worth knowing the binding sentence is broader than the summary.
We couldn't retrieve Netlify's pre-November agreement to compare wording, and some summaries suggest an account-consolidation clause has existed in an earlier form. So treat Section 2.1 as the rule that applies from December 4, not as proof this power is brand new. Section 6.6, the verified-domain listing, is the part Netlify's changelog presents as the change.
Who this actually affects
You, if any of these describe your account:
- You signed up with your day-job email to try Netlify and the project grew into something real.
- A client or agency set up the account on their domain and you've been deploying your own work to it.
- You signed up with a university or school address.
- You signed up with a work email you no longer have access to.
That last one has its own sentence in Section 2.1: if the account's email "becomes invalid or undeliverable, Netlify may suspend or terminate the account." An address you can't read is also an address the consolidation notice goes to.
If your account is on Gmail or your own domain, none of this applies. The trigger is the domain of the email, not where you work.
The five-minute check
Read your account email. In the Netlify app, open your avatar, then User settings. Netlify's docs list email as part of your profile there. If the domain after the @ belongs to anyone but you, keep going.
Read your names the way an administrator would. Your team name, every site name, every *.netlify.app subdomain, every custom domain. Each of those can appear in the listing, and your name goes with them if it's in them.
Make side projects private if they shouldn't be listed. Section 6.6 covers sites that are "publicly accessible", and the Privacy Statement says private and password-protected sites aren't shown. Project visibility is under Project configuration > General > Visitor access. Our guide to Netlify private projects covers the catch: a private project can't receive Stripe or Slack webhooks, so a live app that takes payments has to stay public.
Decide whether to move the account. The Privacy Statement gives two exits. Email privacy@netlify.com to stop being shown to verified organizations. And change your account email to one outside the organization's domain before the date in Netlify's notice to stop the account being moved. Netlify's docs don't walk through changing the account email, so if the field isn't editable for you, ask Netlify support rather than guessing, and do it on a day you can watch your next deploy.
Moving the account is a change to the login your deploys hang off. Before you touch it, make sure you can still sign in with the new address, and that your Git provider connection under User settings still shows the right account.
The part about your users
Most coverage of a terms change like this, when there is any, is about the founder: can my employer see my side project? The clause-level reading adds a second party.
If your app collects anything through Netlify (form submissions, function logs that include request data), that's Customer Content. Consolidation hands control of it to an organization your users never dealt with. If you have a privacy policy that names who holds user data, an account on someone else's domain makes that sentence harder to keep true.
That's also the practical argument for fixing it now rather than when a notice arrives: you'd be making a hosting change with a deadline someone else set.
Can my employer see my Netlify account?
From December 4, 2026, possibly. If your Netlify account uses an email on a domain your employer controls and your employer verifies that domain with Netlify, Netlify may show its administrators that the account exists, its plan type, and information about your publicly accessible sites such as names, URLs and last deploy dates. Netlify says it does not show your name, email or username except where they appear in an account name, site name or URL.
Can a company take over my Netlify account?
Under Section 2.1 of Netlify's Self-Serve Subscription Agreement, if your account email's domain belongs to an organization with a Netlify subscription, the account may be consolidated into that organization's account after notice. If you don't change the email within the period in the notice, the account and its content are controlled by that organization.
How do I stop Netlify showing my account to a verified organization?
Netlify's Privacy Statement says you can opt out of domain visibility at any time by emailing privacy@netlify.com, and that it treats a Global Privacy Control signal as an opt-out request for California residents.
Do private Netlify sites show up for the organization?
No. Section 6.6 limits what Netlify discloses to sites that are publicly accessible, and says it will not disclose content that is not publicly accessible. Netlify's Privacy Statement adds that private and password-protected sites are not shown.
What happens to my users' data if my account is moved?
It goes with the account. The agreement defines Customer Content to include data end users submit to your sites and logs of the requests they make, and Section 2.1 says the organization controls the account including its Customer Content.
What Do Your Public Sites Show?
If a stranger can list your Netlify sites, assume they'll load them. Scan one free and see what it exposes. 60 seconds, no signup.