- Joined
- Jul 24, 2009
- Sythe Gold
- 3,767
- Messages
- 7,432
Hi friends,
Following a discussion with our staff, we have concluded that the circumstances do not warrant the forfeiture of the deposit. Before I proceed to motivate the ruling, I wish to underscore two important points:
Following a discussion with our staff, we have concluded that the circumstances do not warrant the forfeiture of the deposit. Before I proceed to motivate the ruling, I wish to underscore two important points:
- The onus of bearing the risk associated with the inclusion of 'ambiguous' and 'broad' clauses within the ToS rests upon the party that sends the ToS (as opposed to the contracting party). We construe provisions in a manner that mandates unequivocal delineation of the entitlements to be derived from these provisions. Should these provisions remain imprecise and remain devoid of further specification, we shall therefore adopt a more 'restrictive' interpretation.
- Secondly, certain overarching provisions are construed in congruence with Sythe's nomenclature. For instance, the term 'service provider' is a core concept within Sythe's taxonomy. Deviating from the 'folk interpretation' of such definitions is permissible, if specifically specified and elaborated in the ToS. In summation, it is advisable to establish explicit arrangements pertaining to the associated risks and engage in discourse thereof, as opposed to incorporating vague and expansive provisions with the expectation of securing safeguarding in a future dispute.
Then to the dispute. Addressing the specific issues:- The provision concerning customer accounts is inapplicable. Accounts intended for future acquisition constitute stock accounts and is something different than customer accounts. The specific provision is pertinent to customer accounts and stock accounts, and thus, it is not applicable. Moreover, even in the hypothetical existence of such a provision, it remains unproven that Chana is accountable for the bans. Although we recognize that this may be frustrating given, Chana's involvement within the plugin community, it does not serve as hard evidence
- The clause 'Giving any information regarding orders or any information pertaining to 3rd parties outside of the primal services staff and workers' is inherently vague and expansive. If construed in its most extensive sense, this provision could deem almost any action by Chana involving a Primal-related order as a breach. Such a construal we deem unreasonable, consequently prompting our adoption of a more 'restrictive' interpretation. When ruling this, 'information' is construed as data whose leakage would precipitate harm to Primal Services. Throughout the course of this dispute, Primal has not substantiated the leakage of such data. Furthermore, the information proffered by Chana in this thread does not breach the provision, given the absence of explicit indication of harm to Primal and the information's reasonable nature, not suggestive of its use for the substantiation of Chana's arguments within this dispute.
Please pay Chana his deposit, @Primal - The provision concerning customer accounts is inapplicable. Accounts intended for future acquisition constitute stock accounts and is something different than customer accounts. The specific provision is pertinent to customer accounts and stock accounts, and thus, it is not applicable. Moreover, even in the hypothetical existence of such a provision, it remains unproven that Chana is accountable for the bans. Although we recognize that this may be frustrating given, Chana's involvement within the plugin community, it does not serve as hard evidence
Last edited:
