Privacy Policy

mSalesOps is a local-first field sales operations app for attendance proof, inventory, dispatch, invoices, payments, follow-ups, and sync status. This policy explains what data the app stores and when it syncs with CodeServer.

The short version: operational records are stored locally first so teams can keep working during network or server issues. When sync is configured, pending work is sent to the mSalesOps backend for the tenant account. Optional ads, analytics, crash diagnostics, feedback, and billing SDKs may process device-level data under their own policies.

Data You Enter

• Tenant and team details such as business name, role, phone number, GST/state metadata, and active status.
• Inventory, batches, stock ledger entries, dispatches, invoices, payments, customers, and follow-up notes.
• Attendance and media proof references captured for business workflow records.

Local Storage and Offline Use

The app keeps operational records in local app storage and marks pending changes for sync. This lets the app continue showing useful sales and inventory data when the server 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 for your tenant, pending local records are sent to CodeServer and remote changes are pulled back into the app. Sync requests are scoped by tenant and authentication configuration. Do not enter another business' data into your tenant workspace.

Diagnostics, Feedback, Ads, and Billing

• Feedback opens the shared Trei feedback form with the app identifier.
• Client issue reporting and analytics use masked payloads for app health, startup, sync, settings, premium, and ad events.
• Free builds may show ads through Google AdMob and Meta Audience Network 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