Paradrawthe legal stack, drawnSecurity — acceptable use policy 220125 is drafted as an obligation. No other published document mentions it by name, and no clause states that it forms part of the agreement.
“Last updated 22 January 2025”
Wrong? Ask for access to correct it.
General Terms and Conditions — eu general terms and conditions is drafted as an obligation. No other published document mentions it by name, and no clause states that it forms part of the agreement.
“← Back to overview”
Wrong? Ask for access to correct it.
General Terms and Conditions — au general terms and conditions 141125 is drafted as an obligation. No other published document mentions it by name, and no clause states that it forms part of the agreement.
“← Back to overview”
Wrong? Ask for access to correct it.
General Terms and Conditions - US is drafted as an obligation. No other published document mentions it by name, and no clause states that it forms part of the agreement.
“← Back to overview”
Wrong? Ask for access to correct it.
Data Processing Agreement — au data processing agreement is drafted as an obligation. No other published document mentions it by name, and no clause states that it forms part of the agreement.
“Last updated 14 November 2025 Introduction Introduction 1.1”
Wrong? Ask for access to correct it.
Data Processing Agreement — eu data processing agreement is drafted as an obligation. No other published document mentions it by name, and no clause states that it forms part of the agreement.
“Last updated 31 January 2025 Introduction Introduction 1.1”
Wrong? Ask for access to correct it.
Data Processing Agreement — eu specification of data processing is drafted as an obligation. No other published document mentions it by name, and no clause states that it forms part of the agreement.
“Subject matter and purposes of the processing”
Wrong? Ask for access to correct it.
Data Processing Agreement — smb service level agreement is drafted as an obligation. No other published document mentions it by name, and no clause states that it forms part of the agreement.
“5.1”
Wrong? Ask for access to correct it.
Security — golf terms conditions is drafted as an obligation. No other published document mentions it by name, and no clause states that it forms part of the agreement.
“Last updated 24 June 2026 1. Introduction”
Wrong? Ask for access to correct it.
The published set uses the capitalised term “Order Form” 96 times, in 5 documents that create obligations: General Terms and Conditions — cbp general terms and conditions, General Terms and Conditions — au general terms and conditions 141125, General Terms and Conditions - US, General Terms and Conditions — eu general terms and conditions and Data Processing Agreement — smb service level agreement. Searching all 20 published documents for a definition of it — in each of the forms this set uses elsewhere: (the “Order Form”), (“Order Form”), and “Order Form” means — returns nothing.
Searched 20 documents, 2,098 clauses. No match.
Wrong? Ask for access to correct it.
General Terms and Conditions — cbp general terms and conditions ¶14 refers to a Credit Terms. No page of that name appears in the sitemap, the legal index or the trust centre. It may exist and be available on request.
“To the extent that the Subscriber purchases or uses Credits, the Credit Terms and Conditions shall supplement these GTCs and form part of the Agreement. In the event of any conflict or inconsistency between the Credit Te…”
Wrong? Ask for access to correct it.
General Terms and Conditions — cbp general terms and conditions ¶30 refers to a Business Associate Addendum. No page of that name appears in the sitemap, the legal index or the trust centre. It may exist and be available on request.
“To the extent the Subscriber processes, transmits, or otherwise provides Protected Health Information (as defined under HIPAA) through or to the Services, the Subscriber shall not do so unless and until the Parties have …”
Wrong? Ask for access to correct it.
General Terms and Conditions — cbp general terms and conditions ¶229 refers to a Legora Credit Terms. No page of that name appears in the sitemap, the legal index or the trust centre. It may exist and be available on request.
“"Credit Terms and Conditions" means the Legora Credit Terms and Conditions addendum forming part of the Agreement and governing all matters relating to Credits, as further described in Section 1.3.”
Wrong? Ask for access to correct it.
General Terms and Conditions — au general terms and conditions 141125 ¶122 relies on a statement of work. No statement of work was found anywhere in the published set.
“Subject to the Subscriber's and its Affiliates' adherence to this Agreement, Legora grants the Subscriber a perpetual, non-exclusive, non-transferable, non-sublicensable (except to Affiliates), royalty-free license, in t…”
Wrong? Ask for access to correct it.
Privacy Policy — recruiting privacy policy sits in the published set with no incoming reference from any other document in the corpus.
“Date of publication: June 7, 2024”
Wrong? Ask for access to correct it.
Privacy Policy — cookie policy sits in the published set with no incoming reference from any other document in the corpus.
“How You Can Control the Use of Cookies How You Can Control the Use of Cookies”
Wrong? Ask for access to correct it.
All 16 findings above are structural: each names the clause that produced it, so you can settle it by opening the document. The pass that reads two documents against each other has not been run on this corpus.
Legora publishes 20 legal documents. Its own terms name 4 more that we could not find published. Every cross-reference inside them resolves. Nothing says which document wins on a conflict.
Named in Legora’s own terms and not found in its sitemap, legal index or trust centre. It may exist and be available on request.
Read from legora.com on 25 September 2026. A description of how the documents fit together, not legal advice. Is this your company?
