Intellectual Property Lawyers for Virginia

You will need a design patent

Hi, Yes, intellectual property created by you as an employee, within the scope of your employment, under a work-for-hire agreement, probably belongs to your employer. To learn more about your rights under the agreement and any exceptions, you should consult with a qualified attorney.

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.

Yes, you can and should include clauses in an Intellectual Property License Agreement that protect your rights as the licensor. A license agreement is your main tool for controlling how your software is used, setting boundaries for your clients, and limiting your financial exposure. The key is to draft it in a way that leaves no doubt about what rights are granted, what’s restricted, and what happens if there’s a breach. Grant of License Start with a clear license grant. Spell out that you’re giving the client only limited rights, not ownership. Most licensors define the license as non-exclusive, non-transferable, and revocable if the client doesn’t follow the terms. For example, you might allow a client to use the software only for its internal business operations, and only on a set number of machines. It’s equally important to list what the licensee cannot do, such as reverse engineering, modifying, sublicensing, or providing the software to third parties. Intellectual Property Ownership Reinforce that you retain all ownership rights in the software and any related intellectual property. A simple but strong statement is that you hold all right, title, and interest in the software, and the client only receives a limited right to use it under the agreement. This prevents confusion between a license and a sale. You can also require the licensee to notify you if they discover third-party infringement and confirm that you alone have the right to pursue action against infringers. Confidentiality If you’re providing source code, algorithms, or other sensitive information, a confidentiality clause is essential. Define confidential information broadly to include not just the software itself but also any documentation or business information you share. Require the client to protect that information with at least the same care they use for their own confidential material, and make the obligation survive termination of the agreement. Termination Every strong license has a termination clause. Termination for cause should allow you to end the agreement if the client fails to pay, violates the license scope, or breaches confidentiality. Many agreements include a short cure period, such as thirty days, for the licensee to fix the breach before termination takes effect. Spell out the consequences of termination: the licensee must stop using the software immediately, return or destroy all copies, and certify that they’ve complied. Without this, you risk losing leverage if the relationship breaks down. Payment Terms Protect your revenue by making payment terms clear. Define license fees, support or maintenance fees if applicable, the payment schedule, and penalties for late payment such as interest. Courts generally enforce these provisions as long as they’re reasonable. Disclaimers and Limitation of Liability These clauses protect you from lawsuits if things go wrong. A limited warranty might cover basic performance for a set time, but beyond that you should disclaim all other warranties. Standard language is that the software is provided “as is” and you disclaim implied warranties of merchantability and fitness for a particular purpose. To limit your exposure, cap liability at a defined amount, often the fees paid by the licensee in the previous twelve months, and exclude liability for indirect or consequential damages such as lost profits. Courts usually enforce these limits, except in cases of fraud or intentional misconduct. Audit Rights If your pricing model depends on the number of users or installations, an audit right is valuable. This allows you to check, on reasonable notice, that the licensee isn’t exceeding their rights. For example, you might reserve the right to inspect usage records once a year during normal business hours. Governing Law and Dispute Resolution Designating which state’s law governs and how disputes are resolved reduces uncertainty. Many licensors choose their home state’s law and either local courts or arbitration for disputes. Remedies Make sure your agreement lets you seek injunctive relief if the licensee misuses or discloses your software. Monetary damages often aren’t enough to protect intellectual property, so courts will enforce contract terms that authorize immediate injunctive relief. Protect Your Software with Legal Guidance When you’re licensing valuable software, the details in your agreement can make the difference between real protection and unnecessary risk. The lawyers on Contracts Counsel are available to draft, review, or negotiate a license that secures your rights and keeps your business protected.

The terms of your specific agreement are the most important factors to consider. In general, an invention assignment agreement usually means that an employee gives the company any ideas or inventions they come up with while working. The rules can vary by agreement, but they often cover ideas made during work hours, using company resources, or related to the company’s business. In Texas, an agreement can apply to inventions made outside of work hours if they’re related to the company’s business or came from work the company assigned. In one case, the agreement said the employee had to give up all inventions made during or after regular work hours, whether on or off the job, if they were related to the company’s business or came from work the company assigned. Usually, an invention assignment agreement doesn’t apply to ideas that aren’t related to the employee’s job unless the agreement says otherwise. In Atlas Brick Co. v. North, 2 S.W.2d 980, the court said that the title to an invention wouldn’t belong to the employer unless the agreement said that ideas made and perfected under the employee’s contract of employment belong to the employer. Also, if a discovery is made outside the scope and purpose of employment, it belongs to the employee unless there’s an agreement to give up such inventions to the employer. So, it all depends on the terms of the invention assignment agreement. In the case of Halliburton Energy Servs. v. Axis Techs., LLC, the agreement required the employee to turn over all materials related to inventions created during employment, making them the company’s property. But, if the agreement doesn’t cover certain inventions or if the inventions are made outside the scope of employment without using company resources, the employee might still retain ownership.