Security & data flow — for hosting partners
Relay is licensed software you deploy and operate in your environment. You are responsible for infrastructure security, encryption, monitoring and compliance attestations; Relay is responsible for the security of the software it distributes.
Who hosts Relay?
Relay is licensed software deployed and operated within the hosting partner's environment. Relay does not host or maintain access to the financial institution's production member data.
Who is responsible for infrastructure security and compliance?
The hosting partner. That includes infrastructure security, production encryption and key management, monitoring, backups, access controls, incident-response operations, and applicable infrastructure/compliance attestations, including SOC 2 where required.
What is Relay responsible for?
Relay is responsible for the security of the software it distributes, including secure development practices, application-level security controls, dependency and vulnerability management, and security updates. Because Relay does not operate the partner's production environment, Relay does not represent the partner's hosted deployment as being covered by a Relay SOC 2 attestation.
Where does the data live?
In the hosting partner's environment, on infrastructure they select and control. Core banking data is referenced through the adapter layer they map to the institution's APIs, with member permission — not copied to Relay.
Who is on the hook if a helper pays the wrong bill?
No payment executes on a helper's action alone. Helpers prepare; the account holder or a designated approver approves; money movement happens in the institution's existing bill-pay system under its own policies. The hosting partner's agreement and the institution's contract define liability — Relay never moves money.
Who can prepare vs. submit a payment?
Roles are explicit: viewers see balances, helpers prepare payments and organize information, approvers release anything that touches money. Every grant is per-person, per-permission and revocable. The hosting partner is responsible for enforcing these roles in their deployment configuration.
Who runs audit logging and retention?
The application writes audit events for views, preparations, approvals, invitations and permission changes. Log storage, retention periods, tamper resistance, monitoring and evidence collection are operated by the hosting partner, to the records policy they agree with the institution.
What is Relay's own compliance status?
Relay is a software license, not a hosted service, so it carries no SOC 2 report or certification of its own — and we don't claim one. The attestation the credit union asks for is the one covering the hosting partner's environment and operations.
Demonstration environment. This page describes the architecture hosting partners deploy Relay to, and the division of responsibility in the license. The demo uses simulated connections and local sample data — no real member, account or document data is present, and no production security controls, encryption standards or certifications are claimed for it. See the partner portal or review plans.