Skip to content
+90 531 883 33 88

PRODUCT · CONTRACTS · REGULATORY COMPLIANCE

Digital Technologies and AI

From software and AI projects to payment and crypto-asset business models: legal support on contracts, data, permits and disputes.

Scope of the service

The legal framework of a technology product is set by how it actually works.

Digital technology law covers the rights and obligations arising from developing, licensing, launching and using a product. In AI and fintech projects, data, intellectual property, contracts, consumer protection, competition and sector rules may apply at the same time.

“Platform,” “artificial intelligence” or “digital wallet” alone does not determine legal status. What matters is the transaction the product performs, on whose behalf it acts, the flows of data and funds, its users and its target countries. Güneş & Güneş Law Firm carries out this review together with product design, investment, operations and dispute stages.

Where are you in the process?

If there is an incident or a notice, keep its date and the existing records. For a step with a deadline, do not wait for the consultation or for the firm's reply.

Areas of practice

Our legal services in digital technologies

Find the group that matches your need: contracts, permits, data, investment or disputes. Each engagement is scoped to the specific product and the parties’ circumstances.

Business model and investment

Market entry, founder rights, investment rounds, legal due diligence and cross-border structuring.

Review the scope

Software and cloud

Development, acceptance, licensing, open source, source code, service levels and exit from a provider.

Review the scope

Artificial intelligence

Use case, data and model rights, human oversight, biometrics and corporate policies.

Review the scope

Fintech and payments

Fund flows, the scope of the permit from the Central Bank of the Republic of Türkiye (TCMB), electronic money, digital wallets and API arrangements.

Review the scope

Crypto and blockchain

Platforms, custody, tokenization, smart contracts, customer assets and compliance with MASAK.

Review the scope

Data and cybersecurity

KVKK, cross-border transfers, cloud access, data breaches, incident response and notifications.

Review the scope

Platforms and sectors

E-commerce, advertising, connected devices, health technologies, competition, geographic data and telecommunications.

Review the scope

Disputes and compliance

Electronic contracts, record retention, preservation of evidence, litigation, arbitration and compliance training.

Review the scope

Business model, start-up and investment

5 practice topics

Legal classification of a digital business model and market entry

For a new technology product, the first question is not only which contracts to prepare. Whether the activity is subject to a licence, permit, notification, registration or sector regulation should be determined at the start of product development.

  • Review of the business model, product flow, user roles, revenue model and data flow
  • Assessment of the boundary between a regulated activity and a technology or outsourcing service
  • Analysis of B2B, B2C, marketplace, subscription, commission, licence and pay-per-use models
  • Legal map of local rules for foreign technology products entering Türkiye
  • Risk matrix for products offered from Türkiye abroad, with review of each target country
  • Identification of permits, licences, registrations, notifications and competent authorities
  • Alignment of product terms, privacy documents and operating processes
  • Legal planning of pilots, closed betas, regulatory sandboxes and phased launches

Legal classification should be carried out while the architecture and revenue model can still be changed, not at the end of product development.

Technology companies, start-ups and scale-up structures

In technology start-ups, the company structure should be designed together with founders' rights, ownership of intellectual property, fundraising, employee incentives and possible future share transfers.

  • Determination of company type, partnership and management structure
  • Founders’ agreement and shareholders’ agreement
  • Vesting, reverse vesting, leaver and share buy-back mechanisms
  • Share transfer, pre-emption, tag-along, drag-along and exit provisions
  • Legal structuring of employee share options and incentive plans
  • Board of directors, signing authority and reserved matters
  • Transfer to the company of code, designs and content created before incorporation
  • Coordination with financial and technical advisers on technology development zone, R&D and incentive processes

Technology investments, venture capital and investment rounds

In an investment process, the investor’s management, information, liquidation, anti-dilution and exit rights matter as much as the valuation. Non-binding commercial expectations and legally binding provisions should be clearly separated.

  • Confidentiality agreement, term sheet and letter of intent
  • Legal due diligence and data room management
  • Share subscription, share transfer and shareholders’ agreements
  • Adaptation of convertible instruments to Turkish law
  • Representations, warranties, indemnities, closing conditions and liability limits
  • Founder commitments, non-compete and the chain of title to intellectual property
  • Pre-investment restructuring and capital transactions
  • Mergers, acquisitions, strategic investments and exit transactions

The financial, tax and fiscal aspects of the investment are assessed together with the relevant authorised professionals.

Technology mergers and acquisitions and legal due diligence

In technology companies, value often depends less on registration documents than on code, data, customer contracts, open-source components, key employees and third-party services.

  • Review of the company, shares, contracts and permits
  • Chain of title to intellectual property
  • Open-source and third-party licences
  • Personal data, cyber incidents and security commitments
  • Customer concentration, change of control and termination rights
  • AI model, training data and content rights
  • Fintech or crypto licence and regulatory obligations
  • Pre-closing remedies and transition services

International technology contracts and cross-border operations

  • Governing law, jurisdiction, arbitration and enforcement of decisions
  • Multilingual licence, SaaS, distribution and technology transfer agreements
  • Data transfers, export controls and sanctions risks
  • Services and intellectual property arrangements between group companies abroad
  • Offering products in Türkiye by foreign companies and local agreements
  • Expansion abroad of companies based in Türkiye
  • International technology and investment disputes

Software, cloud and intellectual property

6 practice topics

Software development, project, integration and outsourcing agreements

In software projects, if the deliverable, acceptance criteria, intellectual property rights, change requests, third-party components, security and maintenance obligations are not clear, project management can easily turn into a dispute.

  • Agreements for software development, mobile application and web projects
  • Agile development, sprints, backlog, milestones and change management
  • Linking technical specifications, acceptance tests and delivery criteria to the contract
  • Fixed-price, time-and-materials, success-based or hybrid fee models
  • Delivery of source code, object code, documentation and development tools
  • Source code escrow arrangements and business continuity
  • Maintenance, support, updates and release management
  • Subcontractors, personnel changes and key personnel provisions
  • Delay, defects, performance shortfalls, contractual penalties, termination and transition support

