Why do I have to upload private content to the BrowserLab servers? Why can't BrowserLab run locally on my machine?
The concern, which the BrowserLab team understands, is generally for one of three reasons: intellectual property concerns, data privacy concerns, or speed.
Adobe runs licensed copies of various operating systems, browsers, and other types of software configured specifically to request and deliver screen shots. Due to licensing concerns related to this software, Adobe can't redistribute BrowserLab at this time.
To come up with instructions that would allow Adobe's users to copy the BrowserLab server architecture would be a daunting task. It would require constant, error-prone updates and reconfiguration by Adobe's users. Adobe doesn't feel that creating a local version of BrowserLab is a workable answer to those concerns.
As things stand, users must upload content to the BrowserLab servers to generate screen shots, including screen shots of private or local content.
Adobe is committed to keeping its users' content and data private. Here are some of the security measures that Adobe currently uses:
- The data uploaded to BrowserLab is sent from the user's computer directly to Adobe's servers over HTTPS.
- The content and data are stored in a temporary private directory on Adobe's servers. It's only accessible to the screen shot servers and only for that specific screen shot request.
- The content and data are stored only long enough so that Adobe can generate screen shots. After screen shots have been generated or canceled, Adobe permanently deletes the directory and all of its contents.
Keywords:
protext safe security; cpsid_90057
Twitter™ and Facebook posts are not covered under the terms of Creative Commons.
