Intellectual Property Lawyers for Broken Arrow, Oklahoma

Invention Assignment Agreements usually require employees to hand over rights to any inventions they come up with during their employment. But things can get tricky when the agreement tries to claim ownership of something you created on your own time using your own resources. What’s Generally Enforceable Employers often write these agreements in broad terms, sometimes trying to cover anything you invent while you're employed, even if it’s unrelated to your job. Courts usually uphold fair agreements, but they’ll look closely at anything that seems to overreach. Most states try to strike a balance. If an invention is directly tied to your work or the company’s business, the employer may have a valid claim. But if it’s something truly independent that you built on your own time without company tools or knowledge, you’re more likely to keep it. State Laws That Protect Employees Some states have gone further and passed laws that give employees more protection. California’s Labor Code § 2870 is probably the most well-known. It says employers can’t force you to assign inventions that were developed entirely on your own time without using any company resources. The exception is if the invention is connected to the company’s business, research, or your actual job duties. Other states like Washington, Illinois, Delaware, Minnesota, and North Carolina have similar laws. New York passed its own version in 2023, called Labor Law § 203-f, which follows California’s lead. Most of these laws also require employers to give written notice to employees about their rights. In states without specific laws, courts typically rely on general contract principles and public policy. If a contract tries to claim every idea you’ll ever have, that language probably won’t hold up. But if the invention overlaps with your employer’s field, even if you built it at home, the company could still have a real claim. When Employers Still Have Rights Even with legal protections, there are a few situations where the company can still argue ownership: 1. If the invention is related to the business or current projects. 2. If you used any company tools, software, workspace, or confidential info. 3. If the invention came out of your assigned job duties, even if you worked on it after hours. These carve-outs are broader than most people realize. For example, if you’re a software engineer and your side project uses the same coding language or solves a similar problem as your employer’s product, that could raise red flags, even if you used your own laptop at home. How to Protect Your Own Inventions If you want to make sure you keep the rights to something you’ve created, documentation is key. Keep records of when you worked on it, what tools you used, and how it relates (or doesn’t relate) to your job. Don’t use your work email, computer, or cloud storage. And read your agreement carefully. Some contracts require you to disclose all inventions, even personal ones. Disclosure doesn’t always mean you have to assign it, but it can start a conversation you’d rather avoid. The Shop Right Rule Even if you own your invention, your employer might still be able to use it under what’s called the “shop right” doctrine. This means that if you used company time, tools, or resources, the company may have a free, nonexclusive license to use your invention in its operations. You’d still own it, but you couldn’t stop them from using it. Why Jurisdiction Matters The state where you work usually controls which laws apply to your agreement, not the state where your company is based. That can make a big difference. For example, engineers in California have strong statutory protections. Employees in Texas may need to rely on general contract law instead. The Final Analysis Your best move is to have an employment attorney review your agreement. The details matter, and so does your state's law. A good attorney can explain what's enforceable, help you negotiate better terms (like explicit carve-outs for personal projects), and show you how to protect your own work without violating your contract. If you're looking for this type of guidance, the attorneys on Contracts Counsel are available to help. Whether you need a quick contract review or full representation, you can connect with experienced employment lawyers who understand the nuances of invention assignment agreements in your state.

When you're reviewing a Developer Agreement, it’s really important to make sure it covers the basics while also protecting your rights and interests. Here’s a breakdown of what you should look out for in plain terms: Hello! My name is Dolan and I am happy to help. First off, the agreement should clearly describe the scope of work (often called the "SOW") This means it needs to explain exactly what you're expected to do, including the features or functionality of the app, the timeline for delivery, and any milestones. Make it specific. It has to be clear what is defined as intellectual property and then who owns it. Compensation is another big one. The agreement should spell out how much you’re being paid, whether it’s a flat fee, hourly rate, or based on milestones. I Confidentiality clauses are pretty standard, but you’ll want to make sure they don’t go overboard. Termination clauses are also super important. These should say under what conditions either of you can end the agreement. Make sure that if the company decides to end things early, you’ll still get paid for the work you’ve done up to that point. We can always draft these things for you or look over what you've drafted. Best of luck! Dolan