SaaS, cloud, hosting and managed service agreements

In cloud and SaaS relationships, the location of data, service availability, dependency, backup, sub-processors, price changes and exit conditions should be specifically regulated.

  • SaaS, PaaS, IaaS, hosting and managed service agreements
  • Service level, availability, maintenance window and service credits
  • User, administrator and API usage limits
  • Data ownership, data portability, backup and deletion
  • Subcontractors and the sub-processor chain
  • Cross-border data transfers and the location of data centres
  • Scaling, pricing, renewal and unilateral change provisions
  • Suspension, termination, exit support and reduction of supplier dependency

Software licences and intellectual property rights

  • Fixed-term, perpetual, exclusive or non-exclusive licences
  • Licence models based on users, devices, cores, transactions or volume
  • Authorship, transfer of economic rights and software created within an employment relationship
  • Rights in source code, libraries, databases, interfaces, documentation and algorithms
  • Adaptation, reproduction, distribution, reverse engineering and interoperability
  • Technical protection measures, licence keys and audit rights
  • Licence infringement, unauthorised use, interim measures and damages proceedings

Open-source software and third-party component compliance

  • Inventory of open-source components and licence obligations
  • Assessment of copyleft, attribution, source code disclosure and distribution terms
  • Linking the software bill of materials and supply-chain documentation to the contract
  • Usage rights for third-party code, SDKs, models, datasets and APIs
  • Open-source policy and approval processes
  • Legal review of open source in mergers, investments and product sales

The technical code scanning, component discovery and security analysis are carried out by technical experts; the legal and contractual effects of the results are assessed by lawyers.

Technology procurement and corporate purchasing

  • Tender and offer documents, request for information and request for proposal processes
  • Master services agreement, work orders and technical annexes
  • Legal review of suppliers and security questionnaires
  • Service levels, audit, subcontractor and change management
  • Business continuity, disaster recovery and exit plan
  • Price, measurement, acceptance, warranty and liability provisions
  • Reducing single-supplier dependency on technology

Protection of employees, developers and technology assets

  • Employee and independent developer agreements
  • Ownership of works, inventions, designs, code and documentation
  • Confidentiality, trade secrets and access rights
  • Non-compete and employee transfer provisions
  • Personal devices, remote work and acceptable use policies
  • Termination of employment, revocation of access and return or deletion of data
  • Key personnel and knowledge transfer plan

Artificial intelligence, models and automated decisions

3 practice topics

Artificial intelligence systems and responsible AI governance

Artificial intelligence law is not a single legislative text. Personal data, consumer, intellectual property, discrimination, product safety, contract, tort, competition, cybersecurity and sector regulations may apply to the same system together. For businesses with activities, users or markets in the EU, the scope of the EU Artificial Intelligence Act should be assessed separately.

  • Inventory of AI systems and use cases
  • Identification of provider, deployer, importer, distributor and user roles
  • Classification of prohibited, high-risk, transparency-obligated and other use cases
  • AI governance committee, allocation of responsibilities and approval mechanism
  • Risk and impact assessment, human oversight and a complaint channel
  • Model and data cards, technical documentation and decision records
  • Contractual management of accuracy, robustness, security, explainability and discrimination risks
  • Supplier assessment and AI procurement specifications
  • Acceptable AI use policy and training for employees

For matters linked to the EU, the role of the system and its risk group are assessed, as well as the date it is placed on the market and the implementation timeline, which changed in July 2026. Not every AI product is high-risk.

Generative AI, foundation models and training data

  • Corporate generative AI use policy
  • Confidentiality of input information, professional secrecy and personal data risk
  • Verification of outputs, human oversight and liability for incorrect content
  • Data use rights in training, fine-tuning and retrieval systems
  • Copyright, database right, licences and the origin of content
  • Model provider terms, output ownership and indemnity obligations
  • Contractual response to hallucination, discrimination, manipulation and security testing
  • Synthetic media, AI-generated content and deepfake transparency

Shadow AI refers to tools that employees use outside the knowledge or control of the organisation. Approved tools, access, data input, human control and incident reporting rules are set out in the use policy.

Automated decision-making, biometrics and high-impact systems

  • Automated decisions in recruitment, credit, insurance, health, education and public services
  • Profiling, scoring and behavioural prediction
  • Facial recognition, voiceprints, fingerprints and other biometric systems
  • Legal or similarly significant effects of decisions, explanation and appeal options
  • Discrimination and equal treatment risks
  • Data protection impact assessment, human intervention and record-keeping

Fintech, payments and open banking

4 practice topics

In financial technology, the function rather than the product name determines the regulatory result. Whether an application takes on money transfers, payment accounts, electronic money, digital wallets, account information, payment order initiation, crypto-asset trading or custody may lead to different regulatory consequences.

Fintech business model and regulatory boundary analysis

  • Mapping of fund flows, customer assets, transaction parties and the revenue model
  • Distinction between a technology service, a payment service, electronic money, agency and outsourcing
  • Assessment of white-label, API, banking-as-a-service and platform models
  • Separating the roles of bank, payment institution, electronic money institution and technology provider
  • Identification of licensable activities, scope extensions, notifications and permit needs
  • Legal assessment of the business model of providers not established in Türkiye, and the cross-border service and marketing risks

Payment institutions and electronic money institutions

  • Licensing and operating authorisation processes under Law No. 6493 and secondary regulations
  • Preparation of shareholding, management, capital and corporate structure documents
  • Legal assessment of the business plan, product flow, and agent and outsourcing model
  • Framework agreements, user terms, fee and information texts
  • Protection of customer funds and contractual structuring of the flow of funds
  • TCMB supervision, information requests, corrective actions and administrative sanctions
  • Changes in the scope of activity, share transfers, mergers and acquisitions
  • Business continuity, exit plan, record retention and outsourcing agreements

Incorporation and the operating licence are distinct stages. The scope of the activity, the current equity requirements and the remote identification changes of 4 September 2026 are reviewed together with the customer onboarding flow of the product.

