Intellectual Property Lawyers for Rochester, Minnesota

You’re not the first to confuse a KISS Note with intellectual property protection, and you definitely won’t be the last. It’s a common mix-up in the startup world. But here’s the truth: A KISS Note has nothing to do with protecting your software. It’s a financing instrument created by 500 Startups, designed as an alternative to convertible notes and SAFEs for early-stage fundraising. It’s a way for investors to give you money now in exchange for equity later. It does not offer any legal protection for your code or ideas. So What Do You Actually Need to Protect Your IP? If you're building software in California, there are several key legal tools you’ll want to have in place. Start with the ones that offer immediate protection and work your way toward longer-term strategies. Always Start with NDAs If you're showing your software to anyone (whether it's a co-founder, a contractor, an investor, or a beta tester) you need a solid non-disclosure agreement in place before you share anything. It’s your first line of defense, especially if you want to preserve trade secret protection. Your NDA should spell out exactly what you consider confidential. This might include your source code, algorithms, user data, business plans, or any other proprietary information. The agreement should also state how long confidentiality lasts and what the other party can and cannot do with your information. One important note here: California law prohibits non-compete clauses under Business and Professions Code Section 16600. Do not include one in your NDA. It won't be enforceable. Instead, focus strictly on confidentiality and use limitations. Copyright is Automatic, but Registration Matters As soon as you write your code, it’s protected under federal copyright law. That protection applies to the actual expression (the specific code) not to your underlying ideas, functionality, or algorithms. Even though protection is automatic, registering with the U.S. Copyright Office gives you significant legal benefits. You can’t file a federal lawsuit without registration. And if your copyright is registered before infringement occurs, you may be eligible for statutory damages of up to $150,000 per work and recovery of attorney’s fees. The process usually costs between $65 and $85 and takes a few months. Trade Secrets Require Real Effort to Stay Protected If your software includes proprietary algorithms, confidential processes, or unique technical methods that provide a competitive edge, you may be eligible for trade secret protection under the California Uniform Trade Secrets Act. But here’s the catch. That protection only lasts as long as you actively protect the information. This includes limiting access to your source code, using secure development environments, marking documents as confidential, and having everyone involved sign NDAs. You need to treat your trade secrets like actual secrets if you want the law to do the same. Considering Patents? Proceed Carefully Software patents are complex, especially following the Supreme Court’s 2014 Alice decision. You can’t patent abstract ideas, mathematical formulas, or generic computer processes. Your software needs to solve a specific technical problem in a novel, non-obvious way or improve the functionality of a computer system itself. If you've developed something truly unique — like a new data compression algorithm, a better machine learning architecture, or a new way to optimize networking — a patent might be worth exploring. Just keep in mind that the process is expensive, often costing $10,000 to $15,000 with legal fees. It can also take several years. Many software companies choose to rely on trade secrets and copyrights instead. How to Put All of This Into Practice Begin with what you can implement right away. Create a strong NDA template and use it consistently. Register your copyright as soon as your codebase is developed enough to be meaningful. Protect your trade secrets by putting real technical and legal safeguards in place. Track your development process carefully. Version control, timestamps, and contributor logs can all serve as useful evidence in a legal dispute. If you’re working with employees or contractors in California, be especially cautious. The state has employee-friendly laws, so your contracts must clearly state that all work product belongs to your company and that all confidential information stays confidential. When Should You Talk to a Lawyer? Once you’re dealing with patents, investor negotiations, infringement threats, or user data privacy, it’s time to bring in professional legal help. These are complex areas, and the risks are too high to wing it.

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).

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.

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.

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.