Privacy Practices

How privacy is handled in product flows.

This notice describes what happens to data in concrete workflows such as on-device storage, imports, exports, support feedback, and Ask George.

On-device data

Expenses, categories, payees, budgets, notes, and optional place metadata are stored locally on your device to run app features.

CSV import

HomeBudget CSV rows are parsed and used to create expenses and related records in local app storage.

Backup import

ExpensiFamily JSON backups are validated and merged using record IDs. Existing records with matching IDs can be updated.

Export

You can generate JSON or CSV exports and share files through your device share sheet.

Feedback flow

If you submit feedback, the submitted message and optional contact fields may be sent for product support and review.

Ask George

If you use Ask George, the app sends a normalized JSON summary of recent expenses to the ExpensiFamily server. The request includes an anonymous client ID stored locally for quota enforcement, plus currency, locale, and timezone. The expense summary can include local expense IDs, dates, amounts, currencies, categories, subcategories, payees, and recurring flags. If you have budgets, the app may also send budget targets such as category, amount, currency, and date range. The server may forward this data to OpenAI, the current external AI provider, to generate the report. The current data sent to Ask George does not include expense or budget notes/descriptions, attached place metadata, or GPS metadata. The app does not send an OpenAI key and does not call OpenAI directly. The latest successful Ask George report is cached locally on your device with its generation time so reopening the page does not use another daily request.

Last updated: May 21, 2026