Privacy Policy — billzloop


The short version

billzloop has no server. There is no account, no sign-up, and no backend. Your bills, customers, payments and expenses are stored on your phone and stay there unless you deliberately export or back them up yourself.

We cannot see your business data. Not because we promise not to look, but because it never reaches us. There is nowhere for it to go.

The only personal data that ever reaches us is what you type into an email if you choose to contact support.


1. Who is responsible for your data

billzloop is published by onezloop, a name used by techRSR, the developer of billzloop on Google Play. "We" and "us" in this policy mean techRSR.

Contact for privacy questions, data requests and grievances: contact@onezloop.com

That address is the grievance channel for the purposes of §13 of India's Digital Personal Data Protection Act, 2023.

We act as a Data Fiduciary under that Act only in respect of the support correspondence described in section 4. For everything the app stores on your phone, see section 6 — you are the Data Fiduciary there, not us.

Because there is no server and no account, we hold no record of you at all unless you write to us first.


2. What the app stores on your phone

All of the following is written to a database file on your device and to your app's private storage. None of it is transmitted to us at any time.

Contacts

The app asks for contacts permission only when you tap "Choose from Contacts", and only ever reads contacts to show you a list to pick from. Only the entries you tick are saved, and only their name and first phone number. You can decline the permission and use every part of the app; customers can always be added by hand instead.

We never upload your contacts. Nothing is read in the background.


3. What the app never does

  • No analytics, and no telemetry of our own. No usage tracking, no event logging to us or to any analytics service, no advertising or marketing identifiers. No analytics SDK is present in the app at all. The one kind of logging we cannot remove is Google's own, inside the Google Play Billing library — see section 5.2.
  • No crash reporting to us. Diagnostic information is kept in memory on your device and is only ever sent if you choose to email it (section 4).
  • No advertising. There is no ad network in the app and no data is sold, rented, or shared with any data broker.
  • Nothing of yours is uploaded on its own. The app's only network use is the two things in section 5: Google Drive backup, which runs only once you switch it on, and Google Play Billing, which checks your purchase each time the app starts. Neither carries your bills, customers or spends.
  • No Android cloud backup. The app opts out of Android Auto Backup and the Android device-transfer flow entirely, so your ledger is never copied off the phone by the operating system.
  • No profiling or automated decision-making. Nothing in the app scores, ranks, or makes a decision about any person.

4. The only personal data we receive: support email

If you use Settings → Share Diagnostics or email contact@onezloop.com, your own email app sends us a message. You see the full contents and press Send yourself; the app never sends anything on its own and cannot send it in the background.

What a diagnostics email contains: the app version and build number, your device model and Android version, and a log of recent app events and error types. The log is deliberately filtered before it is ever shown to you: it excludes customer names, phone numbers, business names and amounts, and it discards the message text of any error raised by third-party code rather than risk that text carrying your data.

If you ask for a GST tax invoice, your email carries your Google Play order ID, your GSTIN and your business's legal name. We use them only to issue the invoice.

What we do with it: read it to answer your question, fix the bug, or issue the invoice you asked for. Nothing else. It is not used for marketing, not shared with anyone, and not combined with any other data.

Legal basis: you provide it voluntarily for the specified purpose of getting support (DPDP Act 2023, §7(a)).

Retention: support correspondence is kept while your issue is open and for up to 24 months afterwards so we can recognise a recurring bug, then deleted. Ask us at contact@onezloop.com to delete it sooner and we will. Invoice requests and the invoices we issue are the exception: GST law (CGST Act §36) requires us to keep tax records for 72 months, so those are kept for that long.


5. The two things that use the internet

The app declares the INTERNET permission for exactly these, and nothing else. Billing, the ledger, the catalogue, reports, PDF export and .billz import all work with the phone in airplane mode.

5.1 Google Drive backup — optional, off by default

If you switch it on, the app uploads an encrypted backup to your own Google Drive.

  • The scope requested is drive.appdata only. billzloop cannot see, list, or touch anything else in your Drive. The permission does not allow it.
  • The file goes into appDataFolder, a hidden area of your Drive that does not appear in the Drive interface and that no other app can read.
  • What is uploaded is encrypted before it leaves the phone with AES-256-GCM, under a passphrase you choose. Google stores ciphertext it cannot read.
  • Nothing escrows your passphrase. The app remembers it on this phone, in Android Keystore-backed storage, so backups run without asking — but it never leaves the phone. If you lose it and the phone, the backup cannot be recovered — by you, by Google, or by us. That is exactly what makes the previous line true.
  • Connecting Drive means signing in through Google's own sign-in screen. The app shows which Google account is connected, but does not save that address and never sends it to us.

Google's handling of the file, and of the sign-in, is governed by Google's own privacy policy.

5.2 Google Play Billing

