Every time you fill in a form on a cafe's Wi-Fi login page, an exchange takes place: internet access for a quantity of personal data. Law Number 27 of 2022 on Personal Data Protection was promulgated on 17 October 2022 and gave data controllers an adjustment period of up to two years (Article 74). Since that period ended in October 2024, the exchange has had a fully binding legal framework.
What follows is a summary from both sides: as the person whose data is collected, and as the party collecting it.
Note: this article is educational and is not legal advice. For how it applies to a specific situation, consult a competent legal adviser.
Two categories of personal data
The PDP Law separates personal data into two groups with different levels of protection.
| Category | Examples | Level of protection |
|---|---|---|
| General personal data | Full name, sex, nationality, religion, email address, phone number | Standard |
| Specific personal data | Health data, biometrics, genetics, criminal records, children's data, personal financial data | Stricter |
The distinction matters in the context of public Wi-Fi. A portal asking for a name and email sits in the first category. A portal asking for national identity details or financial information enters far more sensitive territory, and needs strong justification.
Your rights as a data subject
The law grants a set of rights you can exercise. The ones most relevant day to day:
- The right to be informed (Article 5). You are entitled to know who is requesting the data, the legal basis, the purpose of processing, and who is accountable.
- The right to rectification (Article 6). Inaccurate data can be completed or corrected on request.
- The right of access (Article 7). You can request a copy of the personal data held about you.
- The right to end processing and to erasure (Article 8). You can ask for processing to stop and for the data to be deleted or destroyed.
- The right to withdraw consent (Article 9). Consent once given can be withdrawn.
- The right to object to automated decisions (Article 10). You can object to decisions made solely by automated processing, including profiling, where they have legal or significant effects on you.
- The right to postpone or restrict processing (Article 11), proportionate to its purpose.
- The right to sue for compensation (Article 12) if your data is mishandled.
- The right to data portability (Article 13). You can obtain your data in a machine-readable format and send it to another controller.
Note that the PDP Law does not set out a specific right to object to marketing as some other countries do. For promotional messages, the most practical routes are withdrawing consent (Article 9) or asking for processing for that purpose to stop (Article 8).
Obligations of a public Wi-Fi operator
If you run a guest network that collects visitor data, you act as a data controller. The main obligations:
Have a lawful basis for processing
Consent is the most common basis in a guest Wi-Fi context. It must be given knowingly, be specific to each purpose, and must not be imposed as a hidden condition.
Give clear notice
The privacy policy must be reachable directly from the portal page, written in language a layperson understands, and explain what data is collected and what for.
Limit collection to what is needed
The data minimisation principle means collecting only what the stated purpose requires.
Apply adequate security
Encryption in storage and in transit, restricted staff access, and activity logging are a reasonable minimum standard.
Set a retention period
Data must not be kept forever. Decide on a period, state it in the policy, and delete regularly.
Prepare an incident procedure
If a data protection failure occurs, the controller must notify the data subjects and the supervisory agency in writing no later than 3 x 24 hours (Article 46). The notice covers what data was exposed, when and how it happened, and the steps taken to deal with it.
Practical steps to protect yourself
Use a dedicated email address for sign-ups
Creating one separate address for free-service registrations keeps your main inbox clear of promotions, and limits the fallout if a leak occurs.
Fill in only the required fields
Many forms collect more than they need. Optional fields can be skipped without affecting the service.
Read the checkboxes rather than just clicking
Look for a separate marketing box and check whether it is pre-ticked. Consent that arrives already ticked does not meet the lawful standard.
Make use of randomised MAC addresses
Modern Android and iOS offer per-network MAC randomisation, which makes tracking across locations harder. It is on by default on most recent devices.
Review app permissions periodically
Apps requesting constant location access or your contact list without a clear reason are worth re-evaluating, regardless of which network you are on.
Signs of unreasonable data collection
- Asking for a national identity number for a service that does not need one.
- No privacy policy provided, or the link does not work.
- The marketing consent box arrives pre-ticked.
- No information about who the data controller is.
- Asking for the password to another service.
- No way to unsubscribe from the promotional messages sent.
Finding even one of these is reason enough to abandon the sign-up and use mobile data instead.
Examples you often meet here
Some situations typical of Indonesia, and how to handle them:
- A café or waiting room asks for your WhatsApp number to log in to Wi-Fi. This is common and not automatically a breach, as long as the purpose is explained. If you are then added to a promotional group or receive broadcast messages you never agreed to, you are entitled to withdraw consent and ask for your number to be deleted.
- A portal asks for your NIK (national ID number) or a photo of your KTP just for internet access. For guest Wi-Fi, a request like this is hard to justify under the principle of collecting only what is needed. Leaked KTP photos are raw material for illegal online loans and for accounts opened in someone else's name. Refuse, and use mobile data.
- A guesthouse or boarding house (kos) asks for a copy of your KTP on arrival. This is more reasonable because guest registration is needed, but you can ask where it is stored, who can see it, and when it is deleted. Writing the purpose and date across a KTP photocopy is a simple habit that makes the copy harder to reuse.
An example access or deletion request
There is no standard form. A short message by email or to the business's official WhatsApp is enough as a written record, for example:
"I am [name], a guest Wi-Fi user at [business name] with number [number]. Under Article 7 of Law No. 27 of 2022, I request a copy of the personal data you hold about me. Under Article 8, I also request that this data be deleted and no longer used for promotion."
For access requests, the controller must respond no later than 3 x 24 hours after receiving the request (Article 32). The same deadline applies to correction requests (Article 30). Keep a screenshot of your message with its date.
Figures and articles worth remembering
| Matter | Provision | Article |
|---|---|---|
| Adjustment period for controllers and processors | Up to 2 years from promulgation | 74 |
| Responding to an access request | No later than 3 x 24 hours | 32 |
| Responding to a correction request | No later than 3 x 24 hours | 30 |
| Breach notification | No later than 3 x 24 hours, in writing | 46 |
| Administrative fine | Up to 2% of annual revenue | 57 |
| Unlawfully obtaining someone else's data | Up to 5 years in prison and/or a fine of up to Rp5 billion | 67(1) |
| Unlawfully disclosing someone else's data | Up to 4 years in prison and/or a fine of up to Rp4 billion | 67(2) |
| Supervisory agency | Established by the President | 58 |
Those criminal penalties apply to anyone, including an employee who copies the customer number list from a Wi-Fi portal and sells it. For a small business owner, that's a strong reason to limit who can open that data.
Understanding the roles: controller and processor
The law distinguishes two roles that determine who is responsible for what.
- The personal data controller decides the purpose and directs the processing. In a venue Wi-Fi context, the business owner is usually the controller.
- The personal data processor processes data on the controller's behalf. A captive portal platform provider is generally the processor.
This distinction matters because the controller remains responsible even when the technical processing is carried out by someone else. A written agreement with the platform provider setting limits on data use is therefore a sensible step, and one small businesses often skip.
A compliance checklist for small venues
| Aspect | Question to answer |
|---|---|
| Basis for processing | What is our lawful basis for collecting this? |
| Minimisation | Is every field genuinely necessary? |
| Notice | Can the privacy policy be opened from the portal? |
| Marketing consent | Is it separate and not pre-ticked? |
| Retention | How long is data kept, and who deletes it? |
| Internal access | Who on the team can see this data? |
| Processor | Is there a written agreement with the platform provider? |
| Data subject requests | Who handles them, and within what period? |
| Incidents | What is the first step if there is a leak? |
Answering these nine questions in writing, even on a single page, already puts your business well ahead of most comparable venues.
Daily habits that protect your data
- Use a password manager so every service has a different password.
- Turn on two-factor authentication for your main email first, since that account is the recovery key for the others.
- Review the list of apps connected to your Google or social media accounts every few months.
- Check whether your email address has appeared in any publicly known breach. If your data did leak, the steps to secure things and the routes for complaining are in the guide to reporting a personal data breach.
- Limit what you share on any online form, not only Wi-Fi portals.
Effective data protection is not the result of one big action, but the accumulation of small habits applied consistently.
Closing
The PDP Law shifts the balance towards the individual, but a law only works when its rights are used. Reading a form before filling it in, refusing excessive requests, and exercising the right to erasure are simple habits with real effect.
For venue operators, compliance is more than avoiding penalties. Transparent data practice is one of the most effective ways to build trust, capital that no marketing budget buys easily.
See also the guide to compliant Wi-Fi marketing and the 12 steps to public Wi-Fi safety.
Frequently asked questions
How long does an operator have to respond to a request for a copy of my data?
Under Article 32 of the PDP Law, the controller must provide access no later than 3 x 24 hours after receiving the request. The same deadline applies to correction requests under Article 30. Make the request in writing, such as by email, so there is a dated record.
May a café ask for a photo of my KTP to log in to Wi-Fi?
No provision names Wi-Fi specifically, but the PDP Law requires collection to be limited to its purpose. For basic guest internet access, a KTP photo is hard to justify. You are entitled to refuse and use mobile data instead.