Depensa
How it worksFeaturesPrivacyFAQChangelog
Get the app
On this page
  1. At a glance
  2. Who is responsible
  3. What Depensa collects
  4. Why Depensa uses it
  5. Where AI comes in
  6. Who processes data on Depensa’s behalf
  7. Where your data goes
  8. How long Depensa keeps it
  9. Your rights
  10. Children
  11. Security
  12. Changes to this policy

Privacy

What Depensa reads, what it stores, and what never leaves your phone.

Effective Oct 10, 2026.

  1. At a glance
  2. Who is responsible
  3. What Depensa collects
  4. Why Depensa uses it
  5. Where AI comes in
  6. Who processes data on Depensa’s behalf
  7. Where your data goes
  8. How long Depensa keeps it
  9. Your rights
  10. Children
  11. Security
  12. Changes to this policy

At a glance

Your passwords stay with you. You sign in to a shop inside a web view on your own phone. Depensa never sees what you type and never receives the shop’s one-time code. It keeps the session the shop hands back, so it can read the pages you are already signed in to.

Depensa reads your order history on the shops you connect, and nothing else: the merchant, the date, the amount, the items, the order id and its status, including refunds. It does not read your messages, your email, or any page outside the shop’s own order history.

Depensa does not sell your data or show adverts, and no data broker is involved. In the app, usage analytics stay off unless you turn them on, and even then they never include your orders. The website counts visits without cookies. The rest of this page says the same things in full.

Who is responsible

Depensa is made by Anirudh, an independent developer in India. Under data protection law he is responsible for your personal data (the “controller”).

Write to depensa@techwithanirudh.com about anything in this policy, including requests about your data. You’ll get a reply from him directly.

This policy covers the Depensa app for iPhone and Android and the site at depensa.techwithanirudh.com. The site sets no cookies and sends no error reports. It counts visits and a few clicks, as described below, without storing anything on your device.

What Depensa collects

Account details, from you. Your email address, a display name if you give one or the name Google shares, your currency and week-start preferences, and your phone’s offset from UTC, so a budget’s month and the monthly summary begin when yours does.

Sign-in records, from Better Auth. The six-digit code emailed to you when you sign in, and the session token issued afterwards, with the IP address and device it was issued to. Depensa deletes a session when you sign out, or within a day of it expiring. If you continue with Google instead, Google confirms who you are and shares your name and email address, and Depensa keeps a record that your account is linked to it. When a Google sign-in carries the same verified email address as an existing account, the two become one account. Depensa holds no password of its own and does not use the Google sign-in to read anything else from your Google account.

Shop sessions, from the shop. When you connect a shop, the session cookies and local storage the shop hands back after you sign in on your phone. Depensa stores them encrypted at rest and uses them only to open the shop’s order-history pages on your behalf. If you sign in to a shop through another account, such as Google, Microsoft or Apple, Depensa also keeps that account’s sign-in cookies from the same sign-in. It encrypts them the same way and keeps them only so the shop’s own sign-in can refresh. It never uses them to open or read that other account, and it deletes them with the shop. Before every shop sign-in, the app shows a notice that Depensa keeps the session and uses it only to read your orders. It opens the shop’s page only after you tap Continue on that notice.

Orders, read from the shop. For each order: merchant, date, amount, currency, items, order id, and status including refunds.

Product photos, read from the shop. When an order page shows a picture of an item, Depensa saves a small thumbnail of it so the app can show it beside the expense. The thumbnail is Depensa’s own stored copy, not a link back to the shop. Depensa deletes it when no expense uses it any more, and when you delete your data or your account.

Things you add, from you. Categories you create, budgets you set for them, manual expenses you enter, and subscriptions you add: a name, an amount, how often it renews, its next renewal date and the time zone it was set in, its category and merchant, whether its charges count as spending, and whether to remind you the day before.

Push tokens, from your phone. A device token, only if you turn notifications on.

Run logs, from the service. When each sync ran and whether it succeeded.

Crash and performance reports, from the app. If the app crashes or a screen is slow, a report with the stack trace, screen name and device details goes to Sentry, so we can fix the fault. These reports carry no order data, cookies or IP address.

