Privacy Policy

Last updated: October 13, 2026

LiveBill ("we", "us") is a mobile app developed by InnoVision Labs that lets sellers share a live view of a bill with customers as it is being created. This policy describes what information the app collects, how it is used, and your choices.

Information we collect

LiveBill supports two ways to sign in, and what we collect depends on which one you use:

Google Sign-In: We receive and store basic account information from your Google profile — your display name and email address. Google also provides a profile photo URL, which LiveBill deliberately does not store: nothing in the app displays it, so it is discarded at sign-in rather than saved. Google accounts are already verified, so no further check is done.
Email and password: We store the email address and display name you provide when creating an account. Your password is handled entirely by Firebase Authentication — LiveBill never sees, stores, or has access to it in plain text. Firebase Authentication sends a one-time verification email to the address you provide, and the app requires that link to be confirmed before the account can be used, to help prevent sign-ups using an email address you don't own.

Either way, before you can sign in or create an account you confirm that you are 18 or older and agree to our Terms of Service and this policy (an account created before that confirmation existed is asked once, the next time the app opens). We record when you confirmed, and the date of the version of these pages you agreed to.

Sellers add shop details to their profile:

Shop name — required before a seller can start a sale, since it identifies them on every bill and receipt their customers see
Address (optional)
Phone number (optional)

When you use LiveBill, the app stores bill and invoice data in Firebase Cloud Firestore, including:

Bill session details (shop name, address, phone, currency, line items, discounts, status, timestamps)
A short numeric PIN used to share a live bill with a customer, and a separate short confirmation code exchanged between seller and customer to complete the join (discarded once the join is confirmed or declined)
Which customer joined a bill (linked to their account ID, once the seller confirms the join)
Completed sale records (invoices) created when a seller marks a bill as paid, with a note of whether each party has removed it from their own history

LiveBill does not collect payment card numbers or process payments inside the app.

To set a bill's currency, the country code of a seller's phone number and which units are listed first, the app reads the country of the seller's SIM card — or, without one, of the mobile network the phone is connected to — on the device itself. This needs no permission, and the country itself is neither uploaded nor stored: what is saved is the currency, as part of each bill, and the country code, as part of the phone number if the seller adds one. If the phone can report neither, the seller chooses a currency's country instead; until they do, the region in the phone's language setting is used to suggest the country code and units.

The app also generates a random device identifier (not derived from any hardware ID) the first time it's installed, and stores it locally on your device and against your account, together with the time that device last signed in. This is used only to enforce one signed-in device per account at a time — see "Single active device" below.

Alongside your profile, LiveBill stores a small amount of operational data against your account. None of it identifies you beyond the account it belongs to, and none of it is shared with advertisers:

Usage counters used for abuse limits: running counts, with the hour or month they apply to, of how many bills you've created, item changes you've made, PINs you've tried, and sales you've cancelled, plus a count of the database reads and writes your usage caused in the current hour and of the writes it caused in the current calendar month. These enforce fair-use limits that stop automated PIN guessing and protect the service from overload. They are counts only — not a log of what you did.
Ad-frequency data: for the current hour, an estimate of the server cost your usage has caused and an estimate of the ad revenue credited back against it; and a running balance of the cost from earlier hours that their ads did not cover, with a flag recording whether that balance currently calls for an ad. These figures decide when the ads described under "Advertising" are shown or skipped, and when the optional rewarded ad is offered; they never stop you starting or joining a sale. The hourly estimates start again each hour; the running balance goes up when an hour's ads fall short, down when an hour's ads more than cover its cost, and is cleared when you choose to watch the optional rewarded ad to the end. The revenue estimate uses the value Google AdMob reports to the app for each ad shown to you, where it reports one, and a fixed conservative estimate where it does not. All of these are internal estimates in fractions of a US cent and are never sent to AdMob or any advertiser. An account used with an earlier version of the app may also still hold a few records that version kept and this one no longer uses or updates: monthly counts of taps on Start New Bill, View Live Bill and Save as PDF; counts of repeated wrong PINs and abandoned sales, with any lockout they caused; the month an upgrade notice was last shown; and whether the full-screen ad after its last completed purchase was watched. They are deleted with the account.

Some things are kept only on your own device and are never uploaded: the payment QR code a seller saves, the role you last used (so the app can open straight on it), the country a seller chooses for their currency on a phone that can't report its own, your display preferences, when a full-screen ad was last shown (for the ten-minute gap described under "Advertising"), and whether you've seen the tip on closing an ad that seems stuck. The app also keeps cached copies of some data already held in your account — your recent invoices, today's sales or purchase totals, and the fact that you've confirmed your age — so it opens quickly. Uninstalling the app or clearing its data removes all of them.

How we use information

