StoreCashierDocumentation Free 1.6.6 Pro 1.5.6 Apps 1.5.0

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 storage

What is stored on the device#

DataWhyKept until
Products, variations, prices, stock of the device’s locations, categories, brandsSelling offlineReplaced by every refresh
Customers (name, code, mobile, e-mail, group, price group, credit limit, balance at download time, address)Picking customers offlineRefreshed
Tax rates, settings, payment accounts, receipt header and logoCorrect totals and receiptsRefreshed
Serial / IMEI numbers in stock at the device’s locationsSerial pickerRefreshed
Mobile plan lines (number, customer, phone, plan, status, due date — no ICCID, IMEI, notes or PINs)Plan payments offlineRefreshed
Outbox: completed sales and register events not yet uploadedOffline sellingUntil the site confirms them
Sales historyReprints, Day reportLast 500 synced sales
ReturnsReprintsLast 100
Held carts, register sessions, sync log, device preferences (printer, language…)Working state—
Device token, device license (certificate), stable device idAuthenticationEncrypted, 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.

Settings This device card including token storage Windows DPAPI and catalogue counts
Settings → This device shows the token storage and how much data the device holds.

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#

ActionWhat happens to the data
App Settings → Log out & unpair this deviceBlocked 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 WindowsProgram 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 AndroidAndroid deletes the app’s data — upload everything first.
Update (Windows or Android)Everything is kept.
Device lost or stolenSite: 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 againPair 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.