Privacy Policy

BillSetu is a local-first billing app for parties, items, stock, invoices, payments, expenses, reminders, and sync status. This policy explains what the app stores and how optional backend sync works.

The short version: billing records are stored locally first so invoices and payment work remain usable during network or server outages. When sync is configured, pending changes are sent to the BillSetu backend for your business workspace. Optional ads, analytics, client issue reporting, and billing SDKs may process device-level data under their own policies.

Data You Enter

• Business profile, staff, party/customer, item, GST/state, and stock information.
• Invoices, estimates, trade documents, payments, expenses, reminders, and report summaries.
• Optional share/export content generated from invoice or PDF previews.

Local Storage and Offline Use

BillSetu keeps operational records in local app storage and marks pending changes for sync. This lets invoices, item catalogs, payments, and reports stay visible when CodeServer or the network is unavailable. Local data is removed when the app is uninstalled unless it has already synced to the backend.

Cloud Sync

If backend sync is enabled, pending local records are sent to CodeServer and remote changes are pulled back into the app. Sync requests are scoped by business workspace and authentication configuration.

Diagnostics, Feedback, Ads, and Billing

• Feedback opens the shared Trei feedback form with the BillSetu app identifier.
• Client issue reporting and analytics use masked payloads for startup, sync, settings, premium, ad, and important-failure events.
• Free builds may show ads through Google AdMob where consent allows.
• RevenueCat is used for the optional remove-ads Premium purchase and restore flow.

Contact

Trei
Email: contact@trei.dev
Website: trei.dev  ·  Contact form