Digital wallets, cards, mobile payments, QR and FAST solutions

  • Assessment of whether a digital wallet is a payment account, electronic money or a technical service
  • Card storage, tokenization, merchant acquiring and payment gateway models
  • Mobile payments, subscription collection, QR and instant payment solutions
  • Regulation of chargebacks, unauthorised transactions, errors, refunds and fraud processes
  • User authentication, transaction security and customer notifications
  • Agreements among the merchant, the bank, the payment institution and the technology provider

Open banking and API ecosystems

  • Legal scope of account information and payment order initiation services
  • ÖHVPS, API access, customer consent and authorisation flows
  • API use, data sharing, service level and liability agreements
  • Strong customer authentication, consent records and retention of transaction trails
  • Data responsibility between the bank, the fintech and the third-party service provider
  • Analysis of the regulatory environment for open finance and new product models

ÖHVPS 2.0.0, announced on 17 March 2026, covers card information and future-dated and recurring payment order initiation functions. Opening new functions for use does not mean that the scope of authority expands automatically.

Crypto-assets and blockchain

6 practice topics

Crypto-asset service providers

Through amendments made in 2024 to the Capital Markets Law No. 6362 and secondary regulations dated 13 March 2025, crypto-asset service providers were brought within the regulatory and supervisory remit of the Capital Markets Board (SPK). Whether the service corresponds to platform operation, custody, initial sale or distribution, transfer or another activity should be determined on the basis of the concrete model.

  • Legal preparation and follow-up of licence and operating authorisation applications
  • Assessment of founder, shareholder, manager, organisational and capital requirements
  • Contractual structure of platform, custody and transfer services
  • Segregation, custody and reconciliation of customer assets
  • Listing and delisting policies
  • Policies on orders, transactions, pricing, liquidity and conflicts of interest
  • Internal control, risk management, internal audit, record-keeping and the independent audit framework
  • Legal coordination of information systems, business continuity and proof-of-reserves processes
  • Share transfers, changes in management, outsourcing and scope extension transactions
  • SPK inspections, information requests, measures and sanction processes

Being on the SPK’s temporary List of Operating Entities does not mean that one is authorised. Transitional decision No. 18/617 of 26 March 2026, current Board decisions and the stage of the application file are checked together.

Bitcoin, Ether and other crypto-asset transactions

The legal assessment of Bitcoin, Ether and other crypto-assets varies according to the design of the asset, its purpose of use, the manner of issue and distribution, the rights promised and the service provider through which transactions are made. The terms “crypto money,” “coin” or “token” alone do not determine legal status.

  • User agreements for trading, custody, transfer and wallet services
  • Claims of unauthorised access to customer accounts, account takeover and fake transactions
  • Responsibility for private keys, seed phrases, and cold and hot wallets
  • Transfers to a wrong address, choice of chain, network forks and airdrop disputes
  • Platform outages, non-execution of orders, and liquidity and price disputes
  • Claims of fraud, phishing, fake investments and market abuse
  • Preservation of evidence, requests for records, injunctions and other interim protections
  • Coordination of the criminal, commercial, consumer, enforcement, inheritance and matrimonial property dimensions

The use of crypto-assets for “payment” purposes in Türkiye is a separate regulatory field. Under the TCMB Regulation on the Non-Use of Crypto-Assets in Payments, there are restrictions on the direct or indirect use of crypto-assets in payments and on offering services for that purpose. Trading or investment transactions should not be confused with the payment function.

Tokenization, digital asset issuance and real-world assets

  • Token models conferring securities, capital market instruments, usage or membership rights
  • Tokenization of real estate, energy, works of art, commodities or revenue streams
  • Initial sale or distribution, public offering, crowdfunding and investment contract risks
  • Establishing the relationship between token ownership and the in rem or personal right over the underlying asset
  • Custody, transfer, secondary market, buy-back and liquidation provisions
  • Multi-regulatory analysis of stablecoins, asset-backed tokens and models with a payment function
  • Legal review of white papers, technical documents, risk disclosures and marketing texts

Blockchain, smart contracts, Web3 and decentralised finance

  • Regulating the relationship between smart contract code and the parties’ legal agreement
  • Liability of the oracle, bridge, protocol, interface, wallet and governance layers
  • Legal classification of DeFi, staking, lending, liquidity pool and yield models
  • Legal personality, representation and liability issues in DAOs and community governance
  • Protocol upgrades, errors, exploits, rug pulls and governance attacks
  • Intellectual property, consumer and marketing provisions for NFTs and digital collectibles

MASAK, KYC and sanctions compliance for crypto-assets

  • Customer identification, identification of the beneficial owner and risk classification
  • Remote identification and identity verification processes
  • Information transfer and record-keeping under the travel rule
  • Suspicious transaction reporting, compliance programme and compliance officer structure
  • High-risk customers, wallets, countries and transaction scenarios
  • Data and contractual risks regarding the use of blockchain analysis tools
  • Reflecting the current rules on transfer periods and limits in operations
  • Assessment of business relationships against national and international sanctions lists

The status of obliged party is determined together with MASAK’s current guidance and the identification arrangements of the relevant institution. Announcements on UN Security Council (BMGK) listing decisions and the notification and transaction-postponement measures under Communiqué No. 34 are reflected in the compliance workflow.

Advertising crypto-assets and investor communications

  • Review of claims about returns, security, reserves, licensing and protection
  • Influencer, referral, campaign, reward and promotion models
  • Risk disclosures and customer information standards
  • Liability arising from misleading, incomplete or comparative statements
  • Compliance review of social media, app store and website content

Personal data and cybersecurity

3 practice topics

Personal data protection and KVKK compliance

  • Roles of data controller and data processor; determination of joint controllership under applicable foreign law
  • Data inventory, processing conditions, retention and disposal policies
  • Notices, explicit consent, cookies and preference management
  • Personal data of employees, customers, users, children and special categories of personal data
  • Data processing, confidentiality and security agreements
  • VERBİS, data subject applications and Board proceedings
  • Automated decisions, profiling and AI applications
  • Response to data breaches and notification processes