Usage events, from the app, only if you turn them on. Sharing is off until you turn it on. The app asks once during setup, with Share analytics or No thanks, and Analytics in Settings turns it on or off at any time. While it is on, the app records when you finish onboarding, connect a source, add an expense by hand or see a refresh fail, and when the app is installed, updated, opened or put in the background. The event for a connected source names the shop’s site, and the one for a failed refresh carries its error code. Each event carries the app version, device model, operating system, language and time zone, and an opaque account id, never your email address. It never carries a merchant, an item, an amount, a category name or anything you typed.

Visits to this website, from your browser. The site counts each page you open and a click on a link that leads to the app: Get the app, the store links, Install on iPhone and its steps, and copying the source address. Each count carries the page’s address without anything after its path, and your browser, operating system, device type, screen size, language and time zone. Nothing is written to cookies or your browser’s storage, and nothing links a visit to your Depensa account. PostHog counts visitors from your IP address and browser with a value it changes every day, then discards the IP address without looking up where you are. If your browser sends Do Not Track or Global Privacy Control, the site sends nothing.

Readers. A reader is a small JSON recipe that tells Depensa how to read one shop’s order pages. Readers are versioned and contain no personal data; you can see what each version read on the source screen in the app. An admin can promote a reader learned from one person’s account for everyone who connects the same shop in the same region. Before promoting, the admin checks that it holds no personal data.

Why Depensa uses it

To run the service. Signing you in, storing your sessions, reading your orders, applying your categories, and showing you your spending. Basis: performance of our contract with you.

To send notifications. Push notifications only if you turn them on. By email, a note naming a source that is signed out and the monthly summary are on until you turn them off in Settings, Notifications; every other email only if you turn it on. Basis: for those two emails, performance of our contract with you, since they report on the service you use; for everything else, your consent, which you can withdraw in the app or in your phone’s settings at any time.

To understand how the app is used. Only if you tap Share analytics during setup or turn on Analytics in Settings, so we can see which features people use and where connecting a source goes wrong. Basis: your consent, which you can withdraw in Settings at any time.

To see how the website is used. Counting visits and clicks, so we know which pages bring people to the app. Basis: our legitimate interest in running the site, which stores nothing on your device and does not identify you. You can object at any time, or turn on Do Not Track or Global Privacy Control in your browser.

To keep the service safe. Detecting abuse, investigating failed syncs, and protecting accounts. Basis: our legitimate interest in running a secure service.

Depensa does not use your data for advertising, profiling or sale.

Where AI comes in

An AI model reads a shop’s order pages once and writes the reader the first time Depensa learns that shop. It does this again only if the shop changes its pages and the reader breaks. On every other sync a deterministic runner replays the reader with no model involved.

The model receives page content: order lists, product names, amounts and dates. It never receives your shop password, and Depensa redacts session cookie values from what it sees. The model reads pages to build a reader. It makes no decision about you, and Depensa makes no automated decision with legal or similarly significant effect on you.

Who processes data on Depensa’s behalf

Each provider below acts on Depensa’s instructions under a contract, receives only what its job needs, and may not use your data for its own purposes.

  • Convex (United States) hosts the database and backend functions. It holds your account details, orders, product photo thumbnails, categories, budgets, manual expenses, subscriptions, shop sessions, push tokens and run logs, encrypted in transit and at rest.
  • Firecrawl (cloud browser provider) runs the server-side browser that opens your shop’s order pages. It handles your shop session and the pages it reads during a sync, and holds a stored browser profile per connected shop.
  • OpenAI (United States) receives order page content in the AI step described above. Depensa does not allow it to use that content to train its models.
  • Resend delivers emails to your address: the sign-in code, the download link when you export your data, and the notifications you choose under Email in Settings, Notifications. Two are on until you turn them off: a note naming a source that is signed out, and on the 1st of each month a summary of the month before. The summary shows what you spent and how it compares, where it went by category, how your budgets went, your biggest order, your busiest day and the merchant you ordered from most. The rest are off until you turn them on: when Depensa can’t read a source, finds new orders on it, or connects it or fails to, when a budget is nearly spent or over, with its amounts, and the day before a subscription you asked to be reminded of renews, with its amount.
  • Vercel (United States) hosts this website. Its servers see your IP address and the pages you request, which it keeps in short-lived request logs. The site sets no cookies and loads nothing from other companies; its visit counts pass through Vercel on their way to PostHog.
  • Expo’s push service delivers notifications to your phone if you turn them on, relaying through Apple and Google.
  • Sentry receives crash reports and performance traces from the app: stack traces, the screen you were on, the method, URL and status of requests the app made, and device and operating system details. The app strips any IP address, cookie, request body, screenshot or order data before anything leaves your phone, so none of it reaches Sentry. The site sends nothing to Sentry.
  • PostHog receives the usage events described above, only while Analytics is on in Settings. It receives no order data, no email address, no session replay and no record of what you type, and it does not look up your location from your IP address. Turning it off stops the app sending anything further and clears the id it was using. PostHog also receives the website’s visit counts described above, through the site’s own address, and discards your IP address once it has counted the visit.

