OVIOS in plain English

Ownership, IP, data protection and selling the product · 7 Oct 2026

We own the code, we own the IP, and we're free to sell OVIOS. Anthropic gets no share and has no say.

1Why we own the code fully

Anthropic's business terms say the customer owns what Claude produces, and Anthropic hands over any rights it might have. The code sits in our own GitHub and runs on servers we pay for. If we stopped using Claude tomorrow, OVIOS would keep running and any developer could carry on.

Commercial Terms, section B: "Customer… owns its Outputs. Anthropic… assigns to Customer its right, title and interest (if any) in and to Outputs."

2We own our IP

In the UK, copyright in computer-generated work belongs to the person who made the arrangements for it to be created. That's us: we decide what to build and review every change. On the business plans, Anthropic will also defend us if someone claims Claude's output copies their work.

Copyright, Designs and Patents Act 1988, s9(3) · Commercial Terms, section K: IP indemnity. It doesn't cover code we change ourselves or our trade marks.

3We have full licence to sell the product

Because we own the code, we can sell OVIOS, license it, charge what we like or sell the whole company. There's no royalty and no permission needed. Ovi using Claude inside OVIOS is a normal, allowed use of Anthropic's API. The only limits: we can't resell access to Claude itself or use it to build a rival AI model.

Commercial Terms, section D.4: no reselling the Services or building competing AI models without approval.
One thing to check: the business terms above apply to Claude Team, Enterprise and API plans. The Pro and Max plans use consumer terms, which say not to use Claude for business purposes. All OVIOS work should be done on a company Team plan.Claude Code docs, Legal and compliance · Consumer Terms, section 11

4What we're liable for under data protection law

Each installer controls its own customers' data. We're the processor: we hold it and use it only as they instruct. Our job is to keep it secure, keep each business separate, use trusted suppliers and tell the customer quickly if something goes wrong. We're only liable if we break those processor duties or go beyond the customer's instructions. Why they collect data, their privacy notices, marketing consent and ICO breach reports are the installer's responsibility. Anthropic can't train on our data.

UK GDPR: Article 28 (processor duties), 32 (security), 33(2) (tell the controller of a breach), 82(2) (limits on processor liability) · Commercial Terms, section B: no training on customer content

5We're not the first to build this way

Building software with Claude is now normal practice for companies of every size, from startups to the Fortune 10.

300,000+
business customers using Claude (Anthropic, Sept 2025)
33%
of Claude Code work is startups building products (Anthropic, Apr 2025)
8 of 10
Fortune 10 companies use Claude (reported 2026)

6Actions: what we need to do

Step 1 · Set up the company

  • Register OVIOS Ltd at Companies House and open a business bank account and card
  • Sign a founders' agreement: shares, roles, and what happens if someone leaves
  • Check the name is free: run a trade mark search before spending on branding

Step 2 · Secure the name and email

  • Buy the domains (e.g. .com and .co.uk) in the company's name, with two-step sign-in
  • Set up Google Workspace on the domain for OVIOS emails: one each, plus hello@ and admin@
  • Get a business password manager so the three of us share logins safely

Step 3 · Put the tools in OVIOS's name

  • Start a Claude Team plan with our OVIOS emails, paid by the company card
  • Open an Anthropic API account for Ovi, owned by the company, with a monthly spend limit
  • Move the code into an OVIOS GitHub organisation, plus Supabase and Cloudflare, with two owners on each

Step 4 · Lock in ownership and protection

  • Sign IP assignments: all three founders and any contractor, covering past and future work
  • Register the OVIOS and Ovi trade marks with the UK IPO
  • Turn on nightly backups of the code and data, stored outside our main suppliers

Step 5 · Before the first paying customer

  • Get the legal documents from a SaaS solicitor: Terms, Privacy Policy and a Data Processing Agreement
  • Register with the ICO and publish our list of suppliers who handle data
  • Get insured: professional indemnity and cyber cover
  • Give each installer its own sealed-off workspace in the app

Plain-English guide, not legal advice; have the solicitor confirm. Sources, checked 7 Oct 2026: Anthropic Commercial Terms (effective 17 Jun 2025) · Consumer Terms · Claude Code legal and compliance · Anthropic, 300,000 business customers · Anthropic Economic Index · Fortune 10 figure (third-party) · CDPA 1988 s9 · ICO UK GDPR guidance