TallyVally

Privacy policy and support for the TallyVally expense tracker

View the Project on GitHub indxneo/tallyvally-legal

Privacy Policy — TallyVally

Effective date: July 22, 2026 Last updated: October 28, 2026

Applies to: the TallyVally mobile app for iOS and Android.

Two iPhone versions. TallyVally 2.0 for iPhone is a rebuilt app. Where it handles your data differently from earlier iPhone versions (1.x) and from the Android app, this policy says “on iPhone, from 2.0”. Everything not marked that way applies to every version.


The short version


1. Who this policy is for and who we are

This policy explains how the TallyVally app (“the app”, “TallyVally”) handles your information. The app is published by Alisher Serikbayev (“we”, “us”, “the developer”). You can reach us about privacy at alishersv.dev@outlook.com.

TallyVally is a personal expense and asset tracker. Its design principle is data sovereignty: your financial history stays on your device by default, and anything that leaves the device is disclosed here.

2. Where your data lives

TallyVally stores your data in a local database (SQLite) inside the app’s private storage on your device. This includes:

There are no user accounts, no sign-in, and no cloud copy of this data under our control. We cannot see your ledger.

On iPhone, from 2.0: a copy in your own iCloud. The app keeps a copy of its database — your receipts, line items, chat history and settings — and of any receipt copies you kept, in its private folder in your own iCloud Drive, so that they come back if you delete the app or move to a new iPhone: on a phone with no receipts, the app offers to bring them back, and does so only if you say yes. The copy is in your Apple Account; it never comes to us and we can never see it. It is on by default. You can turn it off in Settings › Your data › Keep a copy in iCloud; the app asks first, then deletes the copy in your iCloud. If iCloud Drive is off on your iPhone, nothing is copied. Android keeps no such copy.

3. What leaves your device, to whom, and why

Only two features send what you scanned or asked off your device, and both send it to the same recipient: Google’s Gemini AI (generativelanguage.googleapis.com). The requests are routed through our backend proxy — a Supabase-hosted Edge Function — which forwards them to Google and returns the result. The proxy exists so that the Google API key is never embedded in the app; it is infrastructure, not a place where your data is stored.

On iPhone, from 2.0, three more things can leave your device, none of them to us: chat questions may be answered by Apple’s AI (Section 3b); the copy in your own iCloud (Section 2); and, only if your home currency is the Kazakhstani tenge, a request for the National Bank of Kazakhstan’s public exchange rates (Section 3e).

On iPhone, from 2.2.1, each scan or chat also carries the proof that counts your free scans, and our server asks Apple once about your iPhone (Section 3g). None of it is about your receipts.

On Android, a few more things leave your device, none of them about your receipts: with each scan or chat, the proof that counts your free scans (Section 3f); the tenge rates request, as on iPhone (Section 3e); and Google Play’s own billing library, which talks to Google (Section 5).

3a. Scanning a receipt (AI receipt OCR)

When you scan or upload a receipt, the app sends the receipt itself to Google Gemini — either the photo you took or chose, or a PDF you uploaded from Files. Gemini reads it and returns the structured fields (store, date, totals, line items, and — if printed on the receipt — the payment method and card last-4). The extracted result is then saved on your device.

A PDF is sent in full, every page. If a document holds more than the one receipt you meant to scan, everything printed in it is part of what is sent.

Important and honest detail: because the whole receipt is sent for reading — the entire photo, or every page of the PDF — anything visible on it is part of the transmission. If your receipt prints the last four digits of your card and the payment method, those are present in the image and are extracted by Gemini. This is why we disclose Payment Info as data that can leave the device. We never send a full card number, PIN, CVV, expiry, or bank-account number — those are not stored on the receipt and are not handled by the app.

Three small technical values travel with a scan, and none of them is a receipt field. Your phone’s calendar date is sent to Google along with the image, so that a receipt printing no date of its own is filed on your day rather than the server’s. Your home-currency setting (for example USD) and a free-or-premium flag go only as far as our own proxy — the first so it can look up that day’s exchange rate, the second so it can manage its own AI budget. None of the three identifies you, and only the date reaches Google. On Android, and on iPhone from 2.2.1, a scan also carries the proof described in Sections 3f and 3g, which does identify your phone (by a code), so that free scans can be counted.

