Skip to content
El Registro Retributivo .com

Trust

What we do with your team’s salaries

We are going to hold the sex, the job category and the pay of each person in your company. 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

    All communication goes over HTTPS, with HSTS on the website and in the application. The data stored in Firebase (Google Cloud) is encrypted at rest by the provider itself, which manages the keys.

  • Role-based access

    Administration, HR, advisers, employee representatives and each worker see only what is theirs, and this is decided by the database rules, not just by the screen. A worker only sees their own record; the representatives’ access expires and hides from them any group with fewer than three people of one sex.

  • Access log

    Every salary query, every export, every closing and every deletion leaves an event in an append-only audit chain. The event records who, when and what, with identifiers and counts: never amounts or anyone’s sex.

  • Closed versions with a fingerprint

    A closed record is kept exactly as it is: the database rules prevent every account, including the support account, from modifying or deleting it. A correction is a new version pointing to the previous one, and each version carries a SHA-256 fingerprint chained to the one before, so any later alteration can be detected when it is verified.

  • Backups

    In preparation: before the service opens there will be copies outside the database, with tested restoration, and their real frequency will be published. No backup is promised today.

  • Second factor

    In preparation for the opening of the service: it is already programmed with an authenticator app (TOTP; SMS is not accepted). The server and the rules require it to see salaries, closed versions and audits.

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 special category data. For each person we collect their sex, because the record is broken down by sex (art. 28.2 of the Estatuto de los Trabajadores). Nothing about health, trade union membership, origin, religion or any other data under article 9 of the GDPR.
  • No biometric data. No fingerprints, no faces: the application has no way of asking for them.
  • No location. The application neither asks for nor stores anyone’s position.
  • Nothing from computer activity. No screenshots, no keystrokes, no pages visited.

A breach in our system would be a serious problem, because there are salaries in it. That is why individual salaries are never read directly from the database: only the server provides them, with a second factor and an audit event for each query.

Documentation

What we can hand over

Some of these documents are only available 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 of the GDPR, which you can read in full.
Do you use the data for anything else?
Only to provide you with the service. Not to train models, not to produce commercial statistics, not to sell it.
Where is it hosted?
The server functions are configured in Frankfurt (Vercel). The database region (Firebase) will be chosen within the European Union when the project is created and will be published here; today it is still to be verified. The 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. The administration exports the company’s data by section (company, staff, periods, closed versions and audit) in JSON or CSV, and each person can export their own. Every export carries a SHA-256 fingerprint to check it has not been altered and is recorded in the access log.
What happens if I cancel?
The administration requests the closure of the company account after confirming it has downloaded the full copy, and has thirty days to change its mind. Once that period ends, access is closed, invitations are deleted and the staff records are pseudonymised. Closed records and the data supporting them are kept because of a legal obligation (art. 17.3.b of the GDPR), for a planned period of four years, pending the owner’s decision.
Do you have ISO 27001 or Esquema Nacional de Seguridad certification?
Neither of the two. We say so plainly instead of using vague phrases such as “aligned with”. If we ever have one, we will put it here with its number.

The official sources are in Spanish.

Free until 31 May 2027 inclusive. 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.