Infinion
Infinion Solutions Innovate. Integrate. Inspire.
About Products Services Contact Get in touch
About Products Services Contact Get in touch

Legal

Android Privacy Policy

This Privacy Policy applies to the Android applications published by Infinion Solutions. It is the policy to use in Google Play for those apps.

Last updated 18 August 2026

Android Privacy Terms & Conditions Cookie Policy Company information

On this page

Who we are Which apps What the apps process App-by-app Permissions How we use information Storage and retention Sharing Third-party services Security Your rights Children Changes Contact

1. Who we are

This Privacy Policy is issued by Infinion Solutions (“Infinion”, “we”, “us”), an India-based software studio and the developer of the Android applications listed below.

GSTIN: BEWPJ9978R1ZP
Country of operation: India
Contact: hello@infinionsys.com

This page is only for our Android applications. It is not the privacy notice for the infinionsys.com marketing website or contact form. Those are described on the Cookie Policy and Company information pages.

2. Which Android applications this covers

This policy applies to the following Infinion Android applications, including updates published on Google Play:

  • Billora — com.infinion.billora
  • Calcify — com.calcify.app
  • LocalConverter — com.localconverter.app
  • LocalLedger — com.localledger.app
  • Scanora — com.scanora.app
  • ZaykaBill (Android client of the restaurant product)

We do not invent collection we do not perform. Where a feature is optional, user-initiated, or only present in some builds, we say so. The Play Store listing and the permissions screen on your device are the live source for a given installed version.

3. What the Android apps process

Billora, Calcify, LocalConverter, LocalLedger, and Scanora are built as offline-first products. Content you create in the app (invoices, calculations, conversions, expenses, scan history) is stored in a local database on the device by default. We do not operate a general-purpose Infinion cloud that stores that content for every user.

3.1 Categories of information

  • Content you create. Invoices, clients, calculations, files you convert, expense records, receipts you attach, scan and generate history, and settings.
  • Account information (where Sign-In is used). Google may provide email, display name, profile photo URL, and an account identifier. These are stored locally for the session and, where relevant, to bind backups to the same Google account.
  • Device information. The operating system needs standard access for the feature you invoked (camera, files you pick, network). We do not run a separate Infinion device-fingerprinting programme.
  • Usage related to ads (in ad-supported builds). Google AdMob may process advertising identifiers and standard ad signals under Google’s policies. Core tools are designed to keep working if ads cannot load.
  • Diagnostics (only if you enable or send them). Some apps keep crash notes on the device until you choose to share them. Scanora production builds may send technical error reports to a crash service if we have configured one for that build. Those reports are for app stability, not for selling a profile of you.

4. App-by-app practices

4.1 Billora (com.infinion.billora)

Private invoice studio. Invoice, client, product, payment, and business-profile data stay on the device unless you export or back them up.

  • Google Sign-In identifies which Google account owns local data.
  • Optional Google Drive backup uses Drive appDataFolder only (not full Drive). Restores are designed for the same Google account.
  • Optional Browser Access runs a local server on your LAN so a browser on the same network can work with invoices. Traffic is not relayed through Infinion servers. Use it only on networks you trust.
  • Crash reporting is off by default. “Send diagnostics” shares a report only if you do.
  • Ads may appear in some builds. Testing builds may ship with ads disabled.
  • Biometrics (optional lock) stay in the device OS. Billora receives success or failure only.

4.2 Calcify (com.calcify.app)

Offline calculator toolkit (percentage, loan/EMI, currency, units). History stays on the device.

  • Google Sign-In gates access; calculation history is not uploaded to an Infinion backend.
  • Currency “Update Rates” fetches public rates from frankfurter.app when you tap update. Conversion still works offline on cached or embedded rates.
  • Google AdMob may show banner or interstitial ads when a network is available.

4.3 LocalConverter (com.localconverter.app)

On-device conversion of PDF, image, and document files you select. Files are processed on the device through the Storage Access Framework; the app is not designed to upload those files to Infinion.

  • Internet is used for ads (AdMob) and, if configured, Google Sign-In.
  • We do not request broad storage of your whole gallery or disk.

4.4 LocalLedger (com.localledger.app)

Offline expense and budget tracker. Financial records stay on the device unless you export or back them up.

  • Google Sign-In and optional Google Drive appData backups (same-account restore).
  • Camera / photos only if you attach a receipt.
  • Local notifications for budget thresholds you configure.
  • Optional biometric lock.
  • AdMob on the free, ads-supported build.

4.5 Scanora (com.scanora.app)

