OVIOS: who owns what we build with Claude

Short answers for the partners · 7 Oct 2026

We own the code, the business and the customer data contracts. Claude is a tool, like Word. Anthropic gets no share, no rights and no say.

1Ownership and IP

Does what Claude writes belong to us? Yes. Anthropic hands all its rights in the output to us. We pay a subscription; there is no royalty, licence fee or stake. How we know: Anthropic's Commercial Terms of Service assign outputs to the customer.
Can Anthropic claim the business or stop us? No. The code is ordinary TypeScript and SQL in our own GitHub, running on servers we pay for. Drop Claude tomorrow and OVIOS keeps running; any developer can carry on. How we know: nothing in the app needs Claude Code to run, and Ovi's AI model can be swapped.
What if someone says the code copies theirs? On business plans, Anthropic defends us against copyright claims about Claude's output used within its terms. How we know: the IP indemnity in Anthropic's Commercial Terms.
Is AI-written code protected in the UK? Yes. Copyright goes to whoever arranged for the work to be made. We decide what to build and review every change. How we know: Copyright, Designs and Patents Act 1988, s9(3).
The real risk isn't Claude, it's people. Founders and contractors who aren't employees keep copyright in their work unless they sign it over to the company (CDPA s11). Fix: IP assignments, below.

2GDPR: how we stay protected

Who is responsible for the data? Each installer controls its own customers' data; OVIOS only processes it on their instructions, the same as Salesforce, HubSpot and Pipedrive. How we know: UK GDPR, Article 28.
Does Anthropic get our data? Claude Code never sees customer data; it only writes code. Ovi sees one task's records in one workspace. Business terms forbid training on our data. How we know: Anthropic's Commercial Terms and Data Processing Addendum.
What keeps us covered? A DPA signed by every customer, London hosting, each customer walled off, a published sub-processor list, ICO registration (from about £52 a year) and export/delete tools.

3To make it watertight

  1. Use Claude on a company Team plan, not personal accounts
  2. Put GitHub, Supabase, Cloudflare and API keys in company accounts, two directors on each
  3. IP assignments signed by all three founders and any contractor, past and future work
  4. Terms, Privacy Policy and DPA from a SaaS solicitor; register with the ICO
  5. Register the OVIOS and Ovi trade marks with the UK IPO
  6. Nightly backup of code and database outside our main suppliers

Plain-English summary, not legal advice; have the SaaS solicitor confirm. Full detail: "OVIOS – Partner Q&A – Data, Hosting, Ownership and Scale".