Access is the product. Here is how we handle it.
Remote access to payment terminals is a decision about trust. This page describes the access model we commit to before onboarding, without badges we do not hold.
Narrow, time-bound, attributable
The default is no access. Access is requested for a specific task, granted for a limited time, and removed when the task is done.
- Least-privilege sessions. No standing admin accounts on client infrastructure.
- Time-bound access. Credentials and sessions expire; none are shared between engineers.
- Every session is logged. Who connected, when, to which device, and what changed.
- Reviewable on request. Session history and change logs are available to the client.
- Clean offboarding. Access is revoked when an engineer leaves the account or the project ends.
A human on the other end
An escalation path is only real if someone answers. Every account has a named incident lead and a 24/7 route to the shift.
- Named incident lead. One person accountable for the account, not a shared mailbox.
- 24/7 escalation. The shift engineer can reach a decision-maker without waiting for Monday.
- Written severity definition. S1 is defined before the first incident, not during it.
- Post-incident review. What happened, what changed, what prevents a repeat.
Client data stays client data
We process device and transaction data to run the service. It is not a product, and it is not training material.
- No data resale. We do not sell client data.
- No model training. Client data is not used to train models.
- Minimum necessary. We collect the telemetry the service needs, not the whole database.
- Retention. Logs and tickets are kept for the period agreed in the contract.
Report a security issue
If you believe you have found a vulnerability in our site or platforms, email info@isoftservices.net with the subject “Security report”. Please include enough detail to reproduce the issue and give us a reasonable window to fix it before public disclosure.
This page describes our operating model and commitments. It is not a certification and does not list standards we have not been audited against.
Talk to the team that answers at 3 a.m.
Tell us your fleet size and the failure that hurts most. We reply within one business day — usually within a few hours.