Trust
What we do with your team’s data
We are going to hold, for four years, the time at which each person in your company starts and finishes work. It is reasonable to want to know how, and to be able to check it before you sign.
Measures
Concrete security measures
Encryption in transit and at rest
TLS on all communication and encrypted storage. No exceptions and no legacy pages left unencrypted.
Role-based access
Each profile sees what is theirs to see. The view for the employee representatives is served from the server without the fields excluded by art. 6.2 of the draft Royal Decree, which is still in the legislative process. With that role, the database rules no longer allow reading the raw entries (since 19-10-2026): only that view is seen.
Access log
A record is kept, with who and when, of people being added or removed, role changes, approvals, modifications, closings, exports and Inspectorate access through a temporary link.
Entries that cannot be altered
Modifying and deleting clock-ins is forbidden by the database rules, not just in the interface: no account in the application can do it, including your company’s administration. In addition, each entry is chained to the previous one with a SHA-256 fingerprint and the chain is sealed every day, so any later alteration can be detected when it is verified; there is no electronic signature on each entry.
Backups
In preparation: before the service opens there will be encrypted copies outside the database, with tested restoration, and their real frequency will be published. Keeping copies that nobody has ever tried to restore is not having backups.
Second factor
In preparation: not available yet. Today you sign in with a verified email and a password; the second factor will be announced when it exists.
What we do not collect
The best protection is not having the data
Data that does not exist cannot be leaked, lost or misused. That is why the most important security decision we have made is what we do not keep:
- No biometric data. No fingerprints, no faces. It is a special category under article 9 of the GDPR, and a breach involving biometric data cannot be fixed by changing a password: a fingerprint cannot be rotated. Why (in Spanish).
- No continuous location trail. Only the point at the moment of clocking in, and only if you switch on geofences.
- Nothing from computer activity. No screenshots, no keystrokes, no pages visited.
- No diagnosis or clinical data. The fact that someone is on sick leave is recorded as an absence, only with its type and dates, and its visibility is limited by role; nobody gives us the diagnosis.
It is also the reason why a breach in our system would be a serious but limited problem: what is there is clock-in and clock-out times, not anyone’s private life.
Documentation
What we can hand over
Data processing contract
The one under article 28 of the GDPR. You can read it in full before signing.
Template for your team
The prior information that you have to give to your employees.
Verify without depending on us
How to check a receipt, the chain of entries or an expert-evidence package on your own.
Recording protocol
The document required by article 7 of the draft Royal Decree (still in the legislative process), generated from your configuration.
Some of these documents are only available in Spanish.
Where the data is and who processes it for us is covered in data transparency (in Spanish); which parts of the service are working and what commitments we make in the event of an outage or a breach, in the service status (in Spanish); and who is behind the company, in who we are.
Questions
What people usually ask us
- Who is responsible for the data?
- Your company. We are the processor and handle the data on your behalf, following your instructions. That is why there is a data processing contract under article 28, which you can read in full.
- Do you use the data for anything else?
- No. Not to train models, not to produce commercial statistics, not to sell it. We process the data to provide you with the service and nothing else.
- Where is it hosted?
- The server functions are in Frankfurt; the location of the database is being confirmed with the provider. Some providers belong to groups headquartered in the United States, so there could be international transfers, covered by the safeguards of Chapter V of the GDPR. The detail is in the data processing contract.
- Can I take my data with me?
- Whenever you want, including the day you cancel. A full export of the four years in CSV, Excel and PDF, without asking in writing or waiting for anyone. There is also a complete copy of the company in JSON, an open format, with a fingerprint that lets you check it has not been altered.
- What happens if I cancel?
- Closing the company account requires having downloaded the full copy first: the application asks you to confirm it. When it is applied, the company’s access is closed and the data that is not part of the working-time record is deleted; the record is kept for four years (art. 34.9 of the Workers’ Statute), and whoever administered the company and each worker (only with their own records) can download it free of charge, without being able to clock in or change anything. Your team’s data is not held hostage by the subscription.
- Do you have ISO 27001 certification?
- Not yet. We say so plainly instead of using vague phrases such as “aligned with”. It is in the work plan, and when we have it we will put it here with its number.
- RGPDReglamento (UE) 2016/679, arts. 28 y 32
- BOELOPDGDD, Ley Orgánica 3/2018
- AEPDGuía de control de presencia con sistemas biométricos (PDF)
The official sources are in Spanish.
Free until 31 May 2027. Just your email.
No card and no billing details: your email is all you need to start. You register your team in five minutes and you clock in today.