You are using an outdated browser and your browsing experience will not be optimal. Please update to the latest version of Microsoft Edge, Google Chrome or Mozilla Firefox. Install Microsoft Edge

January 20, 2017

New Computer Crimes Act to Tackle Cybercrime amid Public Concerns over Online Freedom

Bangkok Post, Corporate Counsellor Column

The Thai government’s attempts to revamp the 2007 Computer Crimes Act (CCA) and grant authorities more power to investigate and apprehend perpetrators of increasingly diverse cybercrimes has raised consternation among internet users who fear the new and more stringent law may impinge on human rights and place restrictions on online activity in the country.

Thailand’s National Legislative Assembly (NLA) passed draft amendments to the 2007 Computer Crimes Act (CCA) on December 16, 2016, and it is now awaiting publication in the Government Gazette. The law will come into effect 120 days after its publication date.

According to a report issued by the NLA committee responsible for drafting the CCA, the amendments are intended to:

  • Enhance and update the 2007 CCA, which is outdated due to rapid changes in the nature of cybercrimes;
  • Introduce new committees; and
  • Adjust and rationalize the authority of officials under the new law.

However, the public appears not to share the government’s thinking behind this rationale, and before the law was passed, more than 340,000 people signed a petition objecting to the amendments as they believe the new CCA gives excessively broad authority to government agencies to act against online content containing information that is deemed inappropriate.

The activists fear abuse of the new enhanced powers under the new law could adversely affect the rights of people both inside and outside the country, and particular attention is focused on Sections 14, 18, and 20 of the CCA.

Under the new NLA-approved CCA, Section 14 introduces more offenses and offers more room for interpretation. Under this controversial section, the public are prohibited from entering (or knowingly sharing) a computer system that causes “damage to the public, creates panic, or causes harm to public infrastructure, national security, public security, or economic security.”

The broad scope of the new Section 14 operates as a catch-all for a wide range of offenses, thus compelling online users—including businesses—to be more discrete and mindful of publicly sharing information. Some argue this will force users to be more responsible in disseminating content online, while others contend that it serves to restrict freedoms for internet users.

Section 18 has also been severely criticized, as it broadly empowers officers investigating an offense under the CCA or other laws to enquire, request, access, seize, duplicate, and unlock computer systems to obtain the data in question. However, a court order is specifically required for the access, seizure, duplication, or hacking (unlocking) of computer systems that are not in the possession of the officers.

Although no mechanism is prescribed under the law detailing how the courts should exercise their judicial discretion in granting or declining an order, the wording of this section appears intended to limit questions about whether officers are deliberately or excessively exercising their broad authority over the unpossessed computer data.

But Section 18 does not require officers to obtain a court order if they wish to request Service Providers, such as online access providers or social media platforms, to provide “traffic data” information to facilitate an investigation into an offense under the CCA or other laws. Although the public has questioned why a court order is not required, these new powers will undoubtedly cause businesses and other public users to be more mindful of handling their “traffic data,” which could also be interpreted to include data messages sent through work or personal devices and computers.

Section 20 of the new CCA requires the formation of a new Computer Data Screening Committee to be appointed by the Digital Ministry, wherein three out of nine members must be representatives from the private sector, including human rights, media, and other related fields.

This new committee will have the authority to consider and provide second-tier approval to censor “inappropriate” computer data (i.e., defined as against good morals or public order) before the request to censor the “inappropriate” computer data can be submitted for court approval. The subsequent granting of a court approval will result in such data being censored. However, the public have questioned whether authorities need this type of oversight of all inappropriate computer data.

Public attention is now focused squarely on the Digital Ministry, the authority charged with ensuring the smooth implementation of the new CCA. The NLA drafting committee has recommended that the ministry conduct training and educate officials so they have a better understanding of cybercrime investigations and computer data evidence collection, to ensure enforcement of the CCA complies with their intentions.

It is hoped that correct and efficient enforcement by authorities will ease public concerns over the new Computer Crimes Act, although undoubtedly, concerns will remain as the public continues to debate whether the new act is wholly appropriate for computer and online users in Thailand. All business operators in Thailand will need to closely monitor the CCA’s implementation and enforcement to ensure compliance.

RELATED INSIGHTS​ 

