PocketBill

PocketBill is provided by SoftTech Service. This policy explains how the Android app handles information when you create bills, manage customers and products, scan labels, use rewarded ads, and export or share files.

1. Business Information on Your Device

PocketBill stores your business profile and billing settings, products and variants, customer details, bills and drafts, payment records, invoice history, credit history, template settings, and saved logos or product images in the app's private local storage.

Optional profile fields can include contact and address information, GSTIN or PAN, and bank or UPI details. Customers can include names, phone numbers, email addresses, addresses and tax details you enter.

This information is used to create and manage invoices, retain historical invoice snapshots, calculate local sales and customer summaries, manage saved credits, and produce files you request. PocketBill does not require an account and does not operate a cloud synchronization service. The app does not send your business database, customer list, invoice contents, bank details or product photos to a SoftTech Service server.

Payment amounts and methods are records you enter; PocketBill does not execute payments or obtain card credentials from a payment processor. Only enter customer and other third-party information you are entitled to use. You control the information placed on invoices and in exports.

2. Camera, Photos and Label Recognition

Camera access supports barcode scanning, product-label capture, and optional logo or product photography. You can also choose existing images through the system picker. Camera permission is requested when a camera feature is used, and you can deny or revoke it in Android settings. Manual product entry and search remain available.

Barcode and text recognition process images on the device. Google ML Kit does not send the input images, recognized text or recognition outputs to Google servers. Its SDK can send technical information to Google, including device and app information, installation identifiers, feature configuration, performance measurements and error events, for diagnostics, usage analytics, reliability and abuse prevention. These technical transmissions use HTTPS.

For additional details, consult ML Kit privacy information and ML Kit Android data disclosures.

An image you deliberately save as a logo or product image remains in local app storage. Images or text included in a file you share are received by your chosen recipient.

3. Rewarded Advertising and Consent

PocketBill uses Google Mobile Ads for optional rewarded ads and Google's User Messaging Platform (UMP) for consent choices. When online, the app refreshes Google consent information at startup; a required consent form can appear. The advertising SDK is initialized when the rewarded-ad flow needs it and the consent check permits ads. Watching an ad is a separate action you choose.

Google and its advertising services can collect and share IP addresses (which can indicate approximate location), advertising or other device/app identifiers, ad and app interactions, and diagnostic data to deliver and measure advertising, perform analytics, and prevent fraud. Collection depends on SDK behavior, device settings, region and consent choices. Ad-related transmissions use TLS. PocketBill does not supply invoice contents, customer details, product images or bank details as ad-targeting data.

See Google's Privacy Policy, how Google uses information from apps, and Google Mobile Ads data disclosures.

Local credit and reward-session records are retained to apply completed rewards once and prevent duplicate spending. Five initial credits are granted once per store dataset; each new issued bill consumes one saved credit. With zero credits, new finalization is blocked while drafts and existing bill operations remain available. A network connection is needed for rewarded ads, but saved credits can be used offline. Declining or being unable to view an ad does not remove existing records.

4. Permissions and Device Access

PocketBill requests only the permissions strictly required to perform selected features:

5. Backups, Exports, Printing and Sharing

Backups can contain the complete business dataset, including images, drafts, histories and credits. CSV exports contain the selected business records. Invoices can contain customer, business, tax and payment details.

These files are created locally and transferred only to destinations or applications you choose through save, share or print controls. The destination service or printer receives the content under its own privacy practices. A cloud-backed destination you select may upload the file.

6. Diagnostics

PocketBill keeps a bounded in-memory log of allow-listed event codes and timestamps for troubleshooting. It does not automatically upload this application log.

If you select Share diagnostics, the generated file contains the app version, platform, generation time, and available event codes, levels and timestamps. It is shared only with the destination you choose. Review any file before sending it. Google SDK telemetry described above is separate from this optional diagnostics file.

7. Storage, Security and Retention

Business records remain in local storage until you remove the app's data, uninstall the app, or replace the dataset through restore. Archived products/customers and cancelled invoices can remain in the dataset and in historical invoice snapshots; archiving or cancelling is not permanent deletion. The app does not offer permanent deletion of individual historical invoices.

Android's app sandbox restricts ordinary access by other apps. PocketBill does not add database encryption, an app lock or encrypted backup protection. Protect your device with its security controls and protect all exported files. No storage or transmission method is risk-free.

Temporary output files can remain in the app cache until app cleanup or Android removes them. Exported files, safety backups, shared copies, recipient copies and device-transfer copies are not removed automatically when local app data is removed. Google's retention and deletion practices for SDK data are governed by its published privacy information and applicable settings; we do not promise a fixed retention period for data held by Google.

8. Your Choices and Data Deletion

You may edit current profile, product and customer records, manage ad choices, revoke camera permission, stop sharing files, and export a backup. Changing current records does not rewrite saved historical invoices.

There is no PocketBill account to delete. SoftTech Service cannot remotely access or erase your local business database. Contact us at contact@softtechservice.site with privacy questions or requests. If you email us, we use your email address and message to respond; do not send invoices, financial details or customer data unless needed for your request. We keep support correspondence only for as long as needed to handle the request and meet applicable legal obligations.

9. Children's Privacy

PocketBill is a business billing tool and is not directed to children. If you believe a child has provided personal information directly to SoftTech Service, contact us so we can review and address the request.

10. Changes to This Policy and Contact

We may update this policy when the app or its data practices change. The effective date will identify the updated version. Material changes that require notice or consent will be handled as required by applicable law.