Terms of use
These terms cover this website. They do not govern the Sweet platform. That is a signed agreement between Sweet and your institution, and nothing here changes it.
What these terms cover
- Covered
- Your use of this website: reading it, following its links, submitting the contact form, and downloading anything published on it.
- Not covered
- Use of the Sweet platform. That is governed by the written agreement between Sweet and the licensing institution, and by any order form or statement of work under it. Where this page and that agreement disagree, the agreement wins. A marketing site cannot amend a negotiated contract, and should not be read as trying to. Confirmthe name counsel uses for that agreement — MSA, subscription agreement, platform licence — so this page points at the right document.
- Who publishes this site
- Confirmthe exact legal entity name, jurisdiction of incorporation and registered address that these pages bind.
Nothing here is an offer of credit
Sweet builds software for lenders. Sweet is not a lender, does not originate loans, does not make credit decisions and does not decide who qualifies for anything. Nothing on this website is a loan offer, a commitment to lend, a pre-approval, financial advice, or a representation that any borrower will be approved for any product.
Screens shown on this site are illustrations of the software, built for this site. The figures, names and documents in them are not real loans, real borrowers or real institutions.
Accuracy, and the figures on this site
This site publishes performance figures. Each one is published with an as-of date, a definition of what it counts, and its source, on the trust & security page. Read them together: a figure without its definition can be read several ways, which is exactly the problem the definitions exist to remove.
Figures describe what has happened. They are not a forecast, and past platform volume or a reported efficiency gain at one institution does not predict a result at yours. Where this site mentions a projection, it is labelled as one.
Statements about SOC 2 Type II on this site refer to an attestation report issued by an independent CPA firm covering a defined period. They are not a certification, and Sweet does not describe itself as certified.
Acceptable use of this site
Reasonable things, stated plainly:
- Read it, share it, quote it with attribution, and send it to your risk team.
- Do not attempt to gain unauthorised access to any part of it or to any system behind it.
- Do not scrape it in a way that degrades it for other people, and do not submit anything to the contact form that you do not have the right to send us.
- Do not use Sweet's name or marks to imply a relationship that does not exist.
If you find a security issue, the security page says how to report it. We would rather hear it from you.
Content and white papers
The words, artwork, product illustrations and white papers on this site belong to Sweet unless stated otherwise. You may read them, print them and circulate them inside your institution for the purpose of evaluating Sweet. Republishing them, selling them, or presenting them as your own is not covered by that. Confirmwhether counsel wants an explicit licence grant here, and whether the white papers carry different terms when requested through a form.
Photography on this site is licensed stock and is illustrative. People shown are not Sweet employees, customers or borrowers.
Third-party names
This site names other companies' products where that is the clearest way to describe what Sweet integrates with or is compared against, including nCino, DocuSign, Plaid, eOriginal and Wolters Kluwer, Salesforce, and AWS. Those names and marks belong to their owners. Naming them is description, not endorsement, and does not imply a partnership, certification or affiliation beyond what the surrounding text actually says.
Where this site describes an integration, the sub-processor section is the place that says whether data actually moves.
Links to other sites
This site links out to team members' LinkedIn profiles, and to sources. Once you follow one of those links you are on someone else's site, under their terms and their privacy policy, and Sweet does not control what they publish.
Sections not drafted here
A terms of use turns on clauses that only counsel should write. They are listed rather than approximated, because an engineer's version of a liability cap reads like protection and provides none.
| Section | Why it is not written here |
|---|---|
| Warranty disclaimer | What this site is provided as, and what it is not warranted to be. Interacts with the accuracy section below. |
| Limitation of liability | A cap written from memory looks like protection and is not. Counsel sets the shape and the number. |
| Indemnity | Whether website visitors indemnify Sweet at all. Many B2B site terms sensibly do not. |
| Governing law and venue | Depends on the entity and jurisdiction still to be confirmed on this page. |
| Dispute resolution | Arbitration, class-action position, informal-resolution window: a commercial decision, not a default. |
| Termination and suspension of access | What Sweet may do about abuse of this site, and on what notice. |
Until those exist, this page is an accurate description of how the site works and an explicit statement of what it is not. It is not a contract, and the marker at the top says so on every view.
Changes and contact
These terms take effect when the draft marker comes off and counsel sets a date. After that, changes are dated and the previous version stays available on request.
- Legal notices
- Confirmlegal notices address, and the postal address notices must be sent to.
- Governing law
- Confirmjurisdiction — see the counsel checklist above. This is a commercial decision as much as a legal one.
- Page owner
- Confirmwho at Sweet owns these three pages after launch, by role — the person who has to answer a bank's third-party risk questionnaire.