Allowing cookies for one site on Android is often needed when logins, shopping carts, or account tools stop working on a trusted website. Cookies are small files that help a site keep you signed in, remember settings, and store session data. The goal is to make that one site work again while keeping stricter privacy settings for other websites.
On Android, this depends on the browser you use. Some browsers let you manage site permissions in a more detailed way, while others only offer broader cookie settings. In many cases, the safest approach is to keep your normal privacy settings, then use a site-specific exception if the browser supports it, or use temporary steps that affect only the current browsing session.
Table of Contents
How cookie controls work on Android
A browser can block cookies in a few different ways. It may block all cookies, block third-party cookies, clear cookies when you close the browser, or prevent sites from saving session data in private browsing mode. Any of these can stop a website from logging you in or keeping items in a cart.
For most trusted websites, first-party cookies are the key setting. These are cookies set by the site you are visiting. Third-party cookies usually come from embedded services such as payment tools, login widgets, or analytics scripts. If a website uses an external login or checkout service, blocking third-party cookies may still affect it even if the main site is trusted.
Best option if your browser supports site-specific exceptions
If your Android browser offers per-site cookie or site data controls, use that option first. This keeps your stricter defaults in place for other websites.
- Open the trusted website in your browser.
- Open the browser menu.
- Look for site settings, permissions, privacy, or page info for the current site.
- Check whether the browser lets you allow cookies, site data, or storage for that site only.
- Save the setting if needed.
- Reload the page.
- Sign in again or repeat the action that was failing.
If the site uses an external sign-in or payment tool, you may also need to allow related content that the browser treats as third-party storage for that session.
What to do in Chrome on Android
Chrome on Android usually focuses on broader cookie and privacy settings rather than full per-site cookie exceptions. If a trusted website is not working, check the browser privacy settings first and confirm that cookies are not fully blocked.
- Open Chrome on Android.
- Open the menu.
- Go to Settings.
- Open Privacy and security or the cookie-related section shown in your version.
- Check whether cookies are fully blocked.
- If third-party cookie controls are available, keep the stricter setting if the site does not need external login or checkout tools.
- Return to the trusted site and test it again.
If the site still fails and depends on an embedded login, payment step, or account widget, a broader browser setting may be the only available path in Chrome on Android. If you use that step, test the site, finish the task, and then return the browser to your preferred privacy setting.
What to do in Firefox and other Android browsers
Firefox and some privacy-focused Android browsers may use tracking protection, strict site isolation, or automatic cookie clearing. These features can affect one website without blocking cookies everywhere in the same way.
- Open the trusted site.
- Open the browser menu.
- Check for tracking protection, shields, privacy protection, or site protections for the current page.
- Turn off that protection for the trusted site only if the browser allows it.
- Reload the page.
- Try the login, cart, or account action again.
This method is often better than lowering privacy across the whole browser. It changes behaviour only for the website you trust, if the browser supports that level of control.
Useful limits to know before you change settings
Not every Android browser supports cookie exceptions for one site. Some only let you choose between broader cookie rules, such as allowing all cookies or blocking third-party cookies. Private browsing modes also have limits. A website may still fail there because session data is isolated or deleted when the session ends.
A cookie problem may also come from existing saved data. If a site still does not work after allowing the needed storage, clear cookies and site data for that website only if your browser supports it, then sign in again. This can help when old session data is broken.
How to check that the site works and privacy stays tighter elsewhere
After changing the setting, confirm both parts of the goal: the trusted site works, and other sites still follow your normal privacy rules.
- Reload the trusted website.
- Sign in and move to a second page to see whether the session stays active.
- Add an item to the cart if the site has shopping features.
- Open account tools or a checkout step that failed before.
- Visit a different website and confirm your usual privacy settings are still active there.
If the trusted site now keeps you logged in, remembers the cart, or loads account tools normally, cookies are likely working as needed. If only one browser still fails, test the same site in another Android browser. That can help show whether the issue comes from browser privacy controls rather than the website itself.
When a website still does not work
If the site still shows a cookie-related error, the problem may not be basic cookie blocking alone. Some websites depend on related storage, embedded login services, or browser features tied to privacy protection. In that case, check whether the site provides a cookie notice or login guidance, or contact the website owner for the exact domains or browser settings their sign-in flow needs.
If the issue affects a WordPress website you manage, a related help article may be useful: How to Fix the “Cookies Have Been Blocked” Error.