This article tells you what Kelomo stores about you and what it does not store.
Working-time data is the employer’s data
The working time you do for your employer is the employer’s data, not your personal data. In practice that means this:
- Your supervisor and the administrator see your entries, including the drafts – that is, also the days you have not confirmed yet.
- They can edit and manage them.
- They can act on your behalf.
- Every such action leaves a trace in the audit log.
The log makes what happened traceable, but does not prevent any action.
Only the timing from the calendar
If you connect your calendar, Kelomo fetches only the timing of the entries: the start, the end, the duration and the type. Titles, contents or participants are not fetched from the source at all.
Some entries are always skipped: private ones, ones marked as free, cancelled ones and all-day events. See Connect your calendar.
Location when you punch
The employer chooses the level. There are four options: no location is stored, the site is stored, the at-site information (yes or no) is stored, or the coordinates are stored.
The at-site information is computed on the server, and at the geofence level alone no coordinates are stored at all.
There is no background tracking. The location is read once at the moment of the punch, not continuously, and no route log is created. Before the first capture you see the employer’s own notice text.
The location has a retention period, after which the location data is cleared. The punch itself remains, because working-time bookkeeping must be retained. The presence board never shows coordinates. See Clock in and out.
What Kelomo does not have
Kelomo has no screenshots, no keystroke monitoring, no activity percentages and no productivity scoring. This is the current state, not a promise about future versions.
The audit log
The log tells who did what and when. It also covers the supervisor’s and the administrator’s actions on your data.
The log stores the event, not its contents: “Contents are never logged, only the event.”
Where the data is located
- The database, the application infrastructure and the attachments: Hetzner Online GmbH, Helsinki.
Some sub-processors are outside the EU/EEA under standard contractual clauses: payments (Stripe) and AI features, the latter only if they are in use.
Kelomo is the processor, your employer is the controller. If you want to know what has been stored about you, or to request the erasure of your data, the request is addressed to your employer. Kelomo does not answer it directly but directs it to the employer.
If something goes wrong
You want to know what has been stored about you. Ask your employer for the data. The administrator gets the whole personal-data package out with a single action – see GDPR: access requests, retention and erasure.
You do not want your calendar included in the proposal. This is up to you. Switch Use the calendar in the proposal off on the Automation page or press Remove connection.
You do not want your location stored when you punch. The employer decides whether location is stored. It cannot be switched off in the app – raise it with your employer.