Your employees' time data never leaves your Odoo
We built it so that there is no other way.
How it works
The terminal talks directly to your Odoo. A clock-in travels from the device into your database, with no detour through our servers. We could not read your employees' attendance data even if we wanted to. There is no path by which it reaches us.
What our cloud sees at all
Only if you create an account, and even then nothing but technical facts about the device:
- Device name, serial number, the site label you choose (enthalten)
- Firmware version, uptime, queue length, error states (enthalten)
- IP address and signal strength (enthalten)
- The device configuration (enthalten)
- Clock-in times (nicht enthalten)
- Employee names (nicht enthalten)
- Badge numbers (nicht enthalten)
- Working hours and attendance lists (nicht enthalten)
What this means for you
Less data processing paperwork
For the attendance data itself we do not become your processor. The agreement you need covers device metadata only. That is a far smaller scope.
An argument that holds up with a works council
"The manufacturer cannot see our time data" is a statement you can demonstrate. Nobody has to take it on trust.
No dependency on us
If our cloud went down, your employees would keep clocking in. We are not a place where your operation can come to a halt.
Operated in Europe
What little device metadata exists is held in the EU.
Where the line is
This is also why the console shows you no entries. It cannot. Anyone who wants to analyse attendance does so in Odoo, where the data lives. Should we ever want to change that, it would be a deliberate decision on a new legal basis, not a quiet extension.
Questions from the works council?
We walk through the architecture with you, together with your data protection officer if you like.