VIBE CODING · 2026-04-02 · 6 MIN READ
When AI Built It, Who Owns It? IP Questions Answered
You spent three weekends building your app. You described what you wanted, Cursor wrote the code, ChatGPT drafted the copy, Midjourney created the log
BY BIREXIT TEAM
·2026-04-02
·
When AI Built It, Who Owns It? IP Questions Answered
You spent three weekends building your app. You described what you wanted, Cursor wrote the code, ChatGPT drafted the copy, Midjourney created the logo. Now someone wants to buy it for $8,000 — and they're asking: "Do you actually own this?"
Good question. Let's answer it clearly.
The Short Answer: You Probably Own More Than You Think
Here's the thing most vibe coders don't realize: in most cases, you own the app you built with AI tools. Not the AI company. Not the platform. You.
Why? Because you:
- Made the creative decisions about what to build
- Directed the AI with your prompts and feedback
- Assembled the pieces into a working product
- Own the data, the domain, the business logic
But "probably" isn't "definitely," and buyers need "definitely." So let's get specific.
The Code: Who Owns It?
When you build with tools like Cursor, Bolt, or Replit, the AI generates code based on your instructions. Here's the ownership breakdown:
The platforms say: You own the output. Cursor, Bolt, Replit, and most AI coding tools explicitly state in their terms of service that you own the code generated for you.
The legal reality: AI-generated code typically isn't separately copyrightable on its own (courts are still figuring this out), but your selection, arrangement, and customization of that code is yours. More practically: your app as a whole — the combination of code, logic, and user experience you created — is your intellectual property.
The practical takeaway: Check your tool's ToS. For the major platforms, you're covered. Screenshot or save those terms as part of your documentation.
The Design: What About AI-Generated Images and UI?
If you used Midjourney, DALL-E, or Stable Diffusion to create your app's visuals:
- Midjourney: Their ToS says you own the images you create (with a Pro plan; Free plan is different — check current terms).
- DALL-E/OpenAI: You own the images generated.
- Stable Diffusion (open source): No restrictions — full ownership.
The nuance: some platforms prohibit using AI-generated images in commercial products without the right subscription tier. Make sure you're on a paid plan when generating assets for apps you plan to sell.
Logo tip: If your logo is 100% AI-generated, note that in your listing. Some buyers prefer this (no designer to pay for updates), others want a human-designed logo. Either way, be transparent.
The Content: Blog Posts, Copy, Descriptions
Text generated by ChatGPT, Claude, or similar tools? You own it. OpenAI and Anthropic's terms explicitly grant you ownership of outputs you generate. Same for most AI writing tools.
One exception: some tools retain the right to use your prompts/outputs for training. That doesn't affect your ownership — it just means they might learn from your inputs. It's a privacy consideration, not an IP one.
The Tricky Part: Third-Party Libraries and APIs
Here's where vibe coders sometimes get tripped up. Your app likely uses:
- Open source libraries (React, Supabase, etc.) — these come with licenses. MIT and Apache licenses are buyer-friendly. GPL can complicate commercial sales. Check what your app uses.
- Third-party APIs (Stripe, OpenAI, Google Maps) — you don't own these. You have the right to use them under their ToS. Buyers inherit these agreements.
- Paid services — if your app depends on a SaaS tool with a per-seat or usage-based pricing, document this clearly. It affects the buyer's operating costs.
Pro tip: Run your project through a quick dependency check. Ask your AI coding tool: "List all third-party libraries this project uses and their licenses." Include this in your sale documentation.
What Buyers Actually Ask About IP
When a serious buyer does due diligence on a vibe-coded app, they typically ask:
- "Is there any code you didn't write or generate that might be restricted?" — Answer: check your libraries.
- "Do you own the domain?" — Yes, and you'll transfer it via registrar.
- "Are there any open legal issues or IP claims?" — If no, say so explicitly.
- "Can you transfer all accounts associated with the app?" — API keys, hosting, email, social accounts.
None of these are vibe coding-specific problems. They're standard acquisition questions. The difference is that vibe coders sometimes don't know what's in their codebase — which is fixable.
How to Protect Your IP Before Selling
You don't need a lawyer for this (though one doesn't hurt for bigger deals). You need documentation:
1. Screenshot your tool subscriptions. Show that you were on paid plans when generating commercial assets. Date-stamped.
2. Keep your original prompts. A folder of your key prompts shows creative authorship. It's your "creative brief" that proves the AI was your tool, not your co-creator.
3. Register a trademark if you're serious. For apps over $5K–$10K, consider registering your app name as a trademark. It's $250–$350 with the USPTO and takes a few months. Buyers love it.
4. Document what you didn't build. If you used a starter template, note it. If you forked an open-source project, document the license. Surprises kill deals.
The "Who Owns the AI Output?" Debate
Full transparency: the legal landscape is still evolving. Courts around the world are still deciding whether AI-generated works can be copyrighted, and if so, by whom.
The current practical reality: it doesn't matter much for small app sales. When someone buys your $5K app, they're not buying it for copyright protection. They're buying it for the business — the users, the revenue, the problem it solves. Copyright on a small app is largely academic.
What does matter legally: contracts. A well-written purchase agreement that clearly transfers ownership of the app, domain, accounts, and any associated assets is worth infinitely more than a copyright registration.
What to Tell Buyers (Script Included)
When a buyer asks about IP, here's a template response:
"The app was built using [Cursor/Bolt/Replit] under a paid subscription, which grants full ownership of generated code. All visual assets were created with [Midjourney/DALL-E] under commercial-use tiers. Third-party libraries are MIT/Apache licensed — I can provide a full dependency list. The domain, hosting accounts, and API keys are in my name and will be fully transferred at close. No outstanding IP claims or legal issues."
That's it. Confident, specific, reassuring.
The Bottom Line
You built it. You own it. The IP situation for vibe-coded apps is simpler than most people think — and a lot simpler than traditional software, which often has messy employment contracts, contractor agreements, and "work for hire" complications.
As a solo vibe coder, there's no ambiguity about who created the app. You did. With powerful tools you paid for.
Document it, be transparent about dependencies, and get a proper purchase agreement when you sell. That's the entire IP playbook for vibe coders.
Now go price that thing properly — you own it, after all.
Ready to list your AI-built app? Birexit connects non-technical founders with buyers who understand and value vibe-coded products.
RELATED POSTS