Transfer of personal data abroad and multinational data flows

In cloud, analytics, customer relations, support and AI services, data may pass through many countries. The transfer map should cover not only the main service provider but also sub-processors and remote access options.

  • Assessment of adequacy decisions, appropriate safeguards and occasional transfer conditions
  • KVKK standard contracts and notification to the Authority
  • Binding corporate rules and undertaking processes
  • Transfer impact and country risk assessment
  • Coordination of contracts with the EU General Data Protection Regulation and the rules of other countries
  • Data localisation and sector-specific retention obligations

The new transfer system under Article 9 of the KVKK entered into force on 1 June 2024. Where a standard contract is used, the signing and notification procedure should be checked against current Board decisions and announcements.

The obligation to notify the Authority within five business days of signing the standard contract is monitored separately. A foreign provider’s general data processing agreement does not automatically replace the KVKK standard contract.

Cybersecurity law and incident response

Law No. 7545 on Cybersecurity entered into force on 19 March 2025. The law and sector regulations may raise questions of duties, cooperation, supervision and sanctions for critical infrastructure, for organisations working with public institutions, and for natural and legal persons active in cyberspace.

  • Cybersecurity obligations and institutional map
  • Incident response plan, crisis team and decision protocol
  • Management of data breaches, ransomware, business email compromise and system outages
  • Preservation of logs, device data, communications and other digital evidence
  • Notifications to customers, business partners, insurers and competent institutions
  • Supplier security, security annexes and audit rights
  • Cyber insurance policies and claims processes
  • Coordination of administrative investigations, criminal investigations, damages and recourse proceedings

A law firm does not provide penetration testing, forensic imaging or technical incident clean-up services; it coordinates the legal strategy with the competent cybersecurity and digital forensics experts.

The changes to cybersecurity and internet regulations made by Law No. 7590 dated 31 July 2026, and the transitional provisions, are taken into account. No notification is directed to a single institution before the concrete allocation of duties and powers is examined.

Digital platforms and sector-specific products

10 practice topics

Digital platforms, marketplaces and app stores

  • The platform’s role as intermediary, seller, content provider or service provider
  • Seller and user onboarding processes
  • Platform use, seller, developer and API agreements
  • Rules on content ranking, recommendations, ratings, reviews and account closure
  • Intellectual property notice and takedown mechanisms
  • Risks of unfair commercial practices, discrimination and lack of transparency
  • In-app purchases, commissions and subscriptions
  • Fake accounts, counterfeit products, fraud and user complaints

E-commerce, digital content and subscription models

  • Pre-contractual information and distance contracts
  • Terms for digital content, online services and subscriptions
  • Automatic renewal, free trials, cancellation and refund flows
  • Obligations of electronic commerce intermediary service providers and service providers
  • ETBİS, İYS and compliance of commercial electronic messages
  • Campaigns, discounts, comparative prices and digital advertising
  • Right of withdrawal, exceptions, defective digital services and consumer applications
  • Dark patterns and the risks of manipulative user experience

Internet law, content and online reputation

  • Roles and obligations under Law No. 5651
  • Unlawful content, violations of personality rights and privacy
  • Applications for content removal, access blocking and preservation of evidence
  • User content and community rules
  • Disputes over domain names, fake accounts and impersonation
  • Online defamation, insult, commercial reputation and unfair competition
  • Platform requests and correspondence with foreign service providers

For requests for content removal, access blocking and personality rights, the applicable provision, the competent authority and the protection sought are determined separately; it is not assumed that a former application procedure applies to all violations.

Internet of things, connected devices and digital products

  • Joint legal analysis of the IoT device, mobile application and cloud service
  • Product safety, defects, updates and useful life
  • Device data, telemetry, location and biometric data
  • Remote access, security patches and end of support
  • Responsibility of the supplier, manufacturer, importer and software provider
  • Recalls, disclosure of security vulnerabilities and customer notification

Health technologies, insurance technologies and regulated sectors

  • Digital health, remote healthcare, medical device software and health data
  • Insurtech, digital policies, quotes and automated risk assessment
  • Regtech, identity verification, compliance monitoring and fraud detection
  • Education technologies and children’s data
  • Proptech, tourism technologies and travel platforms
  • Energy technologies, smart meters and mobility services
  • Sector-specific permit, data, outsourcing and registration obligations

Digital advertising, adtech, cookies and influencer processes

  • Ad network, agency, publisher and advertiser agreements
  • Cookies, device identifiers and behavioural advertising
  • Consent management platforms and preference records
  • Influencer, sponsored content and affiliate marketing agreements
  • Advertising claims, comparative advertising and consumer transparency
  • Advertising aimed at children and the risks of sensitive profiling

Competition law and digital markets

  • Platform rules, self-preferencing and discriminatory access claims
  • Competition law analysis of data, algorithms and network effects
  • Price parity, exclusivity and tying practices
  • Algorithmic pricing and the sharing of competitively sensitive information
  • App stores, search ranking and access restrictions
  • Competition notification in mergers, acquisitions and technology collaborations
  • Reviews and investigations by the Turkish Competition Authority (Rekabet Kurumu)

Domain names, trademarks and online intellectual property protection

  • Domain name allocation, domain disputes and bad-faith registrations
  • Trademark protection for application, platform, product and service names
  • Counterfeit apps, fake websites and impersonation
  • Rights in digital content, interfaces, games, visuals, music and databases
  • Infringement notices, preservation of evidence, interim measures and damages
  • Licences, assignment, joint use of trademarks and joint development

Geospatial data, maps and location-based services

For products that use maps or location, the data source, the purpose of use and the special permit regime are assessed together; not every item of location data is treated as subject to the same regime.

  • Scope of permits or licences for collecting, producing, sharing and selling geographic data
  • Navigation, location analytics and map use agreements
  • Distinction between data contact, commercial use, sharing abroad and personal data

Technology products with an electronic communications function

