Hodeitek S.L. prepares this document so that your organisation can give it to its employee representatives and its data protection officer (DPO). It describes what the agent does today. Anything decided but not yet applied is marked "planned, not yet in force". This document does not claim that installing the agent ensures compliance with any regulation.
1.What the agent is and why the company installs it
The HodeiShield agent is a program your organisation installs on work computers to check, continuously, security settings of the computer itself (for example, whether the disk is encrypted) and to send the result to the organisation's console. Your organisation installs and manages it and decides what it is used for. It is designed to provide evidence of controls over how computers are configured, not to watch people.
2.What it collects
| What | How often |
|---|---|
| The result of each security check: check code, status (pass, fail, not applicable or error), severity and time of the observation | By default every hour (up to 10 % earlier, never later); the organisation can change the interval. When offline, it is stored encrypted on the computer and sent later |
| The computer name (only if it is a valid network name). It is personal data if it names a person | With every send |
| Up to 16 network addresses of the computer | With every send |
| The operating system (family, name, version and architecture) | With every send |
| Supporting data for each result: at most 32 pairs and 4096 bytes, only yes/no values, numbers and short words from an allow-list | With every send |
| The agent's technical identity and the signature of the send | With every send |
The "pulse". There is no separate heartbeat message: what the console shows as the "pulse" is the send of results itself. Because the agent sends every hour by default, the console can show in which of the last 24 hours a computer sent data, and it stores the time of each observation. That reveals when a computer was switched on, with caveats: a gap of up to 2 hours is normal and, if sends fail, of up to about 4 hours; a paused computer sends no results; and a computer whose credential the platform has refused only sends a probe batch now and then. So a missing pulse does not prove the computer was off.
| Call | When | What it carries |
|---|---|---|
| Sending results (the "pulse") to your organisation's console | Every hour by default. After a failure the next send is delayed, up to 4 hours at most. Not sent while paused | The results due in that cycle (not every check is evaluated every cycle) and the inventory (computer name, up to 16 network addresses and operating system), signed |
| Sending what was stored offline | After the normal send and only if something is stored, for at most half a cycle | Results stored earlier |
| Probe after a refusal | Only if the platform refuses the computer's credential or a send. First probe after 1 hour; the interval grows up to 24 hours at most | One batch of results |
| Enrolment | Once, when the computer is enrolled (up to 3 attempts with the same data) | The agent's public key, a single-use code, the computer name and the agent version |
| Changing the agent's key | Only when an administrator runs it | A new public key |
| Checking for updates | Linux only, every cycle (also while paused), unless the computer has opted out of updates. Windows and macOS do not make this call | Nothing about the computer; like any web server, the release store sees the IP address and the time |
| Asking the console for permission to update | Only if a newer version exists | The agent identifier, the current and candidate versions, the operating system, the architecture and the channel, signed. No results and no computer name |
| Downloading the update | Only if the console allows it | Nothing about the computer |
| Diagnostics | Only if an administrator runs it on the computer | One status request |
| Error report | Only on a failure; can be switched off on each computer | See section 4 |
| Status window and tray icon | Never | Nothing: they make no network call |
While paused. An administrator can pause a computer. While paused, the computer sends no results; on Linux it keeps checking for updates.
3.What it does NOT collect (according to the agent's code)
This list describes the agent's code; network traffic has not been measured on a real computer.
- The agent has no field for sending files, documents, browsing history, or the passwords or credentials of users' accounts.
- It does not read the content of system logs: the checks look at the configuration.
- It does not collect user or account names: the checks report states and counts ("encrypted: yes").
- The MAC address of the network card is not sent.
- The agent's private key never leaves the computer; only the public key travels, at enrolment.
- There is no heartbeat, ping or permanent connection apart from the calls in the table above.
The supporting data of each result goes through an automatic filter before it leaves; that filter recognises patterns, not meaning.
4.Who sees it
- Your organisation, the controller. Today, the hour-by-hour pulse and the time of each check are seen by every console user in your organisation who has the endpoints module; network addresses and the supporting data of each result have role-restricted access. Planned, not yet in force: limiting the pulse and the time of each check to endpoint administrators and reducing them, after 30 days, to state changes and one last contact per day. This document will be updated once that change is applied.
- Hodeitek, the processor, on behalf of your organisation.
- Hodeitek's sub-processors: OVHcloud (hosting, database, storage and logs; Aiven Oy runs the managed PostgreSQL database on OVHcloud's behalf) and Cloudflare, Inc. (DNS, delivery network, firewall and TLS; transfers to the US under the EU-U.S. Data Privacy Framework). The full, current list is at the sub-processors page.
- Agent error reports. Functional Software, Inc. (Sentry), in its European Union region, becomes Hodeitek's sub-processor for the agent's error reports from the fifteenth calendar day after the later of these two dates: the publication of the notice on the sub-processors page and its sending by email to your organisation's contract contact. Until then, Hodeitek processes those reports as controller. Sentry receives a report only on a failure: the scrubbed error message and trace, the process's most recent log lines, the agent version, the operating system and kernel version, the architecture (on macOS, the hardware model) and the memory addresses of the trace, with no user data. It does not receive the computer's name or identifier. The connection's IP address arrives with the transmission; Sentry is configured not to store the IP address (last checked on 6 October 2026); an approximate location (country, city) may still be derived from it. Reports can be switched off on each computer.
- The employee sees five checks on their own screen: disk encryption, firewall, screen lock, automatic updates and agent health.
5.Retention
| Data | Period | Status |
|---|---|---|
| Check results | 365 days from receipt: one year, to cover a yearly audit cycle | Planned, not yet in force |
| Hour-by-hour pulse and time of each check | 30 days in full; after that, only each state change and one last contact per day | Planned, not yet in force |
| Inventory (computer name, network addresses, operating system) | While the computer is enrolled; deleted when it is revoked. A computer that sends nothing for 90 days is revoked automatically | Planned, not yet in force |
| Identity of a revoked computer and enrolment records | 365 days after revocation | Planned, not yet in force |
| At the end of the contract | 30 days to ask for the data back; deletion within 30 days of the request | Planned, not yet in force |
| Backups | 2 days (database) and 14 days (automations) | Planned, not yet in force |
| Offline queue, on the computer | Until sent or until the computer is removed; at most 10,000 items and 32 MiB | In force |
| Error reports (Sentry) | 90 days, according to the Sentry account settings | Service setting |
While a period is marked "planned, not yet in force", data may be kept longer than stated. This document will be updated as each period is applied.
6.Legal basis
The controller is your organisation, which decides the legal basis. The usual basis for processing of this kind is the organisation's legitimate interest and its security obligations. HodeiShield does not decide it: it is a question for your organisation's DPO. This document does not replace that analysis (the balancing test and, where needed, an impact assessment).
Depending on the country, rolling out the agent may require informing or consulting employee representatives, or reaching an agreement with them (for example in Germany, France and Italy). Please check with your DPO or employment adviser before deploying the agent.
Informing the people who use the computers and, where applicable, their representatives is your organisation's responsibility. Hodeitek provides the agent documentation for that purpose.
7.The notice the employee sees (according to the agent's code)
- The status window and the tray icon always show the status of the five checks and make no network call.
- The desktop notice is optional and has three levels that the organisation sets for all its computers, never per person: off; discreet (the default: no desktop notice, and the window and tray show the failing control); and active (one notice when a control starts failing, with no reminders). The notice only says "There is something to review. Open the HodeiShield window to see it.", never which check, which computer or how many.
- Planned, not yet in force: with a new version of the agent policy, the window will show your organisation's regulatory frameworks (on by default; the administrator can switch it off) and, if the organisation sets one, the support contact it chooses.
8.Employee rights and whom to contact
Employees can exercise their rights of access, rectification, erasure, restriction, objection and, where applicable, portability (GDPR, Articles 15 to 21) with your organisation, as controller. The first contact is the DPO or the contact your organisation designates. Hodeitek, as processor, assists the organisation: if a person writes to privacy@hodeitek.com, Hodeitek passes the request on to the organisation. They can also complain to the competent data protection authority.