You might think that because you wrote the code, you have the right to share it, but that’s not how developer agreements usually work. In Washington State, these contracts are enforceable, and they can absolutely stop you from sharing or reusing code you created during a project. It really comes down to ownership, and under most contracts, that ownership belongs to the company, not you. Let’s Talk About Who Owns the Code When you sign a developer agreement, you’re usually agreeing to one of two things: either it’s a “work-for-hire” deal or you're assigning your intellectual property rights. Either way, the result is the same. The company owns whatever you build for them. Since they own it, they get to decide what happens to it. Even if you’re the one who wrote every line, that doesn’t mean you have the right to reuse or share it if you’ve already signed those rights away. This kind of setup is standard in the tech world. Companies need to protect their IP, especially when it includes competitive advantages or trade secrets. That’s why they ask developers to assign rights and agree to keep things confidential. What About Washington State Law? Washington does offer some protection to developers, but it’s limited. There’s a statute, RCW 49.44.140, that says employers can’t claim ownership of inventions you created entirely on your own time, using your own resources, and completely unrelated to their business. That sounds helpful, but here’s the catch. It only applies if you’re an employee, not an independent contractor. And even then, the second your work overlaps with their business or involves any company resources, the protection probably doesn’t apply. So if the code you’re writing is part of a contract, or even just loosely connected to the company’s business, then the company likely owns it. Why This Matters If you violate the agreement, you’re not just risking a slap on the wrist. The company could send a takedown notice to GitHub, file for an injunction, or even sue for breach of contract or copyright infringement. If the code includes anything proprietary, like business logic or algorithms, they might also go after you for trade secret misappropriation. And beyond the legal problems, there’s your reputation to think about. Word travels fast in development circles, especially in local communities. Getting labeled as someone who mishandles IP can make future contracts harder to land. How to Protect Yourself The good news is that you still have leverage before you sign. A lot of companies start with broad IP assignment language, but they’re often open to carving out exceptions. You can ask to include a “prior inventions” schedule that lists tools, frameworks, or libraries you already created. That way, you can keep using your own work in other projects. If open-source contribution is important to you, say so upfront. Some companies will allow developers to contribute non-proprietary or generic components to open-source projects, especially if those contributions don’t compete with their business. Just make sure it’s all clearly spelled out in writing and approved in advance. You might also negotiate a time limit on confidentiality terms. The company will likely want to own the core project code permanently. That doesn’t mean you can’t eventually talk about general techniques or patterns you used, especially after some time has passed. Smart Moves Before You Sign Before you agree to anything, take a moment to list any existing code or tools you plan to use. Try to get those explicitly excluded from the IP assignment, or at least confirm that you’ll retain the right to use them elsewhere. And again, if open-source is part of your career plan, be upfront. Get language in the contract that allows you to publish select components with written approval. If you develop a useful utility during the project and think it might have broader uses, talk to the company before the contract ends. See if they’d be open to letting you open-source it or license it back to yourself for use in future projects. When It’s Time to Bring in a Lawyer If all this feels high-stakes, and it often is, consider having a tech-savvy attorney take a look. A good lawyer can help spot overly aggressive clauses, suggest better language, and help you protect both your rights and your long-term goals. This is especially important if you’re actively contributing to open-source or if you’ve built up your own libraries over time. A little legal help now can save you a lot of trouble later.

A person that owns the intellectual property rights in a product (i.e., the IP owner) can transfer all rights of ownership to another party. You would need to enter into an Intellectual Property Transfer/Assignment Agreement. This agreement would transfer the intellectual property ownership of the product from you to the other party. This is a permanent transfer and you would not have any further rights to the intellectual property in the product once the agreement was signed.

When you’re preparing work for a client, the key issue isn’t whether you’ve run a formal copyright search, but whether you have the legal right to use the image. Copyright law automatically protects most images, so relying on the absence of a watermark or a registration record isn’t enough to keep you safe. Copyright Protection and Ownership Under U.S. law, copyright attaches the moment an original work is created and fixed in a tangible form (17 U.S.C. § 102). That means virtually every photo, illustration, or graphic you find online is already protected. Registration with the U.S. Copyright Office strengthens enforcement rights, but it isn’t required for protection. Likewise, the lack of a © symbol doesn’t mean an image is free to use. Because there’s no central database covering all copyrighted images, a formal copyright search isn’t practical or reliable in most cases. Even if you searched the Copyright Office’s records, you’d only be looking at registered works, which are a small fraction of what’s actually protected. Risks of Using Unlicensed Images If you incorporate an image without permission into a commercial project, you and your client could face serious consequences. Infringement can lead to cease-and-desist orders, statutory damages of $750 to $30,000 per work (and up to $150,000 for willful infringement) under 17 U.S.C. § 504(c), and potential liability for the copyright holder’s attorney’s fees. Courts generally view commercial use as disfavoring any “fair use” defense. Even if you didn’t intend to infringe, liability can still be imposed. Best Practices for Designers The best practice is to focus on obtaining images from sources where the licensing terms are clear and legally sound. For example: • Use reputable stock photo agencies such as Adobe Stock, Shutterstock, or Getty, where commercial licenses are explicit. • Choose Creative Commons images that allow commercial use (e.g., CC BY or CC0), but review license terms carefully. • Confirm public domain status when applicable, such as U.S. federal government works. • Contact creators directly for written permission if you want to use their work. • Keep copies of receipts, license agreements, or permission letters so you can show proof of rights if challenged. Reverse image search tools like Google Images or TinEye can be useful to trace the origin of an image and identify whether it’s sold or licensed by a third party. However, this is a step in due diligence, not a substitute for obtaining rights. Professional Responsibility As a freelance designer, your contracts may hold you responsible for ensuring that the materials you deliver don’t infringe anyone else’s rights. Delivering work that exposes your client to infringement claims can damage your reputation and your client relationship. The safest practice is to assume that any image you didn’t create yourself is protected until you confirm otherwise and secure the proper license.