Walletmix POS Privacy Policy
Effective Date: November 1, 2026 • Last Updated: November 1, 2026 • Entity: Walletmix Limited (Dhaka, Bangladesh) • Contact: info@walletmix.com / +8801335556688
1. Scope & Introduction
This Privacy Policy explains how Walletmix Limited (“Walletmix”, “we”, “us”, or “our”) collects, uses, processes, stores, and protects information when merchants and their authorized staff use the Walletmix POS web platform (https://pos.walletmix.com) and the Walletmix POS mobile applications for Android and iOS (package ID com.walletmix.pos).
2. Categories of Data We Collect
Depending on how you sign in and use Walletmix POS, we collect and process the following categories of data:
- Merchant Account & Identity Data (Personal Info): Owner full name, business name, business address, Business Identification Number (BIN), registered email address, phone number, salted password hashes, and staff member names, roles, phone numbers, and terminal PIN codes.
- Firebase, Google Sign-In & Apple Sign-In OAuth Data: When you choose to sign in using Google Sign-In or Sign in with Apple (via Firebase Authentication), we receive your verified OAuth email address, display name, profile photo URL (if provided), authentication provider identifier, and Firebase User ID (
uid) solely to authenticate your merchant session and link you to your isolated POS workspace. - POS Orders, Inventory & Tax Records (Financial & User-Generated Business Data): Product catalogs, SKUs, barcodes, serialized Dual-IMEI device numbers, restaurant table and Kitchen Order Ticket (KOT/KDS) records, POS sales invoices, split-tender payment method breakdowns (Cash, bKash/Nagad QR reference numbers, Card terminal references, and Credit Due amounts), shift Z-Report summaries, and Bangladesh NBR Mushak-6.3 / Mushak-9.1 VAT calculations.
- Customer Due Ledger (“Bakir Khata”) & Installment Records: When merchants record customer credit sales or hire-purchase (Kisti/EMI) installments, the merchant workspace stores customer names, phone numbers, loyalty tiers, credit limits, due balances, and payment collection histories on behalf of the merchant.
- Subscription & Payment Settlement Data (Web Portal): For commercial SaaS plan subscriptions managed on
pos.walletmix.com, we collect subscription order numbers, selected plan tier, billing cycle, bKash online payment transaction IDs (trxID/paymentID), or corporate bank deposit slip references. Walletmix POS does not store raw customer credit/debit card numbers or MFS PINs. - Device Identifiers, Diagnostics & Crash Logs: Our mobile app and integrated platform SDKs (Google Play Services and Firebase Core / Authentication) collect device/app instance identifiers, operating system version, network state, and crash/performance diagnostic logs to maintain session security, prevent abuse, and ensure application reliability.
3. Purposes of Data Collection & Processing
We process collected data strictly for the following purposes:
- Core App Functionality: Synchronizing POS catalogs, processing sales invoices, tracking branch stock, managing restaurant KOT/KDS queues, maintaining the merchant’s Bakir Khata due ledger, and generating Mushak-6.3 VAT challans.
- Account Management: Creating and authenticating isolated multi-tenant merchant workspaces via Email/Password, Google Sign-In, Apple Sign-In, and Cashier PIN sessions.
- Security, Fraud Prevention & Compliance: Enforcing strict tenant isolation, rate-limiting login attempts, recording tamper-evident hash-chained audit logs, and complying with Bangladesh NBR VAT and financial record-keeping laws.
- App Stability & Diagnostics: Identifying and fixing crashes, network synchronization errors, and latency bottlenecks.
We do NOT sell user or merchant data to third parties, and we do NOT use merchant or customer POS data for third-party advertising.
4. Data Sharing & Sub-Processors
Walletmix Limited does not share your personal or business data with third parties except with essential infrastructure processors acting under our instructions or when required by law:
- Google Firebase / Google Identity Services: Used for OAuth authentication (Google Sign-In and Apple Sign-In token verification) and core app instance security.
- bKash Limited (Web Subscription Checkout): Used when a merchant initiates an online subscription payment on the web portal to verify tokenized payment completion.
- Cloud Hosting & Database Infrastructure: Encrypted virtual private servers and PostgreSQL databases managed by Walletmix Limited for multi-tenant POS state persistence.
- Legal & Regulatory Authorities: Disclosed only if required by a lawful order under the laws of Bangladesh (such as statutory NBR tax audits).
5. Data Security & Multi-Tenant Isolation
- Encryption in Transit: All traffic between the Walletmix POS mobile/web clients and
https://pos.walletmix.comis encrypted via TLS (HTTPS). - Strict Tenant Isolation: Each merchant account is assigned a dedicated, cryptographically scoped
tenantIdand session token prefix. Cross-tenant data access is blocked at the API security middleware layer. - Credential Protection: Merchant owner passwords are hashed using salted cryptographic hashing, and OAuth tokens are verified against upstream Google/Firebase public keys.
6. Data Retention & Account Deletion
Active merchant workspace data is retained for as long as your Walletmix POS account remains open. You may delete your account and workspace data at any time:
- In-App Deletion (Mobile & Web): Open Account / Sign-In or the Ops & VAT tab in the Walletmix POS mobile app (or the top bar in the web portal) and select Delete Account & Workspace Data.
- Web Deletion Without the App: Visit https://pos.walletmix.com/account-deletion to immediately delete your account or submit a deletion request ticket without installing or opening the mobile app.
- Retention Schedule After Deletion: Personal profile identifiers, OAuth UIDs, active sessions, product catalogs, customer Bakir Khata ledgers, and staff credentials are erased immediately upon self-service deletion (or within 48 hours for unauthenticated web/email requests), and aged out of encrypted disaster-recovery backups within 30 days. De-identified statutory tax and payment audit summaries are retained for up to 5 years solely as required by the Bangladesh Value Added Tax and Supplementary Duty Act, 2012, and then permanently purged.
7. Contact Us
If you have any questions about this Privacy Policy, data handling, or your privacy rights, please contact our Data Protection & Support team: