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

February 1, 2017

Government Surveillance, Security, and Privacy: Does Security Always Win? (Part 2)

Data Privacy Asia Newsletter

This article was first published in the Data Privacy Asia Newsletter. For Part 1 of this series, please click here.

A question posed during the Data Privacy Asia 2016 conference held in Singapore in November 2016 was should there be a digital safe place where a person can go dark and be beyond the reach of government?

When attendees of the Data Privacy Asia 2016 conference were polled, a significant portion said they don’t trust their own government and, of course, they didn’t trust any other government either when it came to issues of privacy. At the same time attendees firmly believed that there should be a digital safe place, a place where we can ‘go dark’, a place that we can call our own. This is very fundamental. The EU concept that privacy is a fundamental human right was by and large reflected by the opinion of the conference attendees—and that we cherish our privacy and it’s important to us.

At the same time law enforcement has a legitimate need, using lawful processes such as search warrants for lawful interception and access, to obtain digital data to solve serious crimes.. When we consider the question of digital privacy, we cannot ignore the lawful and reasonable need for law enforcement access. The problem is, unfortunately, that governments around the world have different definitions of what a ‘crime’ is. While we would all agree that murder, rape, kidnapping and other violent crimes justify government access to digital data, on a showing of probable cause and a warrant, what about overly broad definitions of sedition, lese majeste, defamation? When spoken words, Facebook ‘likes’ and posts are considered criminal for expressing an opinion in certain countries, we start to cringe and seek safe places where we can express views without fear of arrest. It is at the fringes, not at the core, that many of us would say a government has gone too far.

The Search for Balance

It’s becoming more and more apparent that the right to privacy must be balanced—and that there is an obligation by a government to still do good old-fashioned police work, based on strong legal principles, and not just vacuum up our personal digital data when we consider where the line should be drawn. In the Apple/FBI case, there existed a situation where the company had created effectively a digital ‘safe place’. Apple, as a company, decided that they were going to strongly encrypt data on the iPhone, such that even in the face of a search warrant, they were unable to help the government obtain a person’s data on their phone. The action by Apple represented a shift in the source of personal liberty and rights. Should we have to rely on tech companies to make these decisions for us? I think there’s an argument that the law should actually provide that safe place, but the reality is this—Apple decided to level the playing field around the world for us all. In the face of differing laws in nations around the world as to what constitutes a ‘crime’ and differing scope of nations’ laws, Apple gave us something that, one could argue nations should be providing, namely, a digital safe place. This is unprecedented—that private tech companies (mostly from the U.S.A.) are empowering us where governments are generally moving in the opposite direction.

Should a foreign government have the legal right to remotely hack, compromise, or search a digital device for domestic criminal investigation in that country and then pass that evidence onto the country that you call home? This is not a theoretical issue. Actually, the U.S. government regularly engages in hacking of computers that it calls network investigative techniques or NITs under rule 41 of the U.S. Federal Rules of Criminal Procedure.

Just how valuable these powers can be became apparent during what is known as the ‘Playpen Case’. In this case the FBI seized a child pornography site that was run on the ‘Dark Web’ and assumed control. The FBI for a time then ran the site seeking to identify those downloading child porn. The FBI deployed a network investigative techniques where they created malware such that anybody that went to that site to download  illegal porn unknowingly downloaded the NIT malware that reported the user’s real IP address back to the FBI. Many of those IP addresses were in the U.S., some were in Europe, and some were in Asia. Arrests were made in the U.S., and for suspects outside the U.S. the FBI reported that information back to the respective countries for prosecution. This was done under a search warrant that extended to computers all over the US and to all over the world.

Since Playpen, Rule 41 has expanded—allowing U.S. judges to issue warrants when somebody is using TOR or they’re using a VPN such that the individual is masking the actual location of their computer and the real IP address. Effectively, U.S. investigations are now worldwide, extraterritorial and independent of local nations’ laws—and of course, other countries can take similar approaches deploying their own malware globally for various objectives they define (e.g. political, criminal or national security).  This global extension of search powers extraterritorially has rendered these investigations borderless and effectively resulted in a free for all in the sense that regardless of where you are and what local laws apply, no one is safe from a foreign or local government search (via malware). Of course, this has always been the case in terms of cyber criminals also seeking to gain access to our data.

The Issue of Biometric Keys

The use of biometric keys is becoming a more and more popular way to protect access to data. For example, fingerprint readers, voice authentication, iris scanners, face scanners. Using biometric keys that are unique to an individual does have the advantage of having a high degree of confidence that the person is who he or she says they are. The problem with the law in the U.S. and many other countries is that biometric attributes are not given the same level of protection as a password stored in somebody’s brain. Some U.S. courts have held that a password in somebody’s brain is protected under the 5th Amendment of the U.S. Constitution—the right to not incriminate yourself. Why? Because there is some degree of processing or thought process needed for someone to write or provide that password—and that thought process, if compelled, is effectively testimonial and therefore would be a violation of the 5th (at least according to some U.S. federal court decisions).

A fingerprint, an iris scan, a face scan or things like that are not so protected. For those of you wondering, from a U.S. legal perspective, you’re much better off turning off the fingerprint function on your iPhone because in the U.S. you cannot take the 5th and withhold your fingerprint to unlock the phone.

If a court issues, for example, a search warrant for the contents of your iPhone and you don’t unlock it, well, physical coercion to actually take your finger and put it on the home button is not going to be a violation of your rights in the United States. Some courts in the U.S. are issuing search warrants for places that include all digital devices found at the location and a requirement that anyone at the location provide their fingers to open such devices. These warrants are not without controversy and the cases and law are not settled, but that is the direction in which the government is moving.  In other countries, they may just throw you in jail until you unlock the phone or physically compel you to put your finger on that home button with no further legal process needed. As such, while convenient, the use of biometrics may not be the wisest decision in terms of keeping governments or street criminals from compelling access to you iPhone. If the government or street criminal has physical possession of your device and of your being—the biometric keys will be of little help.

Summary—This Is a Complex Issue

Privacy is a complex issue and will remain a thorny topic of discussion and legislation for the foreseeable future. As our world becomes more connected and devices, as well as data, form a greater part of our lives, we will all be faced with the question: what is too much when it comes to the balance between privacy and security—and should government be allowed unfettered access to information that we, not so long ago, had viewed as private. At the moment the lines are blurred and technology is driving the discussion as well as the expansion of government powers of mass surveillance and access to each of our digital trails (or digital ‘breadcrumbs’) that we create 24 hours, 365 days a year now from cradle to grave.

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