Used to buy the billzloop Lifetime unlock, and to check whether you already own it.

  • The check runs by itself each time the app starts, without asking. That is what brings Lifetime back after a reinstall or on a new phone without you doing anything. With no internet it simply fails and nothing changes: the app keeps working, and an unlock you already have stays unlocked.
  • We sell Lifetime; Google Play processes the payment, and we receive confirmation that a purchase happened. We never see your card, UPI ID, or any payment detail.
  • Google's own logging. The Play Billing library is code Google supplies, and it sends Google its own diagnostic logs. Google describes them as insight into how billing requests went (such as whether they succeeded or failed) and problems connecting to Google Play. Those logs go to Google, not to us. We cannot read them, and we cannot switch them off without removing the ability to buy.

Google's handling of all of this is governed by Google's own privacy policy.

5.3 Two things that look like network use but are not

  • Remind hands WhatsApp a wa.me link with a message already written. Your WhatsApp sends the message. billzloop makes no network call, learns nothing about delivery, and never contacts anyone on its own.
  • Share Diagnostics hands your mail app a mailto: link. Your mail app sends it, after you read it and press Send.

In both cases the app needs a manifest <queries> entry so Android will reveal that a handler exists. That grants visibility, not the ability to send anything.


6. Your customers' data, and your responsibility

When you store a customer's name, phone number or address in billzloop, you are the Data Fiduciary for that person's data under the DPDP Act, 2023 — not us. We never receive it and cannot act on it.

That means the duties are yours: to tell your customers what you hold and why, to have a basis for holding it, to keep it secure, and to respond if they ask about it. The app is built to help rather than hinder you:

  • The database is encrypted at rest with a key held in the Android Keystore.
  • Every backup file the app writes is encrypted; there is no plaintext option.
  • You can clear a customer's phone number, address or notes at any time by editing them.

A customer who asks you to erase their data: you can edit their record to clear the fields you are not legally required to keep. Note that GST law (CGST Act §36) requires you to retain your books and the documents behind them for 72 months, and income-tax rules impose a comparable six-year duty — so an erasure request does not override your duty to keep the invoices themselves. This is why the app refuses to delete a customer who has bills or payments on record.

If you serve children. A "child" under the DPDP Act is anyone under 18. If your customer is a minor — common in a tuition centre — the Act will require you to obtain verifiable consent from a parent or guardian before processing their data, from 13 May 2027. billzloop has no field for recording that consent today. Our recommendation is to record the parent or guardian as the customer, with the student's name in the customer's Notes, so the person you hold data about and contact is an adult who consented.

None of this paragraph is legal advice. If it matters to your business, speak to someone qualified.


7. Files the app writes to your phone

Some exports are deliberately not encrypted, because their purpose is to be opened by someone else:

The unencrypted ones are readable by nothing else on the phone, but the last two persist until removed. Backup & Data → Clear exported files deletes all of them.


8. Your rights

For the support correspondence in section 4 — the only personal data we hold — you may ask us to:

  • tell you what we hold about you;
  • correct it if it is wrong;
  • delete it;
  • explain what we did with it.

Write to contact@onezloop.com and we will respond. There is no charge, and you do not need to have bought anything.

You may also complain to the Data Protection Board of India if you believe we have not handled your data properly.

For everything stored in the app on your phone, no request to us is needed or possible — it is on your device, under your control, and we cannot reach it.


9. Children

billzloop is a tool for running a business and is not directed at children. We do not knowingly collect any personal data from a child through the support channel. For children's data that you store in the app, see section 6.


10. Data transferred outside India

The only data that leaves India is the encrypted Drive backup you choose to upload, which goes to Google's infrastructure as ciphertext we cannot read, and what Google Play Billing exchanges with Google (section 5.2). Support email is handled by our mail provider. We do not transfer personal data to any country the Central Government has restricted under §16 of the DPDP Act.


11. Security

  • The database is encrypted at rest using SQLite3MultipleCiphers, with a random 32-byte key held in Android Keystore-backed storage. The key never leaves the device.
  • Backups use AES-256-GCM with a key derived by PBKDF2-HMAC-SHA256 at 200,000 iterations from your passphrase. GCM authenticates as well as encrypts, so a tampered backup fails to open rather than decoding to plausible nonsense.
  • A .billz file you were sent is treated as untrusted input: size-bounded, structurally validated, and path-checked before a single row is written.

No security measure is absolute. If you believe you have found a vulnerability, please report it privately to contact@onezloop.com rather than opening a public issue.


12. Changes to this policy

If we change this policy we will update the "Last updated" date above and publish the new version at the same URL. Because the app has no account and no way to reach you, we cannot notify you directly — the in-app link always points at the current version.


13. Contact

contact@onezloop.com — for privacy questions, data requests, grievances, and support alike. Support is free and best-effort for everyone, whether or not you have bought the Lifetime unlock.