Back to practice areas
MRŞ · Law & Mediation

IT & Technology Law

The legal framework for software, SaaS, digital platforms and technology contracts. We begin with the documents specific to the matter, whether clarifying responsibilities before a transaction or assessing an existing dispute.

01 /

What does this cover?

Software, SaaS, platform and technology supply agreements are reviewed for use rights, data processing, service levels and liability. Technical findings need to be understood in their legal context.

  • Software and SaaS contracts
  • Licensing and technology supply
  • Legal assessment of cyber incidents
  • Hosting and infrastructure contracts
  • Publication, access and service outages
  • Domain and admin-account handover
  • Cloud/SaaS portability and exit planning
  • Cyber incidents and digital evidence
02 /

How do we approach the matter?

The product and the parties’ roles are clarified. Agreements, licences and technical scope inform the review of delivery, support, security and obligations at the end of the relationship.

What to prepare before your appointment

  • Software or service agreement
  • Technical scope and licence terms
  • Relevant incident and communication records

Before your appointment, prepare a short chronology, available documents and the support you need. Do not send identity numbers, health information or sensitive case documents through the website.

Frequently asked questions

01Is price the only issue in a SaaS agreement?

Scope, access, support, data return, intellectual property, liability and termination also matter. The business’s reliance on the service is relevant to the review.

02Does commissioning software transfer all intellectual property rights?

Rights to use, modify, reproduce or transfer are assessed under the agreement and applicable law. Technical delivery and transfer of rights are distinct matters.

03Which documents should I prepare for the initial review?

Software or service agreement; Technical scope and licence terms; Relevant incident and communication records. Organise these alongside a chronology. Agree how to share sensitive documents before the meeting.

04How are the next steps determined?

The product and the parties’ roles are clarified. Agreements, licences and technical scope inform the review of delivery, support, security and obligations at the end of the relationship.

05What should a hosting agreement clearly cover?

Define the service scope, availability target, maintenance and outage notice, backup responsibility, data return/deletion, security, subcontractors and exit process. The provider’s and site owner’s duties should be allocated expressly.

06What if an agency will not publish my website or hand over admin access?

Review delivery, payment, source-code, domain and account terms. Preserve invoices, acceptance records and correspondence; any access or handover demand depends on the contract and proven rights.

07How can I recover data when a cloud or SaaS service ends?

Agree in advance on export format, access period, backups, deletion confirmation and migration assistance. Where personal data is involved, assess controller/processor roles and transfer requirements under the applicable data-protection rules.

08What are the first legal steps after a cyberattack or data breach?

Secure the systems while preserving logs, notices and evidence integrity. Identify affected data and parties, then assess contractual notices and whether a statutory data-breach notification and deadline apply.

Relevant legislation and official sources

This content concerns legal matters in Türkiye. Foreign law and cross-border transactions require separate assessment.

Content is for general information and is not personal legal advice. Contact alone does not establish a lawyer-client relationship.

IT & Technology Law | MRŞ Hukuk