Netlify Dec 4 terms: verified domains can see staff accounts and may absorb them

What changed

Netlify published a changelog on Nov 4, 2026 saying it updated its Self-Serve Subscription Agreement, Privacy Statement and Acceptable Use Policy, and that the changes take effect on December 4, 2026. We compared the live Self-Serve Subscription Agreement PDF (Last Updated: November 4, 2026) to the prior PDF archived by the Wayback Machine on Oct 16, 2026 (Last Updated: October 1, 2025), and read the live Privacy Statement (Last updated: November 4, 2026).

Change 1: Verified Domains can see that your account exists

Section 6.6 is new. It is not in the October 1, 2025 agreement. The November 4 text says that if Netlify verifies that an organization owns or controls the domain of the email address on your account, Netlify may disclose to that organization "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."

The same section says Netlify will not, under 6.6, disclose payment information, or your name, email or username "other than as they may appear in any account names, site names, or URLs," and will not disclose Customer Content that is not publicly accessible. "Verification alone does not give that organization access to or control over Customer's account."

Netlify's own changelog puts the same point in plain English: an organization that proves the domain "may show it that your account exists, its plan type, and the names, URLs, and last deploy dates of your publicly accessible sites," and never shows your name, email, username or payment information that way.

Change 2: Account moves are restated, with Customer Content named

The October 1, 2025 agreement already warned, in the preamble before section 1: if the domain of your account email is owned or controlled by an entity that has (or later gets) a direct subscription agreement with Netlify, "your account may be rolled into and consolidated with that organization's account after notification to you," and if you do not change the email, "your account will be controlled by the entity."

The November 4 agreement moves that rule into section 2.1 (Accounts and Email Addresses). It says the account "may be consolidated into that organization's account after notice to Customer." If you do not change the email "within the period stated in such notice, the account, including its Customer Content, will be controlled by that organization."

So Dec 4 is not the first day Netlify could absorb a domain-matched account. What is new for readers is the pairing with Verified Domains visibility, the notice-window wording, and the explicit line that Customer Content goes with the moved account.

Change 3: Privacy Statement adds Verified Organizations and an opt-out

The Privacy Statement dated November 4, 2026 adds an "Organization domains" processing purpose that points to sections 6.6 and 2.1, and a "Verified Organizations" disclosure category with the same account-exists / plan / public-site fields. Section 8 says you can "Opt out of domain visibility at any time by contacting us at privacy@netlify.com," and that changing your account email to one outside the organization's domain before the date in a move notice stops the transfer. The changelog repeats both steps.

What stays the same

Enterprise Master Subscription Agreement customers are still under that agreement, not this self-serve one. The November 4 agreement also keeps Netlify's line that it will not use Customer Content to train or fine-tune AI models unless the customer opts in.

What you can do

Personal projects on a work email are the risk case. Change the email, or email privacy@netlify.com for visibility opt-out, and watch for any move notice after Dec 4.

Coverage (checked Nov 9, 2026): Netlify's own changelog is the announcement. The independent tracker toolongdidnotread.it flagged the Privacy Statement change. A Spanish-language blog (rubenloan.com) also covered it. We found no English-language news story from The Register, TechCrunch or similar on this Dec 4 update when we checked.

Who it affects

Anyone with a Netlify account whose email is on a company or school domain, especially personal projects signed up with a work email

Quick answers

Can my employer see my personal Netlify sites after December 4, 2026?

Only if it verifies ownership or control of the domain on your account email, and only for sites that are publicly accessible. Section 6.6 says Netlify may show account existence, plan type, and public site names, URLs and last deploy dates. It says verification alone does not give the organization access to or control over the account, and private or password-protected site content is not disclosed under 6.6.

Can Netlify move my account into my company's Netlify account?

Yes, if the domain of your account email is owned or controlled by an organization that has a subscription agreement with Netlify. Section 2.1 says Netlify will notify you first; if you do not change the email within the period in that notice, the organization controls the account and its Customer Content. A similar consolidation warning already appeared in the October 1, 2025 preamble.

How do I opt out of domain visibility?

Email privacy@netlify.com. Netlify's changelog and Privacy Statement both say that stops showing your account to verified organizations. Separately, change your account email to one outside the organization's domain before any move-notice deadline if you do not want the account absorbed.

When do the Netlify changes take effect?

December 4, 2026, per Netlify's Nov 4 changelog. The Self-Serve Subscription Agreement PDF and Privacy Statement are both marked Last Updated / last updated November 4, 2026.

Is Verified Domains brand new?

Yes in the self-serve agreement we compared. The October 1, 2025 PDF (Wayback capture Oct 16, 2026) has no section 6.6 and no disclosure of plan type or public site lists to a verified domain owner. Account consolidation for domain-matched emails did already exist in that older preamble.

Source

Detected on the Netlify terms page: https://www.netlify.com/changelog/updates-to-our-terms-and-privacy-statement/. Always check the source; this summary is not legal or financial advice.

Other sources:

• Netlify changelog: Updates to our Self-Serve Subscription Agreement, Privacy Statement, and Acceptable Use Policy (changes take effect Dec 4, 2026)
• Netlify: Self-Serve Subscription Agreement, Last Updated November 4, 2026 (PDF fetched Nov 9, 2026)
• Netlify: Self-Serve Subscription Agreement, Last Updated October 1, 2025 (Wayback Machine capture Oct 16, 2026)
• Netlify Privacy Statement, last updated November 4, 2026 (fetched Nov 9, 2026)
• tldr (toolongdidnotread.it): Netlify Privacy Statement changes dated 2026-11-04

Provenance: detected in our Nov 9 snapshot of the Netlify terms page. Excerpts marked "Quoted from the documents" come from the sources linked above.

Published by QuietlyChanged: pages tracked automatically, each change reviewed by a person before publishing. About · Contact & corrections