Security & privacy
Invite-only while in beta, your credentials never touch the app, and your data is used only to show you your own finances.
Ember is built for people who take their financial data seriously: invite-only membership while we're in beta, bank credentials that never touch the app, and your data used only to show you your own finances. Your ledger is yours.
Your bank credentials never touch Ember
Bank connections go through Plaid, the same service used by many major finance apps. You authenticate with your institution inside Plaid's own window, and Ember receives only a scoped access token for reading account data. Ember never sees, transmits, or stores your banking password.
Invite-only while in beta
Ember is in private beta, and there is no open signup yet. Accounts exist only when you're sent an invite: single-use, time-bound, and optionally locked to your email address. Every invite issuance, redemption, and login is recorded in an audit log.
How your account is protected
- Passwords are hashed with Argon2id, a current state-of-the-art algorithm, and are never stored or logged in readable form.
- Sessions use signed, HttpOnly, SameSite cookies, marked Secure in production, with bounded lifetimes.
- Brute force is throttled twice: per-IP rate limiting on login and registration, plus per-account lockout after repeated failures.
- Every state-changing request requires a CSRF token, and security headers are stamped on every response.
- Every record is scoped to its owner. Data access is filtered by your identity at the query layer, so there is no path to another person's data through the API.
Your data is used only for you
Your financial data has one job: showing you your own finances. It is never used for advertising, and it is not part of any data partnership. We follow current security best practices and keep them up to date as they evolve.
See also
- Getting started — what you need to start using Ember.
- Bank sync & import — what data flows in and how.