Privacy and data safety
Everything you make in Bilva stays on your phone. There is no account, no server holding your work, and no copy of your invoices anywhere but the device in your pocket.
Last updated 25 October 2026
In plain terms
Your invoices stay on your phone
Every invoice, estimate, client, item and payment you enter is stored in the app on your device. None of it is uploaded. Nobody — including me — can read it. If you send a document to a customer, you are the one sending it, through whatever app you choose.
There is no account
No email address, no password, no profile. There is nothing to log in to, so there is no account of yours to leak, sell or hand over.
Contacts are copied, never uploaded
If you pick a customer from your phone’s contacts, the app copies that person’s details into the invoice and stops there. Your contact list is not read in bulk, not stored elsewhere, and not sent anywhere. Say no to the contacts permission and everything still works — you type the name instead.
What is counted
Bilva sends nine anonymous counts of its own, and no others, so I can tell whether the app works: how long it took to send a first document, where people give up on a first invoice, roughly how many documents a phone makes in a month, and whether anyone buys Pro. Numbers are put into buckets before they leave the phone — “7 to 10 invoices”, never “9”. Google Analytics also records its standard ones, such as a session starting and a screen being viewed, none of which carries anything you typed.
Nothing you type can reach a count. There is no code in the app that can attach free text to one, so a client name, a business name, an address, an amount or a document number cannot end up in a count even by mistake. The full list is below.
Advertising is switched off
No ads, no ad identifier, no attribution or install tracking. The permissions that would allow them are removed from the app before it is built, and the build is checked to confirm they are gone. Nothing about you is used to target anything.
Crashes
If the app crashes it reports the crash, the Android version, the device details Crashlytics attaches to a crash and a rough device class, so it can be fixed. No document contents are included.
Deleting everything
Uninstalling the app removes your records from the phone. There is no server copy of your work to delete, because there was never a copy anywhere else. For the purchase record RevenueCat holds, write to support@bilva.app. If you use Pro’s encrypted backup, delete the backup file the same way you would any other file.
Every count Bilva sends of its own
Bilva sends nine events of its own, and no others; Google Analytics also records its standard ones, such as a session starting and a screen being viewed, none of which carries anything you typed. Every value in Bilva’s nine is one of a fixed set of strings; there is no field anywhere that accepts typed text.
| Count | What it can contain |
|---|---|
| first_pdf_shared | How long since first launch, as one of six buckets: under 1 min, 1–5 min, 5–30 min, under 1 day, under 1 week, over 1 week. |
| first_invoice_reached | Which step of a first invoice was reached, as one of seven: opened, business name, business address, customer, first item, previewed, shared. |
| monthly_documents | Invoices and estimates made in the month that ended, each as one of eight buckets: 0, 1, 2–3, 4–6, 7–10, 11–20, 21–50, 51 or more. |
| estimate_issued | Nothing. The count has no detail attached. |
| estimate_converted | Nothing. |
| paywall_viewed | Which entry point opened the Pro screen, as one of nine: the menu, or one of the eight Pro features. |
| pro_purchased | Nothing. |
| first_pro_feature_used | Which of the eight Pro features was opened first: multiple businesses, client signature, deposits, custom templates, encrypted backup, payment reminders, reports, recurring invoices. |
| document_shared | Which of the three share buttons you pressed: WhatsApp, email or other. Never which app answered, so nothing about the apps installed on your phone is reported. |
The formal detail
The same facts, in the form a data protection officer or an app store reviewer will look for.
Who is responsible
BillionEdges is a sole proprietorship of Maneesh Kumar. It is the controller for the anonymous usage and crash data described here, and for the subscription record RevenueCat holds. Contact: support@bilva.app.
BillionEdgesA2603, Opposite Metro University, Sport City 1, Plot No GH-04,
Atul Marg, Bisrakh Jalalpur, Greater Noida,
Noida - 201318, India
Data collected, and why
- App activity, anonymous and bucketed. The nine events above, sent through Google Analytics for Firebase. Purpose: analytics — understanding whether the app works. No user id and no user property is set, so events are not tied to an identity.
- Approximate location. Google Analytics for Firebase derives an approximate area, such as the country or region, from the network address the events above arrive from. Bilva never asks for location permission and never reads the device’s location. Purpose: analytics.
- Crash logs and diagnostics. Stack traces with the OS version, the device details Crashlytics attaches to a crash, and the device tier, through Firebase Crashlytics. Purpose: analytics — finding and fixing faults.
- Purchase state. Google Play billing takes the payment when you buy or cancel Pro, and RevenueCat tells Bilva whether the subscription is active, using a random identifier it creates for the installation. Google Analytics for Firebase also records the purchase event, with the product and its price. Bilva never sees a card number or your Google account details. Purpose: app functionality; analytics for the purchase event.
- Not collected. No name, email address, phone number, postal address, contact list, precise location, photo, file or financial record leaves the device, and Bilva never asks for location permission. Documents, clients, items and payments are stored only on the device and are never transmitted.
Data sharing
No data is sold and none is shared with third parties for advertising. Google acts as a processor for analytics, crash reporting and billing, and RevenueCat for the subscription status. Consent flags in the app deny ad storage and ad user data; the advertising identifier, attribution and install-referrer permissions are removed from the shipped build.
Legal basis and transfers
Where the UK GDPR or EU GDPR applies, the anonymous usage and crash data is processed on the basis of legitimate interests in keeping the app working, and it is not used to identify anyone. The subscription record is processed to perform the agreement you enter when you buy Pro. Analytics and crash data sits on Google’s infrastructure; the subscription record sits on RevenueCat’s, in the United States. Both may be outside your country, and both are governed by those companies’ terms for those services.
Retention and deletion
Your records live on your device for as long as the app is installed and are removed when you uninstall it or clear the app’s data. Analytics and crash data is retained by Google under the default retention period for those products and cannot be traced back to a person. Because no account exists, there is no personal record for me to look up or export. For the purchase record RevenueCat holds, write to support@bilva.app and it will be deleted; any other question is answered at the same address.
Children
Bilva is a tool for running a business and is not directed at children.
This website
bilva.app sets no cookies, runs no analytics and embeds nothing from anyone else. Every page here is plain HTML and CSS served from one place, which is why you are not being asked to accept anything.
Changes
If this policy changes, the date at the top changes with it. A change that widens what is collected will be described here in plain terms, not folded quietly into a paragraph.