{"id":30736,"date":"2026-07-14T16:31:05","date_gmt":"2026-07-14T15:31:05","guid":{"rendered":"https:\/\/www.kaspersky.co.uk\/blog\/?p=30736"},"modified":"2026-07-14T16:31:05","modified_gmt":"2026-07-14T15:31:05","slug":"meta-muse-image-instagram","status":"publish","type":"post","link":"https:\/\/www.kaspersky.co.uk\/blog\/meta-muse-image-instagram\/30736\/","title":{"rendered":"Meta briefly let its AI train on Instagram posts\u2026 before backpedaling"},"content":{"rendered":"<p>On July 7, 2026, Meta <a href=\"https:\/\/about.fb.com\/news\/2026\/07\/introducing-muse-image-meta-ai\/\" target=\"_blank\" rel=\"noopener nofollow\">rolled out<\/a> Muse Image, its first-ever AI image generator. The tool cranks out creative visuals based on photos and text prompts. Its main selling point is its ability to act as an AI agent\u00a0\u2014 meaning the model actually reasons through a prompt, scrapes the web for context, and then builds the AI image.<\/p>\n<p>But <a href=\"https:\/\/www.wired.com\/story\/meta-now-lets-anyone-use-your-instagram-photos-in-ai-images-unless-you-opt-out\/\" target=\"_blank\" rel=\"noopener nofollow\">journalists noticed<\/a> something else entirely: Meta quietly allowed the AI to use content from every Instagram user to generate content without their permission. Just days later, on July 10, they pulled the plug on the feature.<\/p>\n<p>Here is what went wrong for Meta\u00a0\u2014 and why this U-turn is no reason to let your guard down.<\/p>\n<h2>What happened<\/h2>\n<p>Muse Image churns out fun, vibrant images\u00a0\u2014 nothing groundbreaking, on the surface. But here\u2019s the catch: it could use absolutely any public Instagram account as a reference. An AI hobbyist didn\u2019t even need to follow any of the Instagram accounts they used in their prompts. They just had to mention one in their prompt, and they could do whatever Muse Image would let them.<\/p>\n<p>Surprisingly, Meta never gave creators any heads-up that their content was being used. The system didn\u2019t send a single notification \u2014 even if random strangers were making money off the generated images.<\/p>\n<p>Just a few days after the launch, Meta <a href=\"https:\/\/about.fb.com\/news\/2026\/07\/introducing-muse-image-meta-ai\/\" target=\"_blank\" rel=\"noopener nofollow\">announced<\/a> they were pulling the plug. The official line: <a href=\"https:\/\/about.fb.com\/news\/2026\/07\/introducing-muse-image-meta-ai\/#:~:text=We%E2%80%99ve%20heard%20the%20feedback%20that%20this%20feature%20missed%20the%20mark%2C%20so%20it%E2%80%99s%20no%20longer%20available.\" target=\"_blank\" rel=\"noopener nofollow\">\u201cWe\u2019ve heard the feedback that this feature missed the mark, so \u2060it\u2019s no longer available.\u201d<\/a> The company offered zero follow-up on how user content would be protected going forward, or whether something like this could happen again. There weren\u2019t even the usual corporate platitudes about user privacy being their \u201ctop priority\u201d \u2014 let alone promises to scrap the tech for good.<\/p>\n<h2>\u201cI Told You So!\u201d<\/h2>\n<p>Two years ago, we published a post titled, <a href=\"https:\/\/www.kaspersky.com\/blog\/meta-uses-personal-data\/51548\/\" target=\"_blank\" rel=\"noopener nofollow\"><strong>Meta wants to use your posts and photos to train AI\u2026 Or does it?<\/strong><\/a> In it, we did a deep dive into the rumors swirling at the time about Meta potentially tapping user data across all its platforms without permission.<\/p>\n<blockquote><p>It all started back in May 2024, when the internet blew up with <a href=\"https:\/\/twitter.com\/Tantacrul\/status\/1794863603964891567?ref_src=twsrc%5Etfw\" target=\"_blank\" rel=\"noopener nofollow\">reports<\/a> about yet another update to Meta\u2019s privacy policy. Supposedly, starting that June, the company planned to use Facebook and Instagram content to train its generative AI. However, those notifications didn\u2019t go out to everyone \u2014 only a select group of users in the EU and US received them.<\/p><\/blockquote>\n<p>Back in 2024, stories like this just felt like the endless tug-of-war between the media and big tech: the press accuses tech giants of every sin under the sun, and the giants make excuses. Sometimes they swap roles\u00a0\u2014 it\u2019s a classic routine. And sure, according to official data today, Meta AI isn\u2019t training on your private DMs, but anything you actually send directly to the chatbot absolutely becomes brain food for the AI model.<\/p>\n<p>Adding fuel to the fire is a recent story about NameTag, a feature designed to use Meta\u2019s built-in AI assistant to identify people caught in the camera frame of Meta\u2019s smart glasses and feed information about them to the wearer. The code needed to run NameTag was quietly slipped into the Meta AI app, but as soon as journalists caught wind of it, Meta immediately scrubbed the code from the next app update, which dropped just a day after the investigative report. We broke this down in more detail in our post, <a href=\"https:\/\/www.kaspersky.com\/blog\/meta-smart-glasses-nametag-privacy-concerns\/56104\/\" target=\"_blank\" rel=\"noopener nofollow\"><strong>Meta vs. privacy: smart glasses take it a step too far<\/strong><\/a><strong>.<\/strong><\/p>\n<h2>So, what can you do about it?<\/h2>\n<p>During those few days when the public Instagram scraping feature was live, users had to manually tweak their security settings or lock down their profiles to protect their posts. While it\u2019s definitely good news that Meta killed this \u201chelpful new feature\u201d, the relief might be temporary.<\/p>\n<p>Meta is clearly testing the waters with a non-stop stream of new AI capabilities. Sure, if the backlash is loud enough, the company might pivot or shelve a specific feature\u00a0\u2014 but that doesn\u2019t mean the idea itself is dead. Once the tech is built, it can easily make a comeback down the road under a different guise. How? That\u2019s just a marketing puzzle for them to solve.<\/p>\n<p>Both of these incidents are a blunt reminder that big tech can move the goalposts whenever it wants. It can update privacy policies, expand how it uses your data, or train its AI models on your personal information. You can\u2019t completely insure yourself against these shifts, and keeping track of them is a massive headache.<\/p>\n<p>It\u2019s becoming crystal clear that locking down your accounts is more critical than ever, and checking your privacy settings needs to be a regular habit. The less personal data and content you leave out in the open by default, the less material there is to feed these new AI features.<\/p>\n<p>To help you secure your accounts across various services and social media sites, check out our free online tool, <a href=\"https:\/\/privacy.kaspersky.com\/?utm_source=kdaily&amp;utm_medium=blog&amp;utm_campaign=gl_kd-banner_ap0072&amp;utm_content=banner&amp;utm_term=gl_kdaily_organic_hwzuab72aq5ynvk\" target=\"_blank\" rel=\"noopener\">Privacy Checker<\/a>. It\u2019s a vast library of step-by-step privacy guides tailored to your specific OS, platform, and even your browser.<\/p>\n<blockquote><p>Want to know what other risks come with uninvited AI, and how to minimize them? Check out our deep dives here:<\/p>\n<ul>\n<li><a href=\"https:\/\/www.kaspersky.com\/blog\/how-to-switch-off-ai\/55383\/\" target=\"_blank\" rel=\"noopener nofollow\"><strong>Unplugged: how to disable AI on your computer and smartphone<\/strong><\/a><\/li>\n<li><a href=\"https:\/\/www.kaspersky.com\/blog\/how-technology-changes-love\/55283\/\" target=\"_blank\" rel=\"noopener nofollow\"><strong>Love, AI &amp; robots<\/strong><\/a><\/li>\n<li><a href=\"https:\/\/www.kaspersky.com\/blog\/openclaw-vulnerabilities-exposed\/55263\/\" target=\"_blank\" rel=\"noopener nofollow\"><strong>Don\u2019t get pinched: the OpenClaw vulnerabilities<\/strong><\/a><\/li>\n<li><a href=\"https:\/\/www.kaspersky.com\/blog\/ai-generated-sextortion-social-media\/55137\/\" target=\"_blank\" rel=\"noopener nofollow\"><strong>AI and the new reality of sextortion<\/strong><\/a><\/li>\n<li><a href=\"https:\/\/www.kaspersky.com\/blog\/how-to-disable-gemini-on-android\/53771\/\" target=\"_blank\" rel=\"noopener nofollow\"><strong>Is a Gemini AI update about to kill privacy on your Android device?<\/strong><\/a><\/li>\n<\/ul>\n<\/blockquote>\n<input type=\"hidden\" class=\"category_for_banner\" value=\"premium-generic\">\n","protected":false},"excerpt":{"rendered":"<p>Meta&#8217;s new Muse Image AI, launched in early July, was briefly training its image generator on user-published Instagram posts. However, following user uproar, Meta killed the feature less than a week later. Here&#8217;s the breakdown on Meta&#8217;s latest generative AI push \u2014 and why you shouldn&#8217;t let your guard down just yet.<\/p>\n","protected":false},"author":2754,"featured_media":30737,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1622],"tags":[1043,1041,742,3803,363,43,211,788],"class_list":{"0":"post-30736","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-privacy","8":"tag-ai","9":"tag-artificial-intelligence","10":"tag-instagram","11":"tag-meta","12":"tag-personal-data","13":"tag-privacy","14":"tag-social-media","15":"tag-tracking"},"hreflang":[{"hreflang":"en-gb","url":"https:\/\/www.kaspersky.co.uk\/blog\/meta-muse-image-instagram\/30736\/"},{"hreflang":"en-in","url":"https:\/\/www.kaspersky.co.in\/blog\/meta-muse-image-instagram\/30899\/"},{"hreflang":"en-ae","url":"https:\/\/me-en.kaspersky.com\/blog\/meta-muse-image-instagram\/25934\/"},{"hreflang":"ru","url":"https:\/\/www.kaspersky.ru\/blog\/meta-muse-image-instagram\/42272\/"},{"hreflang":"x-default","url":"https:\/\/www.kaspersky.com\/blog\/meta-muse-image-instagram\/56121\/"},{"hreflang":"ru-kz","url":"https:\/\/blog.kaspersky.kz\/meta-muse-image-instagram\/30849\/"},{"hreflang":"en-au","url":"https:\/\/www.kaspersky.com.au\/blog\/meta-muse-image-instagram\/36402\/"}],"acf":[],"banners":"","maintag":{"url":"https:\/\/www.kaspersky.co.uk\/blog\/tag\/privacy\/","name":"privacy"},"_links":{"self":[{"href":"https:\/\/www.kaspersky.co.uk\/blog\/wp-json\/wp\/v2\/posts\/30736","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.kaspersky.co.uk\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.kaspersky.co.uk\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.kaspersky.co.uk\/blog\/wp-json\/wp\/v2\/users\/2754"}],"replies":[{"embeddable":true,"href":"https:\/\/www.kaspersky.co.uk\/blog\/wp-json\/wp\/v2\/comments?post=30736"}],"version-history":[{"count":1,"href":"https:\/\/www.kaspersky.co.uk\/blog\/wp-json\/wp\/v2\/posts\/30736\/revisions"}],"predecessor-version":[{"id":30738,"href":"https:\/\/www.kaspersky.co.uk\/blog\/wp-json\/wp\/v2\/posts\/30736\/revisions\/30738"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.kaspersky.co.uk\/blog\/wp-json\/wp\/v2\/media\/30737"}],"wp:attachment":[{"href":"https:\/\/www.kaspersky.co.uk\/blog\/wp-json\/wp\/v2\/media?parent=30736"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.kaspersky.co.uk\/blog\/wp-json\/wp\/v2\/categories?post=30736"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.kaspersky.co.uk\/blog\/wp-json\/wp\/v2\/tags?post=30736"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}