Privacy Policy

Overview

Dimo is a personal spending tracker for expenses, categories and budgets, payment methods, recurring bills, stats, CSV import/export, lending, and account preferences. It is available as a web app, desktop app, and native mobile apps.

Dimo is local-first: your data lives primarily on your device and syncs privately to your account when you sign in. This policy explains what information is handled, where it goes, and the choices you have.

Account information

Sign-in is provided by WorkOS AuthKit (for example Google or Apple sign-in). Your sign-in provider supplies your name, email address, and optional profile photo. Those profile fields are read-only in Dimo. Name and email may be mirrored into workspace metadata so the app can show your account when a login token omits them. Profile photos from WorkOS are not stored as synced Dimo entities.

Data you create in Dimo

Depending on which features you use, Dimo may store:

• Expense transactions (amounts, dates, notes, categories, payment methods)
• Categories, budgets, and payment method labels
• Recurring bills and related schedule details
• Lending records (contact names or contact IDs, amounts, kinds, optional comments)
• App preferences (for example currency and notification toggles)
• On native iOS with Email suggestions enabled: analyzed email suggestion records, which can include the normalized message body

Money amounts are stored as integer minor units. You can export or import expenses as CSV; imported files are processed on your device to create local records.

Where data is stored

On your device. Web and desktop use a local browser database. iOS uses an on-device SQLite database. Android uses an on-device SQLite database. Local databases are scoped to your signed-in account.

In the cloud (when signed in). An encrypted connection syncs your Dimo entities to a private Convex workspace owned by your authenticated account so data can restore and stay consistent across your devices. Ownership is derived from your sign-in identity; clients do not choose another user’s account.

Address-book contact photos used for lending stay on the device and are never persisted or synced as Dimo data. Contact names and IDs used for lending may sync with lending records.

Optional Email suggestions (iOS)

On iOS, you may optionally connect Gmail for purchase or refund suggestions. Gmail access is read-only and uses Google OAuth. Gmail OAuth tokens stay on your device and are not uploaded through Dimo sync.

Message analysis may use OpenRouter. In “free models” mode, the iPhone calls authenticated Convex actions and a shared OpenRouter key stays only on the server. In “bring your own key” mode, your OpenRouter API key is stored in the device Keychain and analysis goes from the iPhone to OpenRouter. Analyzed suggestions (including normalized body text) can sync as native-owned email records so they restore across your devices. You can disconnect Gmail and delete account data as described below.

Analytics and diagnostics

Hosted web and desktop builds may embed Vercel Analytics and Vercel Speed Insights to measure traffic and performance (for example page views and load timing). Those services do not receive your expense entries, budgets, lending records, or email bodies. Native iOS and Android builds do not embed those Vercel SDKs.

If you install Dimo from the App Store or Google Play, Apple or Google may collect standard install and diagnostics information under their own policies. Dimo does not embed third-party advertising SDKs and does not sell personal data or use your spending data for advertising or profiling.

Third parties

• WorkOS — authentication
• Convex — private cloud sync and related backend functions
• Google / Apple — social sign-in (and Gmail if you connect Email on iOS)
• OpenRouter — optional email analysis when you use that feature
• Vercel — hosting analytics on web/desktop builds only
• Apple / Google — app distribution platforms

Each provider processes relevant data under its own privacy policy when you use that provider’s service through Dimo.

How we use information

Information is used only to:

• Provide, maintain, and improve Dimo’s features
• Authenticate you and sync your workspace across devices
• Optional email suggestion analysis when you enable it
• Understand aggregate web performance (web/desktop analytics)
• Respond to support or privacy requests you send

Retention, sign-out, and deletion

Local data remains on the device until you sign out, delete history, or delete your account. Sign-out stops sync and deletes local Dimo databases on that device before ending the WorkOS session.

Account deletion requires a network connection: it clears your cloud workspace data, then performs the same local and session cleanup. Deleted cloud records are not kept for later restore. Backups you create yourself (for example CSV exports) are under your control.

Children

Dimo is not directed at children under 13. Do not use the app to store information about children.

Security

Sync uses authenticated, encrypted network connections. Local databases and device keychains follow platform storage practices. No method of transmission or storage is perfectly secure; please use a device passcode or biometrics and keep your sign-in provider account protected.

Changes

We may update this policy as the product evolves. Material changes will be reflected on this page with a new “Last updated” date.

Contact

Questions about this privacy policy can be sent to Saiteja Segu at segusaiteja12345@gmail.com.