Updated November 2026
Security
This page describes the security controls in the BusyBooks website and signed-in workspace today.
This demo
Authentication & sessions: Workspace sign-in uses single-use 6-digit email codes (SHA-256 hashed with a server pepper, 10-minute expiry, max 5 attempts, and per-email/IP rate limits). Verified sessions issue an HttpOnly, Secure, SameSite=Lax cookie whose token is stored only as a SHA-256 hash in Cloudflare D1.
Data & bank tokens: All workspace API routes enforce session authentication, same-origin CORS, and per-user D1 isolation. Plaid access tokens remain server-side only and are encrypted at rest using AES-GCM. Bank connectivity is currently configured for Plaid Sandbox testing only.
What a full security page would cover
We will keep this page current as the workspace grows, including:
- Encryption in transit and at rest
- How bank connections are authorized and scoped
- Access controls, logging, and how incidents would be handled
If you believe there is a security issue, email hello@getbusybooks.com.