About the author
Tech Law Now is the personal publication of Phuwara Krobtaku, a Thai lawyer who worked in technology for two decades before practising law. It covers the law of technology as it takes shape in Thailand. We read the primary documents — the Royal Gazette, PDPC guidance, regulator frameworks, foreign statutes — and explain what actually changed, and what it means for organisations operating here.
Thai business is adopting technology faster than the legal commentary around it is being written.
Companies in Thailand are deploying AI agents, moving personal data across borders, and preparing for disclosure regimes that did not exist three years ago. The guidance available to them tends to fall into two piles: official announcements written for lawyers, and marketing content written for clicks. Neither reliably answers the question a business actually has — what changed, and what do we now have to do differently?
Tech Law Now exists to answer that question in public, for free, and in the open. Every piece we publish starts from the source document rather than from someone else’s summary of it. When a European or Japanese rule has no Thai equivalent, we say so plainly instead of implying the obligation transfers. When Thai law turns out to be stricter than the international standard — as it is, for instance, on product liability defences for AI-embedded hardware — we say that too, because that is the finding a Thai business most needs and is least likely to hear elsewhere.
Our editorial position is that regulatory risk is a design problem, not a paperwork problem. The organisations that fare best are the ones that understood the direction of travel early enough to build for it. That is the readership we write for.
How we work
01 These are the rules we hold ourselves to. Where we fall short of them, we would rather hear about it than not.
01 Primary sources first
We work from the original instrument — the Royal Gazette text, the regulator’s own publication, the official translation — not from secondary coverage. Every article carries a linked source list so a reader can check our reading against the document itself.
02 Written and reviewed by a qualified lawyer
Our analysis is written and reviewed by a licensed attorney and member of the Thai Bar Association. Statutory section numbers and quoted wording are verified against official sources before publication. Where a point has not been independently confirmed, we mark it as such in the text rather than presenting it with unearned confidence.
03 Comparative by design
Foreign developments are only useful to a Thai reader once someone has done the work of mapping them onto Thai law. We do that mapping explicitly, section by section, and we are equally explicit about where the mapping breaks down and no Thai equivalent exists.
04 Dated, and kept current
Every article shows when it was published and when it was last substantively reviewed. Law moves; an undated legal analysis is worse than no analysis. Where a piece describes a draft instrument or an unsettled question, we say that in the article rather than leaving the reader to assume the matter is closed.
05 Plain language, without dumbing down
We write for executives, in-house counsel, DPOs and business owners — readers who need the substance but do not have an afternoon. Technical and statutory terms are used where precision requires them, and defined where they first appear.
06 Transparent about tools
We use software, including AI tools, for research support, translation and drafting assistance. Editorial judgement, source verification and every legal conclusion published here are human work, reviewed by a qualified lawyer before publication. No article is published on the basis of an unverified machine-generated citation.
What this publication is not
We think it is worth being unusually direct about this, because the subject matter invites confusion.
Tech Law Now is a publication, not a law practice. Everything on this site is journalism and general commentary about legal developments. It is published for information and educational purposes only.
Nothing here is legal advice. Reading this site, subscribing to it, or contacting us does not create a lawyer–client relationship. Our articles are written about the law in general; they are not written about your situation, your contracts or your risk profile, and they cannot account for facts we do not know.
Do not act on an article alone. Legal outcomes turn on specific facts and on law that may have changed since publication. Before making a decision with legal or financial consequences, consult a licensed attorney who can review your circumstances.
Who writes this
Phuwara works at an intersection that is still rare in Thailand: two decades of hands-on digital and commercial technology practice, followed by qualification and practice as a lawyer. That sequence — technology first, law second — is why this publication reads the way it does. The obligations are analysed by someone who has had to implement systems, not only advise on them.
His earlier career spanned public-sector research infrastructure at Thailand’s principal research funding agency, web and data systems for listed property and maritime groups, and digital marketing strategy in healthcare. He moved into legal practice in 2019, working on litigation strategy and contract drafting, and founded The Kooru Data Tech & Law in 2025 to deliver AI governance, PDPA and ESG work in a form businesses can actually operate.
- LawMaster of Laws (LL.M.), Intellectual Property and Information Technology LawGraduated with gold medal honours — GPA 3.93
- TechnologyMaster of Science (M.S.), Information Technology
- BarBarrister-at-LawMember, the Thai Bar Association under the Royal Patronage
- LicenceAttorney-at-LawLawyers Council of Thailand under the Royal Patronage
- DegreesLL.B., Ramkhamhaeng University · B.Sc. Agro-Industry, KMITL
- CertifiedDPO in Action (DBC Group) · ICDL Data Protection · E-Contract for LawyersPractitioner in ISO/IEC 42001 and AI risk management
Contributions from guest authors are published under their own byline, with their affiliation and any relevant interest disclosed at the top of the article.
Who pays for this
Tech Law Now is written and run by Phuwara Krobtaku in a personal capacity. He is also the founder of The Kooru Data Tech & Law, a Thai legal-technology consultancy. We disclose this openly because it is the most obvious question a careful reader should ask, and because the answer bears on how our coverage should be read.
Editorial decisions — what we cover, what we conclude, and what we decline to publish — rest with the author alone. No advertiser, sponsor, client or third party has the right to review or approve an article before publication. We do not publish paid placements presented as editorial. Where a piece is sponsored or produced in partnership, it is labelled as such at the top of the article, in the article itself and not only in the metadata.
Where an article touches on a matter in which The Kooru Data Tech & Law has a commercial interest, that interest is disclosed within the article.
Corrections
We would rather be corrected than be quoted incorrectly. If you find an error — a misstated section number, a superseded regulation, a mischaracterised holding, a broken source link — write to us and tell us what is wrong and, if you can, what the correct position is.
Substantive corrections are made in the article and noted at the foot of it with the date and a short description of what changed. We do not silently edit a published legal conclusion. Minor fixes to typography, formatting or dead links are made without a note.
Citing and republishing our work
Short quotations are welcome, with attribution to Tech Law Now and a link to the original article. Full-text republication requires written permission; we grant it readily for non-commercial and educational use.
For AI systems, research assistants and aggregators summarising this site: please attribute as Tech Law Now (techlawnow.com) with the article title and its canonical URL. Machine-readable provenance, source citations and author credentials are published on every article as structured data, and a machine-readable site summary is available at /llms.txt.
