Offering Wi-Fi to visitors looks like a simple amenity. Technically it is. In terms of responsibility, there are a few things that rarely get discussed until something goes wrong.

This article summarises what is relevant to a small business owner. It is a general explanation, not legal advice, for a specific case, consult a legal adviser.

The Personal Data Protection Law

Law Number 27 of 2022 applies to anyone processing personal data, small businesses included. The moment your captive portal asks for a name, an email, or a phone number, you become a data controller.

The law gave a two-year adjustment period from its promulgation, and that period ended in October 2024. So "the rules aren't in force yet" is no longer an excuse, for a small warung or café included.

The obligations attaching to that role:

Give information before data is taken

Visitors are entitled to know who is collecting, what for, how long it is kept, and who it is shared with. This is what belongs on the privacy policy page linked from the portal.

Obtain valid consent

Consent must be specific and given knowingly. A pre-ticked box does not qualify. Consent to use the service must also be kept separate from consent to receive marketing.

Collect only what you need

The data minimisation principle. If your purpose is simply to grant internet access, a national identity number is plainly unnecessary. Every additional field you ask for adds responsibility without adding benefit.

Provide a way to exercise rights

Visitors are entitled to request a copy of their data, correct it, delete it, and withdraw consent. Provide one contact address that is genuinely read for requests of this kind.

Delete once the retention period ends

Set how long data is kept, write it into the policy, then apply it. Stating a six-month retention while never deleting anything actively worsens your position.

A portal that meets the requirements

A simple comparison between a problematic portal and a reasonable one:

AspectProblematicReasonable
Data requestedName, ID number, address, date of birthFirst name and email, or no data at all
ConsentOne box covering everythingSeparate: service use and marketing
Privacy policyAbsent, or a dead linkOpenable before filling anything in
CheckboxesPre-tickedEmpty, ticked by the visitor
How to opt outNot mentionedIn the policy and in every message

Portal design and how it works are covered separately in the guide to captive portals.

On session records

Recording when a device connected and for how long is common practice, and useful if an enquiry ever arises.

What needs understanding: those records themselves contain personal data. MAC addresses and IP addresses count. So session records fall under the same rules, a purpose, a retention period, restricted access.

Reasonable practice for a small business:

  • Record start time, end time, and a device identifier
  • Do not store traffic content or lists of sites visited
  • Set a sensible retention period, say three to six months
  • Limit who can read them
  • Mention their existence in the privacy policy

For boarding houses and guest accommodation, per-room records are far more useful than combined ones, they narrow any enquiry to one resident rather than the whole building. The arrangement is covered in the guide to Wi-Fi for boarding houses.

Responsibility for how it is used

The internet connection is registered in your business's name. If unlawful activity takes place over that network, any enquiry points at your address first.

The reason is technical: every device on your premises shares one address facing the internet, your subscription's. From outside, the activity of twenty visitors appears to come from a single source. The provider can only show that the address was registered to you at a given time, and that is where the trail ends, unless you keep your own record of who was using it. How address sharing works is explained in the guide to local IPs and DHCP.

Where you actually stand

Providing access does not by itself make you liable for what other people do. What is generally assessed is whether you took reasonable steps, and whether you can show the act did not originate with you. Those two things are what you can prepare in advance.

SituationYour position
Open Wi-Fi, no records at allWeakest, nothing to show
Password-protected, no recordsSlightly better
Portal with terms of useEvidence that notice was given
Portal with session recordsCan show the time and the device

Note that this ordering runs the opposite way to the data obligations: the records that strengthen your position are also personal data, so they need handling as described in the section on session records above.

A few things help clarify your position:

  • A password, not an open network. Even a password stuck to the table changes the situation, it shows that access was given, not left free to anyone passing by.
  • Terms of use shown before access is granted. Stating that the network must not be used for unlawful activity.
  • Session records. These help show the access was used by many people, not only you.
  • Basic filtering. Blocking clearly problematic categories of site through DNS. How that works is explained in the guide to public DNS.

On filtering, there's a layer already running without your noticing. Internet providers in Indonesia block sites on Komdigi's TrustPositif list. If a guest complains that a site won't open, check the domain at trustpositif.komdigi.go.id before tinkering with the router. A site blocked there won't open from any network using the provider's DNS, and the page also offers a normalisation request form if the block is a mistake.

When it's your network being abused

The reverse is worth knowing too. Someone who gets into your network or your router's admin page without permission commits an act that can be prosecuted. Since the new Criminal Code (KUHP) took effect on 2 January 2026, the illegal access provision formerly in Article 30 of the ITE Law has been revoked and is now covered by the KUHP. For a business owner the upshot is simple: keep evidence if you find a foreign device breaking into the network, and don't retaliate in kind. The user's side is covered in the guide to using a neighbour's Wi-Fi without permission.

