Privacy Policy
Effective 23 September 2026
1. Information we process
Dokan Hisab may process account details such as name, shop name, email address, Bangladesh mobile number, address and role, together with shop records you choose to enter: products, barcodes/SKUs, stock, customers, suppliers, sales, purchases, expenses, dues, returns, bank-ledger entries, staff activity and support tickets.
2. Authentication and security data
Passwords are stored as one-way password hashes rather than readable passwords. The service may process session identifiers, session versions, login timestamps, rate-limit records, IP-related security identifiers, verification/reset-token metadata and audit logs to authenticate users, prevent abuse and investigate account-security events.
3. Why information is used
Information is used to operate the shop-management features, authenticate users, calculate reports, synchronize offline sales, enforce plan and role limits, maintain audit history, process subscription status, send requested transactional messages, prevent fraud/abuse, troubleshoot errors and respond to support requests.
4. Shop-owner and staff access
A Shop Owner controls that shop's staff accounts and role assignments. Staff access is limited by role and platform policy. Staff should only be given access needed for their work. The shop owner is responsible for deciding what customer or supplier information the shop records and who within the shop should be allowed to view it.
5. Platform administration
Authorized platform administrators may access account status, subscription/billing records, audit information, support information and operational shop records when reasonably necessary for security, support, fraud review, incident investigation, service administration or recovery. Administrative actions may themselves be audited.
6. Service providers
Dokan Hisab may rely on hosting, database, email, monitoring and payment providers configured by the operator. Those providers may process the technical, account or transaction information necessary to provide their services. They operate under their own security, infrastructure and contractual terms.
7. Payments
When hosted online payment is enabled, sensitive wallet/card credentials are entered with the payment provider rather than stored directly by Dokan Hisab. Dokan Hisab may retain the amount, payment status, provider transaction/reference identifiers, subscription dates and related verification/audit information needed to reconcile billing and resolve disputes.
8. Offline device storage
The offline POS feature may store pending sale data and a limited authenticated app cache on the user's device until synchronization or sign-out cleanup. Shop owners are responsible for protecting devices, browsers and operating-system accounts used to access their shop.
9. Customer and supplier information entered by shops
Dokan Hisab provides fields for a shop to record customer/supplier information. The shop determines what information it enters and why it needs that information. Do not enter unnecessary sensitive information. Shop owners should use customer/supplier information only for legitimate shop operations and comply with applicable obligations relating to that information.
10. Security
The service uses measures such as password hashing, signed secure sessions, access controls, role checks, same-origin protections, rate limiting, audit records and expiring recovery tokens. No internet service can guarantee absolute security, so users must also protect passwords and devices and report suspected compromise promptly.
11. Retention
Records may be retained while an account is active and for a reasonable period afterward where necessary for account recovery, billing reconciliation, fraud/security investigation, backups, dispute handling, audit integrity or legal obligations. A deleted/suspended subscription does not necessarily require immediate deletion of transaction or audit records where retention remains reasonably necessary.
12. Access, correction and deletion requests
You can correct many shop records directly through the product's supported workflows. Account-level privacy requests can be submitted through Support. We may need to verify identity/authority before acting, and some transaction, billing, security or audit data may need to be retained where deletion would undermine legitimate records or applicable requirements.
13. Security communications
Support will never require your current password, card PIN, mobile-financial-service PIN or OTP. Do not include secrets, reset tokens, database credentials or full payment credentials in support tickets.
14. Policy changes
This Privacy Policy may be updated as the product, providers or operating requirements change. Material changes should be communicated through the website, product or normal support channel.
15. Contact
Privacy and data-handling questions can be submitted to Dokan Hisab through the Support page.