Legal Basics When Selling Software and Code Online

You've built an AI tool, micro-SaaS, or side project. Now you want to sell it. Before you list it anywhere, you need to understand the legal foundations that protect both you and the buyer.

Selling software online is simpler than selling physical goods, but it carries specific legal requirements. Get them wrong and you risk disputes, refunds, or worse—losing your ability to sell again. Get them right and you create a smooth, defensible transaction.

Let's walk through the essentials.

1. Understand What You're Actually Selling

First principle: clarify ownership.

When you sell software, you're typically selling a license to use it, not the actual code or intellectual property. This distinction matters enormously.

Source code ownership: Do you retain it, or does the buyer get it? If you're selling a SaaS tool (cloud-based), the buyer usually never sees the code—they just use the service. If you're selling a downloadable tool or WordPress plugin, the buyer gets the compiled version or files, but may not get the full source.
License terms: Is this a one-time sale or a subscription? Can the buyer resell it? Can they modify it? Can they use it commercially? These are license questions, not ownership questions.
Third-party dependencies: If your software uses open-source libraries, APIs, or frameworks (React, Node.js, OpenAI API, etc.), you inherit their license terms. You must honor them when you sell. If you violate an open-source license, the buyer's use is technically illegal.

Document exactly what the buyer receives and what they can do with it. Ambiguity kills deals.

2. Write a Clear Terms of Service or End User License Agreement (EULA)

A EULA is a contract between you (the seller/licensor) and the buyer (the end user). It doesn't have to be 50 pages—it should be clear and fair.

Your EULA should cover:

Scope of license: Non-exclusive, non-transferable? Can they use it only for personal use, or commercially? One user or unlimited team members?
Restrictions: No reverse engineering, no removing your copyright notice, no renting or leasing it to others.
Disclaimers: "Sold as-is" clauses. Software almost never comes with warranties—state this clearly. "The software is provided without warranty of any kind, express or implied."
Liability limits: Protect yourself by capping your liability. Many agreements say: "In no case shall we be liable for more than the purchase price."
Termination: Under what conditions can you revoke the license? (Usually: if the buyer breaches the agreement.)
Governing law: Which jurisdiction governs disputes? (Pick your home state or country.)

You can use templates—many are available for free or cheap from legal document sites. The key is to have something written that the buyer accepts before purchasing.

3. Handle Intellectual Property Correctly

Three scenarios:

Scenario A: You're the original author. You own the copyright automatically in most jurisdictions (US, UK, EU, etc.). You can license it however you want. Make sure your agreement makes that clear.

Scenario B: You've built on open-source code. Check the license (MIT, GPL, Apache, etc.). If it's GPL, you likely must open-source your code too—you can't sell a proprietary tool built on GPL software. If it's MIT or Apache, you have more freedom, but you must include a copy of the original license and attribution in your sale.

Scenario C: You're selling code you've been paid to write for a client. Stop. You may not own it. Your employment contract or freelance agreement likely gave the copyright to your client or employer. You need their written permission to sell it. This is a common stumbling block.

For each piece of third-party code or library you use, document its license and ensure your use is legal. Include that documentation when you hand over the software to the buyer.

4. Prepare for Escrow and Transaction Protection

When you sell software online without protection, disputes happen: buyer claims it doesn't work, seller disappears after payment, buyer says they changed their mind.

Escrow fixes this. An escrow service (like clAIssified) holds the payment until both parties confirm the exchange is complete. The buyer has proof the software works. You have proof the payment cleared. Only then is the money released.

This isn't just protection—it's trust. Buyers pay more confidently when escrow is involved, and you close deals faster because the buyer isn't afraid.

When you list your software with escrow, make sure your EULA and handover process are documented. The escrow service will want to know: What files are handed over? What documentation or training do you provide? What happens if the buyer finds a critical bug? Setting expectations upfront prevents disputes later.

Conclusion

Selling software legally is straightforward once you know the basics: own what you sell (or have the right to), disclose what the buyer gets and can do with it, respect third-party licenses, and use escrow to protect the transaction.

You've spent weeks or months building your tool. Don't leave money on the table by skipping these steps. A clear EULA and proper escrow take a few hours to set up and pay for themselves in the first sale.