Copyright

While copying was hard, nobody needed this right. Transcribing a book by hand cost roughly what writing one cost, so there was no money in copying.

The printing press broke that balance. A manuscript that took one person two years could be run off by a print shop at hundreds of copies a day. None of that went to the person who wrote it, and complaining produced nothing to point at, because the shop had bought the paper and the ink and owned the machine.

The rule that emerged tied the right to copy back to the person who made the thing. The idea worth holding onto is that the right attached to the content rather than to the object. Buying a book gets you that stack of paper; it does not get you the right to print what's written inside it.

Digital distribution brought the same problem back in a sharper form, because the cost of copying didn't merely fall below press-era levels — it effectively disappeared. Software, design files, photographs and text all sitting under one rule is where that ended up.

The right exists from the moment of creation. There is nowhere to apply and nothing to be examined, so saving a document or committing code is already enough. Registration systems do exist, but they don't create the right; they make it easier to prove in a dispute. Four points explain most of how it behaves.

1. It protects expression, not ideas. Copying someone's code verbatim infringes. Looking at what a feature does and writing your own version does not. Protecting a method or a function itself means going to patents, or keeping it unpublished and managing it as a trade secret.
2. It's a bundle, not a single right. Copying, distributing, putting something online, and adapting it through translation or derivative work are each separate. That's why licensing one image depends on whether it runs on the web only or in print too — different permissions.
3. It expires. In most countries, including Korea, protection lasts until 70 years after the creator's death, after which the work is free for anyone to use.
4. Exceptions exist. Quoting as much as criticism or news reporting requires is written into the law. The scope is narrower than people assume and contested at the edges, so calling an image lifted into a marketing asset a quotation rarely survives contact with a lawyer.

For companies a fifth point matters most in practice: who holds the right. The default is the creator, but work an employee produces as part of the job is assigned to the employer by statute. The gap is everyone who is not an employee. Anything an agency or a freelancer makes stays with them unless the contract says the rights transfer.

Ownership is the question that comes up most. If a logo came from an agency, whether the contract included an assignment clause decides whether you can modify it later. Without one, you can use the files you received, but recoloring or reshaping the mark becomes something you have to ask permission for. The same gap opens with freelance illustrators, contract writers, and anyone who filmed a product video for you.

On the code side, this right is the foundation licenses stand on. An open source license is the copyright holder granting permission to copy under conditions, and copyleft has teeth for exactly the same reason. Breaking the conditions isn't a contract dispute — it's infringement, because the permission to copy was conditional in the first place.

In marketing, images, fonts and audio catch teams constantly. A font distributed free is often free for personal use and paid for commercial use, and a photograph found through a search engine can't be used just because you name the source. Reconstructing this after the fact is painful, so recording where each asset came from and on what terms, at the moment it's added, saves the cleanup. A spreadsheet with asset, source, license and expiry columns is enough, and it takes a minute per item while the memory is fresh.

More recently the question has extended into training data rights. When the text and images used to train a model are themselves protected, whether that use falls inside permitted scope is being argued, and the answer currently differs by country.

"Did you check the commercial license on that font? Free to download isn't free to ship."

Getting something at no cost and being allowed to put it in a product are different facts.

"Can you check whether the agency contract has an assignment clause?"

Whether the company can freely modify the delivered work later depends on it.

"We didn't write that line, it came from a blog, so we can't use it as is."

Naming the source is not a substitute for permission.

When Pagedeck rebranded, the logo came from an outside studio. A year later Noa went to simplify the mark for an app icon, pulled up the contract, and found a clause granting use but nothing transferring the rights. Changing the shape was work that needed fresh permission.

The studio agreed at no extra cost, but waiting on the reply pushed the app release back two weeks. The cost was never the license — it was the two weeks. After that Pagedeck put an assignment clause into its standard design contract template. Around the same time Ravi built a list of every image and font in use and checked the terms on each one.

The most common belief is that naming the source makes use acceptable. School taught everyone to cite sources on assignments, and the habit transfers cleanly enough to feel right. But attribution satisfies a different requirement — naming the creator — and whether you may copy at all is a separate permission. If an ad asset built around someone's blog image becomes a problem, having credited them is not a defense.

The other frequent mistake is assuming the right requires a notice or a registration. The symbol at the bottom of books and websites is familiar enough that it looks like the source of the right. In fact the right attached at creation and the notice only announces it. Treat unmarked material as free to take, and the absence of a mark will do nothing for you afterward.