Receipt scanning is user-initiated: nothing is sent unless you choose to scan or upload a specific file.

3b. Asking the financial assistant (AI chat)

When you ask the in-app assistant a question, the app sends to Google Gemini:

  1. Your typed question (and the recent back-and-forth of the current conversation), and
  2. A summary of your spending used to ground the answer in your real data.

By default, that summary includes aggregate figures (your total spend, number of transactions, average transaction value, total savings, and spending by category) and a short list of the items you buy most often, by name. When your question names a particular store, item or time period, the store names and shopping dates needed to answer it are included as well.

One detail worth being plain about: the list of your most-purchased item names is part of every cloud chat question, not only the ones that mention an item. Store names and dates are not — those travel only when your own question or the recent conversation refers to them. If your receipts record purchases you would rather not have read by an AI service, turn on “Send only totals to AI” (Section 3c), which sends no item names at all, or use on-device chat where your iPhone supports it, which sends nothing for an answer. On-device chat is an iPhone feature; Android has no on-device AI option and always uses the cloud assistant described above.

The chat path never sends your card last-4 or payment method. The grounding summary is built so that card and payment fields are excluded — they are simply not part of what the chat feature reads.

On iPhone, from 2.0: Apple’s AI answers first. With “Use Apple’s most advanced AI” on (Settings › Chat & data; on by default) and an iPhone that supports Apple Intelligence, your question is answered by Apple’s AI on Apple’s Private Cloud Compute servers. It receives your question, the recent conversation, a summary of your spending, and the answers to the questions it asks your receipts to answer you — for example your spending by month or by category, the stores you shopped at, or when and where you last bought an item. It never receives your card last-4 or payment method. Apple says this data is used only to answer you and is not stored. Only when Apple’s AI cannot answer does the question go to Google’s Gemini as described above. Turn the setting off and a simpler Apple AI answers on your iPhone itself, so nothing leaves your device for an answer. On an iPhone without Apple Intelligence, Google’s Gemini answers. Each answer says who wrote it (“Answered by Apple” or “Answered by Google”).

3c. “Send only totals to AI” (opt-in, for stricter privacy)

In Settings → Chat & data you can turn on “Send only totals to AI”. When it is on, the chat feature sends only totals and category breakdowns — no item names, no store names, and no dates leave your device, only the name of the period you asked about (for example “this month”). On Android, the earlier messages of the conversation are not sent either. On iPhone, from 2.0, it limits Apple’s AI in the same way. Answers become less specific in exchange for sending the minimum possible data. This setting is off by default, so the assistant has the detail it needs unless you choose otherwise.

3d. What we do not send anywhere

3e. Exchange rates for the Kazakhstani tenge (iPhone, from 2.0, and Android)

If your home currency is the Kazakhstani tenge, the app downloads the National Bank of Kazakhstan’s public exchange rates, to convert receipts in other currencies at the official rate for their own day. Only a date is sent; nothing about you or your receipts. With any other home currency, the app never makes this request.

3f. Counting free scans and chats (Android)

Free scans and chats on Android are counted by our server, so that deleting and reinstalling the app does not reset them. To do this, each scan and each chat question carries:

What our server keeps: your phone’s code, with how many free scans and free chats it has used (the welcome pack, and this month’s), and when. This is kept for good, so the welcome pack is not given twice. For a subscription, it keeps a scrambled form of the purchase token (never the token itself), when the subscription ends, and which phone codes used it each month. To stop abuse, it also counts requests per internet (IP) address in short time windows; these counters are not linked to your phone code. None of this contains anything you scanned or asked. Google handles the Play Integrity and Google Play checks under its own privacy policy.

On iPhone before 2.2.1, free scans and chats are counted on the phone itself, and none of this applies there. From 2.2.1, see Section 3g.

3g. Counting free scans and chats (iPhone, from 2.2.1)

From version 2.2.1, free scans and chats on iPhone are counted by our server too, so that deleting and reinstalling the app does not reset them. To do this, each scan and each chat question carries:

The first time, our server also asks Apple (Apple’s DeviceCheck) whether this iPhone has used TallyVally’s welcome pack before, and tells Apple that it now has. Apple keeps this as two yes-or-no answers, and the month they last changed, for this iPhone and our app only; they contain nothing about you.

