privacy-hyva-pos

1. Name and Contact Data of the Controller

This privacy policy applies to the data processing by the Hyvä POS iOS app:
Controller: Hyvä Themes B.V.
Dutch CoC: 80794343
VAT id: NL861802329B01
Directors: Willem Wigman
Address: Kloosterweg 1, 6412CN, Heerlen, The Netherlands
Email: info@hyva.io.

2. The Short Version

Hyvä POS is built on a simple principle: your store data is yours, full stop.

We never see the sales you ring up, the customers you serve or the inventory you sell.
Every Magento API call goes directly between your device and your own store — never through any Hyvä Themes server.
Card payments go directly between your device and Mollie's API — never through us.
Credentials, tokens and the local offline cache stay on your device.

3. Free Version and PRO Version

Hyvä POS ships in two flavours, and they differ in what they connect to:

Free version — works against any standard Magento store. The app talks only to your store and (when configured) to Mollie for card payments. There is no licensing, no activation step and no contact with Hyvä Themes' infrastructure of any kind. Hyvä Themes B.V. is not involved at runtime.
PRO version — requires the Hyvä POS Magento module on your store and a paid subscription. PRO adds terminal activation, license validation, fiscal compliance for Germany / Austria / France / Italy, multi-user staff login, offline mode and other shop-floor features. License management is handled entirely by your own Magento store (via a scheduled background job inside Magento) — the device itself still never contacts hyva.io directly.

The sections below note where a behaviour is specific to the PRO version. Anything not labelled applies to both versions.

4. How the App Connects to Your Store

Hyvä POS connects directly from your device to your Magento store. For Magento traffic there is no server in between — no relay, no analytics backend. Every API call goes straight from your device to your store URL over HTTPS, including the sales orders the app places when you complete a transaction.

5. Hardware on Your Local Network

The app talks to point-of-sale peripherals on your local network or over Bluetooth: receipt printers (Epson and compatible), barcode scanners (Socket Mobile, Opticon and other Bluetooth/MFi scanners), cash drawers and customer-facing displays. These conversations never leave your shop's network and are not visible to Hyvä Themes or any third party.

6. Card Payment Integration (Mollie)

If you connect a Mollie account, the app talks to Mollie's API at api.mollie.com directly from your device to start terminal payments, check their status and issue refunds. Hyvä Themes B.V. never sees that data. This applies to both the Free and PRO versions.

Authentication uses Mollie API keys that you paste into the app. Live and test keys are stored separately in the iOS Keychain on your device and are sent only to api.mollie.com.

The app never sees card numbers, CVV codes or any cardholder data — Mollie's certified PCI-DSS infrastructure handles all of that. The app only ever receives a payment status and, for the printed receipt, the last few digits of the card.

7. Local Receipt Storage

Every sale completed on the till — paid by cash, card, store credit, layaway or invoice — is written to a local receipt store on your device. This is the device's authoritative copy of the sale; it powers receipt re-prints, end-of-day shift reports, refund lookups and the in-app sales history. Local receipt storage applies to both the Free and PRO versions.

Where — files live in the app's Documents folder, partitioned per connected store and per calendar month (pos_sales/{storeId}/YYYY-MM.json). Documents is used rather than Caches because receipts are financial records and must survive system-level cache pressure.
What — each entry contains the sale identifier, line items, totals, tax breakdown, payment method(s), the cashier on duty, the attached customer (name and email, when the cashier linked one), and — for card payments — the card scheme and the masked card number returned by the payment terminal (e.g. last four digits). The app never stores full card numbers or CVV.
How long — receipts are kept indefinitely while the store is connected. There is no automatic expiry or pruning.
What happens when you remove a store — removing a store from the app permanently deletes that store's local receipts along with its credentials, offline cache and any in-progress carts. The confirmation sheet shows the receipt count up-front and offers an Export Receipts to File… action that bundles every receipt for that store into a single ZIP archive (shareable via AirDrop, email, Files, etc.) so a cashier who wants a copy can take it off-device before committing the delete. Deleting the app removes everything.
Security at rest — files are written with iOS Data Protection class Complete Until First User Authentication. They are encrypted using the device's hardware secure element and are only readable after the first device unlock following a reboot. Writes are atomic, so a crash mid-write cannot corrupt the file.
Where they don't go — local receipt files are never uploaded to Hyvä Themes, never sent to any third-party SDK (the app embeds none), and are not visible to other apps on the device thanks to the iOS app sandbox. If iCloud Backup is enabled on the device, Apple's standard encrypted-backup mechanism applies to them as it does to any other Documents data.

PRO only: On a PRO terminal, each sale is additionally pushed to your Magento store via the Hyvä POS module's receipt endpoint, where it becomes part of your store's own reporting and audit trail. That server-side copy is governed by the merchant's own data-protection arrangements, not by this policy.

8. Terminal Activation and License (PRO version only)

Each device running Hyvä POS PRO is bound to a terminal record in your Magento admin via a one-time activation code that you generate in your store. License validation and the periodic terminal heartbeat are sent to your own Magento store, never to Hyvä Themes — your store, in turn, refreshes the license token from our subscription server on a scheduled cron job. From the device's point of view, no direct calls are made to hyva.io.

