Trust & compliance
Eight safeguards
Customer data stays minimal, every company's data stays its own, and every action leaves a trail nobody can rewrite.
One shared database with strict company isolation. A company only ever sees its own users, settings, tickets and reports, including through public pages and exports.
Sessions live in secure, httpOnly cookies that page scripts cannot read, and end after the period of inactivity you set.
Repeated failed sign-ins lock the account for a while, and admins can see it. Temporary passwords must be changed at first sign-in.
Queue actions, admin changes, exports and support access are recorded with who, what and when, and cannot be altered.
Choose how long names and mobile numbers are kept, 90 days by default. Then personal fields are removed while counts and times stay in reports.
A privacy notice on the registration page, minimal data, retention limits and deletion on request. The display shows numbers and counters only.
Registration, ticket and status pages work with a keyboard and screen readers, use readable contrast and never rely on colour alone.
Download your configuration and queue data whenever you like, and restore after a clear warning. The platform keeps its own daily backups too.
How it is built
The specific ways HANA QMS keeps each company’s data separate, sign-ins safe and every action traceable.
One shared database where every row belongs to exactly one company, and every query is filtered by it.
Each page and action checks the user’s role and that this specific record belongs to their company and branch.
Session cookies are httpOnly, Secure and SameSite, and end after the idle time your admins set.
Repeated failed sign-ins lock the account and email the admins. Passwords meet a minimum strength.
All traffic between browsers, displays and the service is encrypted.
Sign-in and public pages such as the status lookup limit repeated requests, so queue numbers cannot be guessed.
Queue activity and the audit log record who did what and when, and no user can edit or delete an entry.
Platform staff enter a workspace only through a logged support session, and the company admin can see that log.
After the configured number of days, names and mobile numbers are removed from tickets; counts and times stay.
Restoring a backup shows what will be replaced and needs a typed confirmation, and is recorded in the audit log.
Registration, ticket and status pages work with a keyboard and screen readers and never rely on colour alone.
The product is tested for common web vulnerabilities, aligned with the OWASP Top 10, before launch and at least yearly.
Get started
Click through a real HANA QMS workspace as an admin, a branch manager or a staff member, no sign-up needed. Or tell us about your branches and we will set up a walkthrough.