Service access
Who may use CORE, what users may do, and which restrictions apply to account and platform access.
§ Legal - Terms
Terms of service.
The operating terms for access, acceptable use, service responsibilities, and contract review.
Commercial terms should match the product.
CORE handles credit work, AI-assisted generation, borrower documents, and audit trails. The terms page should keep those obligations clear and contract-ready.
Access + use + responsibilities§ Terms Scope
What terms review should cover.
Customer responsibilities
How customers manage authorized users, borrower files, source materials, review decisions, and compliance obligations.
Risk and contracts
Warranty, liability, confidentiality, governing law, order forms, support commitments, and contract precedence.
§ Fit
Terms topics buyers ask about
The terms should help procurement understand the operating model without overpromising beyond the agreement.
01
Authorized use
02
Customer responsibilities
03
AI-assisted output language
04
Confidentiality and data clauses
05
Order form and MSA precedence
§ Path
Contract review flow
Review service scope
Confirm the modules, users, implementation scope, and support model for the proposed deployment.
Attach the agreement
Use the order form, MSA, DPA, and security materials that govern the actual relationship.
Keep precedence clear
When public terms and signed agreements differ, the governing contract should control.
§ Next Step
For contract review, contact CORE.
Procurement documents should be handled directly until public terms are finalized.