AI projects & vibe coding · One-off engagements · Bordeaux & remote
Your vibe-coded AI project is ready. Let's get the legal side right before launch.
You built your app with Lovable, Bolt, Replit, Cursor or Claude Code, without being a lawyer or a developer. The prototype works, your first customers are signing up… but you still have no privacy policy, no terms of sale and no plan for GDPR and AI Act compliance. I review your documents, assess your risks and help you put everything in place, in plain language.
Sound familiar?
- Your terms of sale and privacy policy were generated by AI or copied from another website, and you have no idea whether they hold up.
- Your app sends user data to OpenAI, Anthropic or Mistral, and you don't know what the GDPR requires.
- You keep hearing about the AI Act but can't tell whether it applies to your project.
- A customer, investor or partner asked you for legal guarantees you couldn't provide.
Why legal issues stall the move from proof of concept to product
Vibe coding tools can produce an app in a few days. They don't produce a contractual framework or regulatory compliance. While the project is just a demo, the stakes are low. From your first real user and your first payment, legal obligations apply.
Generic documents
Terms of sale, terms of use and legal notices copied or generated, which describe neither your service, nor your prices, nor your commitments.
Poorly governed personal data
The GDPR applies from your first user: informing people, legal basis, retention periods, security.
AI providers in the loop
AI model, hosting provider, no-code tools: every provider that receives data must be covered by a contract, including outside Europe.
An AI Act status to determine
The EU regulation on AI imposes obligations that depend on the risk level of your use case and on your role. You first need to know where you stand.
Uncertain intellectual property
Who owns the generated code? Can you sell the app or license it? The terms of the tools you used matter.
Undefined liability
When the AI gets it wrong, who is liable? Without suitable terms, nothing sets out what you promise or what you answer for.
What I do for your AI project
Three legal workstreams to go from prototype to product, scaled to what your project actually needs.
Review your legal documents
Do your current documents really protect you and your users?
- —Review of your privacy policy
- —Review of your terms of sale, terms of use and legal notices
- —Consistency with how the app actually works
- —Corrections ranked by priority, explained without jargon
Assess your legal risks
Know where you are exposed before launch, and where to start.
- —GDPR compliance: data, processors, transfers outside the EU
- —AI Act assessment: risk level and obligations
- —Intellectual property in generated code and content
- —Risk map ranked by priority
Put your documents in place
Documents drafted for your product, ready to go live.
- —Drafting of your privacy policy, terms of sale and terms of use
- —Record of processing activities and data processing agreements (DPA)
- —AI transparency notices and cookie management
- —Support until they are integrated into your app
The legal documents of an AI product ready for launch
Not every project needs all of them: the diagnosis is there to determine which ones you need, and in what order.
- Privacy policy
- It tells your users what data is collected, how it is used, who receives it (AI providers included) and what their rights are. Mandatory as soon as you process personal data.
- Terms of sale
- They govern the sale or subscription: price, payment, term, cancellation, right of withdrawal, warranties. Essential as soon as your service is paid.
- Terms of use
- They set the rules for using the service, prohibited uses, the limits of the AI and each party's liability.
- Legal notice
- It identifies the publisher and the hosting provider of the website or app. Mandatory for any professional online service in France.
- Cookie policy and consent management
- Required as soon as you use non-essential trackers, for example for advertising or some audience measurement.
- Data processing agreements (DPA)
- They govern the providers that process data on your behalf: hosting provider, AI model provider, e-mailing tool.
- Record of processing and impact assessment
- The record documents your data processing. A data protection impact assessment (DPIA) is required when processing is likely to pose a high risk to individuals.
- AI Act documentation
- Informing users when they interact with an AI, labelling generated content and, depending on the risk level, more extensive documentation.
One-off support engagements
No subscription and no long-term commitment: a clear scope and a fixed fee agreed in advance in a fee agreement.
Legal diagnosis
To know where you stand
A quick review of your project to identify what is missing and decide on next steps.
- Review of your existing documents
- Main GDPR, AI Act and contractual risks
- Verbal debrief and written summary
Launch documents
To open your service to the public
The contractual foundation of your product, drafted for your app and your business model.
- Privacy policy
- Terms of sale and terms of use
- Legal notice and cookie policy
- Guidance on integrating them into your app
GDPR and AI Act compliance
To reassure customers and investors
In-depth compliance work, proportionate to the size of your project and its risks.
- Record of processing and data processing agreements
- AI Act assessment and related obligations
- Impact assessment (DPIA) where required
- Action plan ranked by priority
How an engagement works
You don't need to speak legalese. You need to know what is mandatory, what is risky and what to do next.
- 01
First conversation
You present your project, its business model and your launch timeline.
- 02
Fixed-fee proposal
I send you a fee agreement setting out the scope, the deliverables and the amount.
- 03
Analysis and drafting
You walk me through the app. I review the data processed, the providers involved and your users' journey.
- 04
Debrief and roll-out
I hand over the documents and priorities, explained without jargon, and help you put them online.
A lawyer who knows digital products from the inside
Before founding Adella Avocat in Bordeaux, I worked as an in-house lawyer and then as head of legal and compliance, notably at a software publisher and in e-commerce. Terms of sale, SaaS contracts, data protection: I know these topics from the product side, with their time and budget constraints.
My approach is the same for a vibe-coded project: focus on what matters, match the effort to the actual risk and give you documents you understand.

Frequently asked questions
My app was vibe-coded: do I really need terms of sale and a privacy policy?
Yes, as soon as you have real users. A privacy policy is mandatory as soon as you collect personal data, and an e-mail address is enough. Terms of sale or terms of use become essential as soon as the service is open to the public or paid. The tool used to build the app does not change these obligations.
Can I use terms of sale generated by AI or a template found online?
They are a starting point, rarely a reliable document. A template knows nothing about your service, your prices or your providers. Unsuitable clauses, or clauses that breach consumer law, can be set aside by a court and expose you to penalties. I can review and correct your existing documents rather than rewrite everything.
Does the AI Act apply to my project?
The EU regulation on artificial intelligence covers those who develop or use AI systems in a professional capacity. Obligations depend on the risk level of the use case and on your role, provider or deployer. Many apps are mainly subject to transparency obligations, such as telling users they are interacting with an AI. Other uses, for example in recruitment, credit or education, face much heavier requirements. The diagnosis determines where you stand.
I use the OpenAI, Anthropic or Mistral API: what does the GDPR require?
If personal data is sent to the model, the AI provider generally acts as your processor. You then need a data processing agreement, to check where the data is processed, to cover transfers outside the European Union and to inform your users in your privacy policy. You should also check whether your data is used to train the models.
Who owns AI-generated code?
It depends on the terms of the tool used and on the extent of human creative input. Most tools let you use the code they produce, but copyright protection is not guaranteed. It is worth checking before a fundraising round, a sale of the business or signing a major customer.
How much does an engagement cost?
Each engagement is billed at a fixed fee agreed in advance in a fee agreement, based on the format chosen and the complexity of the project. Details are on the Fees page.
Do you work remotely?
Yes. The firm is based in Bordeaux and engagements work very well by video call, anywhere in France. An on-screen demo of the app and access to your documents are all it takes to get started.
Launch your AI product on solid legal ground.
Describe your project in a few lines: what the app does, the tool you used, where you are and what is missing. I will get back to you quickly to discuss it.