To authenticate you and keep you signed in
To sync live bills between seller and customer devices
To show purchase and sales history from completed invoices
To protect backend access using Firebase App Check (Play Integrity on Android release builds)
To diagnose crashes and errors using Firebase Crashlytics (see "Crash and error reporting" below)
To show ads that support the free app using Google AdMob (see "Advertising" below)
To apply fair-use limits and decide how often ads are shown, using the operational data described above

Single active device

For security, an account can only be signed in on one device at a time. If you sign in on a new device, the previous device is automatically signed out — unless that device is in the middle of a sale, in which case the new sign-in is refused until the sale is finished, so signing in elsewhere never cuts a sale off mid-way. This is enforced using the locally-generated device identifier described above — it is not a hardware identifier and is not used for advertising or tracking.

Crash and error reporting

LiveBill uses Firebase Crashlytics to automatically collect crash reports and error logs when something goes wrong — for example, device model, OS version, app version, and the code path that failed. This helps us find and fix bugs. This data is processed by Google Firebase under its own privacy policy.

Advertising

LiveBill is free to use and shows ads served through Google AdMob (part of Google Mobile Ads). Ads take three forms: a banner strip along the bottom of most screens, occasional full-screen ads, and — rarely — an optional rewarded ad you can choose to watch (see below). Banners never appear on a live bill, and no full-screen ad ever appears while a bill is being built or during checkout, for either party.

Where full-screen ads appear depends on your role, and the two are deliberately different:

After a completed purchase, for the customer: the receipt appears first, and one is shown as the customer leaves it — never in front of it.
For the seller, only while the account owes something: the app keeps an hourly tally of the estimated server cost an account causes against what its ads have earned in the same hour. If that hour's ad income has already covered the cost several times over, and nothing is left uncovered from earlier hours, the seller's post-sale ad is skipped entirely. When it does show, it's as the seller leaves the Payment Received screen.
As a seller: also when choosing your role, returning to the dashboard (never as the app opens on it), or after saving an invoice from your sales history as a PDF — but only while the account's usage in the current hour, or an earlier hour that fell short, has not yet been covered by its ads. No full-screen ad is shown while a bill is being built or at checkout, and cancelling a sale does not show one, though the dashboard the seller returns to afterwards can, on the same basis. Saving a receipt as a PDF straight after a sale never shows one.
As a customer: also occasionally after saving an invoice from your purchase history as a PDF, on the same usage-not-yet-covered basis. No ad is shown unasked for joining a sale, entering an incorrect PIN, or cancelling.

Apart from the post-sale one, these full-screen ads are shown only while an account's usage has not yet been covered by its ads — usage counts as covered once its ads have earned several times what it cost — and never more than one every ten minutes. There is no daily limit. This is decided on your device from the time elapsed since the last ad and the account's hourly tally; the cost and revenue figures described under "Information we collect" are recorded against your account only and are not shared with AdMob or any advertiser.

Rewarded ads

A rewarded ad is different from the ads above in two important ways: it is never shown to you unasked, and it is always optional. If an account has used more of the service than its ads have covered, tapping the button that starts a new bill (for a seller) or joins one (for a customer) first offers you a short ad, with two choices: Watch ad or No thanks. The reward is the one the offer states: watch the ad to the end and what the account owes is cleared, so the full-screen ads above that appear only while an account owes something stop until it builds up again. Small uncovered usage adds up across hours, and the offer is made once it reaches a limit; hours whose ads more than cover their cost pay that balance back down.

Declining never stops a sale. Choosing No thanks, closing the ad before it ends, or no ad being available all start the sale — or let you join — straight away; the reward is granted only for an ad watched to the end. The offer is made at most once per tap, and never during a sale. The figures it is measured against are the cost, revenue and running balance described under "Information we collect": they are held against your account only, and none of it is shared with AdMob or any advertiser.

Separately, there is an upper limit on how much of the service a single account can use in a calendar month. It is set far above what any ordinary use of the app reaches, and exists only to stop a single account running up unbounded costs.

AdMob may collect and use device and usage information — such as your Google Advertising ID (GAID), general device information, and app interaction data — to serve and measure ads, as described in Google's Privacy Policy and Google's Partner Sites policy. Ads may be personalized using your advertising ID; you can stop that at any time in Android's Settings → Privacy → Ads ("Delete advertising ID" or "Opt out of Ads Personalization"). LiveBill is not currently offered in the EEA, the UK or Switzerland; before it is, it will ask for consent for ads where the law requires it.

U.S. State Privacy Disclosures

Depending on your U.S. state of residence, you may have specific rights regarding your personal information. Over the past 12 months, we have collected the following categories of information as defined by applicable state laws:

Identifiers — name, email address, Google profile details, and the app-generated device identifier described above.
Commercial information — bill line items, shop details, and invoice history.
Internet or other electronic network activity information — app interaction data, the usage counters and ad-frequency data described above, and crash diagnostics.

