Why do I keep getting signed out of ITVX on the website?

Modified on Fri, 22 May at 1:50 PM

If you find yourself having to regularly sign-in again when revisiting ITVX, it’s usually down to how your internet browser is handling cookies.

Cookies are tiny files that remember who you are so you don't have to log in repeatedly. If these cookies are being deleted, ITVX forgets you're logged in.

Here are the three most common reasons this happens and how to fix it:

1. You are using Private or Incognito browsing

When you use a Private or Incognito window, your browser is specifically designed not to remember you. As soon as you close that tab or window, your ITVX session is wiped.

The Fix: Switch back to a normal, standard browsing window when watching ITVX.

2. Your browser is set to "Auto-Clear" cookies

Some browsers have a setting enabled that automatically dumps all cookies every time you close the app or shut down your device.

To stop your browser from doing this, follow the steps below for your specific browser:

Google Chrome: Go to Settings > Privacy and security > Site Settings > On-device site data and make sure you have "Allow sites to save data on your device" ticked.
Mozilla Firefox: Go to Settings > Privacy and security > Cookies and Site Data and make sure you do not have "Clear cookies and site data when Firefox is closed" checked.
Microsoft Edge: Go to Settings > Privacy, search, and services > Choose what to clear every time you close the browser and ensure you do not have "Cookies and other site data" checked.

3. You are manually clearing your history/cache

If you regularly clear your browser's history or use cleaning software to keep your device tidy, it will log you out of ITVX alongside everything else.

The Fix: When clearing your history manually, look for an option to uncheck "Cookies and other site data" so you stay logged into your favourite websites.

Still having trouble?

If you have checked these settings and are still being logged out, ensure your browser is fully updated, or try using a different browser entirely (like switching from Safari to Google Chrome) to see if the issue persists.