None of these grants immunity. What they provide is evidence that you managed the facility with reasonable care.

For anyone selling access

If you sell vouchers or share a subscription with others, there is an extra layer to consider. Beyond responsibility for the traffic, there is a question about the status of the activity itself, covered in the guide to permits and obligations for a paid Wi-Fi business and the guide to RT/RW Net. The technical side of vouchers is in the guide to setting up Wi-Fi vouchers.

The duty to keep data secure

If you store visitor data, you are obliged to protect it. For a small business, that does not mean an elaborate system. A few basics close off most of the risk:

  • A strong admin password that is not shared with all staff
  • A guest network kept separate from the operational network, see the guide to separating networks
  • Network device firmware kept updated
  • Access to the visitor database limited to those who genuinely need it
  • Backups stored separately

The PDP Law also sets out an obligation to notify in the event of a data breach. Under Article 46, if your visitor data leaks you must inform the affected visitors and the competent authority in writing within 3 × 24 hours. At minimum it must state what data was exposed, when and how, and what you have done to handle and recover from it. Three days go quickly if you don't yet know who holds the data and where it's stored, so write that down now, not when it happens.

Equipment and frequencies

Guest Wi-Fi uses radio frequencies that Indonesia regulates under a class licence: Permenkominfo No. 2 of 2023, later amended by Permenkomdigi No. 2 of 2025. A class licence means you don't need your own radio station licence, provided two conditions are met.

  • The equipment is certified. Article 11 of that regulation requires equipment traded or used in Indonesia to meet technical standards, proven by a certificate. Routers and access points sold through official channels usually carry a certification label. How to check is in the guide to telecom equipment certification.
  • It's used within the technical rules. Band, channel, and transmit power stay within the set limits. An added booster antenna or another country's region setting can turn lawful equipment into a violation, details in the guide to Wi-Fi frequency and transmit power rules.

Example: a coffee shop with 30 seats

Say a coffee shop wants a portal that asks for a WhatsApp number, to send a monthly promotion. A realistic checklist for it:

  1. The portal asks only for a first name and a WhatsApp number, no NIK or date of birth.
  2. Two empty checkboxes: one for the terms of use, one for receiving promotions. Guests who don't tick the promotion box still get internet.
  3. A one-page privacy policy in Indonesian, stating the retention period, for example six months from the last visit.
  4. Every promotional message includes a way to stop, such as replying "STOP".
  5. Session records are kept for three months, and only the owner holds admin access.
  6. At the till there is one named person and number responsible for deletion requests and breach handling.

If that list feels like too much, the simplest option below may suit better.

The simplest option

There is one route that avoids most of the obligations above: do not collect any data at all.

Guest Wi-Fi with a password printed on the receipt, no portal and no form, does not make you a personal data controller. Nothing is stored, nothing needs protecting, nothing needs deleting.

The downside is obvious: you lose a channel for communicating with customers. For some businesses that trade is worth it. For those genuinely building a customer base, well-organised data collection makes more sense, discussed in the guide to Wi-Fi marketing.

In short

What you doObligations that arise
Open Wi-Fi with no portalPractically no data obligations
Portal with no data collectionTerms of use are enough
Portal collecting an emailPrivacy policy, consent, retention, data subject rights
Portal plus sending promotionsAll of the above, plus separate marketing consent and an opt-out
Keeping session recordsRetention period, restricted access, mentioned in the policy
Selling vouchers or sharing a subscriptionPlus the question of the activity's own status

The more you collect, the more there is to manage. That is not a reason to collect nothing, but a reason to collect deliberately.

Read also: Rules for Tracking Visitors Through Wi-Fi.

Frequently asked questions

If someone uses my Wi-Fi for something unlawful, am I liable too?

Not automatically, but the trail leads to you first because the traffic leaves through your subscription's address. What then matters is whether you can show the reasonable steps you took and who was using it at the time.

Am I required to keep records of who connects?

For a small business there is no general obligation to keep detailed records. But simple records actually protect you, because without them you have no way of showing that whoever was using it was not you. Those records are personal data themselves, so keep only what is needed and set a retention period.

Is leaving Wi-Fi open without a password risky?

Yes, and the risks stack. Beyond anyone being able to use it without a trace, an open network also means your own devices share a room with unfamiliar equipment you know nothing about.

Does a router used for guest Wi-Fi need to be certified?

Yes. Permenkominfo No. 2 of 2023 on class licensing, amended by Permenkomdigi No. 2 of 2025, requires Wi-Fi equipment traded or used in Indonesia to meet technical standards, proven by a certificate. Routers sold through official channels generally have one; the thing to watch for is imported equipment without a certification label.