Skip to content
DEEN

Lawyer for start-ups – IT contracts, trade marks & GDPR

For founding teams with digital business models – from contracts and trade mark protection to GDPR (DSGVO) implementation. We advise on start-up law and company formation – as lawyers for founders of digital business models.

Cover image start-up advice: formation, financing and contracts – advice from ITMR Rechtsanwälte
Fachanwalt (certified specialist lawyer)for IT law
Düsseldorf & Hamburgtwo offices
nationwideAdvice for businesses
5,0/5 Google · 167 reviewsWe do not check reviews of us on other platforms that we do not quote verbatim for authenticity. They may therefore also come from people who are not our clients. The rules of the respective platform apply. Reviews that we quote verbatim on our website, by contrast, have been checked for authenticity within the meaning of Section 5b(3) UWG (German Act against Unfair Competition): we compared the reviewers’ names with our client register. We also asked the respective platform to check the reviews for authenticity.Period: October 2016 to date · As of: 28 October 2026
Practice area start-up advice

Which legal building blocks digital start-ups really need before launch and growth

With its start-up advice, ITMR Rechtsanwälte creates the legal structure for digital business models at the interfaces of IT law, trade mark law, GDPR, contract architecture, platform logic and data strategy.

Start-up advice combines information technology law (IT-Recht), trade mark law (Markenrecht) and the General Data Protection Regulation (GDPR, German: DSGVO). This is exactly where the gaps arise in the early phase that later make product launches, investor reviews, larger customer contracts or forced rebrandings expensive. Before market launch, you can go through the most important legal construction sites with the Go-live Legal Launch Board.

This page is aimed at founding teams, start-ups, agencies, platform operators, software and data companies, investors, executives and other professional market participants. The focus is on economically relevant decisions before go-live, in sales and in scaling rather than typical consumer cases. The Business Model Mapper shows at a glance which areas of law your digital business model touches.

Responsible for content: Jean Paul P. Bohne, Fachanwalt für IT-Recht (certified specialist lawyer for IT law), Fachanwalt für Urheber- und Medienrecht (certified specialist lawyer for copyright and media law), AI Officer (DEKRA), reviewed on 23 October 2026 (German version)

Quick start: what is your matter about?

Your contact: Jean Paul P. Bohne, LL.M., MM

Partner, certified specialist lawyer for copyright and media law and for IT law (Fachanwalt für Urheber- und Medienrecht, Fachanwalt für IT-Recht).

Send start-up enquiry

What happens after your enquiry?

After your enquiry, we will get back to you within 24 hours on working days. The first contact is free of charge. You will receive an explicit notice before any costs arise.

  1. A short description is enough. Describe your business model, phase and planned launch. Pitch, contracts and trade mark ideas are helpful.
  2. Receipt and initial sorting. We assess the enquiry on the basis of the project described, the documents and the apparent goal. Deadlines and dates should be clearly recognisable.
  3. Suitable starting point and cost range. We clarify whether an initial consultation, a service package or a specific mandate is the next step. As soon as the scope of the review is clear, we tell you the cost range – before work begins.
Practice

Typical cases from our practice

The following scenarios are abstracted and simplified. Which solution holds up always depends on the specific facts and the contractual situation.

Launch

SaaS before go-live

Starting point
A founding team is planning its market launch.
Key difficulty
Terms and conditions (AGB), data protection and trade mark are open.
Our work
We prioritise the legal building blocks.
Work result
A launch on a sound basis.

Simplified example.

Enterprise

Major customer contract

Starting point
A corporate group wants to use the software.
Key difficulty
Liability and data processing are disputed.
Our work
We review the contract and the data processing (AV) rules.
Work result
A robust contract conclusion.

Simplified example.

Typical constellation from practice

Before the financing round

Typically, it starts like this:
An investor announces due diligence.
The hurdle:
Chains of title and contracts have gaps.
How we proceed:
We organise the documents and close the gaps.
What you have in hand:
Documentation ready for negotiation.

Simplified, typical example without reference to a specific mandate.

What you will have at the end

Services
ServiceConcrete resultNext step
Trade markName, logo, domainName the names and markets
ContractsTerms (AGB), SaaS, freelancersSend drafts
Data protectionGDPR set-upDescribe data flows
AIAI in the productDescribe the purpose of use
Due diligenceInvestor reviewSend data room list