For products that provide communication infrastructure or communication services, the scope of Law No. 5809, the need for authorisation and the exemptions are assessed according to the product’s actual function.

  • Separation of the roles of technology supplier and electronic communications operator
  • Assessment of notifications, rights of use and applications to the regulatory authority
  • Reflection in the contract of infrastructure, access, service continuity, security and record-keeping provisions

Digital records, disputes and ongoing compliance

3 practice topics

Electronic contracts, e-signatures, KEP (Registered Electronic Mail) and digital evidence

  • Use of electronic signatures, mobile signatures, time stamps and KEP
  • Online acceptance, click-through contracts and proof records
  • Identity verification, OTP and transaction confirmation architecture
  • Integrity and retention of electronic records and their presentation to courts
  • Logs, screenshots, emails, messages, blockchain records and metadata
  • Form requirements for electronic contracts and their exceptions

Every electronic approval does not meet the qualified form requirement the law demands. The type of transaction and the specific legislation are reviewed separately.

Disputes arising from technology contracts and digital transactions

  • Late, incomplete or defective delivery of software
  • Disputes on system integration and acceptance testing
  • Service outages, data loss and security breaches
  • Licence excess, unauthorised use and infringement of intellectual property
  • Claims for termination of projects, fees, contractual penalties and damages
  • Account closure on platforms, blocking of payments and content measures
  • Disputes concerning fintech, payments, crypto-assets and digital wallets
  • Interim measures, preservation of evidence, mediation, litigation and arbitration

In digital disputes, the preservation of logs, time stamps, access records, versions and communications should be planned without delay. The method of collecting evidence must be lawful.

Corporate digital compliance programmes and training

  • Inventory of digital legislation and responsibility matrix
  • Policy set for technology, AI, data, cybersecurity and fintech
  • Contract templates and approval thresholds
  • Legal checklist for products and release gates for market entry
  • Procedures for incident notification, complaints, audits and regulatory communication
  • Training for executives, developers, sales, human resources and customer service
  • Periodic compliance review and corrective action plan

Which people and organisations do we work with?

  • Software, SaaS, cloud and cybersecurity companies
  • Artificial intelligence developers, model providers and corporate users
  • Start-ups, scale-ups, founders, angel investors and funds
  • Banks, financial institutions, fintech companies and technology suppliers
  • Payment institutions, electronic money institutions and open banking initiatives
  • Crypto-asset platforms, custody institutions and blockchain projects
  • Digital platforms, marketplaces, apps and e-commerce businesses
  • Health, insurance, tourism, energy, education and real estate technology companies
  • Corporate technology buyers, manufacturers, distributors and public contractors
  • Foreign companies operating in Türkiye or wishing to enter the Turkish market

Important legal distinctions

Which permits and obligations apply to your business model?

Function, flow and authority are examined rather than the product name
Product or activityPriority reviewImportant distinction
Software or technical serviceCode, infrastructure and support servicesIt is examined whether the provider actually becomes involved in funds or customer assets. A contract describing the service as “technical” alone does not remove the need for a licence.
Payments and electronic moneyMoney transfers, payment accounts, wallets, account information, payment ordersLaw No. 6493 and TCMB regulations; the institution’s authority, scope of activity, exemptions and outsourcing model are assessed together.
Crypto-asset servicePlatform, custody, transfer, initial sale or distributionLaw No. 6362 and SPK regulations are the basis. An incorporation permit, an operating authorisation and presence on the interim list are different situations.
Tokenization and Web3Digital right, underlying asset, protocol or automated transactionThe technical structure does not remove the review under capital markets, payment, ownership, contract and consumer law.
Artificial intelligence systemContent generation, classification, recommendation or automated decisionData processing, human oversight, ownership of rights and sector use are examined. The EU scope is determined separately according to the company’s role and market.

Crypto-assets: the distinction between payment and investment

Under the TCMB regulation, crypto-assets cannot be used directly or indirectly in payments, and services for that purpose cannot be offered. Trading, custody or transfer activity is not treated as the same as the payment function.

Review the TCMB regulations (opens in a new tab)

The application list is not an operating permit

The SPK’s temporary List of Operating Entities is an informational list. The entity’s current permit, service type, transitional conditions and any operating restrictions are verified separately.

Read the SPK’s statement on the list (opens in a new tab)

Legal work is not investment advice, financial valuation, reserve verification or a technical security audit. Where required, these tasks are coordinated with the relevant competent experts.

Current regulations

How do the 2026 developments affect your products and processes?

Remote identification in payment services

4 September 2026 · Official Gazette (Resmî Gazete) 33360

Review the official source (opens in a new tab)

The provisions on identity documents, verification and remote customer onboarding have changed. For natural persons who are not Turkish nationals, remote identification with an electronic passport that meets the conditions has been regulated. The customer onboarding screen, record-keeping arrangements, the MASAK conditions and the protection of biometric data are reviewed together.

Türkiye Artificial Intelligence Action Plan

18 August 2026 · Circular No. 2026/9

Review the official source (opens in a new tab)

The plan published for the 2026–2030 period and its coordination arrangements have been added to the current policy framework. This document is not, on its own, a permit for any AI product, nor a conformity certificate covering all private-law obligations.

EU artificial intelligence implementation timeline

27 July 2026 · AI Omnibus enters into force

Review the official source (opens in a new tab)

The amendment in the EU renewed the application dates for high-risk systems. Transparency rules and special transitional arrangements are addressed separately. For systems offered in the EU, or whose output is used in the EU, the extraterritorial scope is examined separately.

New functions in open banking

17 March 2026 · ÖHVPS 2.0.0

Review the official source (opens in a new tab)

Functions to initiate future-dated and recurring payment orders with card information have been opened for use. Contract terms, user authorisation, API liability and the record-keeping flow are checked for consistency with the product’s new functions.

Transition and authority control for crypto services

26 March 2026 · SPK 18/617

Review the official source (opens in a new tab)

