Security and trust

How Time Sense keeps each organisation's data separate, controls who sees what, and records who changed it.

Each organisation's data stays its own

Every organisation's data sits behind a tenant filter that fails closed.

Every read is limited to the caller's organisation, and every write is checked before it is saved.
Uploaded files and live updates stay inside the organisation too.

Roles decide what people can do, and each role assignment decides whose data they can see.

Role-based permissions, managed role by role.
Narrow any role to a company, entity, work location, group or individual employees.
Live dashboards and streams respect the same scope.

Changes are recorded with who made them, when, and what changed.

Before and after values for each change.
Every mobile app request and response is audited, with the channel it came from.
App error reports carry no personal data.

Face data is used only with consent, and withdrawing consent takes effect everywhere.

Each acceptance and withdrawal is recorded on the server, and HR can record consent on an employee's behalf.
Withdrawing consent removes the face from every face kiosk.
Kiosk camera frames are never stored or logged, and the phone's selfie stays in memory only.

Keys and passwords that Time Sense needs to reach other systems are stored encrypted, and never shown again once saved.

AI provider keys are encrypted at rest and decrypted only in memory when a call is made.
Integration credentials, such as ERP and sign-in secrets, are stored encrypted.
The face gallery on each kiosk is kept in encrypted storage on the tablet.

Sign-in, browser headers, exports and device traffic are each hardened against the attacks they attract.

Sign-in is throttled, and resists password spraying and account guessing.
Security headers on every response, and idle sessions sign out on their own.
Exported spreadsheets neutralise injected formulas, and emails encode what they show.
Device and kiosk traffic is throttled, size-limited and checked.

Use Time Sense as a cloud service, or install it on your own servers under a signed licence.

The licence is signed, your server verifies it, and only a verified licence turns features on.
A guard stops the licence clock from being wound back.
The signing key stays with Time Sense and never ships with the software.

Book a demo and we will walk through your shifts, devices and approvals, in English or Arabic.