Finance Owl is built around least-privilege access, encrypted connections in production, and straightforward controls for account security. When you connect external accounts through a supported provider, those credentials are handled in that provider flow rather than stored directly by Finance Owl.
Production traffic is served over HTTPS, and sensitive application data is protected at rest.
Core budgeting and aggregation features are designed for visibility into data, not silent money movement.
Password hashing, token-based auth, 2FA, and passkeys reduce account takeover risk.
Production traffic is delivered over HTTPS/TLS, and we use security headers such as HSTS to reduce downgrade risk. Internal service communication and browser requests are expected to run only against trusted origins that are explicitly configured for each environment.
Sensitive application data and secrets are encrypted at rest, and production infrastructure should run with encrypted storage, controlled backups, and environment-specific secret management. Launch readiness checks in this repo explicitly require those production secrets to be in place.
Passwords are hashed with bcrypt and never stored in plain text. Finance Owl also supports two-factor authentication (TOTP) and passkeys (WebAuthn/FIDO2) for accounts that want stronger protection.
Production deployments should use isolated environments, encrypted storage, and routine recovery checks.
Origin allowlists, secure transport, and service-level isolation reduce exposure between public and internal systems.
Least-privilege access, environment-scoped secrets, and MFA-protected admin access reduce operational risk.
Health checks, logs, and alerting should be enabled before launch so failures are caught quickly.
Backups should be encrypted, tested, and governed by the production environment retention policy.
Dependencies should be reviewed regularly, with security updates and CI checks acting as part of the release gate.
We are using this launch cycle to tighten operational controls, documentation, and evidence collection. If SOC 2 or a comparable audit becomes part of the public trust posture, this page should be updated with the issued report status rather than aspirational language.
We value the security research community and welcome responsible disclosure of vulnerabilities. If you discover a security issue, please report it to us rather than disclosing it publicly.
Email security@financeowl.com with a detailed description of the vulnerability, steps to reproduce, and any supporting evidence. If you need an encrypted reply path, mention that in your report.
We review good-faith reports as quickly as practical, keep researchers informed when follow-up is needed, credit researchers when appropriate, and will not pursue action against responsible disclosure that avoids harm.
If you have security concerns or believe your account has been compromised:
For urgent security incidents, include “URGENT” in the subject line for priority handling.