Q1149. How to process software end-user license agreement (EULA) translations?

Answered by the NYC Visa & Translation certified translation team

Software EULAs are translated for market localisation and for legal certainty, and the practice has specific contours. The legal frame: for Thai consumers, a Thai-language EULA supports enforceability and consumer-protection compliance (Thai consumer protection law expects contract terms to be understandable, and an English-only EULA's unusual terms may not bind a Thai consumer); for enterprise software, the EULA's governing-language clause usually names English, and the Thai or other-language version is informational — the clause must say so explicitly. The translation rules that matter: the licence grant (what the user may do) and the restrictions (what they may not) are the operative core — translated exactly, with the defined terms (Licensee, Licensed Software, Permitted Use) tracked consistently; the limitation of liability and warranty disclaimer clauses are the risk allocation — Thai law constrains how far liability can be excluded for consumers, so the Thai version should be reviewed for local enforceability, not just translated; and the acceptance mechanics (clickwrap, shrinkwrap, browsewrap) interact with Thai contract-formation rules. Points that matter: open-source licence references within the EULA (the third-party components list) are usually left in English with the licence names unchanged — translating the MIT or GPL licence texts creates non-authoritative versions of texts whose English is legally operative; and for app-store distribution, the stores' own localisation requirements layer on top. Practice points: translate the EULA once as a controlled document and version-manage it with the product releases; and for enterprise deals, the negotiated agreement supersedes the standard EULA — translate the negotiated text. Coordinate with counsel on the governing-language and consumer-law points.