Finovo Privacy Policy
In effect from: July 13, 2026
Finovo is an iPhone and iPad app published by ZXApps (operated by the developer Ghayor Abbas, reachable at the contact address listed in §20). It helps you track expenses and income, scan and organize receipts, manage wallets and budgets, follow recurring bills, and split costs with other people. This document explains, in plain language, what the app does with information on your device — and what it deliberately avoids doing.
In this document, "Finovo" or "the app" refers to the application; "ZXApps," "we," "us," or "our" refers to the publisher.
The short version is below in §1. The long version takes the same statements apart and explains them piece by piece.
Index
1. The shortest possible summary
If you stop reading after this section, take these facts with you:
- The financial data you enter — expenses, income, receipts, wallets, budgets, splits — is stored on your device. ZXApps does not operate a server that stores it.
- The app never uploads your receipts, transactions, or attachments to us. Receipt text recognition runs on your device.
- iCloud sync is optional and off by default. If you turn it on, your data syncs only through your own private iCloud account; we never receive a copy.
- Production builds use Firebase Analytics and Firebase Crashlytics (Google services) to understand feature use, diagnose crashes, and improve reliability. We do not send amounts, merchant names, receipt contents, notes, balances, email addresses, or other user-entered financial content to these services.
- Finovo shows ads through Google AdMob. The app may ask for App Tracking Transparency permission before loading an ad; denying it does not block the app or prevent contextual/limited ads.
- We do not sell your personal information for money.
- You can use the app as a Guest with no account, or with Sign in with Apple. We never ask for a password.
- Permissions (Camera, Photos, Location, Notifications) are optional and independent. Denying one only disables that one feature.
- Deleting the app from your device deletes the local data the app stored on that device.
The remainder of this document expands on each of these claims so you can verify them.
2. How Finovo is built
Finovo is what the iOS community calls a local-first app. Practically, that means:
- All of your financial records are created, stored, and analyzed on the same device you use. The app does not maintain a backend service, user database, or login system of its own.
- Your data is held in an on-device database (Apple's SwiftData) and, only if you switch it on, mirrored to your private iCloud through Apple's CloudKit. There is no ZXApps-operated copy in the middle.
- Receipt scanning uses Apple's on-device document camera and the Vision framework for text recognition. Receipt images are read and parsed locally and are never sent to us or to any third party for processing.
- Finovo includes Google services for three defined purposes: Google AdMob to show ads, Firebase Analytics to measure app and feature usage, and Firebase Crashlytics to diagnose crashes and non-fatal errors. These services are described in §8. The app does not include a social-media SDK or a separate third-party attribution SDK.
The reason these architectural choices matter for privacy is straightforward: the app keeps your financial life on your device. Only the limited service data described here leaves it through iCloud, the App Store, AdMob, Firebase Analytics, Firebase Crashlytics, or Apple location services.
3. Inventory of data the app reads and stores
The sections below list, by category, the information Finovo touches while it runs. Your financial records and user-entered content are processed and stored only on your device (and in your private iCloud if you enable sync). Limited advertising, app-activity, and diagnostic data is processed by Google as described in §8.
3.1 Account information
If you choose Sign in with Apple, the app stores an Apple-provided user identifier and — only if you choose to share them on first sign-in — your name and email address (which may be Apple's private relay address). If you continue as a Guest, none of this is collected. This information stays on your device (and your private iCloud if sync is on). We never receive it on a server we control.
3.2 The financial records you enter
Finovo stores what you record, which may include: expenses and receipts, income, merchant and source names, amounts and currencies, dates, categories, notes, payment-method labels, wallets and account balances, budgets, recurring bills and subscriptions, and bill-split details — including names of people you add to a split.
3.3 Receipt images and documents
When you scan a receipt or attach an image or PDF, the file is stored with its record on your device (and your private iCloud if sync is on). Text recognition (OCR) runs on your device using Apple's Vision framework to suggest the amount, date, and merchant. Receipt images are never uploaded to us or to any third party for processing.
3.4 Your current location, on demand
If you choose to add a place to an expense, the app uses your device location once, at that moment, and turns it into a readable place name. Location is used only when you request it, never in the background, and only the resulting place text is stored with that record. The app does not build a location history or derive your home or work address.
3.5 App-internal state
Finovo keeps a small amount of bookkeeping on the device: whether onboarding/setup is complete, your selected currency, notification preferences, your iCloud-sync choice, and a cached copy of your subscription status reported by StoreKit. Your profile name/email (from Sign in with Apple) and currency may sync through your private iCloud so your devices stay consistent.
3.6 App activity and diagnostics
In production builds, Firebase Analytics receives limited app-interaction information such as screen names, feature events, selected currency, built-in category identifiers or random UUID-based identifiers for custom categories (never custom category names), wallet type, whether an attachment or recurring option was used, subscription status, and counts such as wallet or split-participant count. It also collects certain events automatically, such as app opens, first launches, app updates, sessions, and in-app purchases. Firebase may process an app-instance identifier, the Identifier for Vendors (IDFV), the IDFA when it is available after ATT authorization, IP-derived coarse location, and basic device, operating-system, app-version, and language information.
Firebase Crashlytics receives crash reports, stack traces, relevant app state, device and operating-system information, and developer-recorded non-fatal errors. When Analytics and Crashlytics are both enabled, recent analytics events may appear as breadcrumbs leading up to a crash. We deliberately do not attach your name, email address, transaction amounts, merchant/source names, receipt images or text, notes, wallet balances, or other user-entered financial content to analytics events or crash reports.
4. Things Finovo never does
For clarity, here are things the app does not do:
- It does not sell your personal information for money.
- It does not upload your receipts, transactions, balances, or attachments to a ZXApps server — there is no such server.
- It does not send your transaction amounts, merchant/source names, receipt contents, notes, balances, or attachments to Firebase Analytics, Firebase Crashlytics, AdMob, or advertisers.
- It does not use a social-media SDK or a separate third-party attribution SDK.
- It does not use your financial data to target ads. Advertising data and your financial records are kept entirely separate.
- It does not read your messages, browsing history, health data, or data from other apps.
- It does not require you to create an account or share a password.
- It does not perform background location tracking.
The limited data that leaves the device for advertising, analytics, and crash diagnostics is explained in §8.
5. Every permission the app may ask for
Finovo requests only the permissions below, and only at the moment a feature you tapped on requires them.
| iOS permission | Why it is needed | When the prompt appears |
|---|---|---|
| Camera | Scanning a receipt to pre-fill an expense. | The first time you start a receipt scan. |
| Photos | Attaching an existing image or PDF to a receipt. | Only when you pick a photo or file to attach. |
| Location — When In Use | Adding a place name to an expense. | Only when you tap to add a location to an expense. |
| Notifications | Sending the expense reminders and budget alerts you opt into. | When you turn on reminders or alerts inside the app. |
| App Tracking Transparency | Allowing AdMob and participating advertising partners to access the device advertising identifier and use app-related data for personalized advertising and ad measurement across other companies' apps or websites. | Before the first ad load when tracking authorization has not already been decided. |
Saying "no" to any prompt simply disables the feature that needed it. The rest of the app continues to work. If you deny App Tracking Transparency, Finovo can still show contextual or limited ads, but the IDFA is unavailable to the ad request. ATT controls cross-app tracking; it does not turn off Finovo's Firebase Analytics or Crashlytics processing described in §8.2.
6. Where your data physically lives
Because your financial records and user-entered content remain on-device unless you enable private iCloud sync, it helps to know which location holds what:
| Bucket | What's inside | When it goes away |
|---|---|---|
| Standard UserDefaults | App preferences, setup/onboarding flags, selected currency, notification settings, iCloud-sync choice, cached subscription state, and your Apple sign-in identifier/name/email. | When you uninstall the app or sign out (session identity is cleared on sign-out). |
| Local SwiftData store | Your expenses, income, receipts, wallets, budgets, splits, categories, and recurring items. | When you delete the records, or when you uninstall the app. |
| External file storage | Receipt images and attached documents. | When you delete the attachment or uninstall the app. |
| Your private iCloud (optional) | A synced copy of the above, plus your profile name/email and currency, if you turn on iCloud sync. | When you turn off sync and remove Finovo's data via iOS Settings → [your name] → iCloud. |
Nothing in this table is uploaded to ZXApps. On-device storage relies on the same hardware-backed device encryption iOS provides whenever your device is locked.
7. Network behavior of the app
Finovo does not contact a ZXApps-owned server — there isn't one. Outbound network activity during use comes from these sources:
- Google AdMob requests ads from Google's ad servers. This is described in §8.1.
- Firebase Analytics and Firebase Crashlytics send limited app-activity, device, and diagnostic information to Google in production builds. This is described in §8.2.
- StoreKit contacts Apple's App Store servers when you view subscription options, purchase, restore, or when your entitlement is refreshed. Operated by Apple, not by us.
- iCloud / CloudKit synchronizes your data with your private iCloud account, if you enable sync. Operated by Apple.
- MapKit / Apple's reverse-geocoder may turn a coordinate into a readable place name when you add a location to an expense. This call goes to Apple, not to us.
Finovo does not send your financial records to Google or any ZXApps server. Network activity for advertising, analytics, and diagnostics is limited to the purposes and data described below.
8. Google services: AdMob, Firebase Analytics, and Crashlytics
8.1 Advertising and Google AdMob
Finovo displays ads served through Google AdMob (operated by Google):
- Content controls. We configure AdMob to exclude adult (18+), gambling, and sexually explicit ad content to suit a personal-finance audience. We do not control, and cannot guarantee, the specific ads delivered.
- Tracking permission. Finovo may request Apple's App Tracking Transparency permission before loading an ad. If you allow it, AdMob and participating advertising partners may access the IDFA and link app-related data with data from other companies' apps or websites for personalized advertising or measurement. If you deny it, the IDFA is unavailable and Finovo remains fully usable with contextual or limited ads.
- Attribution without IDFA. Google and participating ad networks may use Apple's privacy-preserving SKAdNetwork APIs to measure installs or conversions even when IDFA access is unavailable.
- Data Google may process. Even for non-personalized ads, to serve, cap, and measure ads, improve SDK performance, and detect fraud, Google may process IP address and coarse (IP-derived) location; device identifiers; ads viewed or clicked; other ad/product interactions; device and operating-system information; performance data; and non-user-related crash logs. Google acts as an independent party for this processing under its own policies.
- Your financial data is never used for ads. Advertising runs separately from your records; the app does not share your transactions, receipts, or balances with advertisers.
- Google's policies. Google's handling of this data is described at policies.google.com/privacy and policies.google.com/technologies/partner-sites. AdMob specifics are at support.google.com/admob/answer/6128543.
8.2 Firebase Analytics and Crashlytics
Production builds use Firebase Analytics and Firebase Crashlytics, both operated by Google:
- Analytics. We use product-interaction events and screen views to understand which features are used and improve the app. These events may include the non-content attributes listed in §3.6.
- Diagnostics. Crashlytics collects crash reports, stack traces, relevant application state, device/OS details, and developer-recorded non-fatal errors so we can investigate failures. Analytics events may be attached as pre-crash breadcrumbs.
- Identifiers and technical data. Depending on Google's SDK behavior and device settings, Firebase may process an app-instance identifier, IDFV, or the IDFA when available after ATT authorization, along with IP-derived coarse location and basic app/device metadata. We do not set a Firebase user ID or send your Apple sign-in identity to Firebase.
- Advertising features. Firebase Analytics data may support advertising measurement or personalization if those features are enabled in the connected Google property and the required permission or consent has been obtained. ATT denial prevents IDFA access but does not disable core app-usage measurement through app-instance or vendor identifiers.
- Separation from financial content. We do not send amounts, merchant or income-source names, receipt images or recognized text, notes, balances, email addresses, or other user-entered financial content as Firebase event parameters or crash-report custom fields.
- Availability and retention. Firebase processing is enabled automatically in production builds and is not controlled by the ATT choice. Google retains this data according to our Firebase project settings and Google's applicable retention rules.
- Google's policies. See Google's Privacy Policy, How Google uses information from sites or apps that use its services, and Firebase privacy and security.
9. Subscriptions
Finovo is free to install and use on an ad-supported basis. Advanced features are unlocked through an optional auto-renewing subscription, sold by Apple via the App Store using Apple's StoreKit framework.
What this means in practice:
- Apple — not us — sees your payment method, billing address, and Apple ID.
- The only thing the app receives from StoreKit is a signed entitlement indicating whether your Apple ID currently has an active subscription. No payment identifiers travel with that signal.
- Price, billing period, and any free trial are shown on the purchase screen before you buy.
- Auto-renewal, cancellation, refunds, and Family Sharing are governed by Apple's standard subscription policies. You can manage or cancel a subscription at any time in Settings → [Your Name] → Subscriptions on your device.
Apple's processing of your purchase is described in Apple's privacy policy and the Apple Media Services Terms.
10. Notifications and reminders
If you turn them on, Finovo schedules local notifications (expense reminders and budget alerts) through iOS. These are produced by your device and never go through a push server. The app does not register for remote push notifications and never transmits a push device token. Adjust these anytime in Settings → Notifications → Finovo.
11. Apple frameworks the app relies on
For transparency, here are the Apple-provided system frameworks Finovo uses for user-facing features:
- SwiftData and Foundation — local storage and standard utilities.
- CloudKit — optional sync to your private iCloud.
- AuthenticationServices — Sign in with Apple.
- VisionKit — the on-device document camera for receipt scanning.
- Vision — on-device text recognition (OCR) of scanned receipts.
- PhotosUI / PhotoKit — picking an image to attach.
- Core Location — only when you add a location to an expense.
- MapKit — turning a coordinate into a readable place name.
- StoreKit — subscriptions.
- UserNotifications — scheduling local reminders.
The third-party SDKs in the app are Google Mobile Ads (AdMob), Firebase Analytics, and Firebase Crashlytics, covered in §8.
12. Security posture
Because your financial data stays on the device (and your private iCloud), the security model is essentially the security model of iOS itself:
- App sandbox. iOS prevents other apps from reading Finovo's local container.
- Hardware-backed encryption. When your device is locked, on-device storage is encrypted using the device's hardware keys.
- Private iCloud. When sync is on, data is stored in your own iCloud private database, accessible only through your Apple account — not by us.
- Least-privilege permissions. Each permission is requested only when the matching feature is used.
- No ZXApps server. Because the app never sends your financial data to a server we operate, classes of risk like "server breach" of your records do not apply.
No technical system is ever provably perfect, but the smaller the surface area, the smaller the risk — and Finovo's is intentionally small.
13. Use by minors
Finovo is a general-audience finance utility and is not directed at children under 13. We do not knowingly collect personal data from children under 13 (or under the higher digital age of consent where applicable, such as 16 in parts of the EU). Purchasing a subscription requires you to be 18 or older, or to have a parent's or guardian's consent. If you believe a minor has used Finovo in a way that raises a privacy concern, please write to the address in §20.
14. Controls you always have through iOS
You don't need to file a written request to control what Finovo can see. iOS gives you the tools:
- Settings → Privacy & Security → Camera / Photos / Location — grant, narrow, or revoke each permission independently.
- Settings → Privacy & Security → Tracking — review or revoke Finovo's cross-app tracking permission. Revoking it prevents future IDFA access; it does not disable Firebase Analytics or Crashlytics.
- Settings → Notifications → Finovo — mute reminders and alerts.
- Settings → [Your Name] → Subscriptions — cancel a subscription.
- Settings → [Your Name] → iCloud — remove Finovo's synced data from your iCloud.
- Long-press the Finovo icon → Remove App → Delete App — remove the app and its local data from the device.
These controls are immediate and honored by iOS itself.
15. Notice for users in the EU, the EEA, the UK, and Switzerland
This section provides additional information required by the EU General Data Protection Regulation (GDPR), the UK GDPR, and the Swiss FADP.
Controller. ZXApps, the publisher of Finovo, acts as the controller of the limited personal data processed in connection with the app. Google processes advertising, analytics, and diagnostic data described in §8 under the applicable Google terms and policies.
Legal bases.
- Article 6(1)(b) — performance of a contract — when you ask the app to do something for you (record a transaction, scan a receipt, sync your data, process a subscription).
- Article 6(1)(a) — consent — for permissions you grant through iOS (Camera, Photos, Location, Notifications) and for advertising where applicable law requires consent. Apple's ATT authorization separately controls cross-app tracking and IDFA access. You can withdraw consent or revoke a permission at any time.
- Article 6(1)(f) — legitimate interests — for keeping the app secure, remembering your preferences, understanding aggregate feature use, diagnosing crashes, and supporting the app through advertising, except where applicable law requires consent.
Your rights. Subject to GDPR conditions, you have the rights of access (Art. 15), rectification (Art. 16), erasure (Art. 17), restriction (Art. 18), portability (Art. 20), objection (Art. 21), not being subject to solely automated decision-making (Art. 22), which the app does not perform, and withdrawal of consent (Art. 7(3)).
Because Finovo keeps your records on your own device and iCloud, the fastest ways to exercise these rights are also the most direct: edit or delete records inside the app, revoke an iOS permission, turn off iCloud sync, or delete the app. For a written response about a specific GDPR right, write to the address in §20 and we will respond within one month (extendable by two months for complex matters, with notice to you).
Complaints. You may lodge a complaint with your local supervisory authority:
- European Data Protection Board: edpb.europa.eu
- UK Information Commissioner's Office: ico.org.uk
- Swiss FDPIC: edoeb.admin.ch
16. Notice for users in California
This section addresses disclosures expected under the California Consumer Privacy Act, as amended by the California Privacy Rights Act (the CCPA).
Categories collected. Finovo stores the financial records and account information you provide on your device. Google may process identifiers, internet or other electronic network activity, coarse location, product-interaction information, crash data, and other diagnostic data for advertising, analytics, and app functionality as described in §8.
"Sale" and "sharing." We do not sell your personal information for money and do not disclose the financial records you enter to advertisers. If you authorize tracking, AdMob and participating advertising partners may use identifiers or app-related activity for cross-context behavioral advertising; California law may define that disclosure as "sharing." You can opt out by denying or revoking ATT permission. Firebase Analytics and Crashlytics are used for analytics and app functionality; Analytics may also support advertising measurement or personalization as described in §8.2, but we do not use your financial records for ad targeting.
Your CCPA rights. You have the right to know, to delete, to correct, to opt out of sale/sharing, to limit the use of sensitive personal information, and to be free from retaliation for exercising these rights. To submit a request, email the address in §20; we will respond within the timeframes California law sets. Authorized agents may submit a request with proof of authorization.
17. Notice for users elsewhere
If you live in a jurisdiction not specifically named above — for example, Brazil (LGPD), Canada (PIPEDA), Australia (Privacy Act 1988), Japan (APPI), South Korea (PIPA), or others — many of the rights described in §15 and §16 have analogues in your local law. Because Finovo keeps your data on your device, the iOS-level controls in §14 are usually the most direct way to enforce them. For a written response, write to the email in §20.
18. Cross-border transfers
No international transfer of your financial records occurs through normal use of Finovo, because those records stay on your device and your private iCloud.
Advertising, analytics, and diagnostic data processed by Google (see §8) may be processed in countries other than yours; Google applies safeguards (such as standard contractual clauses) as required by law. If you email us, the content of that email passes through and is retained by the email service we use to read and reply to it.
19. Updates to this document
If we change this Privacy Policy, the "In effect from" date at the top will move. For material changes, we may also provide an in-app notice or request consent where applicable law requires it. Continued use of Finovo after a revised date is taken as acceptance of the revised text, except where local law requires explicit consent.
20. How to reach us
For any question, request, or report related to this Privacy Policy:
- Publisher: ZXApps (Ghayor Abbas)
- Email: zxapps1993@gmail.com
- Subject prefix that helps us route faster: "Privacy — Finovo —"
We do our best to reply within the timeframes required by applicable law and to answer in plain language.
If you ever find a behavior of Finovo that does not match a statement in this document, please tell us. We treat any such mismatch as a bug to fix, not a definition to broaden.