Data & security PRO APP
What StoreCashier POS stores on the counter device, how it is protected, what happens on uninstall and log-out, and the security rules the app follows. Useful for owners, IT staff and anyone deciding where to put a till.
Where: Windows —
%APPDATA%\StoreCashier POS · Android — the app’s private storageWhat is stored on the device#
| Data | Why | Kept until |
|---|---|---|
| Products, variations, prices, stock of the device’s locations, categories, brands | Selling offline | Replaced by every refresh |
| Customers (name, code, mobile, e-mail, group, price group, credit limit, balance at download time, address) | Picking customers offline | Refreshed |
| Tax rates, settings, payment accounts, receipt header and logo | Correct totals and receipts | Refreshed |
| Serial / IMEI numbers in stock at the device’s locations | Serial picker | Refreshed |
| Mobile plan lines (number, customer, phone, plan, status, due date — no ICCID, IMEI, notes or PINs) | Plan payments offline | Refreshed |
| Outbox: completed sales and register events not yet uploaded | Offline selling | Until the site confirms them |
| Sales history | Reprints, Day report | Last 500 synced sales |
| Returns | Reprints | Last 100 |
| Held carts, register sessions, sync log, device preferences (printer, language…) | Working state | — |
| Device token, device license (certificate), stable device id | Authentication | Encrypted, see below |
Never stored: card numbers, card PINs, customer account PINs / passwords, your StoreCashier license key, WordPress passwords. Card payments store only brand, last 4 digits and approval code.

How it is protected#
- Device token (a random secret; the site keeps only a hash) and the device license are stored with Windows DPAPI (Electron safeStorage) or the Android Keystore — readable only by this Windows user / this app. Fallback where neither exists: AES-GCM with a non-extractable key. The token is held in memory only while needed and never written to logs. Settings → This device → Token storage shows which is used.
- HTTPS only to the site (plain HTTP is refused except for local development addresses).
- Windows app: the screen code runs isolated (context isolation, sandbox, no Node.js access), strict content security policy, navigation to other sites and new windows are blocked, and all network requests go through the app’s main process.
- Android: app data is excluded from cloud backups, so the token and unsynced sales are not copied off the device.
- Same permissions as the web POS: every request is checked on the site against the cashier’s permissions, locations and payment accounts. Revoking the device on the site locks the app at once.
- Updates are installed only after a SHA-256 check (App updates).
Log out, uninstall, lost device#
| Action | What happens to the data |
|---|---|
| App Settings → Log out & unpair this device | Blocked while sales are waiting (“n sale(s) are not synced yet – sync them before logging out.”). Otherwise removes the token and all local data (catalogue, held carts, history). The stable device id stays. Revoke the device on the site too. |
| Uninstall on Windows | Program removed; %APPDATA%\StoreCashier POS is kept so unsynced sales are never lost. Re-installing continues where it stopped. Delete the folder by hand to remove everything. |
| Uninstall on Android | Android deletes the app’s data — upload everything first. |
| Update (Windows or Android) | Everything is kept. |
| Device lost or stolen | Site: Revoke the device — its token stops working immediately and its seat is freed. Sales not uploaded from that device are lost with it. |
| Revoked device found again | Pair it again: its unsynced sales upload after pairing. |
Good practice: one Windows user per till, a screen lock when the counter is unattended, and Settings → Re-download all data after big catalogue changes.