Privacy Policy – Finora Effective date: 24 September 2026 Last updated: 24 September 2026 Finora (“the App”) is an independent household-finance, bookkeeping, point-of-sale and inventory application developed and published by Zo Entertainment. Finora is designed to work locally on your device. You can use its core record-keeping features without creating an account. If you choose to sign in with Google, Finora can sync supported financial records through Firebase so that you can use the same account on more than one device. This Privacy Policy explains what information Finora stores, collects, transmits or shares, why it is used, and the choices available to you. 1. Information stored on your device Depending on the features you use, Finora may store information such as: household or business workspace names and settings; accounts, balances, transactions, categories, budgets, bills, expected income, savings goals and debt records; products, stock movements, sales, purchases, invoices, payment records, tax settings and reports; customer and supplier information that you enter, such as name, phone number, email address and address; staff or household member profiles, roles and access settings; notes, audit history and other records you create; app preferences, local security settings and PIN verification data; and attachment references and files that you choose to associate with records. Local Finora records generally remain on your device until you delete them, clear the App's storage, restore or replace the database, or uninstall the App. 2. Optional Google sign-in and Firebase cloud sync Google sign-in is optional. If you choose to sign in, Google Authentication / Firebase Authentication processes your Google account identity, including a Google user identifier and email address, so Finora can associate cloud data with your account. While you are signed in, Finora may sync supported app records through Google Firebase / Cloud Firestore. Synced records can include workspaces, accounts, categories, exchange rates, financial events, journal entries, budgets, products, inventory movements, customers and suppliers, sales, purchases, payment records, bills, expected income, savings goals, debts, tax and payment-method settings, audit records, roles and member access settings. Workspace member profiles can include salted PIN-verification hashes if you configure member PINs. Finora does not store the original member PIN in readable form. The separate App-level PIN and biometric preference remain device-local. Attachment files themselves are not included in Finora's cloud-sync snapshot and remain device-local unless you separately export, share or copy them. Finora uses Firebase as a service provider for authentication and cloud storage. Cloud data is associated with your Finora/Firebase user identity, not sold by Zo Entertainment, and is used to provide account and sync functionality. 3. Backups, import, export, printing and sharing Finora lets you choose files or destinations for backup, restore, import and export. Encrypted Finora backups use a password supplied by you and are written to the destination you select. CSV or other exported files remain wherever you choose to save or share them. When you explicitly print, export or share information, the destination app, service, printer or storage provider you select may receive that information under its own privacy practices. Zo Entertainment does not automatically receive a copy simply because you exported a file. 4. Advertising Finora is supported by advertising. The App uses Google Mobile Ads / AdMob and may use advertising mediation partners such as Meta Audience Network, InMobi and Mintegral when those partners are enabled for an ad request. Advertising SDKs may automatically collect or process information such as: IP address, which may be used to estimate an approximate location; app and advertisement interactions; diagnostic and performance information; device, app-set, advertising or similar identifiers; and information needed for advertising, analytics, measurement, security and fraud prevention. Finora does not send your transaction amounts, budgets, debts, customer records or other financial ledger values to advertising SDKs for ad targeting. 5. Advertising consent and privacy choices Finora uses Google's User Messaging Platform (UMP) to request and manage advertising consent or privacy choices where required. The App checks consent information before starting ad requests. Where Google's privacy-options entry point is required, Finora provides an in-app option to review or change advertising privacy choices. The exact advertising choices available can depend on your country or region, device, Google services, advertising partners and applicable law. 6. Barcode scanning Finora can use Google Code Scanner to scan product barcodes. The scanning UI is provided through Google Play services and does not require Finora to request the Android camera permission. Barcode image processing occurs on the device, and Google states that the scanner does not store the image data or scan result. The related Google ML Kit / Play services functionality may collect device or app information, per-installation identifiers, performance information, feature-event information and error metrics for diagnostics and usage analytics. 7. Biometric and PIN security If you enable biometric unlock, Finora uses the Android system biometric prompt. Finora does not receive or store your fingerprint, face image or raw biometric template. The App-level PIN is stored as a salted cryptographic verification hash rather than the original PIN. App-level PIN data remains on the device. Member PIN verification hashes may be included in optional cloud-synced member access settings as described above. 8. Data retention Local data remains until you delete it through the App where available, clear Finora's app data, replace the database through restore, or uninstall the App. User-created backups and exports remain in the locations where you saved them until you delete them there. When cloud sync is enabled, current and limited previous synchronization snapshots may be retained in Firebase to support synchronization and recovery. Finora also keeps a local recovery copy in some conflict-resolution situations. Third-party services may retain data according to their own policies and legal obligations. 9. Account and cloud-data deletion If you create a Finora cloud account by signing in with Google, you can delete the Finora login account and its associated Finora cloud records from within the App. This does not delete your Google account. In-app path: open Finora → Google account & sync → Delete cloud account & data → confirm and re-authenticate with the same Google account. This process deletes the Finora Firebase login account, Finora cloud synchronization data and this device's database associated with that signed-in account. Separate offline databases, copies on other devices and files that you exported or backed up may still exist and must be deleted separately. You can also use the external account-deletion resource at https://mapuia12.github.io/delete-finora/. 10. Data security Finora uses reasonable technical safeguards designed for the features described above. Network communications with Google/Firebase and advertising services use transport security provided by those services. User-created Finora backup files are encrypted with password-based key derivation and authenticated encryption. No method of electronic storage or transmission can be guaranteed to be completely secure. You are responsible for protecting your device, Google account and exported backup files. 11. Third-party services Finora may use the following third-party services depending on the features and advertising configuration enabled in the release: Google Firebase Authentication and Cloud Firestore – optional sign-in and cloud synchronization; Google Mobile Ads / AdMob – advertising, measurement, analytics and fraud prevention; Google User Messaging Platform – advertising privacy and consent management; Google Code Scanner / ML Kit / Google Play services – barcode scanning and related diagnostics; Meta Audience Network – advertising mediation where enabled; InMobi – advertising mediation where enabled; and Mintegral – advertising mediation where enabled. Those providers process information under their own privacy policies, contractual terms and legal obligations. 12. Children and intended audience Finora is intended for adults managing household or business financial records and is not designed primarily for children. Zo Entertainment does not knowingly design Finora to solicit financial records or advertising profiles from children. 13. International processing Google, Firebase and advertising providers may operate infrastructure and service providers in multiple countries. Information processed by those providers may therefore be processed outside your country, subject to their privacy safeguards and applicable law. 14. Changes to this Privacy Policy We may update this Privacy Policy when Finora's features, SDKs, cloud services, advertising partners, legal requirements or data practices change. The “Last updated” date will be revised when the policy changes. 15. Contact us For privacy questions, account-deletion requests or other data-related requests, contact: Developer/Publisher: Zo Entertainment App: Finora Email: lallianpuia@gmail.com Important: This policy must stay consistent with the exact SDKs and features in the production AAB. If an advertising mediation partner is removed or added, or cloud behavior changes, update this policy and the Play Console Data safety declaration.