Dimo

Purpose of the Dimo app

The purpose of Dimo is to help people track personal spending. Dimo is a personal expense tracker for logging everyday expenses, setting category budgets, managing recurring bills, reviewing spend stats, and optionally suggesting purchases from Gmail on iOS. Your data stays on your devices and syncs privately when you sign in.

Your name, email, and profile photo come from your sign-in provider and are read-only in Dimo.

What Dimo does

Dimo is a personal spending tracker for individuals. It is not a bank, payment processor, tax advisor, or advertising product. You create and manage your own expense data for personal use on web, desktop, and mobile.

Log expenses — record amounts, categories, payment methods, notes, and dates.
Budgets and recurring bills — set monthly category limits and keep subscriptions visible.
Stats — review spending by period, category, and merchant.
Lending records — track money lent or borrowed with people you know (native apps).
Optional email suggestions (iOS) — optionally connect Gmail to surface purchase or refund suggestions you review before anything is saved.

Why Dimo requests Google user data

Dimo requests Google account access only for the purposes below. We do not sell Google user data, use it for ads, or use it to train unrelated models.

Sign-in (name, email, profile photo) — to create and recognize your Dimo account via WorkOS AuthKit so your workspace can sync across your devices. These fields are read-only in Dimo.
Gmail read-only (optional, iOS Email suggestions) — if you choose to connect Gmail, Dimo uses gmail.readonly access to look for purchase and refund emails and suggest expenses you can accept or dismiss. Messages are processed to power those suggestions; Gmail OAuth tokens stay on your device and are not uploaded through Dimo sync. You can disconnect Gmail at any time.

Full details are in our Privacy Policy. See also the Terms of Service.

Privacy policy

The Dimo privacy policy is published on this same site and must match the URL configured on the Google OAuth consent screen: Privacy Policy.