August 10, 2026
On July 31, 2026, Thailand’s Big Data Institute (BDI) launched a public consultation on the principles of a proposed new data-sharing law, with comments accepted until August 31, 2026. If enacted, the law would establish Thailand’s first comprehensive framework for government and private-sector data sharing, creating a systematic, secure, and transparent regime to support analytics, policymaking, research, and innovation. Central Data-Sharing Platform The draft law establishes a central system for data sharing, managed by the BDI. Government agencies would be required to connect to the BDI’s Data Integration and Intelligence Platform (also referred to as D2), in accordance with the BDI’s rules and procedures. Five Dimensions of Data Sharing The draft law covers five key types of data sharing between government (G), businesses (B), and consumers (C): G2B: Private organizations may request government data specifically for research and development purposes. The BDI will assess the applicant’s data governance, security, and privacy capabilities whether such measures meet prescribed standards before forwarding the request to the relevant government agency within 90 days. Any dispute may be escalated to a newly established Data-Sharing Promotion Committee for final determination. G2G: Government agencies may request data from other agencies through the central system. The data-holding agency must respond within 90 days, taking legality, necessity, proportionality, public interest, and personal data protection into account. Disputes may be referred to the Data-Sharing Promotion Committee for adjudication. B2G: In emergency situations involving public safety, economic security, or disaster response, the Minister of Digital Economy and Society may require private entities to provide data through the central data-sharing system. Government agencies must specify the data requested, demonstrate its necessity and expected benefits, and request only data reasonably available to the data holder. Requests for personal data must be limited to the minimum amount necessary. B2C: Royal decrees may
August 10, 2026
Thailand’s Office of the Personal Data Protection Committee (PDPC) recently released draft guidance on records of processing activities (ROPA) for personal data controllers and processors under the Personal Data Protection Act B.E. 2562 (2019) (PDPA). The draft guidance, which was presented to the public on July 7, 2026, addresses both controller records of collection, use, and disclosure of personal data and processor records of processing activities carried out on behalf of controllers. If implemented, the guidance will significantly expand organizational expectations for ROPA preparation, maintenance, and use across all sectors. Key Takeaways The draft guidance contains several important implications for organizations subject to the PDPA: ROPA reframed as a core accountability tool. The guidance elevates ROPA from an administrative record to a central accountability mechanism, connecting controller duties with recordkeeping obligations. ROPA as a source for privacy notices and governance documents. ROPA should serve as the primary source for privacy notices and align with consent management, retention schedules, DPIAs, incident response plans, and vendor contracts. Expanded scope across all activities. ROPA must cover all processing activities across the organization—including security, finance, HR, and external contractors—with correct controller or processor classification for each. Ongoing maintenance and auditability. ROPA must be updated for any change to systems, purposes, or processors, reviewed at least annually, and maintained with version control and a designated owner. Enhanced vendor, processor, and cross-border transfer requirements. Organizations must document all processors, external recipients, and cross-border transfers, specifying purposes, access scope, and destination countries. Linkage with risk assessment, DPIAs, and LIAs. ROPA should assign risk levels to each activity and identify when data protection impact assessments (DPIAs) or legitimate interests assessments (LIAs) are required, functioning as a risk-management tool. ROPA and data breach readiness. Incomplete ROPA can delay breach response and notification. Organizations should map data flows, vendors,
August 4, 2026
Thailand’s Personal Data Protection Act B.E. 2562 (2019) (PDPA) could soon see some important changes, as a draft bill to amend the PDPA has been introduced in the House of Representatives. The draft amendment is currently in the public consultation phase, with comments accepted from July 16 to August 15, 2026. If enacted in its current form, the amendment would make three key changes: expanding the government exemption to cover anticorruption operations, introducing a statutory definition of “government agency,” and restructuring the lawful bases for personal data processing to align with international standards. Background The PDPA has encountered several enforcement challenges since its implementation, including three core problems identified by the bill’s sponsors: (1) the current exemptions for government agencies do not cover anticorruption and misconduct-prevention operations; (2) the PDPA lacks a clear statutory definition of “government agency,” causing legal uncertainty as to which entities are covered; and (3) the existing framework for lawful bases of data processing does not align with international standards—particularly the multiple-lawful-bases system in the EU’s General Data Protection Regulation (GDPR)—making compliance inflexible for both government and private sector entities. Expanded Government Exemption The current PDPA exempts government agencies performing duties related to national security (including fiscal security), public safety, anti-money laundering, forensic science, and cybersecurity. The proposed amendment adds “prevention and suppression of corruption and misconduct” to this list of exempted functions. This would allow anticorruption bodies—most notably the National Anti-Corruption Commission (NACC), which is identified as a directly affected party—to collect, use, and disclose personal data without being subject to PDPA requirements when carrying out their duties. New Statutory Definition of “Government Agency” Notably, while the current PDPA use the term “government agency” in several provisions, the term is not comprehensively defined, creating potential uncertainty as to its scope. The draft bill therefore
August 3, 2026
On July 23, 2026, the Bank of Thailand (BOT) released for public comment its draft Notification on Digital Channel Security, which would significantly expand the scope and stringency of Thailand’s existing mobile banking security framework. If finalized in its current form, the draft notification would extend mandatory security requirements to credit card providers and credit providers, cover internet banking in addition to mobile applications, phase out SMS one-time passwords (OTPs) for transaction authentication, and introduce biometric verification requirements for high-value transactions. The public comment period is open through August 24, 2026. Background The BOT’s existing Mobile Banking Security Notification, issued in 2024, sets minimum security standards for financial institutions, specialized financial institutions (SFIs), and e-money providers, significantly reducing “money-draining app” fraud. However, fraudsters have since shifted to nonbank providers and internet banking channels, prompting the BOT to propose broader security requirements. Expanded Scope of Regulated Entities and Channels The existing Mobile Banking Security Notification covers only financial institutions, SFIs, and e-money providers offering mobile banking services. The draft expands coverage in two key areas: entities and channels. On the entity side, it adds credit card providers and credit providers that offer fund transfers to third parties at other financial service providers or that provide cash withdrawal services to individual retail customers. On the channel side, it broadens coverage to include internet banking in addition to mobile banking. Strengthened Customer Authentication The draft introduces enhanced authentication requirements in three areas: Service enrollment and device changes. Providers must implement rigorous identity verification, notify customers of enrollment results through out-of-band communication channels, and adopt risk-mitigation measures such as cooling-off periods and temporary transaction limits. Transaction-level authentication. Providers must use two-factor authentication for fund transfers, cardless ATM withdrawals, and transaction limit increases. Secure authentication factors. Key requirements include the following: “What-you-know” factors must