TAC HRTAC HR
Trust

Security and Employee Data Protection

Employee data is among the most sensitive information a company holds: ID numbers, iqamas, salaries and IBANs. TAC HR builds security on four layers: each company's data is isolated from every other company, permissions are granular by branch and department, an audit log records who changed what, and punches are protected against spoofing. This page describes what is actually built into the product.

Isolation and permissions

Is my company's data isolated from other companies?

Yes. TAC HR serves many companies and branches on one platform, and tenant isolation is enforced in the code itself, so a user from one company cannot see another company's records. Each company's data stays completely separate from every other's.

How do permissions work?

The system has 111 permissions in 24 groups, granted to each manager at the level their job needs and scoped by branch and department. A Jeddah branch manager sees their branch's employees, a sales department head sees that department, and a payroll accountant sees payroll without recruitment files.

Granted individuallyeach permission is granted on its own within the manager's role, so viewing the employee list is separate from editing employees, editing is separate from deleting them, and viewing payroll runs is separate from editing them. What is not granted stays closed, and a permission with a key that is not in the catalog is refused rather than opening a door by mistake.
Scopeda manager is assigned one or more branches or departments and sees only the employees who fall in one of them. If both scopes are left empty the manager sees the whole company, an employee with no branch and no department is hidden from anyone whose scope is restricted, and the system administrator is never restricted by scope.
Roles for each managereach manager has a role that bundles the permissions their job needs, so what a business owner sees differs from what an HR officer or an accountant sees. The details of what each role opens are on the pages for business owners, HR and finance.

Users and permissions are part of the core platform with any subscription.

Accounts and audit
  • 01

    Is every change to employee data logged?

    Yes. The system keeps an audit log with an activity screen showing the important operations, and each entry records who performed the operation and the network address it came from, and for edits the value of each changed field before and after. Payroll has its own log for salary changes, and a payroll run is locked after approval, so no figure changes after closing without a trace.

  • 02

    How are login accounts protected?

    • Login throttling: six failed attempts on the same account within 15 minutes lock it for 15 minutes, and the counter is cleared at the first successful sign-in, so an employee who forgot a password is not locked out for good. The counter is kept in the database, so a restart does not reset it and running several instances does not bypass it.
    • Device binding: the first successful sign-in from the phone binds the employee's device to their account, and an employee has only one active device at a time. This binding is strict by default for every company, and it is relaxed only if the company itself switches it off explicitly.
    • New device: someone signing in on an unbound phone is blocked and shown a dialog that sends a device change request to management to approve or reject. On approval the old binding is revoked while its record is kept, the account's sessions are invalidated, and the new device is bound when the employee signs in on it.
  • 03

    Are my data backed up?

    Yes. Database backups are taken and stored encrypted with a dedicated key in a storage container reserved for backups and independent of the environment that runs the platform. If the encryption key is missing the backup fails and no unencrypted backup is written, and a restore is verified by comparing the row counts of the core tables before the backup and after the restore.

Punch protection

How is attendance spoofing prevented?

Mobile punches are checked against the geofence in the system, and the app also checks the device's integrity before every punch on Android. The system rejects:

  • Mock locations: a punch is refused if the phone reports that the location comes from a mock provider, if a mock-location app is selected in developer options, or if a known location-spoofing package is installed. The app blocks the attempt and reports it to management, who see it under rejected attempts.
  • Modified phones and emulators: a punch from a rooted phone is rejected. On an emulator the app blocks the punch and reports it to management with the reason "emulator", while signing in to the app itself stays allowed for anyone trying it on an emulator, and the attempt appears to management under rejected attempts on the web.
  • USB debugging: if USB debugging or developer options are on, or a data cable is connected, the app stops the punch and asks the employee to disconnect and try again. This is a device state rather than tampering, so management is not notified of it.
  • A GPS location that disagrees with the network location: the app compares the two when the network location is recent, within five minutes, and judges a mismatch when the gap exceeds two kilometres and three times the combined accuracy of the two fixes, so it blocks the punch and reports it to management.

The app also asks Google Play for an attestation of the device and the app, which the system verifies. Rejected attempts appear to administrators on the web only, never to the employee. A company can also turn on fingerprint or face verification on the phone before a punch is recorded, using a one-time challenge from the system valid for 5 minutes.

Fingerprint devices each have their own key and a log of what was rejected.

Integrations and privacy

How are partner integrations protected?

The read API works with scoped keys, so a partner gets the employees, attendance and payroll summary it needs and nothing more. System events (a new or departed employee, an approved or rejected request, a paid payroll run, a rejected punch) are sent to your system as signed webhooks, so you can verify that a message really came from TAC HR. See the integrations page.

What about rep tracking and location privacy?

Field tracking starts only after the rep agrees to location tracking during work hours. Tracking begins at check-in and ends at check-out or when the rep switches it off, so it does not continue outside work. See rep tracking.

Questions

FAQ

  • Can a branch manager see other branches' data?

    No. Each manager's permissions are scoped to the branches and departments assigned to them, so they see the employees in their own scope and not those of other branches. If the scope is left empty the manager sees the whole company, and the system administrator is never restricted by scope.

  • How many permissions does the system have?

    111 permissions in 24 groups, and that count comes from the permission catalog in the system itself. Each permission is granted on its own within the manager's role, so viewing, editing, deleting and approving are separated instead of one master key opening everything.

  • Can an employee punch from a friend's phone?

    No. The account is tied to the device the employee first signed in from, and someone on a new device is blocked and shown a dialog that sends a device change request. The requests reach management to approve or reject, and the new device is bound only on approval.

  • Can attendance be recorded with a fake location?

    No. The system rejects mock locations and their apps and rooted phones, the app blocks punches from an emulator, and the attempt is reported to management, who see it under rejected attempts on the web. These attempts are never shown to the employee.

  • Where do I see who changed an employee's data?

    On the activity screen tied to the audit log, which lists the important operations on the company's data. Salary changes have their own separate log in payroll, and a payroll run is locked after approval so no figure in it changes without a trace.

  • Can my accounting system receive TAC HR events?

    Yes. The main events are sent to your system as signed webhooks that you can verify, and a read API with scoped keys is available, so your accounting system reaches the employees, attendance and payroll summary it needs and nothing more.

  • Do employees sign in on the web?

    No. Employees use the mobile app only and do not sign in to the web portal, which is for administrators. So employee access is limited to the employee on their own bound device, and the administration screens stay with managers' accounts and their permissions.

  • Who can open the activity log?

    Only people the establishment grants the "view admin accounts" permission; anyone without it is redirected to the dashboard and never sees the log. The log shows only your own establishment's trail, never another's. It can be filtered by module, actor, date and search, and shows 50 entries per page. Employees do not sign in to the web portal at all.

Try it with your own permissions

Security is included in every subscription within the core platform. Isolation and permissions are not sold as a separate service. For prices see the pricing page.

Show us how you work, and we'll show you the difference.

In the demo we walk through a full day in your company: the morning punch, a request, the month's payroll, and the rep in the field, on data like yours.