Google to restrict access to satellite imagery in South Korea over security concerns
According to statements from the tech giant, it plans to introduce enhanced protective measures, including the blurring of critical sites on platforms such as Google Maps and Google Earth. These steps, as stated by the company's vice president for government affairs and public policy, Cris Turner, are part of Google’s response to official demands.
The company emphasized that satellite imagery across the globe is commercially available and can be purchased by anyone. “We have already confirmed our commitment with the (South) Korean government to blur satellite images as required,” the statement read. Google also noted it is looking into the possibility of sourcing images through authorized South Korean providers when appropriate.
This announcement precedes an upcoming government panel meeting scheduled for Friday, during which officials are expected to decide on Google's request to export South Korea’s high-resolution 1:5,000-scale mapping data.
The tech firm submitted its application in February, seeking permission to transfer this mapping data to servers located outside the country. However, the proposal has sparked apprehension, with critics warning that such data transfers could expose sensitive military installations and other secure areas.
Legal Disclaimer:
MENAFN provides the
information “as is” without warranty of any kind. We do not accept
any responsibility or liability for the accuracy, content, images,
videos, licenses, completeness, legality, or reliability of the information
contained in this article. If you have any complaints or copyright
issues related to this article, kindly contact the provider above.
Legal Disclaimer:
EIN Presswire provides this news content "as is" without warranty of any kind. We do not accept any responsibility or liability for the accuracy, content, images, videos, licenses, completeness, legality, or reliability of the information contained in this article. If you have any complaints or copyright issues related to this article, kindly contact the author above.