It was decided that the deadlines for submitting custody agreements, and for the institutions on the list to obtain an authorisation certificate, will be set after authorised custody institutions begin general service. This transitional decision does not remove the licensing conditions; subsequent decisions and the institution’s current status are checked.

Sanctions lists and transaction measures

September 2026 · MASAK announcements

Review the official source (opens in a new tab)

Under Communiqué No. 34, urgent notification and postponement measures are on the agenda for transactions linked to the relevant UN Security Council (BMGK) listing decisions. In payment and crypto compliance, current list screening, match review and the process under Article 19/A of Law No. 5549 are operated together.

Generative AI in the workplace

February 2026 · KVKK guidance document

Review the official source (opens in a new tab)

Tools used outside the organisation’s knowledge, the data entered and the review of outputs should be made visible. The document is an awareness guide; it is not a new law, nor a permit covering every use.

Source review: 4 October 2026. Legislation, a transitional decision, an implementation announcement and a guide differ in legal nature. The provisions in force at the time of the transaction and the latest institutional decisions are applied together.

Artificial intelligence governance

Role, risk and human oversight in the use of AI

The EU Artificial Intelligence Act does not apply in the same scope to every business in Türkiye. Links such as placing products on the EU market, the roles of the parties and the use of system output in the EU are assessed. Data, contract, employment, consumer and sector obligations in Türkiye continue to apply separately.

Role and purpose of use

The duties of the parties that develop the model, offer it under their own name and use it in business processes are separated. Not every use of a model is given the same risk class.

Data and ownership of rights

For systems working with training, fine-tuning and corporate knowledge, personal data, copyright, database rights and trade secrets are reviewed together. Access to data does not give authority to use it for any purpose.

Human oversight and contract

Control of important decisions, the route for objection, records, supplier liability and change management are defined. Technical success criteria are made concrete with the relevant experts; legal conformity is not tied to a model score alone.

Phased implementation timeline for files linked to the EU
DateRegulatory headingCheck in the file
2 February 2025First prohibited practices and AI literacyThe purpose of use and the competence suited to employees’ duties are assessed.
2 August 2025Obligations for general-purpose AI modelsThe role of the model provider and the special transitional arrangements for existing models are checked separately.
2 August 2026Transparency provisions, especially Article 50Users are informed about interaction with AI and about synthetic content within scope, together with the relevant exceptions.
2 December 2026New prohibition and transitional arrangements for certain existing systemsA new prohibition on systems that generate sexual content without consent; transition to the Article 50(2) marking requirement for certain systems placed on the market before 2 August 2026.
2 December 2027High-risk use areas in Annex IIIClassification and obligations in employment, education and other use cases within scope.
2 August 2028High-risk systems embedded in regulated productsThe link to Annex I products and the related conformity assessment are examined together.

Review the European Commission’s current timeline (opens in a new tab)

Deadlines and information security

Data transfers, breach notification and protection of digital records

Cross-border transfers in cloud and AI

The data centre, sub-processors, support access and the model service are mapped together. Under Article 9 of the KVKK it is determined whether an adequacy decision, appropriate safeguards or the limited conditions for occasional transfers apply; a regular data flow is not converted into an occasional exception.

Where a standard contract is chosen, the notification within five business days of signing rule is observed. The conditions for data processing, security and sector-specific localisation obligations continue to apply separately.

KVKK transfer framework (opens in a new tab)Standard contract notification rule (opens in a new tab)

Data breach or cyber incident

Where personal data have been obtained by unlawful means, the data controller should notify the Board without delay and at the latest within 72 hours of becoming aware of the breach. Where there is a delay, its reasons are explained; missing information may be completed in stages.

Notice to the data subjects is given as soon as reasonably possible after the persons concerned have been identified. Not every cyber outage is also a personal data breach; the deadlines for sector, insurance and contractual notifications are determined separately.

Read the Board’s notification procedure (opens in a new tab)

Preserve the records and do not postpone deadline-bound applications.

The time of the incident, account movements, transaction identifiers, contract versions, correspondence and access records are preserved by a lawful method. Private keys, recovery phrases and access passwords are not shared through general communication channels. Technical response and legal notifications are planned together.

From product design to dispute

Our approach to digital technology matters

We assess the product not as a single contract, but across company, data, intellectual property, regulatory compliance and dispute dimensions. The review can also be carried out during the design, development and growth stages, as a preventive review.

  1. Understanding the product and how it actually works

    Product screens, user roles, fund and data flows, the third parties used, the target market and the revenue model are reviewed together.

  2. Legal classification and risk map

    The applicable regulations, the competent authorities, the permits and notifications required, and the priority contract, data, intellectual property and security risks are identified.

  3. Document and control architecture

    Master agreements, user documents, privacy notices, internal policies, the authority matrix and incident management procedures are prepared in alignment with one another.

  4. Implementation and launch

    Legal requirements are translated into the product flow, application screens, customer communication, record-keeping systems and team responsibilities.

  5. Continuous monitoring and change management

    When legislation, the product, a country, a supplier or the revenue model changes, its effect is assessed. Periodic reassessment is carried out in fintech, crypto-assets, artificial intelligence, data and cybersecurity.

  6. Management of incidents, audits or disputes

    Evidence is preserved; notice, formal demand, regulatory communication, interim legal protection, negotiation, mediation, litigation or arbitration options are planned according to the file.

At the start of the work, the scope, responsible persons, document sharing and reporting arrangements are agreed. Legal options, missing information, deadlines and costs are explained; the effect of a product or regulatory change on the file is shared with the client. Technical, financial and legal tasks are clearly separated among the relevant professionals.

Secure preparation

What information is needed for a first legal consultation?

A short summary for first contact

  • Your request: product development, contract, permit, investment or dispute
  • What the product does, its users and its target countries
  • Between which parties data, money or crypto-assets flow
  • Any incident, notice, review or planned launch date
  • A short list of the contract to be reviewed and of the existing permits

Even if your documents are incomplete, you can describe the matter briefly. The necessary records are requested after the scope of the work has been determined; it is not necessary to share the entire system or the customer database.

