Product preview draft
Security
How we approach authentication, secrets, and operational safety in Fareburn.
This page is mock copy for local product review. It is not legal advice and is not a counsel-reviewed policy. Replace before a public launch.
Authentication
Sessions use first-party JWT cookies with short-lived access tokens and rotatable refresh tokens. Sensitive auth routes are rate-limited. Two-factor authentication is not available yet and is not claimed in product UI.
Data handling
- Passwords are stored as bcrypt hashes
- Billing webhooks verify HMAC signatures before processing
- Server secrets stay in environment variables and are never shipped to the browser
What we do not do
Fareburn does not ask for issuer login credentials to scrape balances. Card balances are user-entered or refreshed from your own portfolio records.
Reporting issues
If you find a vulnerability, contact the team via Support in Settings. Please avoid public disclosure until we can investigate.
Questions? See About or Settings → Support.