Request a quote WhatsApp

16 September 2026 · 6 min read

What is Turkey's Law No. 5651? A complete guide for businesses

Who Law No. 5651 covers, what obligations a business has, which records must be kept and for how long, and what inspectors ask for. A plain-language guide for any business offering guest Wi-Fi.

Law No. 5651 is the core Turkish regulation that requires parties providing internet access to keep connection records. Any business offering Wi-Fi to guests — a hotel, café, shop, office, venue or marina — falls within its scope. This guide explains, in plain language, what the law says, what a business must do, and what inspectors actually ask for.

This article is informational and is not legal advice. Assessing your own compliance is the responsibility of the business and its legal counsel.

What is Law No. 5651?

Its full name is the "Law on Regulation of Publications on the Internet and Combating Crimes Committed by Means of Such Publications", in force since 2007. It covers two things:

  1. Procedures for combating online crime and for blocking access to content.
  2. The obligation of parties providing internet access to keep and retain traffic records (logs).

For businesses, the second part matters day to day. The law wants "who connected, when, from which IP" to be recorded and unaltered.

Who does it cover?

The law assigns roles. For businesses the decisive one is mass use provider: a party offering internet access to people at a given location for a given period.

RoleWhoTypical obligation

|---|---|---|

Access providerInternet service providersKeep and retain traffic records, hand them over on request
Hosting providerHosting companiesKeep content-related records
Mass use providerHotel, café, restaurant, mall, hospital, school, office, expo hall, marinaKeep internal IP allocation records, take security measures
Commercial mass use providerThose offering access for a fee or as part of commercial activityThe above plus a permit from the local administration

A hotel or café offering free guest Wi-Fi is included. "It's free, so I'm not responsible" does not hold, because the access is offered as part of commercial activity.

What the business must do

Identify the user

The identity of the person connecting must be verifiable. The most common method is a one-time password over SMS; hotels use room number plus surname, corporate sites use sponsor approval, events use vouchers. See our captive portal login methods guide for a comparison.

Keep traffic records

What is expected is connection data, not content: which internal IP was assigned to which user, which public IP and port was used, when the session started and ended. Page content is not recorded — and should not be.

Protect record integrity

The law requires records to be accurate and intact. In practice this means hashing the log and signing it with a trusted timestamp: change one line later and the signature no longer matches. See timestamped, signed log archives.

Retain and produce on request

Records are retained for the period set by regulation and produced in readable form when an authority asks. Two questions come up: "who was using this IP at this date and time?" and "how do you show this record was not altered?"

Take security measures

Reasonable measures are expected against reaching blocked content and against misuse of the network.

How long must records be kept?

Retention periods and technical details are set by regulation and can change over time. The right approach is to build around a configurable retention period, not a hard-coded number: when the rules change, only a setting should change. Confirm the current period with your legal counsel.

What happens if you don't comply?

The best-known consequence is an administrative fine. But the real risk is usually this: during an investigation you are asked about activity that left your network, and you cannot produce the record. Responsibility then falls on whoever operates the network. For commercial mass use providers, a missing permit is a deficiency in itself.

Implementation checklist

  • [ ] Is the guest network separated from staff and payment networks (separate SSID / VLAN)?
  • [ ] Does everyone join through a verifiable login method?
  • [ ] Are session records complete (internal IP, public IP, port, start, end)?
  • [ ] Are records timestamped and integrity-protected?
  • [ ] Is the retention period configurable, and what happens when it expires?
  • [ ] Can you export a date range within minutes?
  • [ ] Are privacy notices and consents in place? (privacy guide)
  • [ ] If access is commercial, do you hold the required permit?
  • [ ] Are all your branches managed to the same standard?

Is 5651 the same as data protection law?

No — they point in different directions and both apply. 5651 says "keep the record". Data protection law (KVKK) says "process personal data lawfully, keep it only as long as needed, inform the person". A correct setup satisfies both: collect only what is needed, define retention, inform guests on the login screen, and keep marketing consent separate from network access.

Where HotSpot fits

HotSpot runs the guest Wi-Fi login screen (captive portal), collects session records, hashes them, signs them with a trusted timestamp and archives them. You do not need to replace your network: it works with Ruckus, Cisco, Aruba and Meraki controllers and Fortinet, Palo Alto, Sophos and MikroTik firewalls. A requested date range is exported from the panel. See our legal logging page.

HotSpot provides technical infrastructure; legal assessment and advice are out of scope.

Frequently asked questions

I offer free Wi-Fi to guests — am I still in scope?

Charging or not is not the deciding factor. If you offer internet access to people at a location, you are a mass use provider; if access is part of your commercial activity, the commercial obligations apply too.

Are the websites guests visit recorded?

No. What is kept is connection data: which IP was assigned to whom, and when the session started and ended. Page content is not recorded.

Is writing the password on a sign enough?

No. A shared password does not show who connected; the record must be attributable to a person. That is why SMS/OTP, room number verification or vouchers are used.

For a chain, is each branch set up separately?

Installation is per site, but management can run from a single panel, so every location follows the same policy and the same retention standard.

What exactly is asked during an inspection?

Usually a date, time and IP address are given, and you are asked who was using it. The answer should come as a readable export together with the signature showing the record was not altered.

Do I have to buy a logging appliance?

The requirement is the record, not the device. Records can be kept by a hardware appliance or by software integrated into your network; what matters is that they are complete, attributable and integrity-protected.

Next step

We can review your current network against this checklist together. Request a demo or start with our 5651 logging guide.

Let’s simplify your guest Wi-Fi journey

Keep your existing infrastructure and bring access, engagement and 5651 records into one panel.

Request a Free Demo

We use cookies for visit statistics. Cookie policy