Transparency

What data. And why.

A practical overview of data used in TapInn.

Typical data types
DataPurpose
User and role dataData always belongs to one company (tenant). Before anything is read or changed, the API checks that you are signed in to that company and have a role that grants access. If a module is not activated for the company, the API stops the request, so the feature is not just hidden in the menu.
Work hours
  • Work sessions and timestamps
  • Approval, deviations and export history
The core of TapInn is documenting work hours and related events such as breaks, check-out and approval.
Location
  • Location data at specific events
  • Locations, geofences and work assignment
Location is used when necessary to verify a specific action, not as general surveillance.
Attachments and documentation
  • Tasks, comments and attachments where activated
Tasks and photo evidence can be included when a customer actively uses these features as part of their workflow.
Operational dataIn addition to domain information, there is technical metadata needed for operations, security, debugging and session control.

Data handling

What we use, and why.

This page describes data types and processing purposes at a high level. It is meant as a technical supplement to the privacy page, not a legal substitute.