Can a content creator agreement be terminated by either party at any time and without cause?

Depends on what the content creator agreement with the platform says about termination. It likely has the platform covered. If they didn't follow the terms of the agreement, you might have a claim. The claim may be limited in damages as most of these contracts, if well written, have limitations on damages under the contract.

The key elements for a Content Creator Agreement are: 1. Payment Terms/Late Fees: How much will you be paid? When will you be paid? In what manner will you be paid? Are there any services/deliverables that must be provided before you are paid? What are your remedies if the payments are late? 2. Deliverables: Clear project deliverables that list all of the important project details/requirements 3. Timelines and Review & Approval Process: What are the required timelines for completion of the work? How long does the client get to review before the work is considered approved and final? What happens if the client wants to make changes to the work? Do requested revisions change the price? 4. Ownership: Who owns the content - client or content creator? 5. Confidentiality: Information shared between the parties should be kept confidential. 6. Exclusivity: Will the agreement be exclusive or non-exclusive? 7. Term and Termination: When does the relationship start and when does it end? How can the parties terminate the relationship? What are the responsibilities of each party once the relationship is terminated? What happens if there is a breach of the contract?

Yes, in short, a content creator should definitely have a written content creator agreement with the company they're creating content for. Among other things, the agreement will: clarify ownership of the content, define payment terms, set deadlines and expectations, protect against "scope creep" (prevent you from doing extra work at no charge), address various legal risks, including warranties, indemnifications, and compliance requirements, cover non-compete or exclusivity terms, and specify termination rights. This response is for general informational purposes only and does not create an attorney-client relationship. For advice related to your specific matter, consult a qualified attorney licensed in your area.

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.