Skip to content
English
  • There are no suggestions because the search field is empty.

AudioEye and Cookie Blocking Tools

AudioEye has eliminated all cookies and now uses local storage instead to save user accessibility preferences, interface customizations, and personalized settings. All tracking IDs were removed, so the service only stores what users specifically choose for accessibility needs.  

Privacy tools such as cookie blockers, often treat local storage the same as cookies and may block third-party scripts by default. AudioEye's domain can get caught in these broad blocking rules even though it no longer uses cookies.

The solution is to mark AudioEye as a "necessary/essential service" in privacy tools and consent management platforms. This classification is appropriate because AudioEye provides accessibility compliance support, stores only user-requested preferences, performs no tracking, and offers essential functionality for users with disabilities.

By categorizing AudioEye as necessary ensures continued accessibility compliance, maintains functionality for users with disabilities, and keeps the service working regardless of privacy tool settings while still respecting user privacy preferences.

The main takeaway is that while AudioEye has become more privacy-friendly by removing cookies, it still needs to be specifically allowed in privacy tools to function properly for accessibility purposes.