Yeah, you try that. It's a single format that you need to convert yourself to produce woffs, eots and other variations needed for the actual self-hosted deployment, and no matter how you convert, they will never come out looking the same as Google's native versions. This "go ahead, host it yourself" is disingenious and manipulative at best.
http://themes.googleusercontent.com/static/fonts/droidsans/v...
http://themes.googleusercontent.com/static/fonts/droidsans/v...
http://themes.googleusercontent.com/static/fonts/droidsans/v...
Rocket science or not, the bottom line is that these are not available from Google Fonts. You are expected to either use hosted version or muddle through the conversion process.
@font-face generators are dime a dozen. The issue is that they generate kits of subpar quality for Google fonts.
https://developers.google.com/fonts/faq#Download_Fonts
> You can download the fonts to use them for your mockups, in your documents or to host them on your own server.
Google Fonts exists because it's in Google's best interest if everything is online. Having freely available high-quality fonts is a [small] way to help move that along.
Update: No cookies are set by Google either, they're just doing analytics by the user agent sent. The actual font files have 1 year expires headers on them as well, so cookies would be of limited use.