Security at Budgetr

Updated October 14, 2026. Report a concern privately to hello@budgetr.co. Please do not include bank passwords or access tokens.

Current safeguards

• Signed-in sessions are required to access private budgets and bank connections.
• Server-side authorization checks restrict plans and connections to their owner or authorized household access.
• The app uses HTTPS. Database access uses encrypted connections.
• Plaid access tokens are encrypted before storage using AES-GCM; Neon provides encryption for stored database data.
• Plaid secrets and database credentials remain on the server.
• Connections import information; they do not move money.

Operational security policy

Administrative access is limited to people managing the service. The owner reports that SMS MFA is enabled for administrator accounts. Credentials must not be shared in messages or source files. Access changes and suspected credential exposure require review and, when necessary, revocation and rotation.

Current limitations

Budgetr is an early-stage service. Consumer sign-in does not currently enforce a second authentication factor before bank linking. We do not claim an independent security certification, a completed penetration test, or an established recurring vulnerability-scanning program. Written procedures are being introduced; publication of this page is not evidence of a completed security audit.

Incident handling

Security reports are directed to the operator for investigation. Response may include restricting affected access, revoking exposed credentials, correcting defects, and communicating with affected users and providers as appropriate. Do not use a security report to disclose another person's private data.

Data handling

See the privacy policy and retention and deletion policy for collection, sharing, storage, and deletion details.