K-workK-work
ExploreBecome a partner
K-workK-work

The operating system for your workspaces.

Product

  • Spaces map
  • K-work+
  • Pricing
  • Indice K

Resources

  • How it works
  • Flex office
  • Office with no commitment
  • Become a partner
  • K-work guides
  • Spaces by city

Legal

  • Legal notice
  • Privacy policy
  • Cookie policy
  • Terms / Sales
  • Terms of sale (Pro)

Contact

  • contact@kwork.fr
  • LinkedIn
Télécharger dans l’App StoreDisponible sur Google Play
La French TechMembre du pool
French Tech Rennes Saint-Malo

© 2026 K-work by KBEEN SAS. All rights reserved.

Rennes, France

Trust

What K-work does not do

A page to show your works council. It says what the tool does not measure, what the employer, the manager and colleagues see, and how long each piece of data stays. Every sentence describes the product as it works.

Checked against the code on 25 September 2026. The privacy policy prevails.

What K-work does not do

No location tracking

Office attendance is declared by the employee (office, remote, travel, absent): it is never inferred from a GPS position or a Wi-Fi network. When a space booking is checked in from the app, the phone’s position is used to confirm the person is on site: only the distance to the space and the accuracy of the reading, in metres, are recorded with the booking, never the position.

Nothing on computers

K-work installs no monitoring software: no keystrokes, no screenshots, no time spent in applications.

No camera, no microphone

The K Sense sensor measures CO2, temperature, humidity, light and infrared presence. It knows a space is occupied, not by whom; if the space is booked, that presence confirms the booking.

No reports to the manager

When a week has not been declared, the reminder goes to the employee, and to them alone. No real-time alert about a person: the only named message is a periodic summary to HR or administrators, which the company must switch on (off by default).

No automatic sanction

The company’s attendance rule blocks no booking and writes to no file. One day more or less can be read, that is all.

No named comparisons

Comparisons with other companies only appear aggregated over at least five companies, and never point to a person.

Who sees what

What the company administrator sees

  • For each employee, the number of days declared at the office in the week and the gap to the attendance rule. Not the reason for an absence.
  • For payroll, a monthly count per employee of days declared at the office, remote, travelling or absent.
  • The company’s desk and room bookings. An employee who hides their presence does not appear by name: their place stays “taken”, without a name.
  • Occupancy of spaces and buildings, in figures.
  • Through the enterprise API, counts only, with no time of day: never a name, an email, an account identifier, nor any booking one by one. Counts are hidden below 5 distinct people; a group that is too small is merged (a zone into its building, a building into the company), never published on its own; a completed day is published once and then never changes. A person’s visibility does not change past figures: a count names no one, it counts everyone.
  • If the company switches it on (off by default), a weekly or monthly summary of gaps to the attendance rule, sent to HR or administrators, never to the employee, and factual: “2 days declared for a minimum of 3”.

What the manager sees

The declared absences and trips of their team, to organise the work, without the reason. A member who hides their presence is not listed: they are counted, never named.

What colleagues see

Who will be at the office on which days, so people can meet up. Anyone can hide their presence: they then disappear from the floor plan and the team view, and no longer see the others’ days.

What the lobby screen shows

By default, nobody who is present. The company can choose to display their number, their first name and last-name initial, or their first and last name (“names” mode): anyone passing through the lobby, visitors included, can then read them. Anyone who has hidden their presence is counted there, never named.

How long data is kept

Beyond the stated period, data is automatically deleted or anonymised. Where a row says there is no automatic purge, the data stays as long as the account exists.

DataPeriod
Attendance declarations, day by day (office, remote, travel, absent)No automatic purge: kept as long as the account exists, even after leaving the company, then deleted with it
Desk, parking and locker bookings, with the check-in timeNo automatic purge: kept as long as the account exists, even after leaving the company, then deleted with it
GPS distance and accuracy when checking in to a space booking (in metres, never the position)With the booking, as long as the account exists
Raw K Sense sensor readings (CO2, temperature, presence)In normal operation, 23 to 24 hours after receipt by the server. The hourly purge removes readings older than 23 hours; a failed purge can delay deletion. Afterwards, only averages with no identity remain.
Visitors’ name, email, phone, company and purpose of visit90 days after the visit by default (7 days to 3 years, chosen by the company), then anonymised
Audit log: payments, bookings, check-ins, administrators’ actions13 months
K-work team log: sign-ins and actions in its administration tool13 months
Usage log of enterprise API keys13 months
Private messages between members13 months
Availability probes (status page)90 days
Notification identifiers of an inactive device6 months without activity; as the purge runs once a month, an inactive identifier may remain for up to about 7 months
Account deleted at its holder’s requestErased 30 days after the request, within the following hour, except records the law requires us to keep (invoices: 10 years)

The reference

This page summarises. The privacy policy prevails; any question from the works council or an employee can be sent to our data protection officer.

Privacy policyService statusprivacy@kbeen.fr