Easy POS Docs - Privacy Policy

Last updated: 16 August 2026

1. Scope

This policy describes how Easy POS ("the App") handles data. Easy POS is self-hosted software — it runs on your own Frappe/ERPNext site ("Your Site"), and the App's publisher does not operate a central server that receives or stores your business or End Customer data. There is no Easy POS account, sign-up, or central database separate from Your Site.

2. What data the App handles

Through normal use, the App creates and reads standard ERPNext records on Your Site, including:

Customer records (name, contact details, loyalty enrollment) that you or your cashiers enter
Sales Invoice records (items sold, amounts, payment details, taxes)
POS Profile, POS Opening/Closing Entry, Pricing Rule, Item Price, and Loyalty Program records used to run and report on sales

None of this data is transmitted to the App's publisher. It lives in Your Site's own database, subject to your own backup, retention, and access-control policies.

3. Cookies and local storage

The App relies on the same authenticated session cookie your Frappe/ERPNext site already uses for login — it does not set any additional tracking or advertising cookies of its own.

The App is installable as a Progressive Web App. Its service worker caches only static application assets (JavaScript, CSS, icons) on the device for fast repeat loads — it does not cache transactional data or API responses offline; those are always fetched live from Your Site over your existing authenticated session. The App does not include any analytics, advertising, or tracking scripts as of this writing.

4. Third-party processors

If you configure the following optional features, the relevant third party processes data only as much as that feature requires, under your own account with them:

Razorpay — processes payment details when a payment gateway checkout is used, under your Razorpay account and its own privacy policy.
Email / SMS gateway — if you configure receipt delivery, Your Site's own configured email/SMS provider sends the receipt to the End Customer's address/number.

5. Third-party links

Documentation, receipts, or in-app messages may occasionally link to third-party sites (e.g. a payment gateway's own pages). Once you or an End Customer leaves Your Site, the Publisher is not responsible for how that third party collects or uses information.

6. Security

Because the App runs entirely on Your Site, its data security depends on Your Site's own configuration — access controls, HTTPS, backups, and patching. The Publisher takes reasonable care in how the App is coded (e.g. never caching API responses offline, using your existing authenticated session rather than a separate credential store) but cannot guarantee the security of a specific installation, which remains your responsibility.

7. Data subject rights and user options

Because data lives entirely on Your Site, requests to access, correct, or delete personal data (e.g. from an End Customer) should be handled through your own Frappe/ERPNext admin tools (Customer, Contact, Sales Invoice records), following your organization's own data-protection obligations. You can also disable optional data-sharing features (e.g. receipt delivery via email/SMS, or the Razorpay payment gateway) at any time from POS Profile settings.

8. Changes to this policy

This policy may be updated from time to time; the "Last updated" date above reflects the latest revision.

9. Contact

Questions about this policy can be sent to the support email listed in the App's Marketplace listing.

This policy is separate from the Terms of Service governing your use of the App, and the License covering the software itself.