relyBack to Rely
PRIVACY & PROTECTION

Security Policy

Protecting your family's information through layered safeguards, controlled access, and secure cloud infrastructure.

Effective date: October 27, 2026  ·  Version 1.2
Encrypted storageCustomer databases and stored files protected at rest.
Account protectionPasskeys, two-factor authentication, and permission-based access.
AWS infrastructurePrivate networking, audit logs, and managed backups.

1. Purpose and scope

Rely Family LLC ("Rely," "we," "us," or "our") helps families organize financial, personal, and household information in a shared platform. This Security Policy describes the safeguards used to protect that information and the principles governing access, operation, and response to security concerns.

It covers Rely-operated application infrastructure, customer records and documents, authentication, and supported integrations. Our core application infrastructure is hosted on Amazon Web Services (AWS). External providers used for connected services, communications, and AI processing operate their own infrastructure and security controls.

2. Encryption and data protection

Customer databases and stored files are encrypted at rest. Vault files use AES-256 encryption through our storage infrastructure. Public application connections use HTTPS and modern TLS to protect information in transit.

Encryption works alongside authentication and access controls. Authorized processing remains necessary to provide the features you use; these protections do not mean that only you can decrypt information.

3. Account security and authentication

Passkey sign-in. Rely supports passkeys as an alternative to entering a password, using a compatible device or credential provider. Availability depends on device, browser, and account setup. Passkey sign-in remains subject to applicable account verification and trusted-device settings.

Rely supports two-factor authentication, including authenticator-app verification. Available methods depend on account configuration. Verification helps protect sensitive changes to account security settings.

Passwords are protected using hashing, and administrative accounts use multi-factor authentication. Users should protect their credentials, verification codes, and recovery information and promptly report suspected account compromise.

4. Permissions and family sharing

Rely uses workspace membership, roles, and permission checks to control access to features and information. Authorization can depend on the Family Hub, module or record, and action requested. Application requests are checked in the context of the relevant user and workspace.

Family members and invited professionals do not automatically receive identical access. Owners and authorized administrators can grant appropriate access to family members, attorneys, advisors, brokers, and other participants using the controls available in the product. Workspace owners have broad administrative access within their Hub.

Review permissions when responsibilities change. Revoking access within Rely does not retrieve copies previously downloaded or shared outside the service.

5. Infrastructure and network protection

Rely's core application infrastructure is hosted on Amazon Web Services (AWS). Network restrictions and access controls help protect application services and customer data from unauthorized access. Customer file storage is not publicly accessible.

Web application protections help defend against common attacks and malicious traffic. These safeguards reduce risk but cannot guarantee that every attack will be prevented.

6. Credential and administrative protection

Sensitive credentials are protected using encrypted storage and restricted access controls. Access to systems and deployment functions is limited through identity and authorization controls.

Credential handling and administrative access are included in security reviews and ongoing improvements.

7. Connected financial accounts and integrations

Users choose whether to connect supported financial accounts through Plaid. Authorized data supports financial visibility, transaction and cash-flow views, investment information, and related product features. These connections are used for information and analysis, not to initiate payments or execute trades.

Connection information and imported records are protected through encryption at rest and backend access controls. Access to connected-account functions is governed by relevant user and workspace permissions.

Connected providers operate their own services and security controls. Information handling and user choices are described in our Privacy Policy and the relevant provider's policies.

8. AI-assisted features and data processing

AI-assisted features use information needed for the requested or enabled functionality and may involve external service providers as described in our Privacy Policy. User and workspace permissions govern access to information within Rely.

Specialized processing capabilities use isolation and access restrictions designed to limit their access to surrounding systems.

9. Logging and security review

Rely maintains administrative and service-access logs to support investigation and accountability. Logs are protected through encryption and restricted access.

Security checks include infrastructure access review, software-image scanning, and malware protection for designated processing locations. These controls have defined scopes and complement application and infrastructure reviews.

Findings inform remediation priorities and ongoing improvements. Automated checks and logging do not imply continuous human surveillance of every event.

10. Backups, recovery, and retention

Rely uses automated database backups and recovery safeguards to help protect against accidental loss and support service recovery. Recovery capabilities and retention periods vary by service and type of information.

Data retention follows service needs and the practices described in our Privacy Policy. Backup and security-log retention may differ from active application data. This policy does not promise uninterrupted availability or a fixed recovery time.

11. Security concerns and incident response

Report suspected unauthorized access, exposed information, or a vulnerability to support@rely.family with the subject Security report. Include a description, affected feature, approximate time, and steps to reproduce where appropriate. Do not send passwords, access tokens, or unnecessary sensitive records.

Our response priorities are to assess the report, contain confirmed unauthorized access, preserve relevant evidence, correct the cause, and restore affected services. Communication with affected users and partners will reflect the circumstances and applicable obligations. No specific response or resolution time is guaranteed by this public policy.

Please avoid accessing another person's information, disrupting services, or publicly disclosing sensitive vulnerability details while reporting a concern.

12. Policy maintenance and shared responsibility

Rely management is responsible for maintaining this policy and considering security as the service changes. Infrastructure and application controls are reviewed as part of ongoing operation and improvement. Users remain responsible for their own devices, credentials, sharing choices, and the information they choose to connect or upload.

This document describes Rely's security approach and specified controls. It is not an independent audit report or a certification, and AWS certifications do not automatically certify Rely. No system can be guaranteed completely secure.

We will update this page as our controls and services evolve. For security due-diligence questions, contact support@rely.family. This policy supplements our Privacy Policy and Terms & Conditions.