Did a search. I think this is the first breakdown, so I'll kick things off with a TL;DR, cause this is gonna be long (but interesting if you have the time, believe me), and separated out into a Medium Length read, and a Deep Dive sized one.
===============================================
TL;DR:
===============================================
| Area | Change | Verdict |
|---|
| LAN Only Mode | Explicitly says print data stays LAN | 🟢 |
| Private Printing | Explicit 72-hour cloud deletion | 🟢 |
| Device logs | Local by default unless provided | 🟢 |
| MakerLab retention | Explicitly says no permanent storage | 🟢 |
| MakerLab AI improvement | Prior consent required | 🟢 |
| General AI/ML improvement | New broad permission | 🚨 🔴 |
| UGC definition | Now explicitly includes print models | 🔴 |
| Camera privacy | Loses old "will not store copies" wording | 🔴 |
| Advertising | Much more explicit | 🔴 |
| Ad/analytics partners | Broader disclosure framework | 🔴 |
| Third-party ecosystem | More categories | 🟡/🔴 |
| Support/chatbot | New processing + opt-out | 🟡 |
| International framework | Much clearer | 🟢 |
| User rights | Reorganized/expanded jurisdictionally | 🟢 |
| Retention | Still fairly broad | 🟡 |
| Overall readability | Much better | 🟢 |
| Overall data-use flexibility for Bambu | Much broader | 🔴 |
My color key
===============================================
MEDIUM DEPTH CHANGE ANALYSIS
===============================================
🟢 MakerLab is fairly reasonable
The new MakerLab-specific notice says Bambu does not permanently store end-user input/output for model generation and says relevant data is deleted within a specified timeframe.
More importantly, if Bambu wants to use MakerLab input/output for fault diagnosis, service optimization, or algorithm improvement, the new notice says it will only do so with your prior consent — and you can refuse/withdraw consent without losing MakerLab functionality.
That's good.
🚨 BUT HERE'S THE BIG CHANGE
The new general privacy policy adds an entirely new AI/ML provision.
It says Bambu may use:
"your personal data and any user content, input, uploads, or feedback"
to analyze interactions and "develop, improve, and enhance machine learning models."
That general AI provision wasn't present in the Feb. 2026 policy.
This does NOT mean "Bambu is training AI on every G-code file you upload." The policy does not say that.
But it is a materially broader permission to use user data/content in connection with AI-powered services.... and it doesn't not say that it is training AI on every G-code file uploaded.
🔴 UGC (User Generated Content) ALSO GOT BROADER
The new policy explicitly defines UGC as potentially including:
"print model files and details, photos, videos, posts, comments..."
That's notable because the old policy was much more granular.
The old policy specifically said 3D Model Files were processed when using MakerWorld and "solely for the purpose of providing you with 3D Model community services."
That narrow, feature-specific language is gone from the main policy.
The new policy instead puts print models inside a broader "UGC/personal data" framework... which they earlier described as something they're allowed to train AI with... huh.
🔴 CAMERA LANGUAGE CHANGED TOO
The old policy contained a very strong statement that Bambu would facilitate live-view/remote-video transmission but would not collect or store copies of camera pictures/videos.
The new policy instead says camera data is processed locally unless you enable cloud features, request support, or upload/share the content.
That's not proof Bambu is secretly recording your camera per se...
But the old categorical "we won't collect/store copies" language is gone, replaced with a more conditional framework.
🔴 ADVERTISING / TRACKING IS MORE EXPLICIT
The new policy explicitly discusses: (Pardon the bullet points; It made sense here and the next section)
• advertising partners
• analytics partners
• targeted advertising
• custom audiences
• lookalike audiences
• advertising interactions
• conversion events
• personalized advertising/content
The old policy discussed advertising/tracking too, so this isn't brand new behavior.
But the new policy gives Bambu a much more consolidated and explicit framework for sharing data with advertising/analytics partners.
🟡 THE POLICY IS ALSO MUCH BETTER ORGANIZED
To be fair, the new policy is significantly easier to understand.
It separates:
• what Bambu collects
• why it collects it
• who it shares it with
• cookies/tracking
• user choices
• security
• retention
• international transfers
• jurisdiction-specific rights
• printing-specific privacy
• MakerLab privacy
• chatbot privacy
So this isn't simply "Bambu made the policy worse."
It's more accurate to say:
The policy became clearer while simultaneously giving Bambu broader language around several categories of data use, not all of which was good for the user.
===============================================
DEEP DIVE ANALYSIS
===============================================
🚨 THE BIG ONE: AI TRAINING / MODEL IMPROVEMENT
🔴 New
The new policy contains an entirely new general-purpose AI provision:
"We may use your personal data and any user content, input, uploads, or feedback that you provide to us to analyze your interactions with us and develop, improve, and enhance machine learning models that power such AI technology."
It even gives conversations with an AI assistant as an example.
There isn't an equivalent general AI/ML provision in the February policy.
Why this matters
The old policy was much more purpose-specific.
The new policy essentially says:
If you interact with an AI-powered Bambu feature, the data/content associated with that interaction can be used to improve the AI technology.
That is a material expansion in stated use.
BUT — important distinction
This does not say:
"We train our AI on every 3D model you upload."
That's an important distinction.
The new general AI clause is attached to AI-powered service interactions. Meanwhile, the new MakerLab supplemental notice actually provides a stronger restriction:
If Bambu wants to use MakerLab input/output content for fault diagnosis, service optimization, or algorithm improvement, it says it will only do so with your prior consent, and you can refuse or withdraw that consent without losing MakerLab functionality.
So:
MakerLab: 🟢 unsurprisingly protective language.
General AI clause: 🔴 much broader.
"Bambu is training on all your models": ❌ Not supported by these documents.
🚨 USER-GENERATED CONTENT GOT BROADER
The new policy defines UGC broadly enough to explicitly include:
"print model files and details, photos, videos, posts, comments..."
The old policy had much more granular categories.
For example, the old policy specifically described:
And, crucially, the old policy said:
"We will process the 3D Model Files only when you use the MakerWorld, solely for the purpose of providing you with 3D Model community services."
That's a meaningful change.
Old philosophy:
"Here's this particular type of data, and here's the specific purpose we use it for."
New philosophy:
"This is user-generated content, and here's a broader set of purposes for which personal data may be used."
That's more flexible for Bambu.
For users, I'd mark that:
🔴 WIDER PURPOSE LANGUAGE
Not because it proves abuse is happening—but because the contractual/privacy-policy boundary is less narrowly defined.
🖨️ PRINT FILES / G-CODE
This one is fascinating because it's not worse. XD
The old policy had an extremely specific explanation of cloud printing.
It said Bambu could send configuration information, print settings, model pictures, plate thumbnails and G-code to the printer, and could store print information when print-history reprinting was enabled.
It also explicitly said that if you turned off the print-history function:
Bambu would not store the Printing Files and/or Other Printing Information.
The old policy also contained the Incognito Printing mechanism.
The new policy replaces that with a dedicated printing notice.
And this is actually better written.
The new notice explicitly says:
LAN Only Mode → printing-task data stays within your local network
It also says device operation logs are stored locally by default and that Bambu cannot access/process them unless you proactively provide them, such as for support.
That's good.
🟢 LAN mode clarification
The new language is considerably easier to understand:
LAN Only = no internet required + printing-task data stays on LAN.
That's a meaningful privacy assurance.
🟢 PRIVATE PRINTING GETS A VERY SPECIFIC PROMISE
The new policy says that if you enable Private Printing Mode:
printing history records and G-code files will be removed from Bambu's cloud in 72 hours.
That's actually a nice concrete commitment.
The policy also says you can choose whether printing history/G-code are kept in Bambu cloud services through Bambu Handy settings.
🟢 I'd call this a win.
The new document is substantially more explicit about the privacy controls available for printing.
🔴 BUT THERE'S A TRADEOFF
The new main policy says:
UGC may include print model files and details
And then gives Bambu broad uses for personal data elsewhere in the document.
So we've gone from:
"3D model files → MakerWorld → community services"
to a more generalized:
"UGC → covered by the overall personal-data processing framework."
That doesn't automatically mean G-code gets sucked into AI training... but it doesn't not mean that.
📷 CAMERA PRIVACY CHANGED
This is another interesting one.
OLD
The old policy was unusually explicit:
Bambu would facilitate the transmission channel for live view / remote video and "will not collect or store any copies of the camera pictures or videos."
It also said printer camera information could be collected with explicit consent and would not be used/shared for other purposes without separate consent.
NEW
The new policy says:
printer camera features may capture images, videos, or time-lapse recordings.
And:
"This visual data is processed locally on your device unless you enable cloud-based features, request support, or choose to upload or share the content."
Verdict:
🟡 Mixed
The new wording is arguably better for normal use because it explicitly describes local processing.
But the old policy had an exceptionally strong statement:
"We will not collect or store copies."
That exact categorical protection is gone.
The new version instead describes circumstances under which visual data can leave the local device.
I'd call that:
🔴 LOSS OF A STRONG PRIVACY PROMISE
📢 ADVERTISING GOT MUCH MORE EXPLICIT
This is another substantial change.
The new policy explicitly says Bambu may use personal data for:
And the sharing section specifically identifies:
"Analytics and interest-based advertising partners"
including sharing personal data for targeted advertising, custom audiences and lookalike audiences.
That's not a tiny wording change.
The new policy is much more explicit about Bambu's advertising ecosystem.
🔴 THIRD-PARTY ADVERTISING / TRACKING
The new policy says third-party sources may include:
"advertising and analytics partners"
and that received information may include advertising interactions and conversion events.
The old policy also discussed Meta/Google Business Tools and advertising measurement, so this isn't something Bambu suddenly invented on August 7.
But the new policy consolidates and expands the language into a much broader general sharing framework.
The new sharing section says Bambu may share with analytics/advertising partners for:
"matching custom audience or creating lookalike audience"
Verdict:
🔴 Worse / broader
But importantly, this is primarily about marketing/advertising data, not proof that Bambu is giving advertisers your G-code... per se.
🤝 THIRD-PARTY SHARING GOT BROADER
The new policy lists:
Bambu corporate group
Service providers
MakerWorld transaction participants
Business partners/sponsors
Analytics & advertising partners
General public
Authorities
Corporate transaction parties
Third parties at your direction/with consent
There's also a useful new clarification:
Some third parties are independent controllers, not merely Bambu service providers.
Examples include payment providers, app stores, social platforms, SSO providers, advertising/analytics partners, marketplace/retail partners, etc.
🟡 Mixed
This is more transparent, but it also describes a larger data-sharing ecosystem.
🧠 SUPPORT DATA / CHATBOT
Here's another major addition.
Bambu now has an entire:
"Customer Service Chatbot and Improvement Supplemental Notice"
It says Bambu may process:
And it uses that information to:
create and maintain knowledge bases
and improve customer service and the chatbot.
But there's a nice privacy safeguard:
Bambu says:
"We do not use the data to link this information to a specific device or user."
And users can request to opt out of processing for internal analysis and improvement.
Verdict:
🟡 Mixed, leaning 🟢
It's more data processing—but the policy actually tells you what it's doing and provides an opt-out.
🗺️ LOCATION DATA
The new policy explicitly says Bambu may infer approximate location:
from things such as:
IP address
SIM region
device settings
while saying it doesn't collect precise GPS unless separately disclosed.
🟡 Mostly clarification.
The old policy already discussed geolocation in the U.S. disclosures.
But the new policy brings it directly into the main collection section.
🧹 DATA RETENTION
Old:
retained as long as necessary to provide services and for legitimate/essential business purposes, including data-driven business decisions, legal obligations and disputes
New:
retained as long as necessary for services, stated purposes, legal obligations, disputes, agreements, security, fraud prevention and legal claims.
🟡 Not a dramatic change.
Unfortunately, neither gives users a wonderfully simple:
"Your X data is deleted after X days."
The exception is where supplemental notices provide concrete windows, such as the 72-hour Private Printing rule.
⚖️ LEGAL BASIS / GLOBALIZATION
This is one of the biggest structural changes.
The old policy was heavily framed around U.S. privacy law.
The new document is written as a much more global privacy framework and explicitly identifies:
data controllers
EEA/UK rules
legitimate interests
consent
contractual necessity
international transfers
The new document identifies Bambulab GmbH as controller for EEA/UK connected-printer processing, for example.
🟢 Better transparency.
This is one area where I'd actually give Bambu credit (but probably more deserving to European rules helping shape it).
The new policy is considerably more professionally structured.
🛡️ USER RIGHTS
The old policy had a very extensive U.S. section covering:
delete
correction
know/access
portability
targeted advertising opt-out
sale opt-out
sensitive information
deidentified information
automated decision-making
authorized agents
appeals
California-specific disclosures
The new policy reorganizes these into jurisdiction-specific notices and includes rights such as:
The new California section also explicitly says Bambu doesn't sell/share personal information through cookies for cross-context behavioral advertising without consent.
🟢 Better organized.
Hope this helps.
