What are the key provisions to include in a Patent Assignment Agreement?

It would be a good idea for you to have the agreement reviewed by an attorney. You said there's no explicit language regarding termination or notice - is there something implied? With no language regarding termination, most likely either party can terminate at any time, with just a moment's notice, and no reason given. You have asked a lot of questions - I suggest that you post a project here on Contracts Counsel, and ask for an attorney well versed in intellectual property (not me) to discuss your rights, as that is probably the most important issue. An attorney who can also review the language of the entire agreement would be very helpful. (I'm sorry, but I'm not available for this project).

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.

Without seeing the handbook it would be difficult to answer your question. Generally, what an employee creates for the Company is Company property, unless you have an agreement with them that states otherwise. It would also be helpful to know if you are an employee or independent contractor. Sometimes Company's give employee handbooks to independent contractors but the classification of whether you are an employee or independent contractor is important to this analysis.

Running a trademark search before registering your business name isn’t legally required, but it’s one of the most important steps you can take to avoid future problems. Registering your name with the state forms your business entity, but it doesn’t give you trademark rights. Trademark rights come from use in commerce and, if you file with the USPTO, registration at the federal level. Why a Trademark Search Matters The central legal test in trademark law is whether a name is likely to cause consumer confusion. That means you don’t need to copy someone else’s name exactly to get into trouble. Even something that looks or sounds similar in the same or related industry could be enough. If you skip the search and move forward, you risk: • Infringement claims: Another company could demand you stop using the name and, if necessary, sue for damages. • Forced rebranding: If you’ve already invested in your logo, website, signage, or marketing materials, being forced to change your name can be expensive and disruptive. • USPTO rejection: If you apply for a federal trademark, the USPTO will run its own search. If they find a confusingly similar mark, your application will be denied and you’ll lose the filing fees. A well-documented example is when small businesses open under a catchy name, only to receive a cease-and-desist letter from a national chain using a similar name in the same space. Even if you’re in a different state, a federal registration gives that company priority rights nationwide. A proper trademark clearance search should cover more than just identical names. You’ll want to check: • Federal database (USPTO TESS): This is the official record of all registered and pending federal trademarks. • State trademark databases: Many businesses register marks only at the state level. • Common law sources: Unregistered marks can still have legal protection. Check Google, industry directories, social media, and domain names. • Similar variations: Look for phonetic equivalents and alternative spellings, such as “Kwik” for “Quick,” or slight wording changes that could still cause confusion. Professional Assistance You can run an initial search yourself at no cost, but these searches have limits. For example, the USPTO database won’t flag marks that are spelled differently but sound alike, or names with similar meanings. Attorneys and specialized search firms use tools that uncover those kinds of risks. While hiring a professional costs more upfront, it’s often far cheaper than litigation or a rebrand. Limitations A search doesn’t guarantee that your name will never be challenged. Trademark law involves judgment calls about how similar marks are and whether they overlap in goods or services. Still, a thorough search puts you in a much stronger position to defend your choice and move toward federal registration if you want nationwide rights.

Since the user uploaded copyrighted material to your website without your knowledge, generally you will not be automatically liable under the DMCA “safe harbor” provision. As you have already removed the content, make sure that your site has a published DMCA policy and that you have registered your designated agent with the U.S. Copyright Office. Generally, if you have everything in place, most of these matters are resolved without ongoing liability. Feel free to reach out if you need guidance on setting up a policy and agent registration.