Legal
Last updated: November 12, 2026
This page describes how Spero Financial Group LLC (“Spero,” “we”) protects the financial information held in Spero Intelligence. It is the public statement of our Information Security Policy, reviewed at least annually and after any material change to the service. Every practice described here is in place as of the date above. For how we collect and use information, see our Privacy Policy.
Spero Intelligence runs on Amazon Web Services, with its database and user accounts on Supabase (managed PostgreSQL with row-level security), behind Cloudflare. Bank, card and brokerage data arrive through Plaid and SnapTrade, which connect to your institutions with their own credentials; Spero never sees or stores your banking password. Secrets such as API keys are kept in AWS Secrets Manager and are never written into the code.
Access is granted to named individuals on a need-to-know basis, with the least privilege that lets them do their job. Spero staff can only open the clients they are explicitly assigned to; partner firms can only open their own clients; a client can only open their own record. Every request to the service is checked against these rules on the server, and a failed check denies access rather than defaulting to it. The database enforces the same boundaries a second time through row-level security.
The advisor side of the service sits behind an additional network gate (Cloudflare Zero Trust) that only listed company email addresses can pass, authenticated through Microsoft. Source code lives in a private repository whose production and staging branches cannot be force-pushed or deleted; a change from anyone other than a repository administrator requires a pull request with one approval, and the list of administrators is reviewed every quarter.
Dependencies are monitored continuously for published vulnerabilities and for end-of-life releases, with an update opened automatically as soon as an advisory is published. The full codebase receives an automated security review every month and every change receives one before it is released. Automated tests run on every change and block a release when they fail.
Once a vulnerability is confirmed to affect the service, we fix it within:
Every quarter the founder reviews every staff account and role, every partner advisor, every staff-to-client assignment, every client login and the provider consoles, removes anything stale or no longer needed, and signs the record. A sample of the audit trail is reviewed in the same pass.
When an employee leaves, their company Microsoft account is disabled the same day, which immediately closes both the network gate and their sign-in, and their application account is deactivated, which removes every role at once. Role changes take effect on the next request. The quarterly review catches anything missed.
All traffic uses HTTPS. Data is encrypted at rest by our providers, and the credentials that link your institutions are additionally encrypted by the application before they are stored.
A suspected breach or lost credential is reported internally the same day, contained immediately (credential revoked, account or path disabled), assessed for which clients and providers are affected, and notified to affected clients, and to Plaid or SnapTrade where their data is involved, within 72 hours. Every incident and its fix is recorded.
Security questions or reports can be sent to [email protected]. We ask that vulnerabilities be reported to us privately so they can be fixed before being discussed publicly.