Ironcare Service desk

Security and privacy

Built so each dealer sees only its own.

A dealer’s service records hold client names, machines, prices and credit. Ironcare keeps each company’s records apart in the database itself, asks for a second factor from anyone who approves money, and records every change.

Each company separated in the database

Every table that holds a company’s records has row-level security switched on and enforced. The database itself works out which company, branch and person is asking, and returns only their rows.

  • Who is asking is set only after the sign-in is checked; a screen or a request can’t choose it.
  • The application connects to the database without the right to bypass row-level security.
  • Branch, company and role boundaries are tested automatically on every change.

Signing in

Ironcare uses an established sign-in library with sessions kept in the database, not one built for the occasion. A session lasts at most seven days and is never stretched.

  • Managers, administrators, group executives and the credit controller sign in with a code from an authenticator app; each code works once, and backup codes cover a lost phone.
  • “Remember this device” is switched off: every sign-in by these roles asks for the code.
  • Removing someone ends all their sessions at once; anyone can sign out of every device from My account.
  • Sign-in attempts are limited per address.

Every change on the record

Every command writes its result and an audit event in the same step. Each company’s audit events form a chain with signed checkpoints kept outside the database, so a change to past events can be detected.

  • The application may only add audit events; it can’t change or remove them.
  • A separate read-only check verifies the chain against the checkpoints.
  • Audit events carry identifiers and codes, never names, emails or notes.

Documents and photos

A file is judged by its content, not by its name, and stored encrypted outside the database. It is released only through a single-use link for the person who asked, valid for 60 seconds.

  • Files up to 10 MB, in the types a service desk needs: photos and PDFs.
  • Encrypted with AES-256-GCM, with the key kept apart from the files.
  • Scanned for malware before anyone can open them.

Personal data and POPIA

A client’s contact people are seen only by the client’s home branch. Their privacy notice and their consent to service updates are recorded, and their details can be anonymised on an approved request.

  • Anonymising a contact also removes their name, email and number from the free text of every case.
  • Nothing is sent to a client from Ironcare without a channel you have set up and their consent.
  • Ironcare processes your clients’ data on your behalf; an operator agreement comes with your subscription.

Backups and environments

Backups are encrypted and signed, and contain the database, the audit trail and the documents together. A restore drill rebuilds them in a fresh database and checks them.

  • Development and test can never reach live systems: they refuse live addresses, accounts and numbers.
  • Live, test and development use separate databases, keys and credentials.
  • Every change to the engine passes type checks, a dependency audit, a secrets scan and more than 550 automated tests before it is committed.

Questions

What IT and finance ask.

Something else? Email hello@ironcare.io.

Can another dealer see our data?

No. Each company’s records are kept apart by row-level security in the database itself, so another dealer’s screens can’t reach them, whatever they ask for. The separation is tested automatically on every change.

Who at Ironcare can see our data?

Your data belongs to your company. Ironcare’s own staff work with it only to give you the support you ask for, as your operator agreement sets out, and every action in Ironcare is recorded in the audit trail.

Is Ironcare POPIA compliant?

POPIA compliance is a duty of your company as the responsible party, and Ironcare is built to help you meet it: contact people are seen only by their home branch, notices and consent are recorded, and a contact can be anonymised everywhere on an approved request. Ironcare acts as your operator under an operator agreement.

What happens to our data if we leave?

You can export your case list at any time. When you leave, your company’s data is removed from Ironcare, as your operator agreement sets out.

Early access

Bring us a breakdown. We’ll show you the route.

One of your own jobs, from the client’s call to the invoice, with your branches and departments. No slides.

Book a demo