Renvest is not a bank
Renvest organizes household financial data and planning context. It does not hold deposits, issue cards, custody assets, or make payments on a user's behalf.
Trust and security
Built to feel calm, credible, and high-trust from the first screen.
Renvest handles household financial context, so trust is treated as product behavior: private routes, household-scoped data, provider boundaries, reviewable AI output, and clear paths for export, deletion, and support.
Protected access
Authenticated routes are separated from public pages, and session-aware flows keep private household pages behind login.
Household-scoped data
Renvest is designed around household boundaries so app surfaces do not mix one household's operating data with another's.
Plaid connectivity
Supported institutions connect through Plaid, while imports and manual accounts remain available when provider coverage is incomplete.
Retention and removal
Export and deletion flows are explicit, and connected-provider data should be reviewed through the same household workspace where it appears.
Reviewable structure
Shared design primitives, readable status labels, and explicit confidence copy make the experience easier to audit and maintain.
Truth boundary
Clear limits are part of the trust model.
Renvest should be specific about what it does, what it does not do, and which evidence still needs to stay current before a paid beta.
Renvest is not a financial advisor
The product can surface estimates, context, and next-step suggestions, but users remain responsible for decisions and should consult qualified professionals for financial, tax, legal, investment, insurance, or estate advice.
AI output stays reviewable
Assistant responses and receipt extraction can be incomplete or wrong. Renvest should keep source, confidence, and missing-detail states visible before plan changes depend on them.
Launch proof still matters
Security claims depend on production verification: row-level security proof, Stripe and Plaid webhook validation, monitoring, data export, deletion, and support operations must all stay current before paid launch.
Need a deeper walkthrough?