Access and Correction Requests Within 72 Hours: Building the Workflow Into Your Systems
November 13, 2026 · 6 min read · Etzal Group Team
Indonesia's Government Regulation 33 of 2026 (PP 33/2026), effective 16 January 2027, provides that requests from data subjects must be verifiable, recorded and able to be submitted electronically where processing is electronic. According to a summary by law firm DFDL, the regulation, which implements the Personal Data Protection Law, gives 72-hour windows to respond to requests for correction, access, a copy of data, withdrawal of consent and restriction of processing.
Three days is short for a mid-sized company, because one customer's data rarely sits in one place. The name is in the CRM, the invoices in the ERP, the complaints in a chat archive and an old form in someone's spreadsheet. Without a prepared workflow, the first request will consume all three days just on searching.
A note on sources: the article numbers below come from law-firm, consultancy and media summaries, not from the official text. We read the 72-hour windows in one source only, DFDL. Check the articles themselves before you set service targets.
What the regulation asks for
According to Veritask's summary (3 September 2026), Articles 20 to 27 provide that:
- requests must be verifiable and recorded
- requests must be able to be submitted electronically when processing is electronic
- the controller verifies the requester proportionately
- the data subject may complain to the supervisory agency (the Lembaga) if the controller is negligent (Article 27)
DFDL's summary (page updated 28 September 2026) lists 72-hour windows for five things:
| Request | Article, per DFDL |
|---|---|
| Correction | Article 71 |
| Access | Article 77 |
| Copy of data | Article 78 |
| Withdrawal of consent or stopping processing | Article 92 |
| Suspension or restriction of processing | Article 99 |
DFDL also notes that identity verification uses a proportionate mechanism (Article 25).
Two limits. First, the sources we read do not cite a 72-hour window for deletion, so do not treat it the same way. Second, according to RSM Indonesia (18 September 2026), the right to data portability and interoperability (Article 111 paragraph (3)) applies only where processing is based on explicit consent or performance of a contract and is carried out by automated means.
Katadata (3 September 2026) adds two related duties: Article 34 requires a mechanism for obtaining consent, electronic or otherwise, and Article 36 requires the controller to hold proof of the consent given. If someone withdraws consent, you first have to be able to find it.
Because the supervisory agency has not been established, the complaint procedure is not yet clear. Check the latest official announcement.
Designing one request workflow
This section is our practical advice for IT and operations teams handling data subject requests Indonesia will expect from January. The principle: one entry point, one log, one visible clock.
1. Intake
Provide a web form or a dedicated email address named in the privacy notice. The form asks for four things only: the requester's identity, the type of request, the data or service concerned, and a reply contact.
Requests will still arrive by WhatsApp, phone and at the shop counter. Train front-line staff to recognise them and enter them into the same form on the requester's behalf. The clock does not wait for a request to find the right person.
2. Proportionate verification
Proportionate means matched to the risk. We suggest:
- for a corrected delivery address, a confirmation link to the registered email or number is usually enough
- for a copy of full transaction history, ask the requester to log in or answer questions based on data only they would know
- do not request a new identity document unless needed, because that adds sensitive data you then have to protect
Write the verification rule per request type so staff do not improvise each time.
3. A map of where data lives
This decides whether three days is enough. Build a simple table: for each system, what personal data it holds, what the search key is (email, phone number, customer number) and who can export.
The systems most often forgotten: chat archives, call recordings, backups, shared inboxes, email marketing tools and files in shared folders. Decide now how each is searched, and which cannot be searched per person and so need fixing.
4. Logging
Log every request: date and time received, type, verification result, systems checked, action taken, date and time answered, and the handler. The log satisfies the "recorded" requirement and is your evidence if there is a complaint.
A spreadsheet is enough for low volume. If requests reach dozens a month, move to your existing ticketing system with a dedicated category.
5. A monitored clock
Each request has a deadline visible to the handler and their manager. Set reminders at hour 24 and hour 48. Name a deputy for holidays. Decide who has authority when a request cannot be met in full, for example because the data includes information about someone else.
Trade-offs to settle
- Automated or manual. A self-service portal where customers view and correct their own data removes most requests but needs development. A manual flow is cheap at first and expensive as volume grows. Start manual, measure volume for three months, then decide.
- Strict or light verification. Too light, and you may hand data to the wrong person, which is itself a data protection failure. Too heavy, and you obstruct the requester's right. Differentiate by request type.
- Fix the legacy system or limit the data. If an old system cannot be searched per person, the choice is to add search or to stop keeping personal data there. The second is often cheaper.
Test it before January
Ask two employees to file an access request for their own data as customers. Measure how many hours pass before a complete answer is sent and which system takes longest. The result is your fix list.
Handling data subject rights is, in the end, a question of data architecture. If your CRM, ERP and chat archive need to be connected so that a per-person search finishes in minutes, our enterprise software team can help design it.
This article is not legal advice. Confirm the deadlines and duties for your case with legal counsel and the official text of PP 33/2026.
Sources
- Veritask, 3 September 2026: technical rules for personal data protection under PP 33/2026
- DFDL, page updated 28 September 2026: Indonesia personal data protection law, GR 33/2026
- RSM Indonesia, 18 September 2026: summary of PP 33/2026
- Katadata, 3 September 2026: personal data protection regulation takes effect January 2027, new rules on children's data
Frequently asked questions
Must an access request really be answered within 72 hours in Indonesia?
According to DFDL's summary, PP 33/2026 sets 72-hour windows for correction, access, data copies, consent withdrawal and restriction of processing. We read this figure in one source only, so check the articles themselves.
Does the 72-hour window also apply to deletion?
The sources we read do not mention a 72-hour window for deletion. Do not assume it, and check the official text.
Is an online form required?
According to Veritask's summary, requests must be able to be submitted electronically when the data is processed electronically.
Related service
Website Development
Fast, SEO-ready websites that turn visitors into customers.
