MoreProtect more of what is yours
Ask Fee-FiDemo mode
SECURITY CENTER

Protection that is honest about its state.

This interface is passkey- and MFA-ready, but production authentication is not yet connected. No screen claims controls are active before the provider is configured.

Sign-in protection

Production controls and readiness

PasskeysPhishing-resistant sign-in on supported devices
Auth provider required
Email magic linkOne-time sign-in link as a recovery or device fallback
Email provider required
Authenticator-app MFATime-based one-time codes for account protection
Auth provider required
Recovery methodsSecure account recovery and backup-code lifecycle
Planned
Active sessionsReview and revoke signed-in devices
UI ready

Data protection

Implemented boundaries and honest gaps

Server-only Plaid secretsClient ID and secret are read only by server route handlers
Implemented
Access-token boundaryPlaid access tokens are never returned to the browser
Implemented
Protected data schemaEncrypted columns, consent, bill alerts, audit data, and row isolation
Schema ready
Live encrypted storageManaged database and encryption-key accounts still required
Credentials required
Private notification designSeverity, quiet-hour, channel, and per-bill controls with generic push text
Implemented
Audit operationsSchema is ready; monitoring and review need production services
Provider required

How passwordless login will work

Passkeys first, verified email link as fallback

A user enters an email once, verifies it, and creates a passkey secured by Face ID, Touch ID, Windows Hello, Android biometrics, or the device PIN. On later visits the device signs a challenge—no Fee-Fi password is typed or stored. A short-lived, single-use email magic link provides recovery on a new device. The current shared private-beta gate is separate and will be removed when real user authentication is active.

Beta security gate

Before any real customer financial connection

Provision production authentication and the managed database; connect the encryption key; verify webhooks; implement rate limiting, export/deletion jobs, session revocation, monitoring, incident response, restore testing, and independent legal/security review. The repository now contains the fail-closed schema and browser security boundaries, but accounts and operations cannot be manufactured in code.