Your data, with fewer surprises.

Data we collect

• Account information needed to identify linked institutions and accounts.
• Transaction history used for budgeting, trend analysis, and month-over-month comparisons.
• User account information such as email address and profile details.
• Budgeting data created by the user, including categories, groups, and edits.
• Generated budget insights and interactions with them, such as visible impressions, dismissals, helpful or not useful feedback, an optional structured reason, and explicit data corrections.
• Limited onboarding milestones, such as viewing a setup choice, selecting a path, completing an account connection, creating a budget structure, or opening Uncategorized. These events use fixed labels and do not include financial values, transaction details, account numbers, institution names, budget names, or free-form text.

How we use data

• Provide budgeting, transaction review, and historical comparison features requested by the user.
• Generate evidence-backed budget insights, avoid repeating unchanged insights, personalize their order from the user's own interaction history, and evaluate feature reliability.
• Maintain linked account connections and refresh financial data with Plaid.
• Support security, fraud prevention, debugging, and customer support when reasonably necessary.
• Keep onboarding choices consistent and compare which setup path helps users reach a usable budget.

Plaid

Moolah uses Plaid to connect to financial institutions. Plaid may collect and process data as described in Plaid's own privacy materials. Plaid's privacy policy is available at https://plaid.com/legal/.

Retention and deletion

Moolah retains linked account, transaction, and budgeting history while the user account remains active so the app can provide historical budgeting and trend comparison features.

• Disconnecting a bank always revokes the Plaid connection and stops future syncing. The user can choose to keep imported history or permanently delete that institution's imported accounts and transactions.
• History kept after disconnect remains labeled as disconnected, remains visible to current household members, and can be deleted later by the household member who added the account.
• Deleting a Moolah user account removes data owned by that user from Moolah's primary production records, including related insight interaction data. A household member's departure does not delete data owned by the remaining household; a sole owner deletes the household, while an owner of a multi-member household must transfer ownership first.
• Temporary client-side Plaid session artifacts are cleared on logout and account deletion.
• Raw onboarding milestone events are kept for no more than 90 days. Onboarding assignment and event records are deleted when the associated user account is deleted.

Shared household accounts

Every newly linked account is shared with current household members. Moolah records which household member added the account for attribution and account-management actions, but that does not make the account private. Whether the account contributes to the household budget is controlled separately.

Sharing

Moolah does not sell consumer data obtained through the Plaid API. Data may be shared only with service providers or processors needed to operate the product, or when required by law.

Security

Moolah uses authentication, TLS transport, and other technical and organizational controls designed to protect personal information and financial data.

Your choices

Users can review and correct transactions and budgeting data in the app, change whether an account contributes to the household budget, disconnect institutions, delete retained history, and use the authenticated account-deletion flow. For access, correction, deletion, or other privacy requests that cannot be completed in the app, contact us below.

Contact

For privacy-related questions or deletion requests, contact sethchilders92@gmail.com.