Open the Wi-Fi portal in any café and the terms page feels familiar. The same sentences recur everywhere, because they were copied from one another.

The trouble is that some of the most common clauses protect nothing, while one clause that's rarely present is the one most needed.

What this page actually does

Guest Wi-Fi terms have three jobs, and only three:

  • Setting usage boundaries. What may not be done on your network.
  • Providing grounds to cut off access. Without written rules, blocking a user becomes a unilateral decision with nothing behind it.
  • Explaining what data is collected. The part most often forgotten, and the most binding.

What they don't do: remove your responsibility as the network provider. A sentence saying "we accept no responsibility for anything" doesn't make that obligation vanish. The scope is covered separately in the guide to Wi-Fi owner responsibilities.

Clauses that help, and clauses that fill space

ClauseIts value
Prohibition on unlawful activity Useful, grounds for cutting off access
Statement of data collected Useful, and necessary if you collect anything
Fair use limits Useful, grounds for throttling one heavy user
Service provided without warranty Useful, manages expectations about outages
"Free from all legal liability" Near meaningless, obligations don't vanish on paper
Clauses copied from another industry Often irrelevant, and undermines the whole document

A longer page isn't a stronger one. Clear, short terms are more likely to be read, and consent rests on understanding. Three paragraphs that land are worth more than three pages that get skipped.

The part most often got wrong

The moment you ask for a phone number, email, or name on the portal page, you are processing personal data. Your position becomes that of a data controller, with the obligations that follow.

So the terms need to state, in plain language:

  • What data is taken. Item by item, not "certain data".
  • What it's used for. If it's for marketing, say so, don't disguise it as "service improvement".
  • How long it's kept. Indefinite retention is hard to justify.
  • Who else receives it. Including the portal service provider, if any.
  • How to request deletion. One email address suffices, provided someone answers it.

The full obligations are in the guide to collecting customer data, and the legal grounding in the guide to the PDP Law.

The articles of law that touch this page directly

For a business in Indonesia, at least three laws speak directly to what goes on a Wi-Fi terms page. You don't need to memorise them. What you do need to know is that several habits common on portals actually run against them.

RuleWhat it says, brieflyWhat it means for your portal
Law 8/1999 (Consumer Protection), Article 18(1)(a) Standard clauses that shift the business's responsibility onto the consumer are prohibited "All risk is borne by the user" can't be relied on
Law 8/1999, Article 18(2) and (3) Standard clauses that are hard to see, not clearly legible, or hard to understand are also prohibited, and offending clauses are void by law Small grey text under the button isn't just a design issue
Law 27/2022 (PDP), Article 21 Where consent is the basis, the controller must state the purpose, data types, retention period, processing period, and the data subject's rights The five points above are an obligation, not a suggestion
Law 27/2022, Article 22(4) and (5) A consent request that includes another purpose must be clearly distinguishable and in plain language; otherwise it is void by law A marketing tick folded into the continue button risks being invalid
Law 27/2022, Articles 24 and 40 The controller must be able to show proof of consent, and stop processing within 3 x 24 hours after consent is withdrawn A consent record, and an inbox someone actually reads
Law 24/2009, Article 31(1) Indonesian must be used in agreements involving Indonesian private entities or Indonesian citizens An Indonesian version is required; English is an addition

Article 18 of the Consumer Protection Law applies where Wi-Fi is part of your business's service to consumers, as in a café, hotel, or clinic. The PDP Law's adjustment period was two years from its enactment on 17 October 2022 (Article 74). Since October 2024, "the rules aren't in force yet" is no longer an excuse. The law's definition of a data controller also carves out no exemption for small businesses, so a ten-table coffee shop counts too.

This is the most common mistake, and the easiest to fix.

Most portals bundle everything: "By continuing, you agree to the terms and conditions and to receive promotional information." One button, two consents of quite different character.

Agreeing to usage rules is a precondition of using the service, reasonably bundled with the continue button. Agreeing to marketing use of your data is not a precondition, since the Wi-Fi can be provided without it.

Separating them is straightforward:

The continue button covers usage rules

"By continuing, you agree to the network usage rules." Linked to the full page.

A separate tick box for marketing

Not ticked by default, and not blocking the continue button. This is what makes the consent meaningful.

A short note beside the input fields

One sentence saying what the data is used for, right where the user types it, not only on a separate page nobody opens.

Keep a record of the consent

