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

April 1, 2016

The United States vs. Apple and Microsoft: The Makings of a Perfect Storm

Bangkok Post, Corporate Counsellor Column

Last month, a U.S. court in California issued an order to Apple that was metaphorically equivalent to a magnitude 9 earthquake cutting through the Silicon Valley. The order shook the tech world to its core, requiring Apple to write code to bypass a security feature of its product to allow a brute force password attack by the FBI to unlock an iPhone used by one of the terrorists killed by police after the San Bernardino attack in December 2015. That order, and the subsequent filings by the U.S. Department of Justice (DOJ), Apple, and amicus curiae (friend of the court) briefs by tech giants including Microsoft and Google, have resulted in the merits of the case being debated around the world, both for and against the DOJ and Apple. In a surprise move, on March 28, the DOJ requested the court to withdraw the order saying that it had successfully accessed the data on the iPhone and no longer needed Apple’s assistance.

Although the San Bernardino case will not proceed, the issues are far from resolved. Apple has said it will take steps to enhance the security of its products and plug the security vulnerabilities the FBI may have used to access the locked iPhone. The battle will now move to the next level. In the absence of technical alternatives, the U.S. government will continue to attempt to compel Apple and other tech companies to provide access to the digital devices we rely on to store our most sensitive personal and business data, including phones, tablets, and laptops. Without new legislation, the DOJ would be compelled to again argue that the court has the authority to require a tech company to assist the government under the “All Writs Act” (a U.S. law on the books since 1789).

Notably, in the San Bernardino case, Apple had already provided the FBI with the phone data that was stored on the iCloud, and Verizon has released the call details and location tower data (i.e., data pointing to where the phone was). Apple could provide data stored on the iCloud because Apple holds the encryption keys for data stored in their cloud. What the government sought was any other data that may only reside in the phone and was not backed up to the iCloud.

While the Apple case received a lot of press, there is another case pending that is, in many ways, just as important. The combination of these two cases and the U.S. government positions that they reflect may create a “perfect storm” defining how tech companies must walk a tightrope between protecting digital privacy and cooperating with governments around the world that demand access to our data.

That “other” case has the rather long title of “In the Matter of Warrant to Search a Certain E-Mail Account Controlled and Maintained by Microsoft Corporation” (we just call it the “Microsoft” case), and it is currently on appeal to the U.S. Court of Appeals for the Second Circuit. The DOJ is seeking, through a search warrant issued to Microsoft U.S.A., e-mails stored on a cloud server at a Microsoft subsidiary in Ireland. This compelled disclosure to the DOJ would violate Irish law, and would not follow the established procedures required in an existing law enforcement assistance treaty between the two countries.

The DOJ argues that a U.S. search warrant issued to a U.S. cloud provider covers emails no matter where it is stored on the planet. Microsoft is refusing to comply, arguing that a U.S. warrant is only valid in the United States. If the DOJ wants data stored in Ireland, Microsoft contends, it needs to follow established international procedures. The DOJ apparently does not want to jump through those hoops.

If the DOJ prevails, the U.S. government can reach anyone’s emails and documents stored on any cloud provider that the United States can assert jurisdiction over. So as strange as this sounds, a Thai company, using a cloud service provider for its corporate email handling based in Singapore, may find that its emails are divulged to the U.S. government without going through any legal process in Singapore (perhaps in violation of Singapore law) if the cloud provider has a sufficient presence in the United States. If the United States can get away with this, then why not China, the United Kingdom, or any other government that can assert jurisdiction? A decision in favor of the DOJ would change the risk profile for businesses around the world when deciding whether to use the cloud.

The tech community has rallied behind Microsoft and filed dozens of friend of the court briefs, including Apple, Amazon, and the Government of Ireland. As of this writing, the U.S. Second Circuit Court of Appeal has not issued a decision.

Just as ocean waves interact with each other with some becoming bigger, smaller, or cancelling themselves out, the potential combination of outcomes, in terms of the escalating battle between the U.S. government and Apple and the decision in the Microsoft case, can form a perfect storm in terms of both best and worse outcomes depending on one’s view.

A “perfect” outcome for the DOJ would be for Microsoft to lose and be forced to compel its Irish subsidiary to divulge its customer’s e-mail, and for either Congress to mandate that a “back door” be built into encrypted products or for a court to again order a tech company to write code to compromise its own product (and for that order to be upheld on appeal). This perfect storm scenario for the United States would dramatically affect our expectations of privacy for data in our portable devices and in the cloud. Other governments would take similar actions to compel the disclosure of data on devices and in the cloud of those they choose to investigate.

However, if Apple and Microsoft ultimately prevail in their positions, we would feel more confident that our data is more secure. Business models for tech companies would evolve accordingly, but that outcome would most assuredly tempt Congress and governments around the world to consider specific legislation.

A “win” by Apple or Microsoft, and a “loss” by the other, would have other ramifications. If encrypted data on a phone is safe from government access, but governments can reach data in the cloud regardless of where in the world the data is located, a security-conscious company may well opt to store their sensitive data locally and not on the cloud. Governments may then be tempted to compel cloud backups for portable devices and require cloud-service providers to hold the encryption keys. Other outcomes will result if Microsoft prevails but Apple loses in its battle to keep its products secure from others including government agents.

The waves are still in motion. For legal advisors and business executives, the current situation presents serious challenges in making decisions regarding business and legal risk management. Some government access to our data is a fact of life, but to make conscious decisions we need to understand where the limits are. The only certainty is that the outcomes of these cases will affect our personal and business decisions in how we protect our data for years to come.

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