Product and company information

  • Product presentation, demo or screen flows
  • Business model, revenue model and target country information
  • Company and shareholding documents
  • Technical specification, architecture summary and data flow diagram
  • Cloud, API, SDK, open-source, dataset and AI models in use

Records to be requested depending on the file

  • Existing customer, user, supplier and investment agreements
  • Privacy, cookie, notice and explicit consent texts
  • Information security, incident response and business continuity documents
  • Licences, permits, notifications and correspondence with competent authorities
  • For crypto or payment services, a flow chart of funds and assets
  • If there is a dispute, notices, invoices, correspondence, logs and expert reports

Do not share passwords, private keys, recovery phrases, API keys or live customer data. Sensitive documents are not uploaded through the message to the firm; the necessary records are requested after a secure sharing method has been agreed. Information and documents are kept confidential and used only for the legal assessment and for the agreed purpose of the service.

Firm organisation

Antalya-based technology law practice with work across Türkiye

From Antalya across Türkiye

Attorney Umut Güneş founded Güneş & Güneş Law Firm in Kemer on 18 March 1999; since 2007 the firm has carried on its 27 years of professional practice from its physical office in Antalya. Digital technology, AI and fintech matters in all 81 provinces of Türkiye can be handled through remote work, in-person work and coordination with colleagues, as the file requires.

Online contract and product review is planned together with applications to institutions, preservation of evidence, hearings and the conditions for enforcing a decision. Providing services across Türkiye does not mean that there is a physical branch in every province.

International projects connected with Türkiye

The entry of foreign companies into Türkiye and the cross-border activity of companies based in Türkiye are reviewed in terms of the applicable law, jurisdiction, data transfer, certification of documents, translation, service abroad and enforcement of decisions. Communication can be conducted in Turkish, English, German and Russian.

Where local representation abroad is required, we work with an attorney or law firm authorised in that country. The choice of counsel, consultation on the client’s behalf, the scope and agreement of the engagement, planning, document flow, process follow-up, reporting, liability and the coordination fee are determined separately.

Terms of engagement

Scope of service, fees and coordination with experts

Scope of the legal work

Business model review, contracts, permit applications, compliance programmes and dispute follow-up are treated as separate work. The fee is set by agreement according to the scope, the volume of documents, the regulated sector, the time required and any link to a foreign country.

A consultation request does not mean that the matter has been accepted, that a representation relationship has been established or that a time-sensitive step has been taken on. No undertaking is given regarding obtaining a permit, completing an investment, collecting a receivable or the outcome of a case.

Technical and financial work

Code scanning, penetration testing, forensic IT review, reserve verification, financial audit, valuation and tax work are carried out by the relevant experts where needed. Our firm addresses the legal effect of these findings and the coordination of the process.

At the outset it is explained whether expert review, notary fees, translation, court fees, court-appointed expert fees, and travel and representation costs in a foreign country are included in the attorney’s fee.

Clarity before applying

Questions about digital technologies, AI and fintech

Which products does digital technology, AI and fintech law cover?

It is a field of work that extends from software and cloud services to artificial intelligence, from digital platforms to payment, open banking and crypto-asset business models. A single contract or a single institutional permit does not cover all products; function, data, funds and the target market are assessed together.

Review the related explanation

When should a technology start-up begin legal work?

The business model, data flow, ownership of intellectual property and licensing needs should be assessed during product development. Fundamental changes left until after launch may create higher cost and operational risk.

Review the related explanation

Is the person who develops software always its owner?

Ownership of rights is determined according to the relationship with the employee or independent contractor, the contract, the nature of the work and the applicable legislation. Payment of a fee may not mean that all intellectual property rights are transferred automatically and without limit.

Review the related explanation

Are delivering source code and transferring the intellectual property rights in software the same thing?

No. Access to source code may be a technical delivery or a business continuity measure. The transfer of intellectual property rights should be regulated separately, in terms of the type of right, duration, territory, mode of use and statutory formal requirements.

Review the related explanation

What are the most important issues in a SaaS agreement?

Service levels, data ownership, security, sub-processors, cross-border transfers, price changes, suspension, liability, backup, data return and exit support should be regulated together.

Review the related explanation

Are artificial intelligence systems subject to legal oversight in Türkiye?

Yes. In Türkiye, the provisions of the KVKK, intellectual property, consumer, employment, product safety, contract, cybersecurity and sector rules may apply. The 2026–2030 Artificial Intelligence Action Plan is not a general activity permit that replaces these product-level obligations. Where there is an EU link, the scope of the Regulation and its current timeline are examined separately.

Review the related explanation

Can employees enter company data into generative AI tools?

That depends on the tool’s terms, the data use, the storage and model-training settings, the nature of the data and company policy. Entering trade secrets, personal data or customer information without control may create serious risk.

Review the related explanation

Are Bitcoin and other crypto-assets banned in Türkiye?

It cannot be said that there is a single general ban on all crypto transactions. However, in Türkiye crypto-assets cannot be used directly or indirectly in payments, and services for that purpose cannot be offered. Trading, custody, transfer and issuance are assessed under separate regulations.

Review the related explanation

Can every company offer a crypto-asset trading platform or a custody service?

No. The incorporation and operating conditions, and the permits specific to the type of service, are examined. Being on the SPK’s temporary List of Operating Entities does not mean that each entity on the list has received an operating permit. Transitional conditions and current Board decisions should also be checked.

Review the related explanation

Is a technical document alone sufficient to issue a token?

No. The rights the token provides, the manner of issue and distribution, any investment promise, the underlying asset, the secondary market and the target users affect the legal classification. The technical document, contracts, risk disclosures and regulatory permits should be considered together.

Review the related explanation

What can be done if an unauthorised transfer is made from a crypto-asset account?

Account and device security should be secured, and platform records, wallet addresses, transaction identifiers, correspondence and time information should be preserved. A complaint to the platform, a criminal complaint, damages claims, interim measures or other legal routes are assessed according to the parties and the evidence. The fact that a blockchain transaction cannot technically be reversed does not mean that there are no legal remedies.

