Why we’re introducing audioeye-services.com

Accessibility tools and ad trackers have nothing in common. But when it comes to privacy reviews and blocklists, they can end up in the same bucket. For organizations operating under GDPR or strict cookie policies, that's a problem worth solving before it becomes a real one. Here's what we did about it.

What’s changing

We’re moving AudioEye’s accessibility scripts to a new dedicated domain: audioeye-services.com. This domain is completely separate from our corporate and marketing sites, and it’s designed to be entirely cookie-free.

Why it matters

AudioEye's client-facing scripts are privacy-compliant, with no cookies and no tracking. But being served from audioeye.com meant privacy tools could easily group us alongside third-party scripts that aren't. For customers in the EU or those with strict privacy requirements, that created real concerns around compliance and third-party cookie policies. Privacy blocklists and browser tracking protection features don't distinguish by intent — and that's a compliance conversation customers shouldn't have to have.

The new domain eliminates that ambiguity entirely.

• No cookie crossover. Cookies are domain-scoped, so nothing from audioeye.com can be transmitted when scripts are served from audioeye-services.com.

• Cleaner classification. Customers can confidently categorize AudioEye as essential accessibility infrastructure, separate from any marketing or analytics tools.

• Blocklist protection. The dedicated services domain won’t be flagged by privacy tools that target advertising or tracking domains.

A note on cookies

audioeye-services.com is designed to be completely cookie-free. If you ever detect cookies being set from this domain, please reach out to support@audioeye.com and we'll investigate.

Your accessibility tool shouldn't create compliance questions. Now it won't.

Questions about what this means for your site? Reach out to support@audioeye.com.