QR and barcode scanner and generator. History stays in a local database.

  • Camera is used while the scanner screen is open.
  • Photos / gallery to scan an image you pick or to save a generated code if you choose.
  • Google Sign-In gates access; scan history is not uploaded to an Infinion scan-history server.
  • AdMob for the free app. Scan and generate work offline; ads need a network.
  • A production build may send technical crash details (message, stack, app version, OS) to a crash service if we have configured one. That reporter is not designed to include your full history content.

4.6 ZaykaBill Android app

ZaykaBill is a restaurant operations product (billing, menus, kitchen tickets, and related workflows). The Android app is a client of that product. If you or your restaurant create an account or enter operational data, that data is processed to run the product for that restaurant. We do not treat restaurant POS records as public marketing data. Restaurant operators should limit staff access with the roles the product provides. In-product notices for a specific restaurant deployment apply in addition to this page.

5. Android permissions

Apps request only what a feature needs. Typical permissions in our current apps include:

  • Internet / network state — sign-in, Drive backup, optional ads, currency-rate update (Calcify).
  • Camera — Scanora scanning; LocalLedger receipt capture.
  • Photos / media / Storage Access Framework — logos, receipts, files you convert, saving generated codes.
  • Biometric / fingerprint — optional app lock (Billora, LocalLedger).
  • Notifications — LocalLedger budget alerts.
  • Wi-Fi / local network — Billora Browser Access status.

The Play Store listing and Android settings show the exact set for the version you installed.

6. How information is used

  • To provide the Android app feature you asked for (calculate, convert, invoice, scan, track expenses, or run a restaurant workflow).
  • To authenticate you with Google when an app uses Sign-In.
  • To store a backup you requested in your own Google Drive app data folder.
  • To show ads in ad-supported builds, through Google.
  • To investigate a crash if you enable reporting or send diagnostics.

We do not sell personal information. We do not use app content to train public AI models.

7. Data storage and retention

  • On-device app content remains on your device until you delete it, clear app data, or uninstall.
  • Optional Drive backups remain in your Google account until you delete them.
  • ZaykaBill restaurant data is retained to operate the restaurant’s account, as controlled by that restaurant’s operator and any in-product settings.

8. Data sharing

We share Android-app information only in these cases:

  • Google — Sign-In, optional Drive appData backups, AdMob (ad-supported apps), and Play services that the OS uses to install the app.
  • frankfurter.app — Calcify rate updates you request.
  • A crash service — only if configured for that build (Scanora) or if you send a diagnostics file yourself.
  • Someone you choose — when you share a PDF, CSV, image, or backup through Android’s share sheet.
  • Devices on your LAN — only if you turn on Billora Browser Access.
  • Law — if we are legally required to disclose information we actually hold.

9. Third-party services used by the apps

Depending on the app and build, the following third parties may process data under their own terms:

  • Google Privacy Policy (Sign-In, Drive app data, AdMob, Play services).
  • Google advertising technologies for AdMob-supported apps.
  • frankfurter.app when Calcify updates currency rates.

10. Security

Google Sign-In and Drive traffic use HTTPS. Several of our Android apps use on-device measures such as local storage, optional biometric lock, and release hardening (for example backup disabled at the OS level in some manifests). No method is perfect. Keep the device locked, use Sign-In only on your own account, and avoid Billora Browser Access on public Wi-Fi.

11. Your rights and deletion

Depending on applicable law (including Indian IT rules and, if they apply to you, other privacy laws), you may ask us to access, correct, or delete personal data we hold.

  • For on-device app content, delete items in the app, clear app storage, or uninstall. That removes data stored on the device.
  • Revoke Google access in your Google Account. Delete Drive app-data backups from the in-app backup screen or Google’s account tools.
  • Reset or limit your advertising ID in Android settings if you use an ad-supported build.
  • For ZaykaBill restaurant accounts, ask the restaurant operator or email hello@infinionsys.com and name the restaurant and app.

We will need enough information to find a record we actually hold. We may refuse a request that we cannot verify or that the law does not require.

12. Children’s privacy

These Android applications are directed at businesses and general users, not at children under 13 (or the higher age required in your country). If you believe an app has received a child’s personal information on our systems, contact us and we will delete what we hold.

13. Changes to this policy

We will update this page when the Android apps or our legal duties change. The “Last updated” date at the top will change when we do. Continued use of an app after an update means you should read the new text.

14. Contact

For privacy questions about an Infinion Android app, email us and name the app (and package name if you know it).

Infinion Solutions
GSTIN: BEWPJ9978R1ZP
India
hello@infinionsys.com

See also Terms & Conditions, Cookie Policy, and Company information.

Infinion Solutions
Innovate. Integrate. Inspire.
© 2026 All rights reserved
Home Contact Android Privacy Terms Cookies Company hello@infinionsys.com