Intellectual Property Lawyers for Santa Clara, California

When you're reviewing a Developer Agreement, it’s really important to make sure it covers the basics while also protecting your rights and interests. Here’s a breakdown of what you should look out for in plain terms: Hello! My name is Dolan and I am happy to help. First off, the agreement should clearly describe the scope of work (often called the "SOW") This means it needs to explain exactly what you're expected to do, including the features or functionality of the app, the timeline for delivery, and any milestones. Make it specific. It has to be clear what is defined as intellectual property and then who owns it. Compensation is another big one. The agreement should spell out how much you’re being paid, whether it’s a flat fee, hourly rate, or based on milestones. I Confidentiality clauses are pretty standard, but you’ll want to make sure they don’t go overboard. Termination clauses are also super important. These should say under what conditions either of you can end the agreement. Make sure that if the company decides to end things early, you’ll still get paid for the work you’ve done up to that point. We can always draft these things for you or look over what you've drafted. Best of luck! Dolan

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.

As a legal entity, a joint venture (JV) can own a patent. Given the temporary nature of JVs and the fact that there will be multiple owners of any patents, there is a complex mix of intellectual property (IP) ownership rights, dispute resolution, and enforcement issues that need to be agreed upon in order to properly protect everyone's intellectual property rights. Consideration will need to be given to what IP ownership and rights will look like during and after the JV and it may be easier to have both companies listed as the patent authors for inventions from the outset (versus naming the JV as the author). A joint IP agreement is the best solution to outline the rights of each party, the process for developing patentable technologies sufficient to be a patent author, filing and prosecuting patents, and future licensing and exploitation of the patent.

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!

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.