Intellectual Property Lawyers for Lansing, Michigan

Yes, it's generally possible to trademark the name of your software, as long as it is not a generic name or descriptive of the product. You should also do a clearance search to make sure no other company is using the same or similar name for similar services. I would be glad to discuss more details and help with the trademark process. Thanks.

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.

Running a digital content licensing business in Massachusetts actually gives you a solid legal foundation. That said, there are a few important nuances you’ll want to keep in mind. Let’s walk through the full picture, including a few new developments that could impact how you operate. COPYRIGHT IS YOUR STARTING POINT The moment you create something, whether it's videos, images, or written content, it's automatically protected under federal copyright law. That gives you the exclusive right to decide how your work is used, copied, displayed, or modified. And in Massachusetts, there's no broad business license requirement for this type of work. Licensing intellectual property typically just falls under basic business registration. If you're serious about protecting your content, registering your copyrights with the U.S. Copyright Office is a smart move. Without registration, you’re limited to proving actual damages if someone infringes. That's often a costly uphill battle. But with registration, especially if it's done before the infringement occurs or within 3 months of publishing, you open the door to statutory damages ranging from $750 to $30,000 per work. If the infringement is willful, that number can go as high as $150,000. You may also be able to recover attorney’s fees. The filing fee is small, $45 for a single-author online submission or $65 for standard applications, and the legal protection it offers is substantial. One key legal detail: Exclusive licenses must be in writing under 17 U.S.C. § 204 to be enforceable. Non-exclusive licenses do not have that requirement, but oral agreements are harder to prove and much riskier to rely on. Also, keep in mind that exclusive licenses can be recorded with the U.S. Copyright Office. Doing so helps establish priority over competing claims and can strengthen your position in disputes. YOUR LICENSING AGREEMENTS MATTER This is where your business becomes real. Your licensing contracts should be in writing. Verbal agreements simply aren't going to cut it. At a minimum, your agreements should spell out: Scope of Rights: What exactly is the licensee allowed to do? Can they display your work, edit it, or redistribute it? Is the license exclusive or non-exclusive? Be specific. Territory and Term: Where can the content be used, and for how long? There is a big difference between a one-year North American license and a perpetual worldwide one. Payment Terms: Will they pay a flat fee, royalties, or milestone payments? Clarify timing, amounts, and what happens if a payment is late. Attribution: If you want credit, say so clearly. Detail how your name should appear. Termination: Under what circumstances can either party exit the agreement? What happens if someone violates the terms? Warranties and Indemnity: You'll likely warrant that you own the content and have the right to license it. It's also worth requiring that the licensee covers legal costs if they misuse your content. BUSINESS SETUP AND DATA CONSIDERATIONS Massachusetts doesn't require a general business license for most services, but you might need local permits depending on your location. If you're selling digital content, you'll likely need to register for a Sales and Use Tax Certificate with the Department of Revenue, especially if you hit $100,000 or more in remote sales annually. That said, not all digital content is taxed the same way. It depends on how it's delivered, such as streamed or downloaded, and what type of content it is. If you're selling courses, guides, or other educational materials, review Massachusetts DOR Letter Rulings carefully. Many types of downloadable content are not considered taxable. It's worth confirming your specific case with a tax professional or the Department of Revenue. Forming an LLC is a good step for liability protection. In Massachusetts, that means filing a Certificate of Organization with the Secretary of the Commonwealth. The fee is $500. You'll also need to get an EIN from the IRS, which you can do online for free. One new development to keep an eye on is the Massachusetts Data Privacy Act, Senate Bill 2516. Introduced in May 2025, it targets businesses that collect personal data from 25,000 or more residents or make money by selling data. If passed, it could require you to post separate privacy notices for things like geolocation and biometric data, restrict ad targeting to minors and comply with new civil penalties. If your licensing business collects user data or runs a platform, this is one to watch. HOW TO PROTECT YOUR WORK ONLINE The DMCA gives you a clear process to get unauthorized uses of your content taken down. Even if your copyright is not registered, you can still send a takedown notice to the site or platform hosting the infringing material. Your DMCA notice needs to include your contact information, what content is being infringed, where the infringing content appears, a statement that the use is not authorized, and your signature. Most platforms have a specific process or form you'll need to follow. You can look up their DMCA agents on the Copyright Office’s online directory. If you ever start hosting user-uploaded content on your site or platform, consider registering as a DMCA Designated Agent yourself. That gives you safe harbor protections in case users upload infringing content. Registering costs just $6. LICENSING MODELS THAT WORK There are several ways to structure your licensing depending on how you want to monetize: Exclusive Licenses: Higher fee; one client per use case. Ideal for unique or high-value content. Non-Exclusive Licenses: Lower fee, but you can license the same asset to multiple clients. Great for scale. Royalty-Free: One-time payment for broad, ongoing use. Popular with stock content buyers. Creative Commons: Free standardized licenses that can help with visibility but limit your control. They also cannot be revoked once granted. MANAGING RISK AND STAYING COMPLIANT It's smart to watermark your content and keep clear, well-organized records of all your licenses. Monitor for unauthorized use and consider business insurance as your operation grows. If you collect any personal data, Massachusetts law already requires that you maintain a Written Information Security Program, also known as a WISP. That includes encryption for data sent over public networks and other technical and administrative safeguards. Also be aware that digital accessibility requirements continue to evolve. Courts and regulators commonly reference the WCAG 2.1 Level AA as the current benchmark for website and platform compliance. If your site or tools serve the public, aligning with this standard is a strong risk-management move. THE FINAL ANALYSIS Federal copyright law gives you strong baseline protection. Massachusetts contract law enforces your licensing agreements. But the real strength lies in putting your licensing terms in writing and registering your key content early. As your business scales, keep an eye on privacy regulations and make sure your legal foundation grows along with your income. Focus on clarity in your contracts, structure your licensing in a way that fits your goals, and stay current on the laws that affect your specific business model.