In which situations start-up advice makes particular economic sense

What matters is rarely a single law. What matters are the moments when product, trade mark, data, external contributors and sales are all in motion at the same time.

Name, trade mark and public launch

You want to become visible with a new name, an app, a platform or a software product. Then trade mark law, trade mark registration, domain law and, for distinctive interfaces, design law should be considered together before the first major boost in visibility.

External developers, agencies and freelancers

The product is technically ready, but source code, designs, texts or documentation are only partly allocated by contract. Then IT contracts, copyright law and, for confidential projects, the non-disclosure agreement become business-critical.

Website, software as a service and platform operation

Before go-live, general terms and conditions (AGB), terms of use, service descriptions, liability logic and the external data protection side must work together properly. This applies to classic websites as well as software as a service, apps, creator models and marketplaces.

Investor review, enterprise deal and growth

As soon as investors, strategic partners or larger customers carry out reviews, the chain of title, contracts, security organisation, data processing, open source software and access structures become visible. This is precisely when it becomes clear whether founding momentum has already been translated into a robust legal structure.

Practical risk of the early phase

It rarely becomes expensive because of a single section of a law. It becomes expensive when product, trade mark, website, tracking, developer contracts and responsibilities stand side by side at different levels of maturity and must all be tightened up at the same time under time pressure.

Which legal building blocks should really be in place before the launch

Not every detail has to be finished before the first major roll-out. However, some building blocks should be robust, because otherwise they immediately set back sales, due diligence or later product decisions.

Signs, domain and market presence

Check early whether company name, product name, domain and visible design fit together. For in-depth questions, at ITMR the main next steps are trade mark law, registering a trade mark, domain law and design law. For a first basic orientation, the article What is a trade mark and what are its advantages? (in German) also helps.

Product contract, chain of title and exploitability

What matters are clear rules on scope of services, acceptance, changes, liability, support, exit and rights of use. At this level, IT law, IT contract / software contract, drafting terms and conditions (AGB) and, for content or code questions, copyright law are the main supports. For further reading, see Contract drafting in IT law (in German).

Data, data protection and new digital regulation

Anyone processing user, employee or business data needs a robust line on transparency, roles, legal bases, tracking, technical and organisational measures and service provider chains. Depending on the business model, the main areas here are data protection law, data law, artificial intelligence and cybersecurity.

Sales, claims and operational external communication

Growth often fails less because of the product than because of exaggerated statements, vague service promises or inconsistent documents. At this level, marketing law, product advertising, competition law and, for e-mail sequences, the Newsletter Marketing Check are the obvious next steps.

Official working aids for the first preliminary check

Helpful resources are the guidance of the Deutsches Patent- und Markenamt (German Patent and Trade Mark Office) on trade mark searches (opens in a new tab), the official information of the German Patent and Trade Mark Office on examination and registration (opens in a new tab), the search of the European Union Intellectual Property Office (opens in a new tab), the official text of the General Data Protection Regulation (opens in a new tab), Regulation (EU) 2024/1689 on artificial intelligence (opens in a new tab) and the Data Act (opens in a new tab).

What should be clarified first – depending on the start-up's phase

Not every question is equally urgent on day one. What matters is which risks are already business-critical at each stage and which points must necessarily be in place before visibility or negotiation.

Before the public launch⌄

In this phase, what counts above all is freedom to use the signs, the chain of title and robust external communication. This applies in particular if the name, website, pitch deck, app store presence or first campaigns are already prepared.

After the first customer and user data⌄

As soon as real data flows, tracking, support processes or automated analyses start, data protection and governance move to the fore. Then it is no longer enough just to put a privacy policy online.

Before investor review, a larger customer contract or ongoing support⌄

At the latest before due diligence, an enterprise contract or permanently recurring questions, the documents should exist and at the same time be consistent, documented and ready for negotiation.

For data- and AI-driven start-ups, the classic early-phase logic is often no longer sufficient

Anyone who works with user or business data, uses automated functions or builds on platform and cloud structures must organise roles, data flows, contract architecture and governance properly earlier than many founding teams expect. This is precisely why start-up advice should not stop at the privacy policy and terms and conditions here.

Which further topics at ITMR really take you further afterwards

A strong start-up page does not win by repeating every neighbouring area in full. What matters is that it opens the right follow-up page in the right problem context.