We do not sell your personal information, and we receive no money for any disclosure of it. Ads in LiveBill are served by Google AdMob: where personalized ads are enabled, that use of your Google Advertising ID may qualify as sharing for cross-context behavioral advertising (also called "targeted advertising") under some state privacy frameworks. You can opt out at any time, on any Android device, via Settings → Privacy → Ads — "Delete advertising ID" or "Opt out of Ads Personalization" — which we and AdMob honor. We honor applicable opt-out preference signals where required by law, and we do not knowingly process the personal information of anyone under 18 for advertising.

Subject to your state's law, you may have the right to know what personal information we hold, to request its deletion or correction, to opt out of targeted advertising, and not to be discriminated against for exercising those rights. Deleting your account from the app menu exercises the deletion right directly and immediately (see "Data retention and deletion" below); for anything else, contact us at the address at the bottom of this page and we will respond within the timeframe your state's law requires.

How information is shared

Between users: When a seller shares a bill PIN, the customer who joins can see that bill's shop details and line items in real time. When a sale is completed, both parties can see the resulting invoice in their history.
Service providers: We use Google Firebase (Authentication, Cloud Firestore, App Check, Crashlytics) to operate the app, including Google Sign-In for users who choose that sign-in method, and Google AdMob (Google Mobile Ads) to show ads. These providers process data on our behalf, or as independent controllers for advertising purposes, under their own terms and privacy policies.
We do not sell your personal information.

Data retention and deletion

A bill that is still being built is cancelled automatically after 10 minutes without activity, and no sale can run longer than an hour. A bill's live record — finished or not — is then deleted automatically: a cancelled bill typically within a day of being cancelled, and any other typically within two days of being opened or reaching checkout (or sooner, if a new bill reuses its PIN and overwrites it). A sale completed with an earlier version of the app keeps its live record until its PIN is reused.
Each completed sale creates an invoice that appears in the history of the seller and, if one joined, the customer. Each of you keeps an invoice in your history while it is among your 10 most recent completed invoices. Older ones leave your history automatically — including earlier sales from the same day, so a dashboard's "Today" totals count only the sales still in its history.
You can also delete invoices from your own history at any time. Deleting removes an invoice from your history only — the other party keeps their copy, since neither side can erase the other's record of a sale that happened. An invoice is deleted from our database once it is in neither party's history; an account that has been deleted counts as having none. This is carried out by the app on each party's own phone the next time it updates that history (after a sale, or when the dashboard opens), so an invoice can outlast its place in the last 10 until then.
While an invoice exists it keeps a copy of the seller's shop name, address, and phone number as they stood at the time of sale, plus the account identifiers of both parties — so a seller's shop details remain visible on an invoice still in a customer's history even after that seller deletes their account. See Account Deletion for the full detail.
You can delete your account from the app menu, unless you currently have a bill open or in checkout — finish or leave that sale first, then delete. Deletion removes your user profile — including the shop details, usage counters, ad-frequency data and age confirmation described above — removes every invoice from your history (deleting outright those the other party no longer has), and signs you out. Invoices still in the other party's history stay there for them, under the rules above.

Age restrictions

LiveBill is intended for use by adults aged 18 and older. It is not directed at children, and we do not knowingly collect personal information from anyone under 18. Before you can sign in or create an account, you confirm that you are 18 or older (see "Information we collect"); the app can't be used without that confirmation. If we learn that we have inadvertently collected information from a minor, we will delete it promptly — if you believe a minor has provided us information, contact us at the address below.

Where your information is stored

LiveBill is operated from India by InnoVision Labs. The bills, invoices and account profiles LiveBill stores are held in Google Cloud Firestore in Mumbai, India (the asia-south1 region). Sign-in (Firebase Authentication), crash reporting (Firebase Crashlytics), App Check and ads (Google AdMob) are services run by Google, which may process data on servers outside India under Google's own terms and privacy policy.

Your rights

Whoever you are, you can:

Access the personal information we hold about you — email us and we will send you a summary.
Correct it: your shop details can be changed in the app at any time (☰ → Seller Settings); for anything else, email us.
Delete it: delete your account from the app menu, delete sales or purchases from your own history on the dashboard, or email us (see Account Deletion).
Withdraw your consent to our processing of your information, by deleting your account or emailing us. This doesn't undo processing done before you withdrew, and invoices still in the other party's history stay there for them, as described above.
Nominate someone to exercise these rights on your behalf if you die or become unable to — email us with their name and contact details.
Raise a grievance about how we handle your information, with our grievance contact below. We respond to every grievance within one month of receiving it.
Complain to a regulator: if you're not satisfied with our response, and where the law provides for it, you can complain to the Data Protection Board of India — or, if you live outside India, to the data protection authority where you live.

Changes

We may update this policy from time to time. The "Last updated" date at the top will change when we do.

Contact

Questions about this policy: creativesath@innovision-labs.com

Grievances and requests about your information: InnoVision Labs, creativesath@innovision-labs.com. We respond within one month of receiving a grievance.