Request a quote WhatsApp

17 September 2026 · 4 min read

What is 5651 logging? A 2026 guide for businesses

Every business offering guest internet in Turkey must keep records under Law 5651. Which records, for how long, and under which technical conditions? A step-by-step guide.

Any business that offers internet to guests — hotel, cafe, mall, expo venue, hospital, municipality, factory — is treated as a "mass use provider" under Turkey's Law No. 5651. That means you must record who you gave access to and keep a verifiable trace of their sessions. This guide turns the obligation into technical steps.

In short: authenticate the user, store access records with trusted timestamps in a tamper-evident archive, respect the retention period, and be able to hand over a verifiable report on request. This is informational content; assessing legal compliance is the responsibility of the business and its legal counsel.

Who is covered?

Operators serving their own subscribers are "access providers". A business opening its network to guests, customers or visitors is a mass use provider. What matters is that third parties use your connection. Staff and guest networks should run on separate SSIDs with separate policies.

Use caseWhereTypical verification
Hotel guestRoom, lobby, meetingsPMS (room no + surname), SMS fallback
Cafe / restaurantFloor, terraceSMS / OTP, app membership
Expo, congressHalls, boothsVoucher + SMS, high concurrency
Municipality, publicSquares, facilitiesNational ID + SMS
Corporate officeVisitor areasSponsor approval
HospitalWaiting, inpatientSMS, separate policy for companions

What is recorded?

  1. Authentication record: method, verified data, success or failure, timestamp.
  2. Session record: user, MAC, assigned IP, session start and end.
  3. NAT/port record: which internal session used which port range behind a shared public IP.
  4. Consent record: which version of the privacy notice was accepted and when.

Content is not recorded. What is expected is the trace of who connected when, not the pages they visited.

Technical qualities of the archive

  • Timestamping: records are stamped as they are produced, with system clocks synced to a reliable NTP source.
  • Integrity: the archive is signed so that no line can be silently altered.
  • Access control: access to the archive is itself logged.
  • Redundancy: a single copy is not enough; keep a second location.
  • Export format: you must be able to produce a readable, signature-verifiable package on request.

Retention and responding to a request

Retention is defined by regulation and practice; in the field, businesses typically plan for up to two years. When the period ends, records should be deleted in a controlled way — keeping them forever creates a separate privacy risk. A typical request flow: a date and IP/port range arrives, the system finds the matching session and produces a signed report together with the authentication record.

Implementation checklist

  • Is the guest network separated from the staff network?
  • Does every login produce an authentication record?
  • Are clocks synced over NTP?
  • Is the archive signed and backed up?
  • Is the retention and deletion schedule written down?
  • Is the privacy notice visible in the portal and versioned?
  • Do all locations apply the same policy?

Common mistakes

  • Handing out one shared password: records cannot be tied to a person.
  • Leaving logs only on the local disk of a network device.
  • Policies drifting apart as the number of branches grows.
  • Missing or unversioned privacy notice in the portal.

FAQ

Do I have to log content under Law 5651?

No. A mass use provider is expected to keep access and authentication traces, not the content of visited pages.

Is a single shared Wi-Fi password enough?

No, because records cannot be tied to an individual. Authentication should run through a captive portal.

How long should records be kept?

The period is set by regulation; businesses commonly plan for up to two years, then delete.

Why are timestamps required?

They prove when a record was produced and that it has not been altered. An unstamped record has little evidential value.

Is there a different path for hotels?

Yes. Guests have already checked in, so identity lives in the PMS and login happens with room number and surname.

How HotSpot handles it

HotSpot verifies logins at the portal, writes session and NAT records into a timestamped archive, ties retention to policy, and produces signed reports on request. Multi-site businesses run every location from one panel under the same policy.

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