Three reasons:
First, being certified as a Unix says nothing about your licensing, just your compliance to the established standards for being Unix.
Second, because being Unix has nothing to do with your licensing, and everything to do with your being like Unix, an originally proprietary system, and one with a long legacy.
Finally, don't mistake licensing: BSD code can subsequently be closed, and there is no duty of disclosure or source availability. The BSD license is more free on one axis, and less free on another, because of that.
If you choose to make an operating system based on the Linux kernel then you have to distribute it for free under the GPL License,
That's not quite true. You can make an OS based on the Linux kernel with no constraint whatsoever, as long as you keep it for yourself. If you distribute an OS based on the Linux kernel, then you have to distribute the source code of the kernel (or any other part where you've used code from the Linux kernel). You don't have to distribute the rest. For example, most Linux distributions include some proprietary software; the GNU GPL doesn't constrain software that is distributed together with software covered by the GPL.
but if you choose to make an OS based on the Unix kernel
There is no such thing as “the Unix kernel” — not anymore. There are many Unix kernels, of which the Linux kernel is one. Some of them are based on the original Unix from Bell Labs (Solaris, HP-UX), others are not (*BSD, Linux, MINIX).
(example: an OS based on FreeBSD) do you have permission to make it closed-source and to take copyrights making it a proprietary software distributing it non-free?
FreeBSD code comes under a BSD license which is extremely liberal and includes the right to distribute proprietary software based on the BSD-licensed software. FreeBSD is not derived from the original Unix product, which was a commercial product. (BSD was originally companion software for a commercial Unix, and eventually they rewrote all the parts under a free license.)
So if somebody chose to make an OS based on FreeBSD can they sell it as their own modified version, taking copyrights or something like that? This question arose because I know that Mac OS X is based on FreeBSD and it should have used FreeBSD licenses, and OS X is a non-free, closed-source proprietary software.
Yes, the FreeBSD license allows that.
So, can you do that with Unix? Or does Apple have some sort of "agreement"?
You can't do that with the original Unix product, but that hasn't existed as a product for a long time (and there never really was a single Unix product except at the very beginning). You can do that with the Linux kernel (and with the GNU userland, too), as long as you distribute the sources for the GPL parts that you distribute (including your modifications if you modified the sources); you can keep the source of independent components (separate programs and libraries) for yourself. You can do that with FreeBSD, with basically no constraint.
Best Answer
If you live in a country that has ratified the Berne Convention (you probably do), then anything that can be copyrighted is copyrighted, whether or not it is mentioned explicitly. An explicit mention of copyright can help settle disputes and can lead to higher damages in case of violations, but it is not a requirement to claim the protection of copyright.
If you find something on the Internet, there may be a presumption that you're allowed to download it, use it, and possibly even modify it for your private use (that last one depends on the jurisdiction). This is a presumption, not an evident right. If you find code on the author's web page with a mention that you can download it and use it, it's a safe presumption. If you find it on a file sharing website next to other content that is clearly not redistributed legally, then this is not a safe presumption.
In no case can you redistribute the code or a modified version of it without an explicit authorization from the author or rights holder.
If you know who the author is, contact them and ask them to put an explicit license on the work. That's what free software distributions do — and if they can't find the author, they don't distribute the code.