No advertiser or data broker receives anything, and PostHog receives nothing from the app unless you turn Analytics on.

Where your data goes

Depensa is run from India. Convex stores data in the United States, and the other providers run where their infrastructure is, which may be outside your country. When your data leaves the country you live in, Depensa’s contract with each provider and encryption in transit and at rest protect it. If you are in the EEA or the UK, transfers rely on standard contractual clauses or an equivalent lawful mechanism offered by the provider.

How long Depensa keeps it

Depensa keeps your data while your account exists. It deletes run history 30 days after the run ends, and the live sync activity as soon as the run ends. Removing a source drops that shop’s session straight away.

Deleting your account removes your orders, product photos, sessions, readers derived from your account, categories, budgets, subscriptions, preferences and push tokens, and instructs the cloud browser provider to empty the stored shop profile. Delete all data in Settings removes the same things but keeps your account, preferences and push token, and gives you the default categories again. Deleting your account also asks PostHog to delete the person and every usage event sent under your account’s opaque id. Deletion completes within days. Backups held by the hosting provider expire on the provider’s own schedule.

Your rights

Wherever you live, you can ask Depensa to:

  • Access the personal data it holds about you.
  • Correct anything that is wrong or incomplete.
  • Delete your data. You can do this yourself from the app, or ask us.
  • Receive a copy of the data you gave us in a portable, machine-readable form. You can do this yourself with Export your data in Settings. Depensa emails you a link to your account details, preferences, categories, budgets, subscriptions, merchants, the shops you connected with their sync history, and your expenses, deleted ones included, as JSON, with the expenses again as a CSV. Product photos and shop logos are links to the images the app shows, not files in the zip. The link works once and expires after 24 hours, when Depensa deletes the file. The export never includes shop sessions or anything Depensa uses to read a shop.
  • Object to processing based on legitimate interest.
  • Withdraw consent for notifications or analytics at any time, without affecting anything done before.
  • Nominate someone to exercise these rights for you if you are unable to.

Send requests to depensa@techwithanirudh.com. We may ask you to confirm the email address on the account first. We aim to reply within a month.

If you are not satisfied, you can complain to a supervisory authority: the Data Protection Board of India, or if you are in the EEA or the UK, your local data protection authority. We would rather hear from you first, but you do not have to.

Children

Depensa is for people aged 18 or over, or the age of majority where you live, since connecting a shopping account means you must be old enough to hold one. Depensa does not knowingly collect data from anyone younger. If you think it has, write to us and we will delete it.

Security

Every connection is encrypted in transit and stored data is encrypted at rest. A navigation guard confines the server-side browser to the connected shop’s own domain. It lets a page pass through the shop’s own sign-in provider for a few seconds at most, and nothing reads the page while it does. Depensa uses shop sessions only to read order history, and it redacts session cookie values before anything reaches an AI model. No system is perfectly secure; if a breach affects your data, Depensa will tell you and the relevant authority as the law requires.

Changes to this policy

When this policy changes, we post the new version here with a new effective date, and the app tells you if the change matters to you. Continuing to use Depensa after that date means the new version applies.

Depensa
depensa@techwithanirudh.com

Product

How it worksPrivacyDownload on Google PlayInstall on iPhoneChangelog

Legal

Privacy policyTermsDelete account

© 2026 Depensa