About

Legal advice for technology-led decisions.

I combine law, digital regulation and business judgement to support technology projects, implementation work and negotiations.

Approach

Law should help decisions, not stop projects.

MK Legal was created for companies that need legal advice aligned with the pace of technology projects, regulatory pressure and responsibility for business outcomes.

I do not treat law as a separate layer of documents. A useful recommendation should structure risk, identify workable options and support conversations with business, technology teams, suppliers and regulators.

Modern meeting room
Modern workspace

How I work

The key risk often sits between specializations.

A technology contract may involve data, intellectual property, liability for outcomes, supplier security and regulatory obligations at the same time. That is why I analyse matters more broadly than a single label suggests.

  • clear recommendations instead of generic risk catalogues,
  • language that works for lawyers, boards and business teams,
  • solutions that can be used in negotiation and implementation,
  • a combined compliance, technology and operational perspective.

Experience

Experience as a foundation for client work, not a CV.

My background includes work for international technology organisations and projects involving aviation, intellectual property, data protection, cybersecurity and digital regulation. In practice, this means connecting legal requirements with how a product, sales process, supplier relationship and organisation actually operate.

I advise on matters where law meets technology: AI governance, IT contracts, licences, data transfers, cybersecurity regulation, IP protection, negotiations and implementation.

Principles

What good legal advice should provide

Clarity

The client should know what can be done, what should be avoided and which decisions require business approval.

Practicality

Documents should work in negotiations, implementation and disputes, not only look correct in a compliance folder.

Responsibility

Risks must be named honestly, but the recommendation should still lead to action.

Let’s discuss your project.

Describe the topic and check how I can help.

Contact me