The Free version performs none of this — there is no activation, no heartbeat and no license token on the device.

9. Fiscal Compliance (PRO version only — Germany / Austria / France / Italy)

Cash-register transactions in Germany, Austria, France and Italy are legally required to be signed by a certified fiscal device. When fiscal compliance is enabled on a PRO terminal, the app signs each sale via Fiskaly's cloud service (kassensichv-middleware.fiskaly.com, rksv.fiskaly.com, sign-fr.fiskaly.com or sign-it.fiskaly.com, depending on country). Fiskaly receives only the fiscal information the local tax authority requires (timestamp, totals, transaction type) — no customer data and no line items. Fiskaly credentials are provisioned through Magento on terminal activation and stored on the device in the iOS Keychain.

10. What Is Stored on Your Device

Your Magento API token, used to authenticate with your store.
Your Mollie API keys (live and/or test), stored in the iOS Keychain.
Your store URL, terminal name, accent colour and display preferences (currency, time zone, language, lock timeout).
Held carts and any sale currently being built, until that sale is completed or discarded.
Local receipts for every completed sale, as described in section 7.
PRO only: Fiskaly credentials, when fiscal compliance is enabled, stored in the iOS Keychain.
PRO only: Staff PIN hashes for the cashiers who can use the till. Plain PIN codes are never stored.
PRO only: An offline cache of your catalog, customers, prices and tax rules, so the till keeps working when the connection drops. The offline cache is separate from the receipt store and is wiped when you disconnect a store or delete the app.
PRO only: The license token issued by your Magento store.

All of this lives in your device's local storage and is never transmitted anywhere except to your own Magento store and (if configured) Mollie or Fiskaly.

11. What We Do Not Store

Card numbers, CVV codes or any cardholder data — Mollie handles those on its PCI-DSS infrastructure.
Magento admin passwords — only the access token issued by your store.
Plain-text staff PIN codes — they are kept as one-way bcrypt hashes.
Analytics, usage data, crash reports or behavioural telemetry — we don't track anything.

12. Network, Cookies and Third Parties

The app uses an ephemeral (private) networking session. This means:

No cookies are stored between sessions.
No cross-site tracking is possible.
No background network calls are made except, in the PRO version, the terminal heartbeat to your own Magento store and (if enabled) the offline-cache refresh.

The external services the app contacts besides your own Magento store are:

Mollie (api.mollie.com) — only when you have configured Mollie, to start, monitor and refund the card transactions you initiate on the till. Available in both Free and PRO versions.
Fiskaly (kassensichv-middleware.fiskaly.com, rksv.fiskaly.com, sign-fr.fiskaly.com, sign-it.fiskaly.com) — PRO only, and only when fiscal compliance is enabled, to sign each sale for the local tax authority.

The app does not, in either version, make direct network calls to hyva.io.

13. Demo Mode

On first launch the app offers Try Demo. Demo Mode is fully self-contained: the catalog, customers and prices come from data bundled inside the app, no network requests are made and nothing is connected to a real store. Demo Mode is purely a preview of the user interface and is wiped the moment you connect a real Magento store.

14. Removing Your Data

You have two levers:

Remove a store from inside the app — permanently deletes every credential, token, in-progress cart, offline-cache file and local receipt for that store. The confirmation sheet shows the receipt count and offers an "Export Receipts to File…" action so you can save a ZIP off-device first.
Delete the app — removes every credential, token, cache and local receipt the app ever held on your device, across all connected stores.

PRO only: PRO customers can additionally remove the corresponding terminal record on the merchant side by signing in to their Magento admin and deactivating or deleting the terminal entry under Hyvä POS → Terminals.

15. Rights of the Individuals Affected

You have the right to obtain from us:

access to your personal data (GDPR Art 15),
the rectification of your personal data (GDPR Art 16),
the erasure of your personal data (GDPR Art 17),
the restriction of the processing of your personal data (GDPR Art 18) and
the portability of your personal data (GDPR Art 20).

You also have the right to revoke any consent you have given at any time in accordance with GDPR Art 7(3). This means we are no longer allowed to continue the processing of the data which was based on said consent.

You also have the right to lodge a complaint with a supervisory authority in accordance with GDPR Art 77 if you believe that the processing of your data was unlawful. Usually you can direct your complaint to the supervisory authority of your usual residence or workplace or our location.

To exercise any of these rights, send us an email at info@hyva.io.

16. Data Security

All connections to your Magento store, Mollie and (in the PRO version) Fiskaly are made over HTTPS using the highest encryption level supported by iOS. Credentials, API keys and fiscal tokens are stored in the iOS Keychain — the system-level secure storage that protects them with the device's hardware security and the cashier's passcode or biometric lock. Local receipt files are encrypted at rest with iOS Data Protection (see section 7).

We use appropriate technical and organizational security measures to secure your data from accidental or intentional manipulation, partial or complete loss, destruction or unauthorized access by third parties. Our security measures are continuously adjusted to keep pace with technological advancements.

17. Actuality and Change of This Privacy Policy

This privacy policy is currently valid and was last updated in June 2026.

As Hyvä POS evolves, or due to changed legal or official requirements, it may be necessary to update this policy. The current version is always available at this URL for you to view and print.