This is an unusual behavior. Most likely, something is wrong locally. Please reach us at support@browsec.com, and we'll be happy to make Browsec work as it should.