The topic
Nobody enjoys reading about law, and AI tools make it easy to ship before you've thought about it. The good news is that for a small project the legal list is short. It's worth ten minutes before anyone else uses what you've built.
This is general information for UK builders, not legal advice. For anything with real money or sensitive data involved, speak to a solicitor.
The short answer
The main legal risks are unclear ownership of AI-written code, mishandling personal data under UK GDPR, missing or copied terms and privacy policy, and breaking the licence terms of the AI tool or the code libraries it pulled in. Each is easy to handle early and awkward to fix when a customer, buyer or regulator asks.
The longer answer
Who owns what the AI wrote
For a typical AI-assisted project you own your code, because you directed it, reviewed it and edited it. The unclear cases are code generated almost entirely on its own. UK law handles this differently from most countries. Also check your AI tool's terms about who owns its output. It matters most before you sell the business, take investment or sign a client contract.
Personal data
If your app collects names, emails or anything that identifies a person, UK GDPR applies, even for a side project. In practice that means knowing what you collect and why, keeping it secure, having a lawful reason, and being able to delete it on request. It's more manageable than it sounds.
Terms and privacy policy
You need a privacy policy once you collect personal data, and terms of service once you take money. Copying someone else's invites trouble: it won't match what your app does. AI can draft a starting point, but you have to check it says true things about your app.
Licences you didn't read
AI-generated code can include open-source libraries with their own conditions. Most are permissive; a few have obligations if you distribute the software. Your AI tool also has usage terms. Skim both, and keep a list of what your app depends on.
Other things worth a thought
Taking payments brings its own compliance jobs. Insurance may be worth having once you have paying customers. Neither is dramatic, both are easy to put off.
Learn more on Qeetoto
Go deeper with who owns the code when you build with AI coding tools, GDPR for a one-person SaaS, terms of service and privacy policy for an indie app and business insurance for a side project.
Everything on Qeetoto is free to read. No sign-up, no paywall. Questions? Get in touch.