Referencing FIG. 1, the infrastructure 100 includes components to route traffic requests related to the user accessing various URLs from the RDB 109. For example, in some implementations of the infrastructure 100, a proxy server 115 can be installed on the host 118 to receive traffic requests, or URL access requests from the RDB 109. The remote device 112 can be set up with proxy settings 130, which directs the RDB 109 to proxy its traffic to the IP address and port of the host 118. The proxy server 115 receives and forwards the requests to a repeater 110. In some implementations, the repeater 110 is also a type of proxy server. Proxy servers act as intermediaries between request and response, and can provide a variety of functionality, including providing privacy, security, filtering, firewall, speed efficiency, caching, and other functionality. Proxy servers differ in how much exposure they have into the substance of the data they are routing. For example, some proxies implementing SSL inspection have a complete view into the content of the traffic they route, including passwords, and other sensitive data. Other proxy servers, for example, some using the TCP/IP model, may have no access to the payload in the data packets being transmitted, other than some routing information. In a preferred embodiment, both the proxy server 115 and the repeater 110 do not have access to payload or substantive data being transmitted, and only operate on the addresses contained in the data they transmit.