Data and Security
Hyvä POS is on the App Store
The free app is out for iPhone, iPad and Mac: install it from the App Store, connect your Magento store and sell. PRO, the Magento module with a license per terminal, follows shortly. News and pricing are at hyva.io/pos.
What lives on the device, how it is protected, and what happens when a device is lost or replaced.
What Is Stored Where
| Data | Where | Protection |
|---|---|---|
| Store configuration (URLs, settings, catalog cache) | App storage on the device | iOS data protection (encrypted at rest) |
| API tokens, OAuth secrets, payment-provider API keys and access tokens, fiscal signing credentials | iOS Keychain | Keychain encryption; secrets are kept out of the configuration file |
| Admin credentials (stay-signed-in) | iOS Keychain | Device-only: excluded from backups and device transfers |
| Staff PIN verification data | iOS Keychain | Stored as salted, slow hashes (never the PIN itself); device-only |
| Receipts and sales | Encrypted files on the device, grouped per month | iOS data protection; readable after first unlock so background sync works |
| Register closings (Z reports) | A file on the device, kept until Magento holds each closing; on PRO with module 1.4.0 also in Magento under Hyvä POS → Reports → Register Reports | iOS data protection; a closing is not changed once it is issued |
| Terminal identity (PRO) | iOS Keychain | Device-only: a cloned or restored device gets a new identity |
Passwords and passcodes are never stored in plain text. Magento verifies a staff passcode against a strong hash. The device keeps a salted hash of each passcode Magento accepted, computed with a deliberately slow algorithm and compared in constant time, so a staff member who signed in on the device can sign in while the store is unreachable. The saved hash is valid for 24 hours from the store's last confirmation: an online sign-in, a staff sync or a heartbeat. The device measures that time on a clock that setting the device clock back does not change. Wrong-passcode lockouts follow the store's schedule on the device as well, so offline mode cannot be used to bypass them.
Network Security
All traffic is HTTPS, enforced by iOS itself; the app performs no plain-HTTP requests. OAuth-authenticated stores get signed requests on top, which prevents request tampering and replay. API sessions are ephemeral: no cookies, no shared browser state. On PRO, Magento sends a terminal's license and activation details only to the device the terminal is paired with.
Where Receipts Live, and How They Recover
Receipts are the register's record of the sale (local receipts):
- On the device: every receipt is written to encrypted storage the moment the sale completes, immutable from then on.
- In Magento: every sale also produces a Magento order, on both tiers. On PRO, the receipt itself syncs to Magento as well, creating a central, immutable receipt archive.
Recovery follows from that:
| Scenario | Free tier | PRO |
|---|---|---|
| App deleted / device wiped | Receipts on the device are gone; the Magento orders remain your record | Receipts are all in the central archive; nothing is lost |
| Device lost or stolen | Same as above; revoke the store's API token in Magento to cut access | Same, plus Disable the terminal in the Hyvä POS → Store Setup → Terminals grid: the device is locked out on its next heartbeat and its active staff sessions end. This is the way to cut off a lost device. Deactivating a staff member in Magento signs them out of every register at its next heartbeat |
| Device replaced | Reconnect the store on the new device and re-authenticate | Re-activate the terminal on the new device; history is in the archive |
Run PRO where receipts are legally material
Wherever receipts must survive the device they were written on, the PRO receipt archive keeps every receipt in Magento rather than only on the device.
Device Backups and Migration
iOS backups and device-to-device migration transfer the app's configuration and data files, but not the secrets: keychain items marked device-only (credentials, PIN caches, the terminal identity) never leave the original device. A migrated or restored device therefore asks you to re-authenticate the store, and on PRO it presents itself as new hardware that needs its own terminal activation, so a restored backup cannot act as the original register. Register closings are numbered per install of the app: a restored, reinstalled or new device starts a new numbering series at 1, with its own four-character series code, so no closing number is issued twice. Closings the old device still holds upload to Magento under its own series after the replacement.