Hello! Thank you for posting this question. In your case, the other party may claim that you are infringing on their trademark, but proving it is a different case. The Lanham Act provides for a cause of action for infringement of both registered and unregistered trademarks. (15 USC Section 1114(1)(a); 15 USC Section 1125(a)(1)A).)  The 9th Circuit Court of Appeals has laid out some elements to help determine whether it creates an infringement lawsuit. 1. The complaining party has to prove they have a valid, protectable trademark and that they own that trademark; 2. The complaining party must prove that a mark is similar, and it was used without the consent of the moving party in a manner that is likely to cause confusion among ordinary consumers as to the source, sponsorship, affiliation, or approval of the goods.  The likelihood of confusion can occur at the time of the sale, when there is initial interest by a consumer, or even after the sale, if the confusion causes a consumer to no longer buy a service or product connected to the mark. The court considers things like the strength of the original mark, whether you are using it for some fair use purpose, the similarity, the proximity of the products and marketing channels, whether there’s actual confusion, the defendant’s intent, the quality of respective products, and the sophistication of the customers. (Polaroid Corp. v. Polard Elecs. Corp. 287, F.2d. 492, 495 (2d Cir. 1961.) So what this means is that it'd have to be litigated, but you can argue you are not trying to sell products or services using their mark, but rather you are using it for some other purpose, such as to educate people about their business practices. Best of luck!

Here’s how I’d approach structuring an Employee IP Agreement if your goal is to protect your company’s intellectual property without running into enforceability issues under U.S. law. Covering Core IP OwnershipCovering Core IP Ownership First, start with a “work made for hire” clause. It’s a good foundation, but it’s not enough on its own. Under U.S. copyright law (17 U.S.C. § 101), only certain types of work qualify as “made for hire,” and many employee-created assets may fall outside that definition. So you’ll want to pair it with a present-tense assignment clause. Be specific here. Use language like “the employee hereby assigns” rather than “will assign.” That slight shift matters. It ensures the company owns the rights immediately when the work is created. Also, define “intellectual property” broadly. Don’t just list patents or source code. Include software, algorithms, documentation, trade secrets, databases, and anything tied to your business. The scope should clearly include anything created during work hours, using company tools or systems, or connected to your current or future business operations. Disclosure and Documentation You’ll want to require employees to promptly disclose any inventions or creative works they produce. Put it in writing. This gives your company the chance to evaluate whether the work is covered under the agreement. It’s also a good idea to require them to maintain proper documentation. Accurate records can make a real difference in patent filings or if a dispute ever comes up. Pre-Existing IP and Legal Carve-Outs There should be a section where employees list anything they’ve developed or own before joining the company. If they don’t list anything, the agreement should include language confirming they’re representing that no such prior inventions exist. This prevents claims down the road that something developed during employment was actually theirs from before. Now, depending on your state, you may need to include statutory carve-outs. California, Illinois, and Washington all have laws that limit how far IP assignment clauses can go. For example, in California, you’re required to carve out inventions developed entirely on the employee’s own time, without company resources, and unrelated to your business (see California Labor Code § 2870). Without that carve-out, your entire assignment provision could be thrown out. Confidentiality Obligations Make sure there’s a strong confidentiality section. This should cover source code, technical documentation, designs, product plans, customer lists, financial data, and anything else proprietary. Make it clear that the obligation continues even after the employee leaves. You’ll also want to require that all company property and digital assets are returned at the end of employment, including devices, credentials, and files. Ongoing Cooperation and Enforcement Mechanisms Include a clause requiring employees to cooperate in IP protection efforts even after they leave. That could mean signing patent paperwork or providing testimony if needed. To make that enforceable, add a power of attorney clause. This gives the company the authority to act on the employee’s behalf if they’re unwilling or unreachable. It’s a simple way to prevent delays when you’re trying to secure or enforce rights. It’s also smart to include a waiver of moral rights where allowed. This is especially useful for creative works and software. It gives the company full freedom to modify or use the work without needing future approval. Legal Remedies and General Terms Be clear that the company can pursue equitable relief, like an injunction, if there’s a violation. Sometimes monetary damages aren’t enough to prevent harm. Include a severability clause so that if one part of the agreement is invalidated, the rest still stand. Don’t forget to specify the governing law and venue for any disputes. As for restrictive covenants, keep in mind that non-compete clauses are unenforceable in California and heavily restricted elsewhere. Non-solicitation clauses may still be allowed, but they need to be narrowly written. You should have your legal team confirm their enforceability based on your state. Finally, think about consideration. For new hires, the job offer itself usually counts. But for existing employees, you’ll likely need to offer something extra, like a bonus or promotion, to make the agreement stick.