Service
Security and compliance
We help the system guard the data passing through it — who logs in, what gets recorded, and how it updates.
Who it is for
A project that holds fiscal records, payment results, or personal data of customers and staff.
What it covers
- Separate logins for an operator, maintenance, and an administrator
- A record of who changed a machine or a product
- Updates and the closing of old services
- A layout that respects GDPR for the personal data the system holds
What you get
- Fewer shared passwords “for everyone”
- A clear line between a fiscal record and an internal note
- An honest account of what we do not cover
How we do it
An end to the shared password “for everyone”: separate logins for operator, maintenance and administrator, a record of who changed what on the machine and the products, a clear line between fiscal record and internal note, personal data under GDPR rules.
Two things we say openly: we do not issue certificates — if you need one (ISO, PCI and the like), it comes from an independent auditor, while we arrange the practice the auditor later reads; and we do not keep card numbers — the number stays in the terminal, we work only with the amount and the result. You get a short text of what was done and what stays your commitment — because security is also honesty about limits.
How an engagement runs
01. Data
A list of what is kept, for how long, and why.
02. Logins
Roles, and removal of shared passwords.
03. Changes
A trace of who touched settings and products.
04. Handover
A short text on what was done and what remains your duty.
Questions on this topic
Are you PCI or ISO certified?
No. We do not put those marks on the site. If you need a certificate, it comes from an independent auditor.
Do you store card numbers?
No. The card number stays in the terminal and with its operator. We work with the amount and the result.