Review the related explanation

Can crypto-assets be subject to inheritance or matrimonial property division?

Crypto-assets with economic value may, depending on the circumstances, be subject to reviews of the estate, the matrimonial property regime, attachment and liquidation. The identification of the asset, access keys, the manner of custody, the valuation date and the country in which the service provider is located are important.

Review the related explanation

Is a smart contract on its own a legally valid contract?

The fact that code carries out a transaction automatically does not mean that, in every case, the consent, information, form and validity requirements demanded by law are met. The relationship between the legal agreement and the code, the risk of error and oracle failure, and the reversal of the transaction should be clearly regulated.

Review the related explanation

Is a TCMB permit required for a payment or electronic money product?

This depends on whether the product accepts funds, creates a payment account or electronic money, initiates payment orders, and what its role in the transaction is. It is the actual flow of funds and services, not the product name, that should be examined.

Review the related explanation

Are all digital wallets electronic money institutions?

No. Some wallets may be merely a technical tool or a service that stores card information; some models may function as a payment account or electronic money. The flow of funds and the rights obtained by the user determine the legal classification.

Review the related explanation

Which services does open banking cover?

The core categories are providing account information and initiating payment orders. With ÖHVPS 2.0.0, announced on 17 March 2026, card information and future-dated and recurring payment orders have also been added to the scope. Authority, authorisation, API security and data responsibility are examined product by product.

Review the related explanation

Can a foreign technology or fintech company offer remote services in Türkiye?

The mere fact that a company is located abroad does not, in every case, set aside Turkish legislation. Targeting users in Türkiye, local marketing, fund or data flows, consumer relationships and regulated activities should each be examined separately.

Review the related explanation

Is it possible to keep cloud data abroad?

It may be possible; however, the KVKK conditions for transfers abroad, the standard contract and notification obligations, data security, and sector-specific localisation or retention rules should be assessed together.

Review the related explanation

What is the first legal step after a cyber attack?

Alongside the technical response, a plan is made for the lawful preservation of records, legal privilege and confidentiality, notification to the competent authority, contractual notice and the insurance process. In the case of a personal data breach, the rule of notifying the Board within 72 hours at the latest of becoming aware is assessed separately; the deadlines for other notifications may not be the same.

Review the related explanation

Is every transaction made with an electronic signature valid?

An electronic signature is a strong means of proof and of identity verification; however, some transactions are subject to a special form or to official formalities. The type of signature used and the legislation for the transaction should be examined together.

Review the related explanation

Does a law firm carry out technical cybersecurity or code audits?

A law firm manages legal risk, contract, notification, evidence and dispute processes. Technical tasks such as penetration testing, code analysis, reserve verification, financial valuation and forensic IT are carried out by competent experts; their legal consequences are assessed by lawyers.

Review the related explanation

Can the firm work with technology companies outside Antalya?

Depending on the nature of the matter, the competent authority and the need for physical action, we can work with clients in other provinces of Türkiye and abroad through online consultation and secure document sharing. In-person action and hearings are planned where necessary.

Review the related explanation

Did all EU AI rules start to apply on 2 August 2026?

No. While that date is the basis for the transparency provisions, certain existing systems have a transition to 2 December 2026 for marking synthetic output. The dates of 2 December 2027 for Annex III high-risk systems and 2 August 2028 for high-risk systems embedded in regulated products apply. The type of system and the exceptions are examined separately.

Review the related explanation

Does an AI provider not using data for training remove all risk?

No. Storage, sub-processors, remote access, transfers abroad, confidentiality, the conditions for data processing and the use of outputs are assessed separately. Changing a single product setting does not show that legal compliance is complete.

Review the related explanation

Related practice areas

Related Legal Services

This page covers the technology product as a whole. For detailed services on payment and crypto institutions, MASAK compliance or computer crimes, you may review the related pages.

Legal basis

Legislation and official sources

Which core regulations are assessed together?

  • Law No. 6098, the Turkish Code of Obligations
  • Law No. 6102, the Turkish Commercial Code
  • Law No. 5846 on Intellectual and Artistic Works
  • Law No. 6769 on Industrial Property
  • Law No. 6698 on the Protection of Personal Data
  • Law No. 5070 on Electronic Signature
  • Law No. 5651 on the Regulation of Publications on the Internet and the Suppression of Crimes Committed by Means of Such Publications
  • Law No. 6563 on the Regulation of Electronic Commerce
  • Law No. 6502 on Consumer Protection
  • Law No. 4054 on the Protection of Competition
  • Law No. 6493 on Payment and Securities Reconciliation Systems, Payment Services and Electronic Money Institutions
  • Law No. 6362 on the Capital Markets and the regulations on crypto-asset service providers
  • Law No. 5549 on the Prevention of Laundering of Proceeds of Crime, and MASAK regulations
  • Law No. 7545 on Cybersecurity
  • Relevant sector regulations and the foreign law applicable to international activities

Secondary regulations under Law No. 5809 and Law No. 7221 on electronic communications and geospatial data functions; artificial intelligence and data protection rules applicable through the EU link are reviewed separately.

This page is for general information only. It is not a legal opinion, nor a guarantee of outcome, for a specific product or dispute. The concrete assessment is made on the basis of the legislation at the time of the transaction, transitional provisions, contracts and the actual product flow.

Legal consultation

Briefly describe your product or digital dispute.

The product’s function, the parties, the target country and any approaching deadline help the initial assessment. You may request a consultation on contracts, investment, permits, data compliance or a dispute.

For a time-sensitive step, do not wait for a reply. The first consultation clarifies the scope of the legal need, the documents required and the routes that can be assessed.

Open the meeting request page

Do not share passwords, private keys, recovery phrases, API keys or live customer data. Sensitive documents are not sent through the message to the firm; the necessary records are requested after a secure sharing method has been determined. Information and documents are kept confidential and used only for the legal assessment and the agreed purpose of the service. You may review the Confidentiality and Information Security statements.