Intellectual Property Lawyers for Sparks, Nevada

Hello, I wanted to express my interest in helping you understand your trademark rights and the trademark transfer proposal you received. As brief background, I am a US-licensed trademark attorney and have helped clients in similar situations buy, sell, and otherwise transfer trademark rights through transfer agreements. I can also help you prepare and file a federal trademark registration to protect your unique brand name and logo throughout the US. I'd be glad to set up a brief call to learn more about your business and see how I can help. Thanks for your consideration. Best, Roman Vayner (c) 414.628.9099 (e) rvayner@vaynerlegal.com www.vaynerlegal.com VaynerLegal, LLC

Whether you need a Work For Hire Agreement really depends on the project and what both sides are trying to get out of it. You’re not automatically required to sign one, but saying yes or no to that clause can completely change who owns the work and what rights you’ll have moving forward. Just because a client calls something “work for hire” in a contract doesn’t mean it actually qualifies under the law, especially when it comes to freelance design work. Here’s the thing. Under U.S. copyright law, “work made for hire” is a specific exception to the general rule that the creator owns the work. For a freelance project to qualify, two conditions have to be met. First, both parties need to sign a written agreement that says the work is considered “made for hire.” Second, the type of work has to fall into one of nine defined categories under 17 U.S.C. § 101. These include things like contributions to collective works, audiovisual pieces, instructional texts, or compilations. The list is pretty narrow. Standard marketing materials, logos, brochures, or campaign graphics usually don’t make the cut. Courts take a strict approach here, so just checking a box in a contract doesn’t magically make it enforceable. If your project doesn’t meet both requirements, labeling it “work for hire” doesn’t hold legal weight. In that case, the default is that you, the designer, own the copyright unless there’s a separate written agreement transferring it to the client. That leads us to ownership. If there’s no valid Work For Hire clause and no assignment of rights, you retain full copyright. That gives you control over how the work is used beyond whatever license you’ve granted. So if you created a logo and the contract only licenses it for digital use, the client can’t later slap it on T-shirts or license it to a partner without getting your permission first. But if there is a valid Work For Hire clause or an explicit copyright assignment, then the client becomes the legal owner. That means they can use it, change it, resell it, or do whatever they want with it, without needing to pay you again or ask for further approval. You’d have no say over how the work is used, and unless the agreement gives you permission, you wouldn’t even be able to include it in your portfolio. If you want more flexibility, there are alternatives. You can structure the deal with a copyright assignment that still reserves certain rights for you. For example, you could keep the right to show the work in your portfolio or limit resale to direct competitors. Or you could stick with licensing. An exclusive license gives the client broad rights but you still own the work. A non-exclusive license is more limited and usually makes sense for templates or assets used with multiple clients. Portfolio rights, by the way, are often negotiable. Even in exclusive arrangements, you can add a clause that lets you show the work on your website, social profiles, or print materials. Just make sure it’s clearly spelled out. Some corporate clients won’t allow it at all unless it’s written into the agreement. From a practical standpoint, your decision should take into account how much you’re getting paid, how the work will be used, and whether you want to reuse or showcase it later. If you’re giving up all rights, price accordingly. Clients pushing for Work For Hire terms often just want clean, uncomplicated ownership, especially for branding or long-term use. But that doesn’t mean you can’t negotiate. You might agree to transfer ownership only after full payment is received. You might keep the right to use rejected drafts. You might even allow Work For Hire treatment for the final deliverables but retain some creative rights behind the scenes. Also, keep an eye out for boilerplate clauses. Some clients include Work For Hire language by default, not realizing their project doesn’t meet the legal standard. Just because it’s in the contract doesn’t make it enforceable. If the work doesn’t meet the criteria, the clause won’t hold unless there’s a separate valid assignment of rights. When in doubt, it’s smart to run the agreement by an attorney who understands copyright law and freelance creative work. Contracts Counsel connects you with attorneys who handle exactly this kind of issue.

You will need a design patent