What our server keeps: your phone’s code, with how many free scans and free chats it has used (the welcome pack, and this month’s), and when; and, for each installation, its key’s public half, a counter that stops a request from being sent twice, and Apple’s receipt for the key. This is kept for good, so the welcome pack is not given twice. For a subscription, it keeps a scrambled form of the purchase’s ID (never the record itself), when the subscription ends, and which phone codes used it each month. As on Android, it also counts requests per internet (IP) address in short time windows; these counters are not linked to your phone code. None of this contains anything you scanned or asked. Apple handles App Attest, DeviceCheck and the App Store under its own privacy policy.

4. How Google handles the data we send it

The receipt images and chat content described in Section 3 are processed by Google’s Gemini API. Google’s handling of that data is governed by Google’s own API terms and privacy commitments for the API tier in use, not by us.

We are honest about the limit of our knowledge here: confirming and contracting a specific no-retention / no-training Gemini tier is an operational step the developer must complete, and until that is confirmed we do not claim that Google does not retain or use this data. We send Google the minimum needed for the feature to work, we never attach an account or identity to it (there are no accounts), and “Send only totals to AI” (Section 3c) lets you reduce what is sent to totals only. For details of Google’s practices, see Google’s API terms and privacy documentation.

5. No tracking, no ads, no third-party analytics

TallyVally contains no advertising SDKs, no behavioral-analytics SDKs, and no cross-app/cross-site tracking. We do not build advertising profiles, and we do not use the Apple “tracking” mechanisms (App Tracking Transparency is not invoked because we do not track). The iOS privacy manifest declares NSPrivacyTracking = false and an empty tracking-domains list, consistent with this statement. On Android the app requests no advertising identifier and contains no advertising or analytics library.

On iPhone, from 2.2.1, the app uses Apple’s App Attest and DeviceCheck (Section 3g). They are part of iOS, not third-party code, and are used only to count free scans and chats, never for advertising or tracking.

On Android, the app’s only third-party code is Google’s own Play libraries: Google Play Billing, which every app that sells subscriptions through Google Play uses, and Google Play Integrity (Section 3f). Google Play Billing includes Google’s own diagnostics component, which sends Google technical information about how the billing library itself is working (to firebaselogging.googleapis.com). We do not receive that information, and Google handles it under its own privacy policy. There is no Firebase Crashlytics and no Google Analytics in the Android app.

On iPhone, from 2.0, the app contains no third-party SDK at all. On iPhone before 2.0, the one third-party SDK in the app is Firebase Crashlytics, and it is here to report crashes, not to watch you. We are naming it rather than hiding it behind the word “analytics”, because it is a Google SDK and you are entitled to know it is there. What it is not: it records no screen views, no taps, no sessions, and no usage patterns, and it builds no profile. Firebase’s own privacy manifest declares that it collects “Crash Data” and “Other Diagnostic Data”, both not linked to your identity and both not used for tracking — which matches what we have enabled. Section 3d describes exactly what a report contains.

6. Data retention and deletion

7. Security

No method of electronic storage or transmission is perfectly secure, but we minimize what leaves the device and protect what remains on it.

8. Device permissions we request

These permissions are used only for the receipt-scanning feature you initiate, and only on the specific image you choose. We do not access your camera or photo library in the background.

On Android the app declares no camera, photo, or storage permission at all. It asks for internet access, billing through Google Play, and network status (whether you are online); for notifications, only when you choose a reminder before a subscription or bill is charged; and to start after the phone restarts, only so those reminders are set again. Photographing a receipt hands the job to your phone’s own camera app, and choosing a photo or a PDF goes through Android’s own picker, which passes back only the one file you chose.

9. Children

TallyVally is a general-audience financial tool and is not directed to children. We do not knowingly collect personal information from children.

10. International users and data transfer

If you use the app outside the regions where Google processes Gemini API requests, the receipt/chat data described in Section 3 may be processed in another country (for example, the United States). By using the AI scanning and chat features, you understand that this processing occurs as described here.

11. Your choices and controls

12. Changes to this policy

If we change how the app handles data, we will update this policy (and the “Last updated” date) and, where the change is material, surface it appropriately. The version published at https://indxneo.github.io/tallyvally-legal/ is the authoritative version.

13. Contact

Questions about this policy or your data: alishersv.dev@outlook.com.

This policy is governed by the laws of the State of Illinois, United States.