A creditor's request for a debtor's data is a request that a final judgment alone does not oblige a Thai company to grant. Under PDPC advisory opinions, the company must disclose on a court summons or order under Section 24(6); on a creditor's own letter it must run a balancing test under Section 24(5) first. HR, legal teams, banks and creditors' lawyers get a decision table and a letter checklist.
- A final judgment binds the debtor, not the bank or employer. The PDPC found no power in the Civil Procedure Code for a creditor to reach data held by outsiders.
- On a court summons or order, or an order from a state official with legal power, the company must disclose without consent (Section 24(6)).
- On a creditor's letter alone, the company must weigh the request itself under Section 24(5). If it fails, the debtor's consent is needed.
- Disclosure without a basis risks an administrative fine of up to THB 3 million (Section 83) and damages under Sections 77 and 78.
- Every such disclosure goes into the Section 39 record, and the PDPC advises recording the balancing reasons too.
Picture this: on a Monday morning HR opens an envelope from a law firm. Inside are a copy of a final judgment, a certificate that the case is final, and a letter asking for one employee's salary, pay date and bank account number. There is a court seal, a case number and a lawyer's signature. Every page looks official.
Many companies send the data at once because it seems to come from the court. Others refuse every request by citing the PDPA, even when the paper in front of them is a real summons. Both can be wrong, and each mistake has a section of the Personal Data Protection Act B.E. 2562 (2019) or another statute attached to it. The Office of the Personal Data Protection Committee (PDPC) has answered at least three advisory queries on the point. This article sorts the paper into what you must hand over and what you must think about first.
Can a creditor with a final judgment make a bank or employer disclose the debtor's data?
No. The question was put to the PDPC directly, in its advisory opinion on a judgment creditor asking a data controller to disclose the data of a judgment debtor under a final judgment. The applicant, Mr B, held a final judgment of a provincial court ordering the defendant to pay. He still had to trace assets himself, and banks refused to give deposit-account information on the ground that it was personal data.
The answer was not given lightly. The advisory sub-committee heard representatives of the Office of the Judiciary, the Thai Bankers' Association, the Bank of Thailand, the Lawyers Council and the Legal Execution Department, and put the issue to the Personal Data Protection Committee for interpretation under Section 16(10) before replying.
| What the creditor asked | The answer in the opinion |
|---|---|
| An interpretation that, once a creditor holds a final judgment, every bank and relevant state agency must send all of the debtor's data | Not granted. The PDPC found that the Civil Procedure Code contains no provision empowering a judgment creditor to access the debtor's data held by persons outside the case, such as banks |
| Guidelines and a memorandum of understanding with the Bank of Thailand, the Department of Lands, the Department of Land Transport and the Marine Department, so that data is handed over promptly once the evidence is checked | No such guideline was issued. The opinion is legal advice, and the PDPC Office would forward it to the agencies concerned for consideration within their own duties and powers |
| Treatment of the request as part of enforcing the judgment | Disclosure by a bank, the Department of Lands or any other body acting as data controller is not part of court adjudication or legal execution. It is not exempt under Section 4(5), so the PDPA applies in full |
What the PDPC said about the Civil Procedure Code
Civil lawyers should read this part slowly. The opinion states that tracing the debtor's assets after a final civil judgment is the judgment creditor's job; once assets are found, the creditor informs the execution officer, who seizes, attaches or auctions them. The creditor is not left without a route, though. The PDPC pointed to two sections as amended by the Act Amending the Civil Procedure Code (No. 30) B.E. 2560 (2017).
- Section 277, as the opinion summarises it. Where the creditor has reasonable grounds to believe the debtor has more assets than the creditor knows of, or does not know where they are, the creditor may file an ex parte motion for a court inquiry. The court may summon the debtor or any other person likely to give useful statements, and may order that person to produce documents or material evidence relating to the debtor's assets, on such terms as the court sees fit.
- Section 283, as the opinion summarises it. Where there is reason to believe that assets, accounts, documents, letters or other objects relating to the debtor's property or business are in a place occupied by another person, the creditor may apply ex parte for a search warrant. The court inquires without delay and, if satisfied on the evidence, may issue a warrant for the execution officer to inspect and seize within the limits the court considers necessary.
The PDPC therefore concluded that the Civil Procedure Code already lays down the steps for reaching information about a judgment debtor's assets, and that Mr B could use them. The Code itself is not in our law corpus, so the paragraphs above report only the opinion's own summary. Anyone drafting a real motion must work from the current text of the Code.
Which letters must you obey at once, and which leave the decision to you?
Read together, the three opinions sort incoming paper into groups by the power of the sender. The lawful basis differs, and so does the burden on the company. In the first group there is nothing to weigh. In the others the company must reason, record and defend its own choice if the debtor complains.
| Who is asking | What they show | Disclose or not | PDPA basis | What to log |
|---|---|---|---|---|
| A court | A summons or court order to give a statement or produce documents or material evidence | Disclose what the summons or order specifies. No consent needed | Section 24(6) with Section 27, paragraph one (judgment-creditor opinion) | Case number, summons number, date, items sent, recipient |
| A state agency or official empowered by statute to demand documents, such as a competent official of the Office of the Consumer Protection Board | A written demand citing the empowering section | Disclose, limited to what is necessary for the demand | Section 24(6) with Section 27, paragraph one, and Section 21, paragraph two (2) (mobile-operator opinion) | Statute and section cited, title of the official, items sent; enter in the Section 39 record |
| A judgment creditor or the creditor's lawyer | A letter of request with the judgment and a certificate of finality | No duty to disclose. The company weighs the request; if it passes, it may disclose; if not, the debtor's consent is needed | Section 24(5) with Section 27, paragraph one | The three-step assessment, the reasons for disclosing or refusing, items sent, and the disclosure itself under Section 27, paragraph three |
| The company's own lender, asking for the company's list of borrowers as business collateral | A clause in the loan agreement between the company and its lender | May disclose if the assessment passes, limited in both items and frequency | Section 24(5); not consent tied to the customer's loan contract and not Section 24(3) (personal-loan company opinion) | The assessment, the clause barring the lender from other uses, the channel for objections |
| A person or body with no statutory power to demand, simply asking for cooperation | A courtesy request citing no empowering section | Do not treat it as a legal obligation. Find another basis case by case | Section 24(6) is not available; Section 24(5) may be, if the assessment passes (observation in the mobile-operator opinion) | Reasons for disclosing or refusing, and the reply letter |
| A debt collector phoning HR | Nothing in writing | Give nothing over the phone. Ask for a written request | No basis yet, until a written request can be assessed | Date, time, caller's name, what was asked, what was said |
(6) it is necessary for compliance with a law to which the Data Controller is subjected.
The judgment-creditor opinion says that a controller receiving a summons or court order, or an order from another state agency or official with legal duties and powers, has a duty to disclose. For a request from the judgment creditor it switches wording: the controller has a duty to consider. The gap between those two phrases is the whole subject of this article.
(5) it is necessary for legitimate interests of the Data Controller or any other Persons or juristic persons other than the Data Controller, except where such interests are overridden by the fundamental rights of the data subject of his or her Personal Data;
With only a creditor's letter, how should the company weigh it?
The PDPC points to a three-step Legitimate Interest Assessment (LIA), with particular attention to whether the creditor's interest is no less weighty than the privacy the debtor would lose. If the request fails any step, disclosure needs the debtor's consent. Each step is explained in Legitimate Interest Under PDPA: Three Questions to Answer.
| Step in the opinion | What the PDPC asks you to consider | Questions to put to this letter |
|---|---|---|
| 1. Purpose Test | Whether the reason for, and benefit of, the disclosure is lawful | Is there really a final judgment? Is the requester the judgment creditor or a properly authorised agent? Is the aim enforcement, or pressure on the debtor? |
| 2. Necessity Test | How necessary the disclosure is, and whether another route would affect the data subject's rights less | Could the creditor apply to the court through the routes the PDPC described? Does the request go beyond what is needed to identify assets? Would confirming current employment be enough? |
| 3. Balancing Test | The creditor's interest against the debtor's fundamental rights, without undue impact on the right to privacy | Would the debtor expect an employer to pass this to an outsider? Does the privacy notice mention this kind of recipient? Does the data touch other people, such as family, or include Section 26 data? |
Step two is where creditors' letters most often fail, because the same opinion has just explained that a court route exists. A company that replies by pointing the requester to the Civil Procedure Code, and undertakes to comply with any summons or court order at once, has the opinion behind it and is not obstructing enforcement.
If the debtor objects
Data disclosed on the Section 24(5) basis is open to objection under Section 32(1). The opinion says that when the debtor objects, the controller must prove either a compelling legitimate ground or that the disclosure serves legal claims. That burden sits with the company, not with the creditor who already has the data.
(b) the collection, use, or disclosure of such Personal Data is carried out for the establishment, compliance or exercise of legal claims, or defense of legal claims;
Three opinions, three answers: which one is your company?
No exemption under Section 4(5). The holder must disclose on a court summons or order under Section 24(6). On a creditor's request alone it must assess under Section 24(5), and needs consent if the request fails. Banks must also follow the financial institutions business law, and state agencies the Official Information Act B.E. 2540 (1997).
The PDPC said that making consent to this disclosure a condition of the customer's loan contract cannot be done under Section 19, paragraph four. The contract basis in Section 24(3) does not fit either, since the disclosure serves the company. What remains is an assessment under Section 24(5), with items and frequency kept to what is necessary and a way for customers to object.
The Office used a competent official's power under Section 5(4) of the Consumer Protection Act B.E. 2522 (1979) to demand documents and evidence. The operator therefore has a duty to disclose under Section 24(6) with Section 27, paragraph one, may do so beyond the original purpose under Section 21, paragraph two (2), must send only what is necessary under Section 22, must log it, and should name this kind of agency in its privacy notice.
The mobile operator: a state requester does not switch the PDPA off
The operator asked whether the request fell under the Section 4(2) exemption for agencies charged with state security. The PDPC answered that the exemption covers only activities connected with maintaining state security; receiving consumer complaints and protecting consumer rights is broad work of a different kind. The PDPA therefore applies. That finding takes nothing from the agency's power, because the PDPC went straight on to say the operator must hand over what was demanded.
The lesson for companies is in the opinion's next sentence. A controller that discloses to a state-security agency is not itself exempt and keeps every PDPA duty. It is the same principle set out in Police Want Customer Data: What a Thai Company May Hand Over, which deals with criminal cases; this article is its civil and commercial counterpart.
The PDPC added that a telecom operator must also follow its sector rules under Section 3(1) of the PDPA: the frequency allocation law, the telecommunications business law, and the broadcasting and telecommunications regulator's notification of 17 August 2023 on protecting telecom users' personal data. Any regulated business, whether a bank, an insurer or a hospital, should open its own statute alongside the PDPA.
The loan company: one day your lender may ask for your whole debtor book
The company's lender required names, ID numbers, addresses, phone numbers, contract numbers, outstanding instalments and claim values for its borrowers, to prepare for a future assignment of claims, with the pool topped up monthly. The company asked whether it could simply write consent into its customers' loan contracts.
Also, the entering into the contract, including any provisions of the service shall not be a condition to obtaining consent for the collection, use, or disclosure of Personal Data that is not necessary or not related to such contract entering, including the provisions of the service.
The PDPC also noted that consent can be withdrawn at any time, so collateral that depends on a continuing flow of data would rest on an uncertain basis. The route it left open is Section 24(5): a commercial interest can be a legitimate interest if the three-step assessment passes. Its examples include that an assignment does not make the customer liable for more than the existing debt, and that the customer could in good faith expect such use.
Conditions follow. Send only the items needed for the collateral; prefer less identifying data where it does the job; review the frequency; name this kind of recipient in the privacy notice under Section 23(4); provide a channel for objections under Section 32(1); and bind the lender not to use the data for anything else, under Section 27, paragraph two and Section 37(2).
A debt collector phones HR. What may you say?
This happens more often than a lawyer's letter, and a second statute comes in. Section 8 of the Debt Collection Act B.E. 2558 (2015) bars a debt collector from contacting anyone other than the debtor for the purpose of collection, apart from a person the debtor has designated, and narrowly limits what may be asked of anyone else.
Contact with any other person apart from the person under paragraph one may be made only for the purpose of inquiring about or confirming debtor contact location information or information about the person whom the debtor has designated for debt collection
Section 8 is a duty on the collector. It does not order the employer to answer and gives the employer no PDPA basis. It still helps HR a great deal. If the caller is a debt collector as defined in Section 3 and asks about salary or pay dates, or mentions that the employee owes money, the caller is going beyond what Sections 8 and 11(3) of that Act allow. The company has no reason to cooperate.
AIPDPA's suggested practice is one sentence for whoever takes the call: the company does not give employee information by phone, please write to the legal team. Then note the date, time and caller's name. This is good practice, not a legal duty, but it removes the risk of one member of staff disclosing on the company's behalf with no assessment at all.
Wrongly disclosing versus wrongly refusing: what does each cost?
The two mistakes are punished in different places. Disclosing without a basis falls under the PDPA: civil, administrative and, in some cases, criminal. Refusing when the law demands disclosure falls under the statute that empowers the requester. The table cites only sections in our corpus and what the opinions themselves state.
| Mistake | Consequence | Source |
|---|---|---|
| Sending a debtor's data to a creditor with neither consent nor a Section 24 basis | Administrative fine of up to THB 3 million | PDPA Section 83 (breach of Section 27, paragraph one) |
| The data sent includes Section 26 data, such as health data or criminal records | Administrative fine of up to THB 5 million and, where the conditions of Section 79, paragraph one are met, imprisonment of up to six months, a fine of up to THB 500,000, or both | PDPA Sections 84 and 79 |
| The debtor suffers damage from the disclosure, for example collection calls at work | Compensation whether or not the act was intentional or negligent, plus punitive damages of up to twice the actual compensation at the court's discretion | PDPA Sections 77 and 78 |
| Sending the whole file, beyond what the summons or demand names | Administrative fine of up to THB 3 million | PDPA Section 83 (Sections 21 and 22); the mobile-operator opinion stresses disclosure only as necessary |
| Disclosing and not recording it | Administrative fine of up to THB 1 million | PDPA Section 82 (Section 39, paragraph one) with Section 27, paragraph three |
| Refusing to send documents demanded by a competent official of the Consumer Protection Board under Section 5 | The PDPC states that this is a criminal offence under Section 45 of the Consumer Protection Act B.E. 2522 | Mobile-operator opinion (that Act is not in our corpus, so no penalty figures are given) |
| Refusing a court summons or order by citing the PDPA | The PDPC's view is that the company has a duty to disclose as ordered, so the PDPA is no excuse. The consequences of disobeying a court are set by procedural law | Judgment-creditor opinion (procedural consequences not stated here; the Code is not in our corpus) |
Any Data Controller who violates or fails to comply with section 21, section 22, section 24, section 25 paragraph one, section 27 paragraph one or two, section 28, section 32 paragraph two, or section 37, or who obtains consent by deceiving or misleading the data subject about the purposes, or fails to comply with section 21 which applies mutatis mutandis according to section 25 paragraph two, or fails to send or transfer the Personal Data in accordance with section 29 paragraph one or paragraph three, shall be punished with an administrative fine not exceeding Baht three million.
The court shall have the power to order the Data Controller or the Data Processor to pay punitive damages in addition to the actual compensation rendered by the court as deems fit, but shall not exceeding two times of such actual compensation amount
The defence a creditor's letter cannot give you
Section 77 lets a controller escape civil liability in two situations. The second is exactly on point.
(2) an action taken in compliance with an order of a government official exercising its duties and power under the law;
On its wording, a company that discloses under a court summons or a competent official's demand has this defence available if the debtor sues. A company that discloses on a letter from a creditor or the creditor's lawyer does not: a creditor is not an official and a letter is not an order. This is AIPDPA's reading of the text, not a PDPC opinion, but it explains why the two kinds of paper carry such different risk for the person who signs the reply.
Who inside the company is exposed
Administrative fines and compensation fall on the data controller, meaning the company. Criminal liability under Section 79 is tied to Section 26 data, and where the company commits a criminal offence, Section 81 can reach individuals: those who gave the instruction, and those who had a duty to instruct or act and did nothing. A company in which nobody is assigned to check data requests before they are answered is exposed on that second limb.
In the case where the offender who commits the offense under this Act is a juristic person and the offense is conducted as a result of the instructions given by or the act of any director, manager or person, who shall be responsible for such act of the juristic person, or in the case where such person has a duty to instruct or perform any act, but omits to instruct or perform such act until the juristic person commits such offense, such person shall also be punished with the punishment as prescribed for such offense.
A request for debtor data has arrived. What do you check before replying?
The list applies to any letter asking for data about a debtor, customer or employee. Items 1 to 3 place the letter in a row of the decision table. Items 4 to 8 apply whether you disclose or refuse. Where an item is AIPDPA's good practice and not a legal duty, it says so.
- Who signed it? A court, an execution officer, a competent official of a state agency, or a party's lawyer? A court seal on an attached copy of the judgment does not turn a lawyer's letter into a court order.
- What power does it cite? Does it name the statute and section that empower a demand for documents? If it only asks for cooperation, the mobile-operator opinion has already said Section 24(6) is unavailable.
- Is it genuine? Call the court's or agency's switchboard, not the number printed on the letter. (Good practice.)
- Whose data, which items, which period? If the request is broad, such as all information, ask in writing which items are needed and why.
- On what basis was the data collected, and is Section 26 data mixed in? Check your record of processing first. Remove health data or criminal records, or pass the matter to a lawyer.
- Assess and record. For a Section 24(5) request, run the three steps and have an authorised person sign. The PDPC advises entering the balancing reasons in the Section 39 record.
- Send only what is necessary, and send it securely. Extract the named items, redact other people's data in the same document, and use a traceable channel, under Sections 22 and 37(1).
- Log the disclosure or the refusal. Date, requester, document relied on, items sent, basis and approver, under Section 27, paragraph three.
A five-question self-test
Answer yes or no. Two or more noes mean your company could disclose wrongly, or refuse wrongly, with the very next envelope.
- Do the staff who open post and answer phones know where every data request must go, and that they must not answer it themselves?
- Can the company tell a court summons or order from a letter written by a party to the case?
- Is there a three-step assessment form ready to use, and a named person with authority to sign it?
- Do the customer and employee privacy notices list courts, state agencies and persons entitled by law as recipients under Section 23(4)?
- How many disclosures to outsiders did the company make last year? Can you answer from your records, or only by asking each department?
A seven-day plan before the next letter arrives
- Day 1Set one intake point. Every letter or call asking for personal data goes to legal or the DPO. Tell HR, accounts, sales and reception.Section 37(1)
- Day 2Look back twelve months: what was sent to creditors, lawyers or agencies? Where nothing was recorded, record it now with whatever reasons the evidence supports.Section 27 para. 3 · 39
- Day 3Write a one-page triage sheet from the decision table: court, empowered official, creditor, courtesy request.Section 24(5), (6)
- Day 4Prepare the three-step assessment form for creditor requests, name the approver, and prepare a refusal letter that points to the court route the PDPC described.Section 24(5) · 32(1)
- Day 5Review customer and employee privacy notices. Add the recipient categories and purposes for disclosures required by law.Section 23(1), (4)
- Day 6If you routinely send debtor lists to a lender, an assignee or a collection agency, review the items, the frequency and the purpose-limitation clause in line with the loan-company opinion.Section 22 · 27 para. 2 · 37(2)
- Day 7Run one drill with three hypothetical inputs: a court summons, a creditor's lawyer's letter, and a call from a debt collector. Does each reach the right person within a day?Good practice
For creditors and their lawyers: how do you ask and actually get the data?
Mr B's opinion tells creditors plainly that the route with compulsion behind it runs through the court. Once a court issues a summons or order, the bank or employer has a duty to disclose under Section 24(6) and no PDPA ground to refuse. A direct letter is still permitted, but the recipient may decline, and a careful recipient will decline unless the letter helps it pass the assessment.
- State a narrow purpose. Enforcement of which judgment, with proof that it is final and proof of your authority to act.
- Ask for no more than you need. Request the items that identify assets, not the personnel file. A broad request fails the necessity step every time.
- Explain why this route. The recipient has to answer whether a less intrusive way exists.
- Accept limits on use. Section 27, paragraph two binds you already. Confirming it in the letter helps the recipient decide.
- If you are a debt collector under the Debt Collection Act, do not tell the employer that the debtor owes money, and do not ask for more than contact location information. Sections 8 and 11(3) prohibit it.
The Person or juristic person who obtains Personal Data as a result of the disclosure under paragraph one shall not use or disclose such Personal Data for any purpose other than the purpose previously notified to the Data Controller in the request to obtain such Personal Data.
What do the three opinions leave unanswered?
An advisory opinion is the sub-committee's view on the facts put to it. It is legal advice, not an order or a judgment. Mr B's opinion carries extra weight because the Personal Data Protection Committee interpreted the point under Section 16(10) before the reply went out. Even so, at least four matters are not settled, and this article does not settle them either.
- The outcome of the balancing in any given case. The PDPC set out the method. It did not say a judgment creditor always wins or always loses. Each request must be assessed on its own facts.
- Sector law for banks and state agencies. The opinion says only that the financial institutions business law and the Official Information Act B.E. 2540 must also be followed, and that controllers may consult the Bank of Thailand or the Office of the Official Information Commission.
- The form of a motion, time limits and the consequences of ignoring a summons. These are in the Civil Procedure Code, which is not in our corpus.
- Each type of paper an execution officer may send. The opinion speaks generally of orders from state agencies or officials with legal duties and powers and does not classify them one by one. If you cannot tell whether a document is an order, have a lawyer read it before replying.
If you are unsure on what basis each dataset in your company was collected, start with choosing the right PDPA lawful basis. For how to describe recipients in a notice, see a privacy notice people actually read, and for the full list of PDPA sanctions, the PDPA penalties guide.
Frequently asked questions
A creditor sends a final judgment and asks for an employee's salary. Must the company disclose?
Not yet. Under the PDPC's opinion, a request from a judgment creditor gives the company a duty to consider it under Section 24(5) with Section 27, paragraph one. If the assessment fails, the employee's consent is needed. The duty to disclose arises on a court summons or order, or an order from a state official with legal power.
We received a court summons to produce documents about a debtor's assets. Do we need the debtor's consent?
No. The PDPC treats this as compliance with a law to which the controller is subject, under Section 24(6) with Section 27, paragraph one. Send what the summons specifies and no more, and enter the disclosure in your records.
Can a bank refuse to give a debtor's account data by citing the PDPA?
On a direct request from the creditor, yes, if the assessment under Section 24(5) fails, and the bank must also follow the financial institutions business law. On a court summons or order, the PDPC's view is that the bank has a duty to disclose.
A state agency asks for customer data as a courtesy and cites no empowering section. Must we send it?
The mobile-operator opinion observes that where the requester is not exercising a statutory power to demand, Section 24(6) cannot be the basis. Another basis must be found case by case, such as Section 24(5). In practice, ask in writing which statutory power is being used.
Can we write into the loan contract that the customer consents to disclosure to our own lender?
The PDPC told the loan company that making this consent a condition of the loan contract cannot be done under Section 19, paragraph four, because it is generally not necessary for or related to the customer's loan. It pointed to Section 24(5) with a three-step assessment.
A debt collector phones to ask whether an employee still works here. May we answer?
Section 8 of the Debt Collection Act lets a collector ask third parties only about the debtor's contact location information, but it does not order the employer to answer, and the company still needs its own PDPA basis. The safe practice is to give nothing by phone and ask for a written request.
You have read it. Now get it done
Open the demo account to see the real AIPDPA system with a sample company: RoPA, the 72-hour breach clock, data subject requests, cookie consent and ready-to-use documents, all in one place.
From 2,900 THB/year (11 modules) · all 24 modules from ENTERPRISE at 19,900 THB/year · demo account, no sign-up
No time? Have our lawyers handle it →Kooru's lawyers set it up and act as your DPO
Law and sources
- Personal Data Protection Act B.E. 2562 (2019) — Section 3 · 4 · 19 · 21 · 22 · 23 · 24 · 27 · 32 · 37 · 39 · 77 · 78 · 79 · 81 · 83 · 84
- Debt Collection Act B.E. 2558 (2015) — Section 3 · 8 · 11 (3)
Text in the "The text" boxes is copied word for word from AIPDPA's legal knowledge base, transcribed from the Royal Gazette and official documents; every edit is checked by the system against that base, character by character. English wording is an unofficial translation; the Thai text prevails. This article is general information, not legal advice for a particular case.