Name, product designation and protection strategy

When conflicts between signs, scope of protection, domains or distinctive interfaces become economically relevant, the way leads to trade mark law, registering a trade mark, domain law and design law.

Product contract, development and platform terms

For development projects, software as a service, licence chains, service specifications and operational documents, IT law, IT contract / software contract, drafting terms and conditions (AGB) and, for confidential projects, the non-disclosure agreement are the supports.

Data protection, tracking and data transparency

As soon as personal data, tracking, rights of access or data breaches are at issue, the further work should run via data protection law, data protection set-up and, for website front ends, via privacy policy and website review.

Data access, artificial intelligence and new product regulation

For data-based cooperations, connected products or artificial intelligence, data law, implementing the Data Act, artificial intelligence and, for governance questions, compliance take you further.

Open source software, enterprise review and technical supply chain

When third-party components, copyleft risks, licence terms or build processes requiring documentation become relevant, open source law and open source compliance belong in the preparation early on. Especially in due diligence and with larger customer contracts, this point often becomes relevant later than expected – and then all the more expensive.

Helpful articles for preparation

Anyone who wants to read up in advance will find solid follow-ups in What is a trade mark? (in German), Contract drafting in IT law (in German), ChatGPT and AI in companies (in German) and MG4 and open source (in German).

Which mistakes catch up with start-ups later in due diligence and negotiations

Many problems arise less often from a single legal mistake than from several small gaps that coincide at the wrong moment.

  • The product name is used publicly before the trade mark situation, classes and domains have been seriously checked.
  • External developers or agencies were paid, but the transfer of rights of use, source code, design files or documentation is not properly regulated.
  • Terms and conditions, terms of use or data protection texts were copied from other business models and do not fit your own service.
  • Tracking, newsletters, social media advertising and claims go live although data protection, competition law and operational approvals do not fit together.
  • Open source software, third-party modules or external tools are used productively without seriously examining the licensing and documentation consequences.
  • Domains, cloud access, repositories or administrator roles are in fact held by individuals or service providers rather than robustly by the company.
  • The data room for investors or larger customers is only put together once the first critical query has already come in.

Particularly underestimated: registration does not replace a conflict check

Anyone who only registers a name but does not seriously check earlier rights shifts the risk into opposition, cancellation or forced rebranding. This is precisely why the trade mark question should be seriously clarified before public visibility and not only after the first campaigns.

How ITMR supports start-ups in practice

The right form of support depends less on company size than on pace, risk and team depth. For some cases, a focused early-phase check is enough; others need ongoing structural work.

Quick start before launch or investor meeting

If name, product, website, first contracts or a short-term investor meeting are coming up, a focused start via a start-up meeting (Start-up-Gespräch) or an initial consultation (Erstberatung) is often the most sensible first step.

Building up core documents robustly

If documents, chain of title and product logic are to be set up in a structured way, the concrete work streams usually run via IT contract / software contract, drafting terms and conditions (AGB), registering a trade mark and, for data-driven models, via data protection set-up.

Resolving special questions in a technically sound way

For open source software, artificial intelligence, data access, platform obligations or security questions, a precise in-depth review is often more important than a general full review. The main follow-ups here are open source compliance, artificial intelligence, data law and cybersecurity.

Ongoing support instead of repairs under time pressure

For recurring questions on contracts, data, marketing, intellectual property rights or compliance structures, an ongoing solution via the outsourced legal department or service packages is often more economical than a series of isolated individual mandates.

Jean Paul P. Bohne, LL.M., MM

IT law, trade mark law, copyright law, data protection, artificial intelligence

Particularly suitable when contracts, intellectual property rights, platform logic and data-driven product questions interlock.

Andreas Buchholz

IT law, data protection, e-commerce, litigation, start-ups

Particularly strong in product and contract logic, e-commerce structures and contentious negotiation or enforcement situations.

Dominik Skornia, LL.B.

Data protection law, IT law, data law

Particularly useful when data protection, data flows and digital contract or product questions come together in one mandate.

If the launch or review is already under way

Then what is usually needed is clear prioritisation rather than an abstract overall treatise: what must become robust immediately, what can go into the next sprint and which special subject matter must be examined in depth in a targeted way?

Continue to Close due diligence gaps before the next round and Check ongoing support for the start-up.

