Security without theatre
Before the technical language, the practical boundaries are simple: your plan belongs to your account, banking credentials are never requested, and DueSimple cannot move your money.
Six safeguards
Each layer states the practical boundary first. Open the disclosure for the implementation detail.
Built into the product
Your account requires verified access, supports password recovery, and can add an authenticator-app second step.
Verified email flows, secure sessions, password recovery, optional TOTP MFA, and recent-authentication checks form the account boundary.
Built into the product
The browser receives only the access needed for your signed-in session—not the credentials that administer the service.
Service credentials stay server-only. Authenticated operations validate the user, workspace, environment, and allowed action before financial data is touched.
Enforced control
A signed-in account can reach its own workspace, while the database independently enforces the same ownership boundary.
Row Level Security and server authorization independently limit each account to its workspace. Two-user adversarial tests exercise that boundary.
Built into the product
Errors can be investigated without copying household names, amounts, notes, emails, imported rows, credentials, or tokens into diagnostics.
Logging and error-reporting paths retain privacy-filtered request context and identifiers while excluding financial payloads and secrets.
Operational practice
Private exports and sensitive-action checks give you a deliberate path to retrieve or remove account data.
Account deletion, backup recovery, retention, and purge procedures remain operational responsibilities that must be maintained and verified.
Product boundary
It cannot connect to your bank, hold money, monitor transactions, or initiate a payment.
Planned payments and contributions do not change real balances until the user explicitly confirms completion.
Sensitive information
Never enter online-banking passwords, full card or account numbers, authentication codes, security answers, government identification numbers, tax identifiers, or information that is not needed for a planning record.
Explicit boundaries
Fictional data only
The guided demo uses one fixed fictional household and does not accept personal financial information.