Security and Service Provider Addendum
Version 1.0, effective 2026-11-17
This addendum is part of the Agreement between Ryse Software, LLC (the Provider) and the Customer. It applies to all Customer Content, including nonpublic personal information about the Customer’s borrowers (customer information). It is written so that a Customer can meet the FTC Safeguards Rule, 16 CFR Part 314, which requires a financial institution to require its service providers by contract to maintain safeguards, and so that banks and credit unions can meet their third-party risk expectations.
1. Security program. The Provider maintains a written information security program with administrative, technical and physical safeguards appropriate to the customer information it holds. It includes:
- encryption of customer information in transit and at rest, and a second layer of application encryption for the most sensitive fields;
- access limited to personnel who need it, and strong sign-in for every staff member of the Customer;
- a log of sign-ins, changes and reads of sensitive records, which cannot be altered through the application;
- backups encrypted before they leave the server, kept away from it, and restored on a schedule to prove they work.
2. Use of customer information. The Provider uses customer information only to provide the Cloud Service to the Customer, and as the Customer directs. It does not sell customer information, and does not use it to train any artificial intelligence or machine learning model.
3. Incident notice. The Provider will notify the Customer without undue delay, and within 72 hours, after confirming an incident that affects the Customer’s data. It will notify the Customer as soon as possible of any incident that materially disrupts or degrades the Cloud Service, or is reasonably likely to, for four hours or more. The notice says what is known, and the Provider updates it as it learns more and cooperates with the Customer’s response. The Customer remains responsible for any notice the law requires it to give.
4. Assurance. On request, the Provider provides its written account of how data is protected and answers reasonable security questionnaires. If it obtains an independent audit report, such as a SOC 2 report, it provides that report under confidentiality.
5. Subprocessors. The Provider lists its subprocessors publicly, gives 30 days’ notice before adding one, holds each to obligations that protect customer information at least as well as this addendum, and is responsible for their performance.
6. Audits and examinations. The Provider will cooperate with the Customer’s reasonable audits and examinations. For a Customer that is a bank or credit union, this includes access for its regulators as the law provides.
7. Continuity. The Provider maintains backups and a tested way to restore them, and a plan to restore the Cloud Service after a disruption.
8. Return and deletion. At the end of the term, the Provider returns and deletes customer information as the Terms provide, and certifies the deletion in writing.
9. The Customer’s part. The Customer is responsible for its own information security program, including who it gives access to, what it configures, and designating its Qualified Individual. Where the Customer chooses how borrowers sign in, that choice and any written approval it requires are the Customer’s.