The time and the version of the terms in force then. Without this record you can't demonstrate consent was ever given.

An adequate outline

As a starting point rather than a ready document, adapt it to your venue, and where the stakes are significant, a review by someone qualified is worth the cost.

  1. Who provides this network. Business name and contact details.
  2. Service provided as-is. No guarantee of speed or availability.
  3. What isn't allowed. Unlawful activity, attempts to reach other systems, and interference with other users.
  4. Fair use limits. If speed or duration is capped, say so.
  5. Data collected and why. The five points from the section above.
  6. User rights over their data. Access, correction, deletion, withdrawal of consent.
  7. Termination of access. That access may be stopped if terms are breached.
  8. Effective date. Undated terms are hard to refer back to.

Example: a small café with a MikroTik hotspot

Picture a twenty-table café in Yogyakarta. The internet is a home plan, guest Wi-Fi runs through a MikroTik router with a hotspot login page, and the owner wants to collect WhatsApp numbers to announce new menu items.

A MikroTik hotspot login page is an HTML file in the hotspot folder on the router. It can be downloaded, edited, and uploaded back. That means you can write the terms text and the separate tick box yourself, without subscribing to a portal service. The short text on the login page could read like this (shown here in English; the Indonesian version comes first on the real page), linking to the full version:

"This Wi-Fi is provided for café guests, with no guarantee of speed. Don't use it for unlawful activity or to disrupt other users; we may cut off access if that happens. The WhatsApp number you enter is used to log Wi-Fi sessions and kept for 90 days. [ ] I'd also like menu and promo updates by WhatsApp (optional, may be left unticked). To stop promos or request deletion: email the café address shown on site."

A few notes on this scenario:

  • If a phone number isn't really needed, MikroTik's hotspot has a trial login mode that grants access for a set time without an account. For a café that only wants to limit session length, it's the easiest way to collect zero data. Setting up the hotspot is covered in setting up a MikroTik hotspot for a Wi-Fi business.
  • The 90 days is only an example. What matters is that the number on the page matches what actually happens on the router or your portal service.
  • Venues with many foreign tourists, in Bali or Labuan Bajo for instance, should show an English version alongside the Indonesian one, not instead of it.
  • Whoever holds that inbox needs to know that a withdrawal of consent must be acted on within 3 x 24 hours, including when it arrives on a Saturday.

Keeping it aligned with what actually happens

Terms that don't match reality work against you, they become evidence that you stated something you didn't do.

Mismatches commonly found:

  • Stating data is kept six months while the portal system keeps it indefinitely.
  • Claiming the guest network is separate from operations when they're the same, see the guide to separating guest networks.
  • Promising deletion on request, with nobody reading the stated inbox.
  • Naming a business entity different from the one displayed at the venue.

Also worth confirming: that the terms page can actually be opened. A portal that never appears renders all of this moot, the causes are covered in the guide to a Wi-Fi login page that won't appear.

The bottom line

Guest Wi-Fi terms are useful for setting boundaries and explaining data, not for erasing responsibility. Clauses promising the latter are better not relied upon.

Separate consent to usage rules from consent to marketing, state plainly what you collect, and make sure the content matches what you actually do. The cheapest way to reduce risk remains the same: collect less to begin with.

Frequently asked questions

Do terms and conditions actually protect the Wi-Fi owner?

Partly, not entirely. They're useful for setting out what isn't allowed and giving grounds to cut off access. What they can't do is remove obligations that attach to you under applicable rules, those don't disappear because you wrote otherwise.

Is an "I agree" button enough?

For acceptable use, that button is adequate. For collecting personal data, consent needs to be more specific: users must know what is taken and what for. Bundling both into one tick makes the data consent weak.

Should the terms be in two languages?

An Indonesian version is required, since Article 31 of Law 24/2009 mandates Indonesian in agreements involving Indonesian private entities or citizens. If many of your visitors are foreign tourists, add an English version alongside it. Consent rests on understanding, and terms nobody understood are hard to call agreed.

How quickly must I act when a guest withdraws consent to their data?

Article 40 of the PDP Law requires processing to stop within 3 x 24 hours of receiving the withdrawal request. So the email address on the terms page has to be genuinely read, weekends included.

Can we require a national ID number before granting Wi-Fi?

Technically it can be asked for, but it's almost never worth it. That data is excessive for guest Wi-Fi, raises the damage if it leaks, and adds to your obligations as a data controller. A phone number or email covers nearly every need.