Android browser privacy settings can change after an app update, a device migration, or a switch to a different browser. When that happens, websites may stop keeping you signed in, forget preferences, clear shopping carts, or show cookie notices again. A short cookie settings checklist helps you find what changed and restore normal website behaviour without turning off privacy protections for every site.
Cookies are small files a website uses to keep a session active, remember settings, and store basic site data. On Android, cookie behaviour is also affected by tracking protection, site data rules, private browsing, and per-site exceptions. That is why the same website can work differently after a browser change even when your login details are correct.
Table of Contents
Start with the recent change
Before changing settings, note what changed most recently. The most common triggers are a browser update, moving to a new Android device, changing the default browser, or resetting privacy settings during setup. This helps you focus on the browser that now opens the site, not the one you used before.
If the issue started only on one trusted site, check that site in the same browser each time during testing. If the issue affects many sites, the cause is more likely to be a browser-wide privacy setting.
Review core cookie permissions
Open the Android browser you are currently using for the affected site.
Go to the browser’s privacy or site settings area.
Check whether cookies are allowed.
If third-party cookies have a separate control, review that setting as well.
If the browser offers a stricter tracking mode, note whether it may limit some cookie-related functions.
Logins, shopping carts, account tools, and saved preferences often depend on cookies. If cookies are blocked, a site may load but not keep your session. If only third-party cookies are limited, some embedded sign-in or consent tools may behave differently while the main site still loads.
Check site data retention and auto-delete rules
Some Android browsers remove cookies and site data automatically when you close the app, close tabs, or after a set period. Others clear site data as part of stronger privacy routines. After an update or browser switch, these rules may be enabled again.
Look for settings related to clearing browsing data on exit.
Check whether the browser deletes cookies automatically after inactivity.
Review any setting that removes site data for unused sites.
Confirm that you are not using a cleanup tool that clears browser data in the background.
If a site works during one session but forgets you later, an auto-delete rule is a common cause. This is expected behaviour when cleanup settings are active.
Compare tracking protection with website function
Tracking protection can block cross-site storage, limit site scripts, or restrict cookie use in some situations. This improves privacy, but it can also affect logins, account areas, consent tools, or saved language settings on some websites.
Review the browser’s tracking or privacy level and check whether it was reset to a stricter mode. If the problem affects one trusted site, use a per-site exception if the browser allows it. This keeps privacy protections active elsewhere while letting that site function normally.
Verify per-site exceptions and content settings
Many Android browsers let you allow or block cookies for one site without changing the global setting. This is often the best option when only one website is affected.
Open the trusted site in the browser.
Open the site-specific settings or permissions panel.
Check whether that site has a custom rule for cookies or site data.
Remove an old block rule or add an allow rule if needed.
Reload the site and test the affected action again.
This approach is especially useful if logins, shopping carts, or account tools stop working on one website but other sites behave normally. For more detail on this method, see How to allow cookies for one site on Android browsers without weakening privacy everywhere else.
Make sure you are not testing in private browsing
Incognito mode on Android changes how cookies and site data are handled during the session. It can be useful for testing, but it does not behave like normal browsing. Session data is treated as temporary, so websites may not stay signed in or remember choices after the private session ends.
If a site only fails in Incognito mode, that may be normal for that browser. Test again in a regular tab before changing broader privacy settings. For more detail, see Incognito mode on Android browsers and cookies: what is actually saved, deleted, or still visible.
Use a simple restore test
After each change, test one clear action on the same site. Good examples are signing in, adding one item to a cart, dismissing a cookie notice, or changing a language setting. Then close and reopen the browser and test again. This shows whether the browser is now keeping the cookie and site data as expected.
If the site starts working after a single setting change, stop there. A narrow fix is usually better than lowering privacy settings across the whole browser.
When the issue is still not clear
If websites behave differently after an update or browser switch, the cause is often one of these: cookies are blocked, site data is cleared automatically, tracking protection is stricter than before, or a site-specific exception is in place. Review those controls first and test in a regular tab.
If the problem is limited to a cookie banner on mobile, site owners may also need to review how the banner behaves on Android. See Cookie consent pop-ups on Android: a site owner checklist to reduce mobile friction without breaking compliance.