Privacy Policy
Mandala POS · Effective: 19 November 2026
Mandala POS is point-of-sale and store management software operated by C.A.N. Tech Pvt. Ltd., Kathmandu, Nepal ("CAN Tech", "we", "us"). This policy covers the Mandala POS apps, the Mandala POS service and the website https://mandalapos.com. It says, in plain words, what information we collect, why, who else touches it, how long we keep it, and how to get it corrected or deleted.
If you have any question about this policy, contact us at support@mandalapos.com or +977 9842387048.
1. What we collect
Your account. When a store owner signs up we collect the store's name, the owner's name, a Nepali mobile number (verified with a one-time SMS code), a password, and optionally an email address. Staff accounts (manager, cashier and other roles) hold a name and a phone number or email, chosen by the store that creates them. Passwords are never stored as written; we keep only a strong one-way hash. One-time SMS codes are valid for 5 minutes, are stored only as hashes, and their records are deleted about a day after they expire.
Your store's business data. Everything your team enters to run the store: products, barcodes and prices, bills and payment records, returns, purchases and supplier records, stock entries, counters and shifts, staff accounts and roles, day open and close records, and the activity log (who voided, discounted, refunded and so on). This data belongs to your store (see the Terms of Service); we host and process it to provide the service.
Your store's customers. Staff may record a customer's name, phone number and balance for credit ("pay later") sales, and a buyer's name and PAN when a tax invoice needs them. The store, not CAN Tech, decides whether to enter this information and is responsible for it (section 8).
Loyalty members. If a store runs a loyalty programme, it records for each member who joined: name, mobile number, a member card number, the date the member joined and that the member agreed to join, and then the points earned, used, adjusted and expired, with the bill each came from (section 9).
Images. A store may upload a logo and product images. We strip hidden metadata (including location data) from images before storing them. Uploaded images are served from a public web address; treat them as public content.
Security and audit records. For sign-ins, one-time code requests and sensitive actions we record the IP address, device description and timestamps. We use these to protect accounts (rate limits, lockouts, fraud prevention) and to keep the tamper-evident audit trail the product is built around.
Phone notifications. When push notifications are switched on, the app registers the device with us: its Firebase installation ID (an identifier of this app install), the platform (Android or iPhone), the app version and the language setting. We use it only to send the store's own business-day reminders.
This website. The website sets no cookies, runs no scripts and uses no analytics or advertising. Our web server keeps an ordinary access log (IP address, time, the page requested, the browser's description of itself and the page that linked to ours) to keep the site secure and working.
2. What we do not collect
- No location data. The app does not read your GPS location. (Some Android versions list a location permission because Android requires it to scan for Bluetooth printers; we do not receive or store any location.)
- No SMS to your customers. Mandala POS does not send loyalty or marketing messages to a store's customers. The only SMS we send are one-time codes and account notices to the people who use the app (for example the temporary password for a store account that we set up for its owner).
- No advertising and no ad SDKs.
- No analytics or behavioral tracking SDKs in the app.
- Camera only for scanning and photos you take. If you use the camera to scan barcodes, the picture is read on your device to find the barcode and is not stored or sent to us. A photo you choose to use as a logo or product image is uploaded.
- No access to your contacts or files, except a photo you explicitly pick or take as a logo or product image, and spreadsheet files you explicitly pick to import products.
- No advertising identifiers and no hardware identifiers such as the device serial number or IMEI. The only identifier of the app install is the Firebase installation ID described in section 1.
3. How we use information
- To provide the service: run your store's selling, billing, returns, purchasing, stock, reporting and staff features, and keep them in sync across your counters and devices.
- To meet tax law: when your store has IRD billing on, issue tax invoices and send the data IRD requires to its Central Billing Monitoring System (CBMS).
- To secure the service: verify sign-ins, prevent fraud and abuse, enforce role permissions, and keep audit logs of sensitive actions.
- To support you: respond when you contact us.
- To manage plans: apply your plan's limits and trial status.
- To improve reliability: review error reports, only if we switch error reporting (Sentry) on. It is off unless we turn it on.
We do not sell personal information. We do not use it for advertising. We do not profile you.
4. Who else processes data
We share data only with organizations that need it to run Mandala POS or that the law requires, and only what each needs:
| Organization | What they receive | Why |
|---|---|---|
| Inland Revenue Department, CBMS (Nepal) | When IRD billing is on: tax invoice and credit note data, including the buyer's name and PAN where entered | Required by Nepal's electronic billing rules |
| Nest Nepal (servers and databases in a Nepal data centre) | Hosts our servers and databases (your store's live business records) | Running the service |
| Google Drive (Google, outside Nepal) | Our hourly backups of the service's databases, encrypted on our server before they are uploaded, with a key that only CAN Tech holds. Google stores the files but cannot read what is inside them | Backups, so your records can be restored |
| Sparrow SMS (Nepal) | Your mobile number and the SMS text (one-time codes, account notices) | Delivering SMS in Nepal |
| Google Firebase (Google, outside Nepal) | A device-integrity token during signup on Android and iPhone (App Check), and, when push notifications are on, the device registration described in section 1 | Blocking abuse signups; sending notifications |
| Sentry (only if error reporting is switched on) | Technical error reports. Known personal and secret fields are removed before sending. A report carries internal user, store and branch numbers | Fixing crashes and bugs |
| Cloudflare (R2 object storage) | Uploaded logos and product images | Image hosting |
Google (Drive and Firebase), Cloudflare and Sentry process data on servers outside Nepal. Your store's live business records are in a Nepal data centre, but the encrypted backups of them are kept on Google Drive, outside Nepal, and uploaded images are kept with Cloudflare, outside Nepal.
5. Where data lives and how it is protected
- Every store's data lives in its own separate database, isolated from every other store's, on servers in a Nepal data centre.
- Backups are encrypted on our server before they leave it, with a key that only CAN Tech holds and that is never kept on the server. The encrypted files are stored outside Nepal (Google Drive).
- All traffic between your devices and our servers is encrypted (HTTPS).
- Passwords and manager PINs are hashed; one-time codes are stored only as hashes; sign-in tokens are short-lived and revocable, and changing a password signs out old sessions.
- Your store's IRD credentials are stored encrypted and used only to send your bills to CBMS.
- Rate limits and lockouts guard sign-in, one-time codes and manager-PIN approvals.
- Access to the servers is limited to authorised CAN Tech staff, and updates reach the servers only through a restricted, logged channel.
- On your own device, the app keeps a working copy of the information it has loaded, so screens load fast and existing information can be looked up if the connection drops (changes cannot be made offline). That copy is wiped when you log out. Sign-in tokens are kept in the device's secure storage.
No system is perfectly secure. If we learn of a data breach that affects your personal information, we will inform affected account owners without undue delay and tell them what happened and what we are doing about it.
6. How long we keep data
- Billing records (bills, tax invoices, credit notes, day-close records and their audit logs): for at least the period Nepal's tax law requires, even if the store closes its account or asks for deletion. They are never physically deleted by the app, and the backups keep a copy from every fiscal year end.
- Other account and business records: for as long as the store's account exists, then deleted after the wind-down period in the Terms of Service.
- One-time SMS codes: valid for 5 minutes; their records are deleted about a day after they expire.
- Backups: every hourly backup is kept for 7 days, the newest backup of each day for 35 days, the newest of each month for 24 months, and the backups from each fiscal year end are kept (they are removed only by a recorded decision). A backup file that we delete stays in Google Drive's trash for another 30 days. Deleted data can remain in backups until they expire.
7. Your choices and rights
- See and correct. Owners can view and edit their store's data in the app, except records that the law and the product keep unchangeable (a tax invoice is corrected by a credit note, not edited). You may ask us for a copy of the personal information we hold about you.
- Delete your account. The owner can ask us to delete the store account, by email or phone (see the contact details below). We delete what we can and keep billing records only for the legal period above. A staff member's login is removed by the store's owner (the account is marked deleted and can no longer sign in), or at their request by us; records of actions they performed at work are part of the store's business records.
- Withdraw consent. You may withdraw consent by deleting your account or contacting us; records the law requires are kept as described above.
- Complain. Contact us first at support@mandalapos.com. You also have whatever rights Nepali law (including the Individual Privacy Act, 2075) gives you.
8. Your store's customers
Mandala POS is a tool used by stores. When a store records a customer's name, phone number, balance or PAN, the store is the one collecting that information, and CAN Tech processes it only on the store's behalf (and sends tax invoice data to IRD where the law requires). Customers should direct requests about their data to the store they bought from.
9. Loyalty programmes
A store may switch on a loyalty programme in Mandala POS. It is off until the store turns it on.
- The store is the controller. The store decides to run the programme, who joins and what the points rules are. CAN Tech processes the members' data only on the store's behalf, as in section 8. A member who has a question or a request about their points or their data should ask the store.
- Opt-in. A staff member enrols a customer only after the customer agrees, and the app records that agreement and the date at enrolment. A customer who has not joined is never given points. The store, not CAN Tech, must be able to show that the customer agreed.
- What is stored. For a member: name, mobile number (Nepali numbers only), a member card number (the letter M and 8 digits), the opt-in and its date, the points balance and a history of entries. Each entry says whether points were earned on a bill, taken back after a void or return, used on a bill, adjusted by a manager (with the reason the manager typed and who did it) or expired, and the bill it belongs to. A member's purchases appear in the history only as the bill reference and the points; the store's bills are kept as described in section 6.
- No messages. Mandala POS sends no SMS or other message to members.
- Who sees it. The store's staff who have the permission to see customers, and CAN Tech support when the store asks for help. Nothing about a member is shared with another store, with IRD (members' points are not part of the tax invoice) or with any advertiser.
- The customer display. If the store uses a second screen facing the customer, it shows the cart, the price, the saving, the amount to pay and, for a member, the points the sale will earn. It never shows a member's name, phone number, card number or points balance, or a bill number.
- Leaving and deletion. A member can ask the store to delete their data. The store's owner or an admin uses Delete member data, with a reason. The name becomes "Deleted member", the mobile number and the store's note are erased, the opt-in is withdrawn, the member's card stops working and any points left are given up. This cannot be undone. Kept, because the store's bills and its points accounting must still add up and billing records are kept for the legal period in section 6: the bills, the points history as numbers with no name, and the member card number printed on old receipts. The store's audit trail cannot be edited, so a name or phone number typed in an earlier change to the customer stays in that trail. A store cannot delete a customer who still owes it money; the dues are settled first.
- Corrections. A mistake in a member's name or number is corrected by the store in the app. A points balance is corrected only by an adjustment with a reason, never by erasing the history.
- Expiry. If the store sets points to expire, expired points are recorded as an expiry entry; the store tells its members the rule.
10. Children
Mandala POS is a business tool for store owners and their staff. It is not directed to children, and you must be at least 18 to create an account.
11. Changes to this policy
If we change this policy in a way that matters, we will post the new version with a new effective date and tell account owners in the app or by SMS.
12. Contact
C.A.N. Tech Pvt. Ltd.
Kathmandu, Nepal
Email: support@mandalapos.com · Phone and WhatsApp: +977 9842387048