Yes, many of our clients utilize AudioEye on applications within a company Intranet and/or behind a login.
For content behind a login which receives manual testing and remediation services, AudioEye requires a "dummy" account that encompasses all available functionality in order for our team to conduct the testing and write the manual remediation code.
Since AudioEye runs in a user's already-authenticated browser session, most web-based applications do not require whitelisting for automated testing and remediation to work properly. However, internal applications running on a company's Intranet may need to whitelist AudioEye's assets for proper functionality. For best results, we recommend whitelisting AudioEye domains as *.audioeye.com. If domain whitelisting will not work for your organization, please reach out to your AudioEye point of contact or firstname.lastname@example.org for assistance.