1. What we use
Dumala uses small files and browser storage to keep the service secure, remember necessary session or branch context, provide the app-like POS experience, and support offline operation. We do not currently use non-essential advertising or analytics cookies. If that changes, we will provide the notices and choices required by applicable law.
2. Necessary cookies
- Authentication and session cookies: keep an owner or staff session active and help protect authenticated routes.
- Branch and application context: remember the branch or workspace context needed to render the correct POS experience.
- Security and request controls: support secure navigation, form submissions, and abuse prevention.
Blocking necessary cookies can prevent login, checkout, order tracking, or POS functions from working.
3. Local storage and IndexedDB
Offline POS data
The POS may keep catalog data, workspace settings, device information, queued orders or sales, and audit data in IndexedDB or local storage so that work can continue during a connectivity interruption. Unsynchronized records may remain on the device until they are successfully synchronized or intentionally cleared.
Cached business information
Depending on the enabled workspace features, a browser may cache branch, product, inventory, receipt, shift, report, or other operational information. Some data can be sensitive personal or business information. The organization must use device locks, unique accounts, sign-out, permissions, and device-revocation procedures.
How to clear it
Sign out where the application provides that control, then clear the site’s cookies and storage through the browser settings when a device is transferred, lost, shared, or retired. Clearing storage before synchronization can remove unsent records; follow the organization’s recovery procedure first.
4. Service worker and public assets
Dumala may use a service worker to cache public application assets and support installation or offline behavior. Private authenticated HTML is not intentionally cached by the service worker. Users should still treat a POS device as a sensitive endpoint and keep its operating system, browser, lock, and user access secure.
5. Payment-provider sessions
When a subscription payment is started, the payment provider may set or use its own browser or security mechanisms. Those mechanisms are controlled by the provider’s terms and privacy notice. Dumala is designed not to store the full card number or security code.
6. Managing preferences and questions
You can manage or clear cookies through your browser. Essential storage cannot be turned off without affecting the Service. For questions about personal data, contact the address in the Privacy notice. For operational or device issues, use Complaints and support.