Company
The legal entity for Renvest is Renvest Labs, LLC.
Privacy
Renvest Privacy Policy
DRAFT / NOT COUNSEL APPROVED · REN-LEGAL-DRAFT-2026-08-18-E1
This draft describes the privacy posture Renvest should operate under before accepting paid users. It must be reviewed by legal counsel before publication as binding policy. For the public subprocessor list referenced below, see /subprocessors. To contact Renvest about privacy, email security@renvest.app.
For a narrower explanation of AI prompts, receipt extraction, and review boundaries, see /ai-data. For export, correction, deletion, and retention operations, see /data-controls.
Account Eligibility
Renvest accounts are for adults only. Children may be household members.
Financial Data We Process
Renvest may process account, balance, transaction, household, financial profile, budget, cash-flow, liability, asset, sync-health, and settings data that users provide directly or authorize through aggregation providers.
Household And Child Context
Financial Profiles are household financial contexts, not child user accounts. Renvest should not require a child's date of birth, login, or sensitive identity details to separate dependent accounts.
Aggregation And Provider Limits
When users connect accounts, Renvest requests provider data needed to show balances, transactions, sync status, reconnect needs, and calculations. Provider availability, latency, and accuracy can affect freshness.
AI Assistant And Receipt Extraction
When AI features are enabled, the household financial assistant sends a minimized household snapshot scoped to the requesting user's household, plus the user's redacted typed prompt, to OpenAI for inference. Voice/realtime intake is deferred from the current public product. If voice is explicitly enabled in a future or separately configured environment, live microphone audio and a minimized household snapshot may be processed during that active session. Receipt extraction may send receipt image or PDF bytes and extracted receipt text context to extract merchant, date, total, taxes, payment hints, and item details. Receipt item categorization may send merchant and line-item candidates. Transaction categorization may send merchant, description, amount, direction, posted date, and allowed category names. Liability statement extraction may send uploaded statement image or PDF bytes plus sanitized debt context. OpenAI is a subprocessor; Renvest does not authorize OpenAI to train models on this traffic. AI output is suggestive and reviewable, not financial truth, and assistant output is run through a personal-information scrubber before display. AI can be wrong and is not financial, legal, tax, or investment advice. See Subprocessors for the full list and links to each vendor's data processing terms.
Subprocessors
Renvest uses Supabase (database, auth, storage), Vercel (hosting), Plaid (bank account aggregation), Stripe (subscription billing), and OpenAI (AI inference) to operate the product. Quiltt is a conditional, feature-flagged financial API integration whose production activation is not proved. The authoritative subprocessor list, the data categories each receives, the processing region, and each vendor's Data Processing Agreement and privacy notice are published at /subprocessors and are updated when any subprocessor changes.
Analytics
Product analytics should measure activation, trust, retention, and monetization without sending raw balances, transaction names, account names, child names, emails, provider tokens, or account numbers.
Retention
Renvest retains household financial data for as long as the household account is active so the planning, sync, and reconciliation features work correctly. Standard assistant messages are pruned by the retention processor after the configured retention window, defaulting to 90 days. Pinned assistant conversations and receipt records are retained while the household account is active so users can review prior decisions and receipts. Archiving a receipt hides it from the active receipt vault and deactivates receipt-backed budget allocations, but the private receipt record and evidence file remain retained for household history unless the household data is deleted. Some records may be retained briefly when required for security, billing, backup integrity, legal obligations, or abuse prevention. Account deletion removes the associated household financial data on the schedule selected in the deletion flow.
Export And Deletion
The self-service workbook export is generated on demand and is limited to the accounts selected in the request, the latest returned balance snapshot for each selected account, and transactions returned for those selected accounts. It does not include unselected accounts, budgets, cash-flow plans, debts, goals, planning data, profile data, receipts, assistant history, credentials or provider tokens, or a background delivery or archival-retention promise. Users can request account deletion from the product; deletion supports an immediate mode and a thirty-day-hold mode. Deletion removes the user's household membership and the associated household financial data on the schedule selected. For a data subject access response, correction, deletion outside the product flow, or records omitted from the self-service export, use the support-assisted privacy route through the security inbox below. That route does not itself claim delivery or human acknowledgement.
Security
Renvest uses household-scoped authorization, row-level security in the database, redacted application logs, AES-256-GCM provider-token encryption bound to the connected-item identifier, signed Plaid and Stripe webhooks, and least-privilege operational access. The current security posture is summarized in our Security Posture document. Renvest does not sell household financial data.
Contacting Renvest About Privacy
Privacy questions, data subject access requests, and deletion requests outside the product can be sent to the security inbox shown below. Include the household identifier or registered email so Renvest can verify the request before acting.