Backdating contracts verbal contracts and contract splitting
This is sometimes done in "master" agreements that are available to the affiliates of one or more parties. For example, California Evidence Code § 622 provides: "The facts recited in a written instrument are conclusively presumed to be true as between the parties thereto, or their successors in interest; but this rule does not apply to the recital of a consideration." (Emphasis added; hat tip: Commenter "Kazu" at the Adams Drafting blog.) See also the notes to CD-25.2. When an agreement is made to settle a dispute, it can be really advantageous for the background ssection of the signed agreement to document that fact. According to plaintiffs, there had been numerous business disputes, between Tzolis and them, concerning the sublease. (a) The parties intend to use the Agreement as a pre-negotiated set of terms and conditions for one or more purchase orders, statements of work, or other specific agreements incorporating the Agreement by reference.
Unless you say otherwise, I'll credit you in these materials for any suggestions that I incorporate. The receiving party likely would prefer instead to have a bright-line "sunset," after which the receiving party can do whatever it wants without having to incur the burden of analyzing the facts and circumstances. SUGGESTION: Consider requiring segregation of Confidential Information — or a Receiving Party could elect to segregate Confidential Information on its own initiative, even without a contractual requirement — for easier compliance with this section.
] [NOTE: Don't rely on the drafts below as a substitute for legal advice about your specific situation. If the receiving party's confidentiality obligations are allowed to expire, the disclosing party might thereafter find it difficult — or, more likely, impossible — to convince a court to enforce any trade-secret rights in the relevant information. A receiving party might find it to be tremendously burdensome and expensive to try to return or destroy all copies of a disclosing party's confidential information, even those in emails, backup systems, etc.
See the Cautions for more details.] The period (i) beginning on the effective date of the Agreement and (ii) continuing until the information question qualifies for at least one exclusion from Confidential Information status under CD 188.8.131.52. [CITATION NEEDED] The language, any other right or obligation under the Agreement, addresses the situation in which an agreement includes noncompetition or non-solicitation provisions in addition to confidentiality provisions — the language attempts to make it clear that the confidentiality obligations continue even if (for example) the non-competition covenant expires. Downer, Equitable Exceptions to the Rule Against Perpetual Contracts, Intellectual Property Litigation, Volume 21, No. Such an argument, though, would have to overcome the long-established rule that "[t]rade secret licenses may endure even where the trade secret itself is destroyed by general disclosure." Nova Chemicals, Inc. The requirement of disclosing-party consent to destruction has in mind the situation in which the disclosing party doesn't itself have a copy of Confidential Information to be destroyed.
Suggestion: If you incorporate one or more Common Draft provisions by reference, consider using your browser's "Save to PDF" or "Print to PDF" capability to preserve a copy of this deskbook for future reference. Receiving parties, of course, generally prefer to have fixed expiration dates for confidentiality obligations. PRO TIP: Unfortunately, sometimes parties forget about return-or-destruction obligations.
The long-term goal of the Common Draft project is to serve as a lasting, public repository of carefully-drafted contract provisions that cover a wide variety of business needs, with annotations, commentary, and student exercises. A receiving party might want an expiration date for confidentiality obligations as a safe harbor. A disclosing party will want to follow up to be sure that the return-or-destruction requirement is actually complied with; if it were to fail to do so, a receiving party (or a third party) could try to use that as evidence that the disclosing party did not take reasonable precautions to preserve the secrecy of its confidential information, as discussed in this annotation.
[for] the transportation and delivery of goods." (Wikipedia.com). Another useful patent-law analogy might the requirement of corroboration to support an assertion that an issued patent is invalid due to prior public use. In the Seventh Circuit's Fail-Safe case, the court pointedly noted that the plaintiff had not marked its information as confidential; the court affirmed the district court's summary judgment dismissing the plaintiff's claim of misappropriation. A disclosing party should always insist on imposing confidentiality obligations on a receiving party; otherwise, a court is likely to hold hold that the disclosing party had failed to make reasonable efforts to protect its confidential information. For the avoidance of doubt, the Receiving Party's undertaking of the obligations of the Agreement concerning Confidential Information is not intended and should not be interpreted as in itself establishing a confidential‑ or fiduciary relationship between the parties.