Google's SEO api algorithm leaked

[gws]

For anybody interested or bored out of their minds Google accidentally published its seo api details.
https://hexdocs.pm/google_api_content_w ... rence.html

[smartersign]

I'm both.. thrilling read! The funny thing about accidentally posting to the GoogleAPI GitHub is that, even though these were sensitive internal documents, Google technically put them out there under an Apache 2.0 license. So, anyone who found them got a "perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license," which basically means they're now freely available online.

[Tim Julius]

I'm both.. thrilling read! The funny thing about accidentally posting to the GoogleAPI GitHub is that, even though these were sensitive internal documents, Google technically put them out there under an Apache 2.0 license. So, anyone who found them got a "perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license," which basically means they're now freely available online.

How does accidentally posting sensitive internal documents to GoogleAPI GitHub under an Apache 2.0 license affect their availability and usage rights? Does this mean that anyone who finds them can legally access and use them?