Judgment Header
Dirak Asia Pte Ltd and another v Chew Hua Kok and another [2013] SGHCR 1
[2013] SGHCR 1
High Court of Singapore9 Jan 2013Suit No 109 of 2010 (Summons No 4323 of 2012)
Published judgment text with court metadata, source links, and stable paragraph anchors.
Cited in 4 later decisions. No negative treatment detected.
Citations and treatment detected automatically from later judgments and the authorities this decision relies on.
Later cases and laws citing this decision
“as after Sum 13/2019 was filed (on 12 March 2019) and shortly before the eDiscovery Order was made on 17 April 2019. The plaintiffs relied on Dirak Asia Pte Ltd and another v Chew Hua Kok and another [2013] SGHCR 1 (“Dirak Asia”) to argue that it was sufficient for the defendant to have practical access to the email ac”
“e of control as to constitute power; the practical ability to obtain those documents is to be seen and assessed in context: Hai Jiao at [46]; Dirak Asia Pte Ltd and another v Chew Hua Kok and another [2013] SGHCR 1 at [35]–[36].”
“ssages exchanged between HHC and Liang, which includes but is not limited to the 30 Dec Message (see generally, Natixis ([29] above) at [35]; Dirak Asia Pte Ltd and another v Chew Hua Kok and another [2013] SGHCR 1 at [35]–[36]). To be clear, I am not saying that the claimant is in control of these other messages becau”
“em (or proprietary) right to the WeChat messages in HHC’s possession. However, subsequent cases have not read the requirement so narrowly. In Dirak Asia Pte Ltd and another v Chew Hua Kok and another [2013] SGHCR 1, the court observed that “a rigid adherence to Lord Diplock’s perceived definition of ‘power’ as an ‘enfo”
Earlier cases and laws this decision relies on
No outgoing citations detected.
Auto-detected from judgment text; not a substitute for a citator check.
Judgment Header
Dirak Asia Pte Ltd and another v Chew Hua Kok and another [2013] SGHCR 1
Case Metadata
Case No: Suit No 109 of 2010 (Summons No 4323 of 2012)
Case Metadata
Court: High Court of Singapore
Case Metadata
Decision Date: 2013-01-09
Wrong text, a broken link, out-of-date content, or a removal request — tell us and we'll check it against the official source.