A business has multiple options for protecting its intellectual property when working with an independent contractor. For a few examples: 1. A "work made for hire" agreement or clause can establish that the business is the owner of intellectual property that the independent contractor creates. 2. A confidentiality or non-disclosure agreement or clause can require the independent contractor to maintain the confidentiality (and limit or prohibit the independent contractor's disclosure) of the business' confidential or proprietary information. This can include the business' trade secrets (one type of intellectual property), as well as other information that might not rise to the level of trade secrets. 3. A non-competition agreement or clause can prohibit the independent contractor from using, or allowing someone else to use, the business' intellectual property to compete with the business. An independent contractor agreement with intellectual property considerations could implicate various federal and state-specific laws. A knowledgeable North Carolina attorney should be able to help you with an independent contractor agreement that complies with all the applicable laws. To ensure that you have a clear understanding of the intellectual property rights associated with your independent contractor agreement, you should consult with a knowledgeable attorney.

When you're dealing with a technology transfer agreement, it's important to understand that you're not selling your software. You're licensing it. That might seem like a small difference, but it really isn't. Licensing means you're keeping ownership of your intellectual property while letting someone else use it under clearly defined terms. If you're based in Arizona, you've got a legal system that takes written contracts seriously and generally holds both parties to exactly what’s spelled out. So clarity matters—a lot. Be Specific About What's Being Licensed Don't just say you're licensing "software." Spell out what that includes. Are you talking about the source code? Object code? Documentation? APIs? Maybe there's configuration data, algorithms, or some embedded proprietary know-how. Lay it all out. Also, be clear on whether things like updates, bug fixes, or patches are part of the deal or if those require separate terms. Courts in Arizona won't guess what you meant. They’ll go by what’s in the document. Keep Your IP Rights Locked Down Make sure the agreement says you're not transferring ownership. You're only granting the rights specifically listed in the license. Anything not spelled out stays with you. Without that language, you could run into disputes later—especially if the licensee makes improvements. Want to avoid headaches? Clearly state that you own any enhancements unless you decide otherwise. Be Intentional About the License Structure Think through how you’re structuring the license. Is it exclusive, non-exclusive, or somewhere in between? An exclusive license can be powerful, but it limits your flexibility. If you're giving up other opportunities, it's reasonable to ask for higher compensation and make sure the licensee meets clear performance targets. On the flip side, a non-exclusive license gives you room to work with others. You can also narrow the license by geography, industry, or even specific use cases. And don’t forget to address sublicensing. If it’s allowed, include approval rights and make sure you’re compensated fairly if they sublicense to others. Choose a Payment Model That Reflects Value There’s no one-size-fits-all way to get paid. You might go with an upfront fee for past development work, ongoing royalties based on sales, or milestone payments tied to things like product launches or regulatory approval. Each has its pros and cons. Whatever you choose, protect yourself with audit rights. You want access to the licensee’s records if something seems off. That usually means giving them notice, checking things during business hours, and shifting the audit costs if the discrepancies are significant. Protect Your Work from Unintended Use If you’ve used open-source components, you need to disclose that—and understand how those licenses impact what you can legally offer. GPL code, for example, can bring in obligations that might not work with your business model. Copyright registration isn’t mandatory, but it gives you the ability to sue in federal court and can unlock statutory damages and legal fees. If you've developed novel algorithms, you might consider a patent—but only if the innovation meets the standards. It's not always worth the cost, so weigh that carefully. Make Sure the Licensee Does Something with Your Tech If you’re giving someone exclusive rights, set performance expectations. What does commercialization look like to you? It might mean releasing a product by a certain date, hitting minimum sales, or committing to a marketing budget. If those things don’t happen, you need a remedy—like converting the license to non-exclusive or ending the agreement altogether. The goal is to make sure your technology doesn’t sit unused. Clarify Support and Ongoing Involvement Are you expected to provide support? If so, spell out exactly what that means. Documentation, training, installation help, bug fixes, future updates—whatever it is, define it. Also decide whether that’s included in the license or billed separately. If you’re providing source code, put strict confidentiality and usage terms in place. In some cases, a source code escrow might be appropriate, with release conditions like your bankruptcy or failure to maintain the code. Limit Your Liability Arizona has adopted the Uniform Commercial Code, so if you don’t include specific disclaimers, you might be stuck with certain implied warranties. That includes things like fitness for a particular purpose. You’ll want to limit that while still affirming that you own the software and that it generally works as described. Also, set a cap on liability. Most developers limit it to the total fees paid under the agreement and exclude indirect or punitive damages. You don’t want to be held responsible for how someone else uses your tech. Mutual Indemnification Matters If someone accuses your software of infringing their intellectual property, you might agree to cover the licensee’s costs. But it needs to go both ways. They should indemnify you too—especially if they modify your code or use it in a regulated environment where compliance issues could come up. You don’t want to be liable for something outside your control. Don’t Skip Export Control Compliance Yes, export control rules apply even to downloadable software. If your product includes encryption or certain types of AI or analytics, it may fall under specific federal regulations. Many tools qualify for License Exception ENC, but that’s not automatic. Misclassification can lead to serious fines. If you're licensing internationally—or even just to a foreign-owned company based in the U.S.—you need to get this right before moving forward. Understand How Arizona Law Will Handle Your Agreement Arizona courts usually enforce what’s written. If it’s not in the contract, don’t expect the court to fill in the gaps. That makes detailed drafting essential. Arizona also supports reasonable non-competes and confidentiality terms, which isn’t true in every state. Just make sure any restrictions are tied to legitimate business interests and kept within reasonable limits for time and geography. Spell Out What Happens at the End Termination clauses are your safety net. Cover scenarios like breach, bankruptcy, missed milestones, or even changes in company control. Include cure periods where appropriate. Be specific about what happens when the agreement ends—does the licensee have to stop using the software immediately? Can they finish selling what’s already been produced? Make that clear. Also, specify which obligations survive termination. Usually, confidentiality and IP rights continue, even after the main agreement ends. Plan Ahead for Disputes Choose Arizona law to govern the agreement. If your licensee is in another state or country, decide where and how disputes will be handled. Arbitration can be quicker and cheaper, but it might limit your access to things like injunctive relief. Consider requiring mediation first to give both sides a shot at resolving issues early. And don’t forget a prevailing party clause—Arizona courts do enforce them, and it could help you recover attorneys’ fees if you end up in a legal fight. The Final Analysis Technology licensing isn't just about protecting your IP. It's about setting clear, enforceable expectations from the start. Arizona law gives you the tools to do that, but it only works if your agreement is well-drafted and forward looking. Define what you're licensing, retain ownership, protect your downside, and make sure the deal drives results, not just risk. If you're a software developer navigating a tech transfer deal or reviewing an agreement someone else drafted, don’t go it alone. Having the right legal language in place from day one can prevent years of headaches down the road.