<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://consumerrights.wiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Jake01756</id>
	<title>Consumer Rights Wiki - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://consumerrights.wiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Jake01756"/>
	<link rel="alternate" type="text/html" href="https://consumerrights.wiki/w/Special:Contributions/Jake01756"/>
	<updated>2026-04-29T07:09:34Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.44.0</generator>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=Bootloader_unlocking&amp;diff=24422</id>
		<title>Bootloader unlocking</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=Bootloader_unlocking&amp;diff=24422"/>
		<updated>2025-09-12T04:21:14Z</updated>

		<summary type="html">&lt;p&gt;Jake01756: /* References */ fix the cite&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Incomplete}}{{ToneWarning}}&lt;br /&gt;
&lt;br /&gt;
The bootloader is the core layer of a computerized device that connects the software to the physical hardware. In smartphones, the bootloader allows the mobile device to start up with an operating system such as iOS for iPhones and Android for most other smartphones. Bootloaders are generally established by the manufacturer and are shipped to retailers and consumers in a &amp;quot;locked&amp;quot; state, tying the hardware to a specific operating system chosen by the manufacturer. To unlock a bootloader is to disconnect the physical device from a particular operating system, allowing users more control over their purchased smartphones. This is especially relevant for users who wish to [[de-Google]] their android devices, the act of removing Google products and services for privacy, flexibility, and other concerns.&lt;br /&gt;
&lt;br /&gt;
==Background==&lt;br /&gt;
History and technical details here... &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Unlocking the bootloader of a smartphone allows the user to install an alternative system on the device, also more popularly known as a custom ROM.&amp;lt;ref&amp;gt;{{Cite web |date=19 Aug 2025 |title=Android ROM |url=https://www.pcmag.com/encyclopedia/term/android-rom |url-status=live |archive-url=https://web.archive.org/web/20241223222958/https://www.pcmag.com/encyclopedia/term/android-rom |archive-date=23 Dec 2024 |website=PCMag}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Difference from Rooting&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Need to expand on this&lt;br /&gt;
==Benefits of unlocked bootloaders==&lt;br /&gt;
&lt;br /&gt;
===&#039;&#039;&#039;1. Better Privacy&#039;&#039;&#039;===&lt;br /&gt;
Most custom ROMs do not contain any of the components that send data to the manufacturer, Google, and their partner companies.&amp;lt;ref name=&amp;quot;:0&amp;quot; /&amp;gt; In some cases, they even contain components that prevent individual apps from doing so, such as:&lt;br /&gt;
&lt;br /&gt;
*[https://doc.e.foundation/support-topics/advanced_privacy_main.html /e/&#039;s Advanced Privacy]&lt;br /&gt;
*[https://calyxos.org/docs/tech/datura-details/ CalyxOS&#039;s Datura Firewall]&lt;br /&gt;
*[https://github.com/iodeOS/ota iodéOS&#039;s blocker]&lt;br /&gt;
&lt;br /&gt;
====Workaround Google Play Services====&lt;br /&gt;
On a default Android system there is a deep integration with Google Play Services. This is a system process that requires access to files, contacts, storage, call logs, SMS messages, location, camera and microphone. And without this process running, basic system apps will not function.&amp;lt;ref&amp;gt;{{Cite web |last=Aragon |first=Jonah |date=21 Jul 2024 |title=Android |url=https://www.privacyguides.org/en/android/#install-a-custom-distribution |url-status=live |access-date=17 Aug 2025 |website=Privacy Guides}}&amp;lt;/ref&amp;gt; Alternative systems avoid this process entirely, or use a privacy preserving workaround such as:&lt;br /&gt;
&lt;br /&gt;
*[https://grapheneos.org/features#sandboxed-google-play GrapheneOS&#039;s Sandboxed Google Play]&lt;br /&gt;
*[https://github.com/microg/GmsCore/wiki MicroG]&amp;lt;ref&amp;gt;{{Cite web |last=Gordon |first=Arielle |date=7 Jun 2019 |title=The Open Source Project That Keeps Google&#039;s Hands Off Your Android Data |url=https://www.vice.com/en/article/the-open-source-project-that-keeps-googles-hands-off-your-android-data/ |url-status=live |archive-url=https://web.archive.org/web/20250630130025/https://www.vice.com/en/article/the-open-source-project-that-keeps-googles-hands-off-your-android-data/ |archive-date=30 Jun 2025 |access-date=19 Aug 2025 |website=Vice}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
*[https://unifiedpush.org/ Unified Push]&lt;br /&gt;
&lt;br /&gt;
===&#039;&#039;&#039;2. Expanding Device Lifespan&#039;&#039;&#039;===&lt;br /&gt;
Most custom ROMs are free of bloatware and can thus be used extend the longevity of phones that have become unusable due to the default system growing larger with each manufacturer update. Especially on low-end phones, these updates usually end up exhausting the built-in storage after sometimes as little as two years. This renders the devices slow and unstable and leaves no room for user data. Custom ROMs are typically much smaller than the manufacturer software. Consequently, many old phones can run even faster with a custom ROM than they were when new, thus often more than doubling their useful lifespan.&amp;lt;ref&amp;gt;{{Cite web |title=By how much do custom roms really extend Phone lifespans? |url=https://www.reddit.com/r/AndroidQuestions/comments/gdq2rc/comment/fpj11ay/ |access-date=2025-08-23 |website=Reddit}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |date=2023-03-10 |title=Xiaomi Redmi 8a - olivelite with Dual Sim |url=https://community.e.foundation/t/xiaomi-redmi-8a-olivelite-with-dual-sim/29192/12 |url-status=live |access-date=2025-08-23 |website=/e/OS Community}}&amp;lt;/ref&amp;gt;&amp;lt;!-- Please provide better sources than forums and reddits. You can read the citation guide on this wiki for more tips --&amp;gt;&lt;br /&gt;
===&#039;&#039;&#039;3. Updates after device is abandoned by manufacturer&#039;&#039;&#039;===&lt;br /&gt;
Low-end devices usually receive only a few years or even months of security updates.&amp;lt;ref&amp;gt;{{Cite web |title=Android Update Matrix |url=https://www.androidupdatetracker.com/update-matrix |access-date=2025-08-23 |website=Android Update Tracker}}&amp;lt;/ref&amp;gt; Since most custom ROMs are built by the open source community, installing one of these custom ROMs allows users to receive security updates for the Android system and default components like web browser engines and PDF readers much longer than with the manufacturer&#039;s OS.&amp;lt;!-- Source? --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===&#039;&#039;&#039;4. Customization&#039;&#039;&#039;===&lt;br /&gt;
Some applications cannot be removed easily with the default OS. A custom ROM can be used to only include the applications the user wants, potentially with customization options that aren&#039;t originally available by default.&amp;lt;!-- Source? --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Why most devices are locked==&lt;br /&gt;
&lt;br /&gt;
===Security===&lt;br /&gt;
A locked bootloader protects the device from what is often called an [[wikipedia:Evil_maid_attack|Evil Maid Attack]]. This is when a person with physical access to a device can manipulate the operating system, often when the device is left unattended or when handed over for inspection by authorities such as customs upon entering a country. &lt;br /&gt;
&lt;br /&gt;
A locked bootloader ensures that the operating system is intact and cannot be changed to differ from the state in which the manufacturer has released it.&lt;br /&gt;
&lt;br /&gt;
===DRM and ecosystem control===&lt;br /&gt;
Example Text&lt;br /&gt;
&lt;br /&gt;
===Locks from mobile carriers===&lt;br /&gt;
Example Text&lt;br /&gt;
&lt;br /&gt;
==Availability==&lt;br /&gt;
Unlocking the bootloader is only [[Phones that do not allow bootloader unlock|possible on some, but not all Android devices]]. Apple has measures in place to prevent users from installing third party operating systems on iPhones and iPads.&amp;lt;!-- Source? --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Alternative Android-based Operating Systems==&lt;br /&gt;
These include, but are not limited to:&lt;br /&gt;
&lt;br /&gt;
*[https://grapheneos.org/ GrapheneOS]&lt;br /&gt;
*[https://iode.tech/iodeos/ IodéOS]&lt;br /&gt;
*[https://e.foundation/e-os/ /e/OS]&lt;br /&gt;
*[https://lineageos.org/ LineageOS]&lt;br /&gt;
*[https://calyxos.org/ CalyxOS]&lt;br /&gt;
&lt;br /&gt;
*[https://source.android.com/ AOSP (Android Open Source Project)] , also known as &amp;quot;stock&amp;quot; Android.&amp;lt;ref&amp;gt;https://eylenburg.github.io/android_comparison.htm&amp;lt;/ref&amp;gt;&amp;lt;ref name=&amp;quot;:0&amp;quot;&amp;gt;{{Cite web |last=Patel |first=Pratham |date=20 Feb 2024 |title=5 De-Googled Android-based Operating Systems to Free Your Smartphone from Google and other Big Tech |url=https://itsfoss.com/android-distributions-roms/ |url-status=live |archive-url=https://web.archive.org/web/20250707220149/https://itsfoss.com/android-distributions-roms/ |archive-date=7 Jul 2025 |access-date=19 Aug 2025 |website=It&#039;s FOSS}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
&amp;lt;references /&amp;gt;&lt;/div&gt;</summary>
		<author><name>Jake01756</name></author>
	</entry>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=Google&amp;diff=24421</id>
		<title>Google</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=Google&amp;diff=24421"/>
		<updated>2025-09-12T04:17:27Z</updated>

		<summary type="html">&lt;p&gt;Jake01756: /* Ban on third-party tech support ads */ remove spacing&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{CompanyCargo&lt;br /&gt;
|Founded=1998&lt;br /&gt;
|Industry=Technology&lt;br /&gt;
|Logo=Google.webp&lt;br /&gt;
|ParentCompany=Alphabet Inc.&lt;br /&gt;
|Type=Subsidiary&lt;br /&gt;
|Website=https://www.google.com/&lt;br /&gt;
}}&lt;br /&gt;
&#039;&#039;&#039;[[wikipedia:Google|Google LLC]]&#039;&#039;&#039;, founded in 1998 by Larry Page and Sergey Brin, is one of the most influential technology companies in the world.&amp;lt;ref&amp;gt;{{Cite web |title=Largest tech companies by market cap |url=https://companiesmarketcap.com/tech/largest-tech-companies-by-market-cap/ |url-status=live |website=companiesmarketcap.com}}&amp;lt;/ref&amp;gt; Originally developed as a search engine to organize and index the growing amount of information on the internet, Google has since expanded into a wide range of services and products, becoming a central player in digital advertising, software, hardware, and cloud computing.&amp;lt;ref&amp;gt;{{Cite web |date= |title=Google Products |url=https://about.google/products/ |access-date=10 Mar 2025}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Google&#039;s search engine remains its most well-known service, but the company has significantly diversified its offerings. Key products include the [[Android]] operating system, the [[Google Chrome]] web browser, [https://wikipedia.org/wiki/Google_Drive Google Drive] for cloud storage, [https://wikipedia.org/wiki/Google_Maps Google Maps], [[YouTube]], and [[wikipedia:Google_Play|Google Play]].&amp;lt;ref&amp;gt;{{Cite web |title=Helpful products, built with you in mind |url=https://about.google/intl/ALL_us/products/ |url-status=live |access-date=5 Apr 2025 |website=[[Google]]}}&amp;lt;/ref&amp;gt;{{Citation needed}} Additionally, the company provides digital advertising services through Google Ads, generating the majority of its revenue.&amp;lt;ref&amp;gt;{{Cite web |date=4 Feb 2025 |title=Alphabet Announces Fourth Quarter and Fiscal Year 2024 Results |url=https://abc.xyz/assets/a3/91/6d1950c148fa84c7d699abe05284/2024q4-alphabet-earnings-release.pdf |url-status=live |access-date=5 Apr 2025}}&amp;lt;/ref&amp;gt; In recent years, Google has also developed hardware products such as the Pixel smartphone and Nest smart home devices.&lt;br /&gt;
&lt;br /&gt;
Google has faced ongoing scrutiny related to data privacy, competition, and its dominant position in the market, such concerns have stretched as far back as 2012.&amp;lt;ref&amp;gt;{{Cite web |last=Cohen |first=Adam |date=5 Mar 2012 |title=Will We Ever Get Strong Internet Privacy Rules? |url=https://ideas.time.com/2012/03/05/will-we-ever-get-strong-internet-privacy-rules/ |url-status=live |access-date=5 Apr 2025 |website=Time}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |date=6 Sep 2023 |title=REPORT: Google at 25: From “Don’t Be Evil” To ¯\_(ツ)_/¯ |url=https://techoversight.org/2023/09/06/google-at-25/ |url-status=live |access-date=5 Apr 2025 |website=The Tech Oversight Project}}&amp;lt;/ref&amp;gt; The company has been the subject of various legal and regulatory challenges, particularly concerning antitrust issues, the use of personal data, and its impact on consumer choice.{{Citation needed}} The US government is currently engaged in an antitrust lawsuit against Google, with a decision expected early 2025.&amp;lt;ref&amp;gt;{{Cite web |date=25 Nov 2024 |title=Closing Arguments, November 25: Once, Twice, Three Times a Monopolist |url=https://www.usvgoogleads.com/trial-updates/closing-arguments-november-25-once-twice-three-times-a-monopolist |url-status=live |access-date=5 Apr 2025 |website=US v Google}}&amp;lt;/ref&amp;gt; {{UpdateNeeded|date={{subst:August}} {{subst:2025}}|reason=We need updates on this situation.}}&lt;br /&gt;
&lt;br /&gt;
In December 2024, Google announced to organisations that use its advertising products, that from 16 February 2025, it will no longer prohibit them from employing [[wikipedia:Fingerprint_(computing)|fingerprinting]] techniques.&amp;lt;ref&amp;gt;{{Cite web |last=Almond |first=Stephen |date=19 Dec 2024 |title=Our response to Google’s policy change on fingerprinting |url=https://ico.org.uk/about-the-ico/media-centre/news-and-blogs/2024/12/our-response-to-google-s-policy-change-on-fingerprinting/ |url-status=live |access-date=5 Apr 2025 |website=ico.}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Anti-consumer incidents==&lt;br /&gt;
&lt;br /&gt;
===Service shutdowns===&lt;br /&gt;
&lt;br /&gt;
====Google Play Music shutdown====&lt;br /&gt;
[[wikipedia:Google_Play_Music|Google Play Music]] was a service that allowed users to purchase music, listen via streaming, and download to the local device; alternatively users could pay for a subscription to listen to all music available through streaming. It was publicly launched on the 16th November 2011 and later shutdown in December 2020.&amp;lt;ref&amp;gt;{{Cite web |date=4 Aug 2020 |title=Google Play Music, Music Play Store &amp;amp; Music Manager are going away – everything you need to know |url=https://support.google.com/youtubemusic/thread/62843644/google-play-music-music-play-store-music-manager-are-going-away-%E2%80%93-everything-you-need-to-know?hl=en |url-status=live |access-date=5 Apr 2025 |website=[[Google]]}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |last=Amadeo |first=Ron |date=28 Oct 2020 |title=RIP Google Play Music, 2011 – 2020 |url=https://arstechnica.com/gadgets/2020/10/rip-google-play-music-2011-2020/ |url-status=live |access-date=5 Apr 2025 |website=ArsTechnica}}&amp;lt;/ref&amp;gt; Google Play Music further allowed users to upload their own songs to listen on all their devices, with a limit of up to 50,000 files.&amp;lt;ref&amp;gt;{{Cite web |last=Hoffman |first=Chris |date=11 Jan 2017 |title=How to Upload Your Music Library to Google Play Music |url=https://www.howtogeek.com/288231/how-to-upload-your-music-library-to-google-play-music/ |url-status=live |access-date=5 Apr 2025 |website=How-To-Geek}}&amp;lt;/ref&amp;gt; Users were able to purchase songs individually or buy whole albums that they could then download and listen to, or stream through the internet.&amp;lt;ref&amp;gt;{{Cite web |date=15 Jan 2020 |title=How To Buy Music From Google Play (Now YouTube Music) |url=https://www.technobezz.com/buy-music-google-play |url-status=live |access-date=5 Apr 2025 |website=Technobezz}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In October 2020, Google announced that they would be shutting down Google Play Music, with it being fully shut down by December.&amp;lt;ref&amp;gt;{{Cite web |last=Li |first=Abner |date=3 Dec 2020 |title=Google fully shuts down Play Music around the world |url=https://9to5google.com/2020/12/03/google-play-music-dead/ |url-status=live |access-date=5 Apr 2025 |website=9To5Google}}&amp;lt;/ref&amp;gt; This went ahead with a warning to their users to begin migrating to [[wikipedia:YouTube_Music|YouTube Music]], and that they would be losing access to their purchased songs. Google recommended users should download their purchased songs before the service would shut down.&amp;lt;ref&amp;gt;{{Cite web |date=4 Aug 2020 |title=YouTube Music will replace Google Play Music by end of 2020 |url=https://blog.youtube/news-and-events/youtube-music-will-replace-google-play-music-end-2020/ |url-status=live |access-date=5 Apr 2025 |website=YouTube Official Blog}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
After the shut down, users lost access to the music they paid for, with no way to download them. Google justified this by transferring all playlists and purchase history to YouTube Music, and only refunding songs that were not directly available,&amp;lt;ref&amp;gt;{{Cite web |date=10 Oct 2023 |title=What happened to my songs on Google Music? |url=https://darwinsdata.com/what-happened-to-my-songs-on-google-music/ |url-status=live |access-date=5 Apr 2025 |website=Darwin&#039;s Data}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |last=Chaney |first=Sarah |date=5 Feb 2022 |title=What Happened to Google Play Music? |url=https://www.makeuseof.com/what-happened-to-google-play-music/ |url-status=live |access-date=5 Apr 2025 |website=MUO}}&amp;lt;/ref&amp;gt; with no guarantee that the songs will remain available through the new service. Users found that their purchased songs were no longer able to stream at 320kbps on YouTube Music compared to Google Play Music unless they paid for the monthly subscription.&amp;lt;ref&amp;gt;{{Cite web |last=Cutlack |first=Gary |date=23 Dec 2012 |title=Google Music UK: everything you need to know |url=https://www.techradar.com/news/software/google-music-uk-everything-you-need-to-know-1120176 |url-status=live |access-date=5 Apr 2025 |website=TechRadar}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |last=L. Hald |first=Nicole |date=24 Mar 2025 |title=How Is YouTube Music Sound Quality in 2025? Is It Any Good? |url=https://www.noteburner.com/youtube-music-tips/youtube-music-audio-quality.html |url-status=live |access-date=5 Apr 2025 |website=NoteBurner}}&amp;lt;/ref&amp;gt; If a user failed to initiate the transfer of their music library or locally download their songs by 24th February 2021, then they lost all access and all data associated with Google Play Music.&amp;lt;ref&amp;gt;{{Cite web |last=Sodhi |first=Tanishka |date=8 Feb 2021 |title=Google Play Music Data Will Be Deleted on February 24: Here’s How to Transfer to YouTube Music |url=https://www.gadgets360.com/how-to/news/google-play-music-data-deleted-february-24-youtube-how-to-transfer-files-playlists-billing-information-2365609 |url-status=live |access-date=5 Apr 2025 |website=Gadgets 360}}&amp;lt;/ref&amp;gt; YouTube Music does not provide the option to download songs as MP3s, with local downloads requiring an internet connection every 30 days to continue working offline.&amp;lt;ref&amp;gt;{{Cite web |title=Download music and podcasts to listen to offline |url=https://support.google.com/youtubemusic/answer/6313535?hl=en-GB&amp;amp;co=GENIE.Platform%3DAndroid |url-status=live |access-date=5 Apr 2025 |website=[[Google]]}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====Google Stadia shutdown====&lt;br /&gt;
In January 2023, Google announced the shutdown of its cloud gaming service, Stadia, which was launched in November 2019.&amp;lt;ref&amp;gt;{{Cite web |title=RIP Google Stadia: the latest news on the discontinued cloud gaming service |url=https://www.theverge.com/23380140/google-stadia-ending-shutdown-latest-news-gaming-tech |url-status=live |access-date=5 Apr 2025 |website=The Verge}}&amp;lt;/ref&amp;gt; Stadia required users to purchase games individually, unlike other gaming platforms that offer subscription-based access. Upon the service&#039;s closure, Google promised to refund consumers for their purchases, including both games and hardware. The refunds for games and software were issued automatically.&amp;lt;ref&amp;gt;{{Cite web |last=Ravenscraft |first=Erin |date=10 Nov 2022 |title=Stadia Is Dying. Here’s What’s in Your Refund and How to Get It |url=https://www.wired.com/story/how-to-get-your-google-stadia-refund/ |url-status=live |access-date=5 Apr 2025 |website=Wired}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Stadia users were effectively renting access to games, as the platform did not allow for traditional ownership or offline play. With the service discontinued, consumers were left without access to the content they had purchased. Stadia users who had bought controllers and other peripherals for the service were also impacted by the shutdown. While Google offered refunds to customers, many Stadia consumers were left with equipment that no longer performs the advertised functions and limited recourse for repurposing or reselling their devices.&amp;lt;ref&amp;gt;{{Cite web |last=Ashworth |first=Mack |date=5 Oct 2022 |title=Stadia Shut Down: How To Use Your Hardware Now Google’s Shutting It Down |url=https://www.gamerevolution.com/guides/852697-stadia-shut-down-how-to-use-controller-chromecast-without-app |url-status=live |access-date=5 Apr 2025 |website=Game Revolution}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Google Stadia controllers were limited to Wi-Fi connectivity, however upon shut down they started offering an update to allow them to connect through Bluetooth, the update service website was scheduled to shut down on the 31st December 2025.&amp;lt;ref&amp;gt;{{Cite web |last=Devine |first=Richard |date=17 Jan 2023 |title=Bluetooth support for Google Stadia Controller arrives — Here&#039;s how to enable it and play PC games |url=https://www.windowscentral.com/gaming/pc-gaming/bluetooth-support-for-google-stadia-controller-arrives-heres-how-to-enable-it-and-play-pc-games |url-status=live |access-date=5 Apr 2025 |website=Windows Central}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====&#039;&#039;&#039;Manifest V2 shutdown&#039;&#039;&#039;====&lt;br /&gt;
On July 24, 2025, Google permanently disabled all Manifest V2 extensions for Chrome 138 users, and disabled the ability to turn them back on.&amp;lt;ref&amp;gt;{{Cite web |date=2021-09-23 |title=Manifest V2 support timeline |url=https://developer.chrome.com/docs/extensions/develop/migrate/mv2-deprecation-timeline |archive-url=https://web.archive.org/web/20250808191702/https://developer.chrome.com/docs/extensions/develop/migrate/mv2-deprecation-timeline |archive-date=2025-08-08 |access-date=2025-08-12}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Manifest V3 disabled the &amp;lt;code&amp;gt;webRequestBlocking&amp;lt;/code&amp;gt; permission in the &amp;lt;code&amp;gt;webRequest&amp;lt;/code&amp;gt; API&amp;lt;ref&amp;gt;{{Cite web |date=2023-03-09 |title=Replace blocking web request listeners {{!}} Chrome Extensions {{!}} Chrome for Developers |url=https://developer.chrome.com/docs/extensions/develop/migrate/blocking-web-requests |url-status=live |archive-url=https://web.archive.org/web/20250614074559/https://developer.chrome.com/docs/extensions/develop/migrate/blocking-web-requests |archive-date=2025-06-14 |access-date=2025-08-12 |website=Chrome for Developers}}&amp;lt;/ref&amp;gt;, preventing many ad content blockers from working.&amp;lt;ref&amp;gt;{{Cite web |date=2024-09-26 |title=Understanding Manifest V3 and the Future of uBlock Origin |url=https://ublockorigin.com/ |url-status=live |archive-url=https://web.archive.org/web/20250812114916/https://ublockorigin.com/ |archive-date=2025-08-12 |access-date=2025-08-12 |website=uBlock Origin - Free, open-source ad content blocker}}&amp;lt;/ref&amp;gt; Google cites performance reasons &amp;lt;ref&amp;gt;{{Cite web |date=2023-03-09 |title=Replace blocking web request listeners {{!}} Chrome Extensions {{!}} Chrome for Developers |url=https://developer.chrome.com/docs/extensions/develop/migrate/blocking-web-requests |url-status=live |archive-url=https://web.archive.org/web/20250614074559/https://developer.chrome.com/docs/extensions/develop/migrate/blocking-web-requests |archive-date=2025-06-14 |access-date=2025-08-12 |website=Chrome for Developers |quote=&amp;quot;In Manifest V2, blocking web requests could significantly degrade both the performance of extensions and the performance of pages they work with.&amp;quot;}}&amp;lt;/ref&amp;gt;, but this is dubious; restricting content blockers prevents users from impeding their tracking and surveillance, meaning they can create a larger profit from the data gained. This is likely the ulterior motive, although unproven.&lt;br /&gt;
&lt;br /&gt;
===&#039;&#039;&#039;Pixel 4a battery reduction update&#039;&#039;&#039;===&lt;br /&gt;
{{Main|Pixel 4a Battery Performance Program}}&lt;br /&gt;
On January 6, 2025, Google issued a software update to the Pixel 4a that significantly decreased battery capacity on &amp;quot;Impacted Devices&amp;quot;. Not all units were affected. It&#039;s speculated that the affected units have defective batteries and may pose a safety risk if the update is not applied, but Google never disclosed the reason(s) that the update was deemed necessary. Google removed all factory images for previous versions of the system software from their website, making it difficult to revert the update.&lt;br /&gt;
&lt;br /&gt;
As compensation, Google offered a free battery replacement only in select countries. In other countries, you could choose between a $50 USD payment or $100 USD worth of Google Store credits. However, some users reported difficulty obtaining their compensation.&lt;br /&gt;
&lt;br /&gt;
===Blocking sideloading of unverified Android apps===&lt;br /&gt;
{{Main|Google blocking sideloading of unverified Android apps}}&lt;br /&gt;
On 25 August 2025, &#039;&#039;&#039;[[Google]]&#039;&#039;&#039; announced that starting in 2026 it will block the installation of Android apps from outside the Play Store unless the developer has verified their identity with Google. The policy will first roll out in Brazil, Indonesia, Singapore, and Thailand in September 2026, with global enforcement targeted for 2027.&amp;lt;ref name=&amp;quot;:0&amp;quot;&amp;gt;{{Cite web |last=Frey |first=Suzanne |date=25 Aug 2025 |title=A new layer of security for certified Android devices |url=https://android-developers.googleblog.com/2025/08/elevating-android-security.html |url-status=live |access-date=25 Aug 2025 |website=Android Developers Blog}}&amp;lt;/ref&amp;gt;&amp;lt;ref name=&amp;quot;:1&amp;quot;&amp;gt;{{Cite web |last=Perez |first=Sarah |date=25 Aug 2025 |title=Google will require developer verification for Android apps outside the Play Store |url=https://techcrunch.com/2025/08/25/google-will-require-developer-verification-for-android-apps-outside-the-play-store/ |url-status=live |access-date=25 Aug 2025 |website=TechCrunch}}&amp;lt;/ref&amp;gt; This marks a significant change to Android&#039;s long-standing support for sideloading apps.&lt;br /&gt;
&lt;br /&gt;
Devices without Google Mobile Services or running custom ROMs are exempt.&amp;lt;ref name=&amp;quot;:22&amp;quot;&amp;gt;{{Cite web |last=Anderson |first=Tim |date=2025-08-26 |title=Google kneecaps indie Android devs, forces them to register |url=https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |url-status=live |archive-url=https://web.archive.org/web/20250829170329/https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |archive-date=2025-08-29 |access-date=2025-08-26 |website=The Register}}&amp;lt;/ref&amp;gt; Critics argue this restricts user freedom, impacts independent developers, and may enable Google to block apps it disapproves of, such as ad-blockers, raising concerns about privacy and control over personal devices.&amp;lt;ref name=&amp;quot;:2&amp;quot;&amp;gt;{{Cite web |last=Anderson |first=Tim |date=26 Aug 2025 |title=Google kneecaps indie Android devs, forces them to register |url=https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |url-status=live |access-date=26 Aug 2025 |website=The Register}}&amp;lt;/ref&amp;gt;&amp;lt;ref name=&amp;quot;:3&amp;quot;&amp;gt;{{Cite web |first= |date=26 Aug 2025 |title=Google will block sideloading of unverified Android apps starting next year |url=https://www.bleepingcomputer.com/forums/t/810335/google-will-block-sideloading-of-unverified-android-apps-starting-next-year |url-status=live |access-date=26 Aug 2025 |website=BleepingComputer}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Not providing a solution for Pixel devices bricked due to switching slots, flashing certain ROMs, downgrading the OS, or installing the June 2025 update===&lt;br /&gt;
Numerous Google Pixel phones have gotten bricked as a result of different use cases, such as accidentally switched slots, flashing custom ROMs or downgrading the bootloader version of the device after an Anti-Rollback (ARB) increment, accidentally or otherwise&amp;lt;ref&amp;gt;{{Cite web |last=Simons |first=Hadlee |date=2025-08-26 |title=Some Pixels are bricked and Google apparently won&#039;t help revive them |url=https://www.androidauthority.com/google-pixel-phones-bricked-3591218/ |url-status=live |access-date=2025-09-11 |website=Android Authority}}&amp;lt;/ref&amp;gt;. The device enters an emergency download (EDL) state, where it refuses to enter fastboot or recovery mode, making it near impossible to repair. The only way to fix it is to load recovery firmware onto the RAM and flash a working version of Android from there.&lt;br /&gt;
&lt;br /&gt;
However, this recovery firmware is inaccessible to the public, and is not possible to create without Google&#039;s private keys. This makes it impossible to repair a device in this state, other than to do a complicated J-TAG repair by unsoldering and resoldering the UFS chip or by replacing the motherboard altogether. Google stores and service centers outside of the US do not offer support for the device if it is out of warranty, even though the issue is completely fixable by software.&lt;br /&gt;
&lt;br /&gt;
Numerous developers have worked on trying to find a solution to this issue, and have succeeded to varying extents. However, devices bricked due to the ARB trigger remain impossible to fix. Google has not provided any recovery images to resolve this issue, despite there being a sizable post on their bug tracker.&amp;lt;ref name=&amp;quot;:4&amp;quot;&amp;gt;{{Cite web |date=2025-08-10 |title=Pixel recovery bootloaders lack security reasoning for guarding |url=https://issuetracker.google.com/issues/437705274 |url-status=live |access-date=2025-09-11 |website=Google IssueTracker}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |date=2025-03-12 |title=Pixel devices getting bricked / stuck in Pixel ROM Recovery after flashing AOSP-based builds with Android 15 QPR2 (BP1A.250305.019) |url=https://issuetracker.google.com/issues/402455330 |url-status=live |access-date=2025-09-11 |website=Google IssueTracker}}&amp;lt;/ref&amp;gt; despite the fact that Google providing the recovery images for the repair will not compromise security, as explained by one of the developers in their report.&amp;lt;ref name=&amp;quot;:4&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Controversies==&lt;br /&gt;
&lt;br /&gt;
===Google device repair program restrictions===&lt;br /&gt;
{{Main|Google asserts the right to seize your phone during a repair}}&lt;br /&gt;
Google&#039;s Service &amp;amp; Repair Program terms explicitly state that any device containing non-Google-authorized parts &amp;quot;will not be returned&amp;quot; to the customer.&lt;br /&gt;
&lt;br /&gt;
===Target API level requirements for Google Play apps===&lt;br /&gt;
Google&#039;s policy of requiring apps for Android to target recent API levels to appear in the Play Store&amp;lt;ref&amp;gt;{{Cite web |date=31 Aug 2024 |title=Policy Center |url=https://support.google.com/googleplay/android-developer/answer/11926878?hl=en |access-date=May 9, 2025 |website=Play Console Help}}&amp;lt;/ref&amp;gt; creates a continuous cycle of maintenance and redevelopment that can be especially burdensome for smaller developers, indie creators, and consumers.&lt;br /&gt;
&lt;br /&gt;
The requirement for apps to target newer APIs each year serves some legitimate security and feature purposes. However, it also effectively functions as a form of forced obsolescence. Even perfectly functional apps that don&#039;t need technical updates must be regularly reworked just to remain visible on the Play Store.&lt;br /&gt;
&lt;br /&gt;
This creates several issues:&lt;br /&gt;
&lt;br /&gt;
*Development resources must be allocated to updating apps rather than creating new features&lt;br /&gt;
*Smaller teams and individual developers are placed at a disadvantage attempting to keep up with the constant update cycle&lt;br /&gt;
*Legacy apps that are no longer actively maintained disappear, even if they&#039;re still useful&lt;br /&gt;
*The cost of maintaining apps increases, potentially making some projects financially nonviable&lt;br /&gt;
*Losing access to previously purchased apps when upgrading devices&lt;br /&gt;
*Users being unable to reinstall older apps that worked perfectly well for their needs&lt;br /&gt;
*Facing unexpected costs to replace functionality they&#039;ve already paid for&lt;br /&gt;
*Dealing with the frustration of discovering favorite apps have disappeared&lt;br /&gt;
&lt;br /&gt;
While Google argues this approach improves the Android ecosystem&#039;s security and functionality, it does place a significant burden on developers and can lead to the premature &amp;quot;death&amp;quot; of otherwise functional applications.&lt;br /&gt;
&lt;br /&gt;
This creates a troubling disconnect in digital ownership. Consumers reasonably expect that when they purchase an app, they should maintain access to it across their devices over time. Instead, they discover their digital purchases can effectively vanish due to policy decisions beyond their control.&lt;br /&gt;
&lt;br /&gt;
===Ban on third-party tech support ads===&lt;br /&gt;
Google prohibits tech support ads on their platform if they are not authorised by the manufacturer.&amp;lt;ref&amp;gt;{{Cite web |last=Graff |first=David |date=31 Aug 2018 |title=Restricting ads in third-party tech support services |url=https://blog.google/products/ads/restricting-ads-third-party-tech-support-services/ |website=Google}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
==Anti-consumer legal cases==&lt;br /&gt;
&lt;br /&gt;
===Rodriguez v. Google LLC (5/21/21 - Present)===&lt;br /&gt;
Google&#039;s Web &amp;amp; App Activity setting had the ability to be paused. Reportedly, despite this setting being paused by consumers, Google would continue to collect consumer data regardless of consent.&amp;lt;ref&amp;gt;{{Cite web |title=Rodriguez v. Google LLC |url=https://www.googlewebappactivitylawsuit.com/Home/FAQ#faq1 |url-status=live |access-date=5 Apr 2025}}&amp;lt;/ref&amp;gt; This case is currently ongoing and has yet to receive a judgment.&amp;lt;ref&amp;gt;[https://www.googlewebappactivitylawsuit.com/Home/Documents Important Documents]&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Epic Games, Inc. v. Google Inc. (8/13/20 - 5/31/25)===&lt;br /&gt;
Google takes a 30% share of all revenue made through all sales made on the Play Store, which is a comparable figure to other digital storefronts such as the [[Apple App Store]] and [[Steam]].&amp;lt;ref&amp;gt;{{Cite web |last=Marks |first=Tom |date=7 Oct 2019 |title=Report: Steam&#039;s 30% Cut Is Actually the Industry Standard |url=https://www.ign.com/articles/2019/10/07/report-steams-30-cut-is-actually-the-industry-standard |url-status=live |website=ign.com}}&amp;lt;/ref&amp;gt; On 13th August 2020, [[Epic Games]] CEO Tim Sweeney updated both iOS and Android versions of &#039;&#039;Fortnite&#039;&#039; to redirect users to Epic Games&#039; storefront to purchase in-game currency (&amp;quot;V-Bucks&amp;quot;) alongside the respective first-party storefront, with incentives including cheaper prices if buying from Epic Games directly. This violated the Terms of Service of both Apple and Google&#039;s storefronts, and &#039;&#039;Fortnite&#039;&#039; was removed from both app stores the same day.&lt;br /&gt;
&lt;br /&gt;
Epic Games would use this motion to file federal lawsuits against both Google and Apple, citing that these practices meant that the companies were engaging in anti-competitive behavior. Google lost in the lawsuit, but attempted to appeal the decision, in which they lost again.&amp;lt;ref&amp;gt;{{Cite news |last=Hollister |first=Sean |date=31 July 2025 |title=Epic just won its Google lawsuit again, and Android may never be the same |url=https://www.theverge.com/news/716856/epic-v-google-win-in-appeals-court |access-date=21 August 2025 |work=The Verge}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==See also==&lt;br /&gt;
&lt;br /&gt;
===Products and Services===&lt;br /&gt;
&lt;br /&gt;
[[List of Google products]]&lt;br /&gt;
===Controversies===&lt;br /&gt;
&lt;br /&gt;
*[[Advertising overload]]&lt;br /&gt;
*[[Google follows Samsung, asserts the right to steal your phone during a repair]]&lt;br /&gt;
*[[Google Pixel Watches do not come with repair options]]&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
&amp;lt;references /&amp;gt;&lt;br /&gt;
[[Category:Google]]&lt;/div&gt;</summary>
		<author><name>Jake01756</name></author>
	</entry>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=Google&amp;diff=24420</id>
		<title>Google</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=Google&amp;diff=24420"/>
		<updated>2025-09-12T04:16:13Z</updated>

		<summary type="html">&lt;p&gt;Jake01756: /* Google Play Music shutdown */ clarify a bit&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{CompanyCargo&lt;br /&gt;
|Founded=1998&lt;br /&gt;
|Industry=Technology&lt;br /&gt;
|Logo=Google.webp&lt;br /&gt;
|ParentCompany=Alphabet Inc.&lt;br /&gt;
|Type=Subsidiary&lt;br /&gt;
|Website=https://www.google.com/&lt;br /&gt;
}}&lt;br /&gt;
&#039;&#039;&#039;[[wikipedia:Google|Google LLC]]&#039;&#039;&#039;, founded in 1998 by Larry Page and Sergey Brin, is one of the most influential technology companies in the world.&amp;lt;ref&amp;gt;{{Cite web |title=Largest tech companies by market cap |url=https://companiesmarketcap.com/tech/largest-tech-companies-by-market-cap/ |url-status=live |website=companiesmarketcap.com}}&amp;lt;/ref&amp;gt; Originally developed as a search engine to organize and index the growing amount of information on the internet, Google has since expanded into a wide range of services and products, becoming a central player in digital advertising, software, hardware, and cloud computing.&amp;lt;ref&amp;gt;{{Cite web |date= |title=Google Products |url=https://about.google/products/ |access-date=10 Mar 2025}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Google&#039;s search engine remains its most well-known service, but the company has significantly diversified its offerings. Key products include the [[Android]] operating system, the [[Google Chrome]] web browser, [https://wikipedia.org/wiki/Google_Drive Google Drive] for cloud storage, [https://wikipedia.org/wiki/Google_Maps Google Maps], [[YouTube]], and [[wikipedia:Google_Play|Google Play]].&amp;lt;ref&amp;gt;{{Cite web |title=Helpful products, built with you in mind |url=https://about.google/intl/ALL_us/products/ |url-status=live |access-date=5 Apr 2025 |website=[[Google]]}}&amp;lt;/ref&amp;gt;{{Citation needed}} Additionally, the company provides digital advertising services through Google Ads, generating the majority of its revenue.&amp;lt;ref&amp;gt;{{Cite web |date=4 Feb 2025 |title=Alphabet Announces Fourth Quarter and Fiscal Year 2024 Results |url=https://abc.xyz/assets/a3/91/6d1950c148fa84c7d699abe05284/2024q4-alphabet-earnings-release.pdf |url-status=live |access-date=5 Apr 2025}}&amp;lt;/ref&amp;gt; In recent years, Google has also developed hardware products such as the Pixel smartphone and Nest smart home devices.&lt;br /&gt;
&lt;br /&gt;
Google has faced ongoing scrutiny related to data privacy, competition, and its dominant position in the market, such concerns have stretched as far back as 2012.&amp;lt;ref&amp;gt;{{Cite web |last=Cohen |first=Adam |date=5 Mar 2012 |title=Will We Ever Get Strong Internet Privacy Rules? |url=https://ideas.time.com/2012/03/05/will-we-ever-get-strong-internet-privacy-rules/ |url-status=live |access-date=5 Apr 2025 |website=Time}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |date=6 Sep 2023 |title=REPORT: Google at 25: From “Don’t Be Evil” To ¯\_(ツ)_/¯ |url=https://techoversight.org/2023/09/06/google-at-25/ |url-status=live |access-date=5 Apr 2025 |website=The Tech Oversight Project}}&amp;lt;/ref&amp;gt; The company has been the subject of various legal and regulatory challenges, particularly concerning antitrust issues, the use of personal data, and its impact on consumer choice.{{Citation needed}} The US government is currently engaged in an antitrust lawsuit against Google, with a decision expected early 2025.&amp;lt;ref&amp;gt;{{Cite web |date=25 Nov 2024 |title=Closing Arguments, November 25: Once, Twice, Three Times a Monopolist |url=https://www.usvgoogleads.com/trial-updates/closing-arguments-november-25-once-twice-three-times-a-monopolist |url-status=live |access-date=5 Apr 2025 |website=US v Google}}&amp;lt;/ref&amp;gt; {{UpdateNeeded|date={{subst:August}} {{subst:2025}}|reason=We need updates on this situation.}}&lt;br /&gt;
&lt;br /&gt;
In December 2024, Google announced to organisations that use its advertising products, that from 16 February 2025, it will no longer prohibit them from employing [[wikipedia:Fingerprint_(computing)|fingerprinting]] techniques.&amp;lt;ref&amp;gt;{{Cite web |last=Almond |first=Stephen |date=19 Dec 2024 |title=Our response to Google’s policy change on fingerprinting |url=https://ico.org.uk/about-the-ico/media-centre/news-and-blogs/2024/12/our-response-to-google-s-policy-change-on-fingerprinting/ |url-status=live |access-date=5 Apr 2025 |website=ico.}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Anti-consumer incidents==&lt;br /&gt;
&lt;br /&gt;
===Service shutdowns===&lt;br /&gt;
&lt;br /&gt;
====Google Play Music shutdown====&lt;br /&gt;
[[wikipedia:Google_Play_Music|Google Play Music]] was a service that allowed users to purchase music, listen via streaming, and download to the local device; alternatively users could pay for a subscription to listen to all music available through streaming. It was publicly launched on the 16th November 2011 and later shutdown in December 2020.&amp;lt;ref&amp;gt;{{Cite web |date=4 Aug 2020 |title=Google Play Music, Music Play Store &amp;amp; Music Manager are going away – everything you need to know |url=https://support.google.com/youtubemusic/thread/62843644/google-play-music-music-play-store-music-manager-are-going-away-%E2%80%93-everything-you-need-to-know?hl=en |url-status=live |access-date=5 Apr 2025 |website=[[Google]]}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |last=Amadeo |first=Ron |date=28 Oct 2020 |title=RIP Google Play Music, 2011 – 2020 |url=https://arstechnica.com/gadgets/2020/10/rip-google-play-music-2011-2020/ |url-status=live |access-date=5 Apr 2025 |website=ArsTechnica}}&amp;lt;/ref&amp;gt; Google Play Music further allowed users to upload their own songs to listen on all their devices, with a limit of up to 50,000 files.&amp;lt;ref&amp;gt;{{Cite web |last=Hoffman |first=Chris |date=11 Jan 2017 |title=How to Upload Your Music Library to Google Play Music |url=https://www.howtogeek.com/288231/how-to-upload-your-music-library-to-google-play-music/ |url-status=live |access-date=5 Apr 2025 |website=How-To-Geek}}&amp;lt;/ref&amp;gt; Users were able to purchase songs individually or buy whole albums that they could then download and listen to, or stream through the internet.&amp;lt;ref&amp;gt;{{Cite web |date=15 Jan 2020 |title=How To Buy Music From Google Play (Now YouTube Music) |url=https://www.technobezz.com/buy-music-google-play |url-status=live |access-date=5 Apr 2025 |website=Technobezz}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In October 2020, Google announced that they would be shutting down Google Play Music, with it being fully shut down by December.&amp;lt;ref&amp;gt;{{Cite web |last=Li |first=Abner |date=3 Dec 2020 |title=Google fully shuts down Play Music around the world |url=https://9to5google.com/2020/12/03/google-play-music-dead/ |url-status=live |access-date=5 Apr 2025 |website=9To5Google}}&amp;lt;/ref&amp;gt; This went ahead with a warning to their users to begin migrating to [[wikipedia:YouTube_Music|YouTube Music]], and that they would be losing access to their purchased songs. Google recommended users should download their purchased songs before the service would shut down.&amp;lt;ref&amp;gt;{{Cite web |date=4 Aug 2020 |title=YouTube Music will replace Google Play Music by end of 2020 |url=https://blog.youtube/news-and-events/youtube-music-will-replace-google-play-music-end-2020/ |url-status=live |access-date=5 Apr 2025 |website=YouTube Official Blog}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
After the shut down, users lost access to the music they paid for, with no way to download them. Google justified this by transferring all playlists and purchase history to YouTube Music, and only refunding songs that were not directly available,&amp;lt;ref&amp;gt;{{Cite web |date=10 Oct 2023 |title=What happened to my songs on Google Music? |url=https://darwinsdata.com/what-happened-to-my-songs-on-google-music/ |url-status=live |access-date=5 Apr 2025 |website=Darwin&#039;s Data}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |last=Chaney |first=Sarah |date=5 Feb 2022 |title=What Happened to Google Play Music? |url=https://www.makeuseof.com/what-happened-to-google-play-music/ |url-status=live |access-date=5 Apr 2025 |website=MUO}}&amp;lt;/ref&amp;gt; with no guarantee that the songs will remain available through the new service. Users found that their purchased songs were no longer able to stream at 320kbps on YouTube Music compared to Google Play Music unless they paid for the monthly subscription.&amp;lt;ref&amp;gt;{{Cite web |last=Cutlack |first=Gary |date=23 Dec 2012 |title=Google Music UK: everything you need to know |url=https://www.techradar.com/news/software/google-music-uk-everything-you-need-to-know-1120176 |url-status=live |access-date=5 Apr 2025 |website=TechRadar}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |last=L. Hald |first=Nicole |date=24 Mar 2025 |title=How Is YouTube Music Sound Quality in 2025? Is It Any Good? |url=https://www.noteburner.com/youtube-music-tips/youtube-music-audio-quality.html |url-status=live |access-date=5 Apr 2025 |website=NoteBurner}}&amp;lt;/ref&amp;gt; If a user failed to initiate the transfer of their music library or locally download their songs by 24th February 2021, then they lost all access and all data associated with Google Play Music.&amp;lt;ref&amp;gt;{{Cite web |last=Sodhi |first=Tanishka |date=8 Feb 2021 |title=Google Play Music Data Will Be Deleted on February 24: Here’s How to Transfer to YouTube Music |url=https://www.gadgets360.com/how-to/news/google-play-music-data-deleted-february-24-youtube-how-to-transfer-files-playlists-billing-information-2365609 |url-status=live |access-date=5 Apr 2025 |website=Gadgets 360}}&amp;lt;/ref&amp;gt; YouTube Music does not provide the option to download songs as MP3s, with local downloads requiring an internet connection every 30 days to continue working offline.&amp;lt;ref&amp;gt;{{Cite web |title=Download music and podcasts to listen to offline |url=https://support.google.com/youtubemusic/answer/6313535?hl=en-GB&amp;amp;co=GENIE.Platform%3DAndroid |url-status=live |access-date=5 Apr 2025 |website=[[Google]]}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====Google Stadia shutdown====&lt;br /&gt;
In January 2023, Google announced the shutdown of its cloud gaming service, Stadia, which was launched in November 2019.&amp;lt;ref&amp;gt;{{Cite web |title=RIP Google Stadia: the latest news on the discontinued cloud gaming service |url=https://www.theverge.com/23380140/google-stadia-ending-shutdown-latest-news-gaming-tech |url-status=live |access-date=5 Apr 2025 |website=The Verge}}&amp;lt;/ref&amp;gt; Stadia required users to purchase games individually, unlike other gaming platforms that offer subscription-based access. Upon the service&#039;s closure, Google promised to refund consumers for their purchases, including both games and hardware. The refunds for games and software were issued automatically.&amp;lt;ref&amp;gt;{{Cite web |last=Ravenscraft |first=Erin |date=10 Nov 2022 |title=Stadia Is Dying. Here’s What’s in Your Refund and How to Get It |url=https://www.wired.com/story/how-to-get-your-google-stadia-refund/ |url-status=live |access-date=5 Apr 2025 |website=Wired}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Stadia users were effectively renting access to games, as the platform did not allow for traditional ownership or offline play. With the service discontinued, consumers were left without access to the content they had purchased. Stadia users who had bought controllers and other peripherals for the service were also impacted by the shutdown. While Google offered refunds to customers, many Stadia consumers were left with equipment that no longer performs the advertised functions and limited recourse for repurposing or reselling their devices.&amp;lt;ref&amp;gt;{{Cite web |last=Ashworth |first=Mack |date=5 Oct 2022 |title=Stadia Shut Down: How To Use Your Hardware Now Google’s Shutting It Down |url=https://www.gamerevolution.com/guides/852697-stadia-shut-down-how-to-use-controller-chromecast-without-app |url-status=live |access-date=5 Apr 2025 |website=Game Revolution}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Google Stadia controllers were limited to Wi-Fi connectivity, however upon shut down they started offering an update to allow them to connect through Bluetooth, the update service website was scheduled to shut down on the 31st December 2025.&amp;lt;ref&amp;gt;{{Cite web |last=Devine |first=Richard |date=17 Jan 2023 |title=Bluetooth support for Google Stadia Controller arrives — Here&#039;s how to enable it and play PC games |url=https://www.windowscentral.com/gaming/pc-gaming/bluetooth-support-for-google-stadia-controller-arrives-heres-how-to-enable-it-and-play-pc-games |url-status=live |access-date=5 Apr 2025 |website=Windows Central}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====&#039;&#039;&#039;Manifest V2 shutdown&#039;&#039;&#039;====&lt;br /&gt;
On July 24, 2025, Google permanently disabled all Manifest V2 extensions for Chrome 138 users, and disabled the ability to turn them back on.&amp;lt;ref&amp;gt;{{Cite web |date=2021-09-23 |title=Manifest V2 support timeline |url=https://developer.chrome.com/docs/extensions/develop/migrate/mv2-deprecation-timeline |archive-url=https://web.archive.org/web/20250808191702/https://developer.chrome.com/docs/extensions/develop/migrate/mv2-deprecation-timeline |archive-date=2025-08-08 |access-date=2025-08-12}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Manifest V3 disabled the &amp;lt;code&amp;gt;webRequestBlocking&amp;lt;/code&amp;gt; permission in the &amp;lt;code&amp;gt;webRequest&amp;lt;/code&amp;gt; API&amp;lt;ref&amp;gt;{{Cite web |date=2023-03-09 |title=Replace blocking web request listeners {{!}} Chrome Extensions {{!}} Chrome for Developers |url=https://developer.chrome.com/docs/extensions/develop/migrate/blocking-web-requests |url-status=live |archive-url=https://web.archive.org/web/20250614074559/https://developer.chrome.com/docs/extensions/develop/migrate/blocking-web-requests |archive-date=2025-06-14 |access-date=2025-08-12 |website=Chrome for Developers}}&amp;lt;/ref&amp;gt;, preventing many ad content blockers from working.&amp;lt;ref&amp;gt;{{Cite web |date=2024-09-26 |title=Understanding Manifest V3 and the Future of uBlock Origin |url=https://ublockorigin.com/ |url-status=live |archive-url=https://web.archive.org/web/20250812114916/https://ublockorigin.com/ |archive-date=2025-08-12 |access-date=2025-08-12 |website=uBlock Origin - Free, open-source ad content blocker}}&amp;lt;/ref&amp;gt; Google cites performance reasons &amp;lt;ref&amp;gt;{{Cite web |date=2023-03-09 |title=Replace blocking web request listeners {{!}} Chrome Extensions {{!}} Chrome for Developers |url=https://developer.chrome.com/docs/extensions/develop/migrate/blocking-web-requests |url-status=live |archive-url=https://web.archive.org/web/20250614074559/https://developer.chrome.com/docs/extensions/develop/migrate/blocking-web-requests |archive-date=2025-06-14 |access-date=2025-08-12 |website=Chrome for Developers |quote=&amp;quot;In Manifest V2, blocking web requests could significantly degrade both the performance of extensions and the performance of pages they work with.&amp;quot;}}&amp;lt;/ref&amp;gt;, but this is dubious; restricting content blockers prevents users from impeding their tracking and surveillance, meaning they can create a larger profit from the data gained. This is likely the ulterior motive, although unproven.&lt;br /&gt;
&lt;br /&gt;
===&#039;&#039;&#039;Pixel 4a battery reduction update&#039;&#039;&#039;===&lt;br /&gt;
{{Main|Pixel 4a Battery Performance Program}}&lt;br /&gt;
On January 6, 2025, Google issued a software update to the Pixel 4a that significantly decreased battery capacity on &amp;quot;Impacted Devices&amp;quot;. Not all units were affected. It&#039;s speculated that the affected units have defective batteries and may pose a safety risk if the update is not applied, but Google never disclosed the reason(s) that the update was deemed necessary. Google removed all factory images for previous versions of the system software from their website, making it difficult to revert the update.&lt;br /&gt;
&lt;br /&gt;
As compensation, Google offered a free battery replacement only in select countries. In other countries, you could choose between a $50 USD payment or $100 USD worth of Google Store credits. However, some users reported difficulty obtaining their compensation.&lt;br /&gt;
&lt;br /&gt;
===Blocking sideloading of unverified Android apps===&lt;br /&gt;
{{Main|Google blocking sideloading of unverified Android apps}}&lt;br /&gt;
On 25 August 2025, &#039;&#039;&#039;[[Google]]&#039;&#039;&#039; announced that starting in 2026 it will block the installation of Android apps from outside the Play Store unless the developer has verified their identity with Google. The policy will first roll out in Brazil, Indonesia, Singapore, and Thailand in September 2026, with global enforcement targeted for 2027.&amp;lt;ref name=&amp;quot;:0&amp;quot;&amp;gt;{{Cite web |last=Frey |first=Suzanne |date=25 Aug 2025 |title=A new layer of security for certified Android devices |url=https://android-developers.googleblog.com/2025/08/elevating-android-security.html |url-status=live |access-date=25 Aug 2025 |website=Android Developers Blog}}&amp;lt;/ref&amp;gt;&amp;lt;ref name=&amp;quot;:1&amp;quot;&amp;gt;{{Cite web |last=Perez |first=Sarah |date=25 Aug 2025 |title=Google will require developer verification for Android apps outside the Play Store |url=https://techcrunch.com/2025/08/25/google-will-require-developer-verification-for-android-apps-outside-the-play-store/ |url-status=live |access-date=25 Aug 2025 |website=TechCrunch}}&amp;lt;/ref&amp;gt; This marks a significant change to Android&#039;s long-standing support for sideloading apps.&lt;br /&gt;
&lt;br /&gt;
Devices without Google Mobile Services or running custom ROMs are exempt.&amp;lt;ref name=&amp;quot;:22&amp;quot;&amp;gt;{{Cite web |last=Anderson |first=Tim |date=2025-08-26 |title=Google kneecaps indie Android devs, forces them to register |url=https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |url-status=live |archive-url=https://web.archive.org/web/20250829170329/https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |archive-date=2025-08-29 |access-date=2025-08-26 |website=The Register}}&amp;lt;/ref&amp;gt; Critics argue this restricts user freedom, impacts independent developers, and may enable Google to block apps it disapproves of, such as ad-blockers, raising concerns about privacy and control over personal devices.&amp;lt;ref name=&amp;quot;:2&amp;quot;&amp;gt;{{Cite web |last=Anderson |first=Tim |date=26 Aug 2025 |title=Google kneecaps indie Android devs, forces them to register |url=https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |url-status=live |access-date=26 Aug 2025 |website=The Register}}&amp;lt;/ref&amp;gt;&amp;lt;ref name=&amp;quot;:3&amp;quot;&amp;gt;{{Cite web |first= |date=26 Aug 2025 |title=Google will block sideloading of unverified Android apps starting next year |url=https://www.bleepingcomputer.com/forums/t/810335/google-will-block-sideloading-of-unverified-android-apps-starting-next-year |url-status=live |access-date=26 Aug 2025 |website=BleepingComputer}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Not providing a solution for Pixel devices bricked due to switching slots, flashing certain ROMs, downgrading the OS, or installing the June 2025 update===&lt;br /&gt;
Numerous Google Pixel phones have gotten bricked as a result of different use cases, such as accidentally switched slots, flashing custom ROMs or downgrading the bootloader version of the device after an Anti-Rollback (ARB) increment, accidentally or otherwise&amp;lt;ref&amp;gt;{{Cite web |last=Simons |first=Hadlee |date=2025-08-26 |title=Some Pixels are bricked and Google apparently won&#039;t help revive them |url=https://www.androidauthority.com/google-pixel-phones-bricked-3591218/ |url-status=live |access-date=2025-09-11 |website=Android Authority}}&amp;lt;/ref&amp;gt;. The device enters an emergency download (EDL) state, where it refuses to enter fastboot or recovery mode, making it near impossible to repair. The only way to fix it is to load recovery firmware onto the RAM and flash a working version of Android from there.&lt;br /&gt;
&lt;br /&gt;
However, this recovery firmware is inaccessible to the public, and is not possible to create without Google&#039;s private keys. This makes it impossible to repair a device in this state, other than to do a complicated J-TAG repair by unsoldering and resoldering the UFS chip or by replacing the motherboard altogether. Google stores and service centers outside of the US do not offer support for the device if it is out of warranty, even though the issue is completely fixable by software.&lt;br /&gt;
&lt;br /&gt;
Numerous developers have worked on trying to find a solution to this issue, and have succeeded to varying extents. However, devices bricked due to the ARB trigger remain impossible to fix. Google has not provided any recovery images to resolve this issue, despite there being a sizable post on their bug tracker.&amp;lt;ref name=&amp;quot;:4&amp;quot;&amp;gt;{{Cite web |date=2025-08-10 |title=Pixel recovery bootloaders lack security reasoning for guarding |url=https://issuetracker.google.com/issues/437705274 |url-status=live |access-date=2025-09-11 |website=Google IssueTracker}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |date=2025-03-12 |title=Pixel devices getting bricked / stuck in Pixel ROM Recovery after flashing AOSP-based builds with Android 15 QPR2 (BP1A.250305.019) |url=https://issuetracker.google.com/issues/402455330 |url-status=live |access-date=2025-09-11 |website=Google IssueTracker}}&amp;lt;/ref&amp;gt; despite the fact that Google providing the recovery images for the repair will not compromise security, as explained by one of the developers in their report.&amp;lt;ref name=&amp;quot;:4&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Controversies==&lt;br /&gt;
&lt;br /&gt;
===Google device repair program restrictions===&lt;br /&gt;
{{Main|Google asserts the right to seize your phone during a repair}}&lt;br /&gt;
Google&#039;s Service &amp;amp; Repair Program terms explicitly state that any device containing non-Google-authorized parts &amp;quot;will not be returned&amp;quot; to the customer.&lt;br /&gt;
&lt;br /&gt;
===Target API level requirements for Google Play apps===&lt;br /&gt;
Google&#039;s policy of requiring apps for Android to target recent API levels to appear in the Play Store&amp;lt;ref&amp;gt;{{Cite web |date=31 Aug 2024 |title=Policy Center |url=https://support.google.com/googleplay/android-developer/answer/11926878?hl=en |access-date=May 9, 2025 |website=Play Console Help}}&amp;lt;/ref&amp;gt; creates a continuous cycle of maintenance and redevelopment that can be especially burdensome for smaller developers, indie creators, and consumers.&lt;br /&gt;
&lt;br /&gt;
The requirement for apps to target newer APIs each year serves some legitimate security and feature purposes. However, it also effectively functions as a form of forced obsolescence. Even perfectly functional apps that don&#039;t need technical updates must be regularly reworked just to remain visible on the Play Store.&lt;br /&gt;
&lt;br /&gt;
This creates several issues:&lt;br /&gt;
&lt;br /&gt;
*Development resources must be allocated to updating apps rather than creating new features&lt;br /&gt;
*Smaller teams and individual developers are placed at a disadvantage attempting to keep up with the constant update cycle&lt;br /&gt;
*Legacy apps that are no longer actively maintained disappear, even if they&#039;re still useful&lt;br /&gt;
*The cost of maintaining apps increases, potentially making some projects financially nonviable&lt;br /&gt;
*Losing access to previously purchased apps when upgrading devices&lt;br /&gt;
*Users being unable to reinstall older apps that worked perfectly well for their needs&lt;br /&gt;
*Facing unexpected costs to replace functionality they&#039;ve already paid for&lt;br /&gt;
*Dealing with the frustration of discovering favorite apps have disappeared&lt;br /&gt;
&lt;br /&gt;
While Google argues this approach improves the Android ecosystem&#039;s security and functionality, it does place a significant burden on developers and can lead to the premature &amp;quot;death&amp;quot; of otherwise functional applications.&lt;br /&gt;
&lt;br /&gt;
This creates a troubling disconnect in digital ownership. Consumers reasonably expect that when they purchase an app, they should maintain access to it across their devices over time. Instead, they discover their digital purchases can effectively vanish due to policy decisions beyond their control.&lt;br /&gt;
&lt;br /&gt;
===Ban on third-party tech support ads===&lt;br /&gt;
Google prohibits tech support ads on their platform if they are not authorised by the manufacturer.&amp;lt;ref&amp;gt;{{Cite web |last=Graff |first=David |date=31 Aug 2018 |title=Restricting ads in third-party tech support services |url=https://blog.google/products/ads/restricting-ads-third-party-tech-support-services/ |website=Google}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Anti-consumer legal cases==&lt;br /&gt;
&lt;br /&gt;
===Rodriguez v. Google LLC (5/21/21 - Present)===&lt;br /&gt;
Google&#039;s Web &amp;amp; App Activity setting had the ability to be paused. Reportedly, despite this setting being paused by consumers, Google would continue to collect consumer data regardless of consent.&amp;lt;ref&amp;gt;{{Cite web |title=Rodriguez v. Google LLC |url=https://www.googlewebappactivitylawsuit.com/Home/FAQ#faq1 |url-status=live |access-date=5 Apr 2025}}&amp;lt;/ref&amp;gt; This case is currently ongoing and has yet to receive a judgment.&amp;lt;ref&amp;gt;[https://www.googlewebappactivitylawsuit.com/Home/Documents Important Documents]&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Epic Games, Inc. v. Google Inc. (8/13/20 - 5/31/25)===&lt;br /&gt;
Google takes a 30% share of all revenue made through all sales made on the Play Store, which is a comparable figure to other digital storefronts such as the [[Apple App Store]] and [[Steam]].&amp;lt;ref&amp;gt;{{Cite web |last=Marks |first=Tom |date=7 Oct 2019 |title=Report: Steam&#039;s 30% Cut Is Actually the Industry Standard |url=https://www.ign.com/articles/2019/10/07/report-steams-30-cut-is-actually-the-industry-standard |url-status=live |website=ign.com}}&amp;lt;/ref&amp;gt; On 13th August 2020, [[Epic Games]] CEO Tim Sweeney updated both iOS and Android versions of &#039;&#039;Fortnite&#039;&#039; to redirect users to Epic Games&#039; storefront to purchase in-game currency (&amp;quot;V-Bucks&amp;quot;) alongside the respective first-party storefront, with incentives including cheaper prices if buying from Epic Games directly. This violated the Terms of Service of both Apple and Google&#039;s storefronts, and &#039;&#039;Fortnite&#039;&#039; was removed from both app stores the same day.&lt;br /&gt;
&lt;br /&gt;
Epic Games would use this motion to file federal lawsuits against both Google and Apple, citing that these practices meant that the companies were engaging in anti-competitive behaviour. Google lost in the lawsuit, but attempted to appeal the decision, in which they lost again.&amp;lt;ref&amp;gt;{{Cite news |last=Hollister |first=Sean |date=31 July 2025 |title=Epic just won its Google lawsuit again, and Android may never be the same |url=https://www.theverge.com/news/716856/epic-v-google-win-in-appeals-court |access-date=21 August 2025 |work=The Verge}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==See also==&lt;br /&gt;
&lt;br /&gt;
===Products and Services===&lt;br /&gt;
&lt;br /&gt;
[[List of Google products]]&lt;br /&gt;
===Controversies===&lt;br /&gt;
&lt;br /&gt;
*[[Advertising overload]]&lt;br /&gt;
*[[Google follows Samsung, asserts the right to steal your phone during a repair]]&lt;br /&gt;
*[[Google Pixel Watches do not come with repair options]]&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
&amp;lt;references /&amp;gt;&lt;br /&gt;
[[Category:Google]]&lt;/div&gt;</summary>
		<author><name>Jake01756</name></author>
	</entry>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=User:Jake01756&amp;diff=24125</id>
		<title>User:Jake01756</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=User:Jake01756&amp;diff=24125"/>
		<updated>2025-09-08T06:28:44Z</updated>

		<summary type="html">&lt;p&gt;Jake01756: Created page with &amp;quot;Hi! I love consumer rights. Go consumers!&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Hi! I love consumer rights. Go consumers!&lt;/div&gt;</summary>
		<author><name>Jake01756</name></author>
	</entry>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=Category:1Password&amp;diff=24124</id>
		<title>Category:1Password</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=Category:1Password&amp;diff=24124"/>
		<updated>2025-09-08T06:28:09Z</updated>

		<summary type="html">&lt;p&gt;Jake01756: create the category page :)&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;1Password is a multi-platform subscription-based [[Password manager]] developed by [[AgileBits Inc]].&lt;/div&gt;</summary>
		<author><name>Jake01756</name></author>
	</entry>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=1Password&amp;diff=24123</id>
		<title>1Password</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=1Password&amp;diff=24123"/>
		<updated>2025-09-08T06:26:57Z</updated>

		<summary type="html">&lt;p&gt;Jake01756: /* Market control */ typo&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Incomplete}}&lt;br /&gt;
{{ProductCargo&lt;br /&gt;
|Company=Agilebits&lt;br /&gt;
|ProductLine=1Password&lt;br /&gt;
|InProduction=Yes&lt;br /&gt;
|ArticleType=Product&lt;br /&gt;
|Category=Software,Password Managers&lt;br /&gt;
|Website=https://1password.com/&lt;br /&gt;
|Description=1Password is a secure password manager that stores and encrypts passwords, login details, and other sensitive information in a digital vault&lt;br /&gt;
|Logo=1Password-logo.png|ReleaseYear=2006}}1Password is a multi-platform subscription-based [[Password manager]] developed by [[AgileBits Inc]]. One of the unique elements of this password manager is the combination of a master password with a second secret key generated on-device (i.e., not in the cloud). Unlocking a user&#039;s vault therefore requires &#039;&#039;&#039;both&#039;&#039;&#039; pieces of information to decrypt and access. Conventional [[Two factor authentication]] using either software tokens or hardware-based tokens (e.g., [[Yubikey]], [[Google Titan]]) can be added to further secure a vault. 1Password is not open source and not self-hostable.&lt;br /&gt;
&lt;br /&gt;
Beyond passwords, 1Password is capable of storing myriad site credentials including one-time codes, emails / user names, and additional notes. A user can also choose a preferred single sign-on service to login.&lt;br /&gt;
&lt;br /&gt;
==Consumer impact summary==&lt;br /&gt;
&lt;br /&gt;
===Freedom===&lt;br /&gt;
Users can import existing passwords from other managers and export passwords and other content in formats suitable for importing into other managers. 1Password is not a walled-garden. Allowing the subscription to expire places an account in a read-only state, allowing the user to download their passwords and other saved content.&lt;br /&gt;
&lt;br /&gt;
&amp;quot;You can export your 1Pasword information at any time. If you discontinue payment, your account will enter a frozen (read-only) state that still allows you to retrieve and export your information. Your export will be limited to the information you saved in 1Password. We can’t guarantee that vault permissions, group structures, and other details about relationships between people and information are included.&amp;quot;&amp;lt;ref name=&amp;quot;privacy&amp;quot;&amp;gt;{{Cite web|url=https://support.1password.com/1password-privacy/|title=About 1Password and your privacy|access-date=2025-09-05|date=2025-02-27|work=1Password Support}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Privacy===&lt;br /&gt;
Extracted directly from the privacy policy,&lt;br /&gt;
&lt;br /&gt;
&amp;quot;We’ll never lock you out of your 1Password account, but we’re unable to decrypt it for you.&amp;quot;&amp;lt;ref name=&amp;quot;privacy&amp;quot; /&amp;gt; (implies anything in it is hidden from the company, which, considering this is a password manager, is a very good thing)&lt;br /&gt;
&lt;br /&gt;
&amp;quot;You have the right to know what we know. You have the right to know what we know about you and see how we handle that information. If you make such a request, you’ll receive a screenshot of what we can see about you in our systems. To protect customer privacy, these requests will be carefully authenticated beyond demonstrating control of the registered email address.&amp;quot; (expect to be any identifying information you have to provide in order to use the service such as email, name, address, payment information)&lt;br /&gt;
&lt;br /&gt;
===User security===&lt;br /&gt;
Users should be aware that using password manager browser extensions increases their vulnerability to clickjacking&amp;lt;ref&amp;gt;{{Cite web|url=https://www.bleepingcomputer.com/news/security/major-password-managers-can-leak-logins-in-clickjacking-attacks/|title=Major password managers can leak logins in clickjacking attacks|work=Bleeping Computer|date=2025-08-20|first=Bill|last=Toulas|access-date=2025-09-05}}&amp;lt;/ref&amp;gt;  where the autofill feature of password managers is abused to trick the password manager into leaking user credentials and other sensitive details.&amp;lt;ref&amp;gt;{{Cite web|url=https://cybernews.com/security/password-managers-autofill-credentials-for-attackers/|title=Major flaw affecting password managers: they autofill credentials for attackers|first=Ernestas|last=Naprys|date=2025-08-21|work=Cybernews|access-date=2025-09-05}}&amp;lt;/ref&amp;gt; It is always best practice to copy in these elements on trusted pages manually.&lt;br /&gt;
&lt;br /&gt;
===Business model===&lt;br /&gt;
Subscription based, has a strong emphasis on enterprise credential management, especially for secret management for software development (e.g., SSH keys, authentication tokens, API keys, etc.).&lt;br /&gt;
&lt;br /&gt;
===Market control===&lt;br /&gt;
{{Incomplete section}}&lt;br /&gt;
1Password claims on its website that it is industry leading. &lt;br /&gt;
&lt;br /&gt;
Password managers are pretty much a dime a dozen these days, highly competitive. &lt;br /&gt;
&lt;br /&gt;
==Incidents==&lt;br /&gt;
This is a list of all consumer protection incidents related to this product. Any incidents not mentioned here can be found in the [[:Category:{{PAGENAME}}|{{PAGENAME}} category]].&lt;br /&gt;
&lt;br /&gt;
===1Password Okta instance breach, discovered (&#039;&#039;29 Sept 2023&#039;&#039;)===&lt;br /&gt;
1Password published a blog post disclosing an internal investigation of the breach.&amp;lt;ref&amp;gt;{{Cite web|url=https://blog.1password.com/okta-incident/|title=Okta Support System incident and 1Password|date=2023-10-23|first=Pedro|last=Canahuati|work=1Password Blog|access-date=2025-09-05}}&amp;lt;/ref&amp;gt; It largely appears one of the attackers actions triggered an email to a member of the IT team who acted swiftly to contain the breach. The company reported user data was not exfiltrated or decrypted.&lt;br /&gt;
&amp;lt;gallery&amp;gt;&lt;br /&gt;
File:Okta-incident-report.pdf|PDF document report&lt;br /&gt;
&amp;lt;/gallery&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==See also==&lt;br /&gt;
*[[Bitwarden]]&lt;br /&gt;
*[[LastPass]]&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
{{reflist}}&lt;br /&gt;
&lt;br /&gt;
[[Category:{{PAGENAME}}]]&lt;/div&gt;</summary>
		<author><name>Jake01756</name></author>
	</entry>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=1Password&amp;diff=24122</id>
		<title>1Password</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=1Password&amp;diff=24122"/>
		<updated>2025-09-08T06:25:44Z</updated>

		<summary type="html">&lt;p&gt;Jake01756: /* Privacy */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Incomplete}}&lt;br /&gt;
{{ProductCargo&lt;br /&gt;
|Company=Agilebits&lt;br /&gt;
|ProductLine=1Password&lt;br /&gt;
|InProduction=Yes&lt;br /&gt;
|ArticleType=Product&lt;br /&gt;
|Category=Software,Password Managers&lt;br /&gt;
|Website=https://1password.com/&lt;br /&gt;
|Description=1Password is a secure password manager that stores and encrypts passwords, login details, and other sensitive information in a digital vault&lt;br /&gt;
|Logo=1Password-logo.png|ReleaseYear=2006}}1Password is a multi-platform subscription-based [[Password manager]] developed by [[AgileBits Inc]]. One of the unique elements of this password manager is the combination of a master password with a second secret key generated on-device (i.e., not in the cloud). Unlocking a user&#039;s vault therefore requires &#039;&#039;&#039;both&#039;&#039;&#039; pieces of information to decrypt and access. Conventional [[Two factor authentication]] using either software tokens or hardware-based tokens (e.g., [[Yubikey]], [[Google Titan]]) can be added to further secure a vault. 1Password is not open source and not self-hostable.&lt;br /&gt;
&lt;br /&gt;
Beyond passwords, 1Password is capable of storing myriad site credentials including one-time codes, emails / user names, and additional notes. A user can also choose a preferred single sign-on service to login.&lt;br /&gt;
&lt;br /&gt;
==Consumer impact summary==&lt;br /&gt;
&lt;br /&gt;
===Freedom===&lt;br /&gt;
Users can import existing passwords from other managers and export passwords and other content in formats suitable for importing into other managers. 1Password is not a walled-garden. Allowing the subscription to expire places an account in a read-only state, allowing the user to download their passwords and other saved content.&lt;br /&gt;
&lt;br /&gt;
&amp;quot;You can export your 1Pasword information at any time. If you discontinue payment, your account will enter a frozen (read-only) state that still allows you to retrieve and export your information. Your export will be limited to the information you saved in 1Password. We can’t guarantee that vault permissions, group structures, and other details about relationships between people and information are included.&amp;quot;&amp;lt;ref name=&amp;quot;privacy&amp;quot;&amp;gt;{{Cite web|url=https://support.1password.com/1password-privacy/|title=About 1Password and your privacy|access-date=2025-09-05|date=2025-02-27|work=1Password Support}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Privacy===&lt;br /&gt;
Extracted directly from the privacy policy,&lt;br /&gt;
&lt;br /&gt;
&amp;quot;We’ll never lock you out of your 1Password account, but we’re unable to decrypt it for you.&amp;quot;&amp;lt;ref name=&amp;quot;privacy&amp;quot; /&amp;gt; (implies anything in it is hidden from the company, which, considering this is a password manager, is a very good thing)&lt;br /&gt;
&lt;br /&gt;
&amp;quot;You have the right to know what we know. You have the right to know what we know about you and see how we handle that information. If you make such a request, you’ll receive a screenshot of what we can see about you in our systems. To protect customer privacy, these requests will be carefully authenticated beyond demonstrating control of the registered email address.&amp;quot; (expect to be any identifying information you have to provide in order to use the service such as email, name, address, payment information)&lt;br /&gt;
&lt;br /&gt;
===User security===&lt;br /&gt;
Users should be aware that using password manager browser extensions increases their vulnerability to clickjacking&amp;lt;ref&amp;gt;{{Cite web|url=https://www.bleepingcomputer.com/news/security/major-password-managers-can-leak-logins-in-clickjacking-attacks/|title=Major password managers can leak logins in clickjacking attacks|work=Bleeping Computer|date=2025-08-20|first=Bill|last=Toulas|access-date=2025-09-05}}&amp;lt;/ref&amp;gt;  where the autofill feature of password managers is abused to trick the password manager into leaking user credentials and other sensitive details.&amp;lt;ref&amp;gt;{{Cite web|url=https://cybernews.com/security/password-managers-autofill-credentials-for-attackers/|title=Major flaw affecting password managers: they autofill credentials for attackers|first=Ernestas|last=Naprys|date=2025-08-21|work=Cybernews|access-date=2025-09-05}}&amp;lt;/ref&amp;gt; It is always best practice to copy in these elements on trusted pages manually.&lt;br /&gt;
&lt;br /&gt;
===Business model===&lt;br /&gt;
Subscription based, has a strong emphasis on enterprise credential management, especially for secret management for software development (e.g., SSH keys, authentication tokens, API keys, etc.).&lt;br /&gt;
&lt;br /&gt;
===Market control===&lt;br /&gt;
{{Incomplete section}}&lt;br /&gt;
1Password claims on it&#039;s website that it is industry leading. &lt;br /&gt;
&lt;br /&gt;
Password managers are pretty much a dime a dozen these days, highly competitive. &lt;br /&gt;
&lt;br /&gt;
==Incidents==&lt;br /&gt;
This is a list of all consumer protection incidents related to this product. Any incidents not mentioned here can be found in the [[:Category:{{PAGENAME}}|{{PAGENAME}} category]].&lt;br /&gt;
&lt;br /&gt;
===1Password Okta instance breach, discovered (&#039;&#039;29 Sept 2023&#039;&#039;)===&lt;br /&gt;
1Password published a blog post disclosing an internal investigation of the breach.&amp;lt;ref&amp;gt;{{Cite web|url=https://blog.1password.com/okta-incident/|title=Okta Support System incident and 1Password|date=2023-10-23|first=Pedro|last=Canahuati|work=1Password Blog|access-date=2025-09-05}}&amp;lt;/ref&amp;gt; It largely appears one of the attackers actions triggered an email to a member of the IT team who acted swiftly to contain the breach. The company reported user data was not exfiltrated or decrypted.&lt;br /&gt;
&amp;lt;gallery&amp;gt;&lt;br /&gt;
File:Okta-incident-report.pdf|PDF document report&lt;br /&gt;
&amp;lt;/gallery&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==See also==&lt;br /&gt;
*[[Bitwarden]]&lt;br /&gt;
*[[LastPass]]&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
{{reflist}}&lt;br /&gt;
&lt;br /&gt;
[[Category:{{PAGENAME}}]]&lt;/div&gt;</summary>
		<author><name>Jake01756</name></author>
	</entry>
</feed>