Security

How we protect your data

Your Security Is Our Top Priority

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.

Our Security Commitment

Encrypted

Production traffic is served over HTTPS, and sensitive application data is protected at rest.

Scoped Access

Core budgeting and aggregation features are designed for visibility into data, not silent money movement.

Layered Controls

Password hashing, token-based auth, 2FA, and passkeys reduce account takeover risk.

Encryption and Data Protection

Data in Transit

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.

Data at Rest

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.

Password Security

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.

Connected Account Providers

How Linked Account Access Works

  • Provider-hosted authentication: When bank linking is enabled, sign-in happens through the connected provider flow rather than storing your banking credentials directly in Finance Owl.
  • Scoped permissions: Core aggregation flows are intended to surface balances and transactions. If optional banking tools require broader permissions, they should be presented explicitly before you approve them.
  • Provider controls: Provider-specific security, compliance, and availability details are governed by the vendor you use for account connectivity and should be reviewed alongside their own public documentation.
  • Revocable access: You can disconnect linked accounts at any time through the app, which should revoke future sync access for that institution.

Infrastructure Security

Cloud Hosting

Production deployments should use isolated environments, encrypted storage, and routine recovery checks.

Network Security

Origin allowlists, secure transport, and service-level isolation reduce exposure between public and internal systems.

Access Controls

Least-privilege access, environment-scoped secrets, and MFA-protected admin access reduce operational risk.

Monitoring

Health checks, logs, and alerting should be enabled before launch so failures are caught quickly.

Backups

Backups should be encrypted, tested, and governed by the production environment retention policy.

Dependency Management

Dependencies should be reviewed regularly, with security updates and CI checks acting as part of the release gate.

Compliance

Security Program Status

Review before launch

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.

Additional Compliance

  • GDPR: The product is designed to support access, export, correction, and deletion requests when those rights apply.
  • CCPA/CPRA: The app includes workflows for disclosure and deletion requests that should be reviewed against the final production data practices.
  • Payments: If paid plans are enabled, card collection should be handled by the configured payment processor rather than stored directly by Finance Owl.

Responsible Disclosure / Bug Bounty

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.

How to Report

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.

What We Ask

  • Give us reasonable time (90 days) to address the issue before public disclosure
  • Do not access or modify other users' data
  • Act in good faith and avoid disrupting the Service

Our Promise

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.

Security Contact

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.