It is actually even safer.
Conventional HSTS only takes effect after the first request to the site, and until the user clears his browser's cache (each browser may handle this differently but I assume clearing all browsing data should also delete the HSTS list), and I believe HSTS does not persist between non-private and private browsing due to privacy concerns.
"Preloaded" HSTS works by telling everyone that you wish your HSTS header to be shipped with browser updates, so that browsers know your site should only be accesses using HTTPS even if your user never visited your site before. It has some implications of course, mainly not being able to opt-out (let's say you go back to HTTP, not only will your existing users not be able to connect because they saw your HSTS header, but new users won't either because the HSTS header is bundled with their browser).
I believe you also have to submit the site manually using Google's form as I don't think they crawl the internet looking for preload headers, at least not yet.