Account and work
Accounts are supplied by the business; the staff app has no public user registration. Depending on role, it supports POS, tables, kitchen, cashdesk, warehouse, reports and administration. This includes customer and staff information, financial records, chosen imports and uploaded media.
An authorized administrator can view existing courier location and history received from the server. The staff app does not collect its own GPS location. The route view is drawn locally without sending coordinates to a map-tile or geocoding service.
Payroll and employment records
When the business uses Human Resources, authorized administrators can enter employee personal numbers, employment periods, schedules, check-in and check-out events, attendance-device identifiers, salary history, allowances, deductions, advances, debts, expenses and payments. Leave or absence dates, types and notes can also be recorded. If entered by the business, leave types such as medical and maternity leave can reveal health or pregnancy information. These records are linked to the employee and store, sent to the business server and used for attendance, payroll calculations, payments and reporting. Access is restricted by system roles and permissions. Approved payroll records, expenses and payments are retained for business history and auditing under the business's retention policies. They are not used for advertising or advertising tracking.
Login, biometrics and NFC
The password is used for verification by the server and is not stored as a remembered login password. The retained session is protected by the operating system. Biometrics are optional: Face ID or fingerprint unlocks a retained session without giving the app the biometric template.
The mobile staff app does not offer PIN login. PIN is used only in the installed desktop application where configured and allowed by the business. The Profile NFC credential can be used to present the phone at the POS; it is not a requirement for mobile-app login. NFC uses a credential and limited proofs rather than only a readable card number. Explicit logout and revocation stop the relevant session from being used.
Camera, files and alarm
The camera decodes QR codes on the device; scan imagery is not uploaded. Images or import files you choose are sent to the business server. Printing or sharing can send the document to the chosen printer or destination.
The local kitchen alarm is foreground sound output when enabled. It does not record from the microphone. The app does not request microphone or device-GPS permission for these functions.
Notifications and technical information
When you enable notifications, the installation and Firebase/APNs token are associated with the account, store and session. Automatic notifications use generic text and technical identifiers; administrator-written messages can contain custom titles and text. Users should not put secrets in them.
Google Firebase and Android ML Kit can process installation, app, device and performance information for their functions. The app does not include advertising or personalized-ad tracking.
Unconfirmed actions and deletion
Releases with recovery can retain encrypted local actions until the outcome is confirmed. These can contain customer or document information. If an administrator creates or changes another account, its unconfirmed request can contain that account’s newly set password until recovery; this is not storage of the administrator’s login password.
The manual deletion request in Profile is available in releases that include it. We target acknowledgement and manual handling within seven calendar days; actual erasure timing and necessary retention will be communicated according to the business and its obligations. For any release you can use info@nursoft.al without reinstalling. See Ordex account and data deletion for details.