Glossary

Key terms

Due diligence
Legal review by investors or buyers.
GDPR (DSGVO)
Datenschutz-Grundverordnung (General Data Protection Regulation, GDPR).
Chain of rights
Proof that rights of use lie fully with the company.
Rebranding
Forced change of name or trade mark.

These terms explain the language used on this page. What matters is always the specific individual case.

Provisions

Provisions and reliable sources

The following statutory provisions and regulations are cited on this page.

Basics
ProvisionContentPractical significance
DSGVODatenschutz-Grundverordnung (General Data Protection Regulation, GDPR)Data processing in the product.
FAQ

Frequently asked questions about start-up advice

The following answers provide a sound framework for typical founder situations. What remains decisive, however, is always the business model, chain of title, data flow, product architecture and negotiating position.

Are you about to launch, sign a larger customer contract or undergo an investor review?

Then the next sensible step is usually clear prioritisation along the business model and the most visible risks rather than a blanket full review.

Continue to Discuss a specific case with ITMR and Sort out the early phase or an urgent case first.

Does every start-up need a trade mark immediately?

Not necessarily on day one. But at the latest before the name, app, platform or product is rolled out publicly and visibly with budget, it should be clarified whether the sign, classes and territory of protection hold up. For many digital models, name, logo and domain are economically relevant assets early on. A later rebranding often costs considerably more than a proper preliminary check.

Are terms and conditions and a privacy policy enough to start?

Often not. Terms and conditions (AGB) and a privacy policy are only part of the legal outer shell. Depending on the business model, product and project contracts, developer or agency contracts, terms of use, data processing agreements, confidentiality rules, approval processes and robust technical and organisational measures are added. A software product, a marketplace and a creator platform do not need the same documents.

What do investors or enterprise customers check first?

The focus is on robustness and documentation: who owns the name, code, design, content and data sets? Are external developers properly integrated? Do contracts, security organisation and data protection structure hold up? Are intellectual property rights, domains, access and responsibilities documented in a traceable way? Unclear chains of title and disorganised processes almost always slow down transactions.

What is particularly critical with freelancers, agencies and external developers?

Particularly critical is the assumption that payment automatically transfers all rights to the company. Stated so generally, this is not true. The scope of rights of use, editing, sublicensing, source code, design files, documentation, handover, confidentiality and cooperation in handovers should be expressly regulated. Equally important is who actually controls domains, cloud access, repositories and administrator roles.

When does regulation on artificial intelligence and data become relevant early on?

Earlier than many teams assume. As soon as the product trains with user or business data, generates content, derives recommendations, automates decisions, reads device data or depends heavily on platform and data access rules, pure data protection building blocks are often no longer sufficient. Then roles, data flows, contract architecture, transparency and governance must be considered early so that the roll-out does not later have to be scaled back organisationally or technically.

Next step

Setting up your start-up on a sound legal footing

Note on the legal status

Legal status: 23 October 2026. This overview provides initial orientation and does not replace a review of the specific case.

Responsible for content: Jean Paul P. Bohne, Fachanwalt für IT-Recht (certified specialist lawyer for IT law), AI Officer (DEKRA), reviewed on 23 October 2026 (German version)

Responsible lawyer for start-up advice at ITMR

Jean Paul P. Bohne, LL.M., MM

Rechtsanwalt (attorney) | Partner | Business mediator

  • Fachanwalt für Urheber- und Medienrecht (certified specialist lawyer for copyright and media law)
  • Fachanwalt für IT-Recht (certified specialist lawyer for IT law)
  • AI Officer [DEKRA]
  • Certified Information Privacy Professional/Europe [CIPP/E]
  • Cert. Information Privacy Manager [CIPM]
  • External data protection officer [TÜV]
  • Data protection officer [TÜV]
  • Data protection auditor [TÜV]
  • IT compliance manager [TÜV]

T: +49 211 737547-70
E: bohne@itmr-legal.de

Profile Bohne

Andreas Buchholz

Rechtsanwalt (attorney) | Partner

  • Fachanwalt für IT-Recht (certified specialist lawyer for IT law)
  • External data protection officer
  • Data protection officer [TÜV]
  • E-commerce manager [IHK]

T: +49 211 737547-70
E: buchholz@itmr-legal.de

Profile Buchholz