Skip to the content

Set retention, legal holds and data-subject requests

Set how long Central Lite keeps each class of record, put a legal hold on the records a case needs, and answer a person's access or erasure request.

Built, not yet claimed preview: this guide describes a package that has not passed its release gate.

Set how long Central Lite keeps each class of record within its floor and ceiling, narrow the bounds with a retention profile, put a legal hold on the records a case needs on Central Lite and on every enrolled machine but CI runners, release it only with several admins' passkeys, and answer a person's access or erasure request by their pseudonyms.

1. Check the retention in force

Central Lite keeps each upload class for a number of days, counted from the record's arrival at Central Lite: security and audit 396 days (13 months), operational 90 and telemetry 30 by default. garm-central retention show prints the profile in force, each class's days with its default, floor and ceiling and the events due now, the profiles you can select, and any pending erasures. The desktop records of a Mac's computer-use airbag and capture monitor preview are security records; input that passes the airbag leaves none.

retention set CLASS DAYS changes one class within its bounds: 183 to 2,557 days for security and audit, 1 to 730 for operational, 1 to 365 for telemetry. A value outside them is refused, not moved, so evidence cannot be deleted early by configuration; the database holds the same bounds below the command. Each change is chained in Central Lite's audit log.

garm-central retention show
garm-central retention set security 730

Checked by the walk: this command ran as written on a Central Lite host.

2. Narrow the bounds with a retention profile

A retention profile may lower a class's ceiling or raise its floor, never beyond the defaults' bounds. The catalog ships standard (the bounds as they are) and eu-ai-act-deployer-logs (an operational floor of 184 days). For a works agreement, define your own with retention define-profile: each class it changes needs a reason, and the basis is chained. A profile something selects is neither redefined nor removed.

retention profile ID selects it for the org, and a value outside the new bounds moves to the nearer one; --node HOST selects one for a single machine, and --inherit returns it to the org's. Central Lite signs the settings for the nodes, which apply the profile to their own store within the machine's bounds. On a machine, the dashboard's Privacy & retention screen names the profile in force and whose it is, and how long each class is kept there. In the console, Transparency shows “Retention in force”, and “Compliance settings for nodes” selects a profile with “Select for the org with a passkey”.

garm-central retention define-profile works-agreement --name "Works agreement 2026" --description "The ceilings our works agreement sets for activity records" --basis "Works agreement of 2026-03-01, clause 7" --ceiling operational=60 --reason "operational=the agreement keeps activity records at most 60 days"
garm-central retention profile works-agreement

Checked by the walk: this command ran as written on a Central Lite host.

The dashboard's Privacy & retention screen: the profiles in force, what stays on this machine, and how long each class of record is kept

See also

Prepare a works-council or DPIA pack

Generate templates that describe what your deployment collects, keeps and sends, and switch the fleet to the non-monitoring profile during talks.

3. Run a retention pass

garm-central serve runs a retention pass when it starts and every hour (--retention-every, or off). retention run runs one now: events, delegations, recorded losses, cost rows and support bundles past their class's days are deleted page by page, each page chained with its counts, and pending erasures that are due are finished. It prints how many records each class deleted and how many a hold kept.

A pass never deletes what a standing legal hold covers. It never sweeps Central Lite's own records either: its audit chain, alerts, nodes, certificates, approvals and rollouts stay.

garm-central retention run

Checked by the walk: this command ran as written on a Central Lite host.

4. Place a legal hold

A hold's scope is all, a machine Central Lite knows (host: and its host id), a task (task: and its id) or a person by a pseudonym nodes upload (subject:kh1: and 32 hex digits). --class limits it to classes (none: every class), and --from and --until to a record-time range, inclusive, where a date alone covers the whole day. Placing one is a single admin action, chained with its reason; legal-hold list shows the holds that stand, and legal-hold show one hold with its release requests.

The hold also reaches every enrolled machine but CI runners, in a list Central Lite signs, without its reason, on the machine's next delivery over the control channel, not at once (an offline machine gets it when it next connects). There it stops retention, shedding, checkpoint clean-up and rollback for what it covers, and agentgarmd legal-hold list shows it as placed by central: and your org; if the hold is not there yet, the delivery has not arrived, so run it again. A machine cannot match a person's pseudonym, so a subject: hold holds everything on it; root cannot release a hold Central Lite placed.

Exporting a task's evidence bundle from Central Lite places a task: hold on that task for you, or reuses one that stands, so the records behind a bundle you handed out are not deleted; it reaches the machines like any other hold and is released the same way. A task: hold covers the task's records, whoever wrote them inside it, and nothing else. An export on the machine places no hold: it prints the agentgarmd legal-hold place --scope task: command to run. The bundle itself is a file outside both stores, which retention never reaches.

garm-central legal-hold place --scope all --class security --class audit --from 2026-10-01 --until 2026-10-31 --reason "case 2026-17: keep October's enforcement evidence"
garm-central legal-hold list
sudo agentgarmd legal-hold list

Checked by the walk: these commands ran as written on a Central Lite host and a Linux node enrolled in Central Lite, and the output showed placed by central:.

5. Release a hold with several admins

A release takes M distinct admins' passkey assertions over a challenge bound to the hold and the request; the console has no legal holds screen, so this is done on the Central Lite host. legal-hold release opens a request that lives 24 hours by default (5 minutes to 72 hours). M is 2, or 1 when the org has a single admin, which is warned; --required raises it, up to every admin who may approve. Only admins holding owner, or security for the whole org, with a passkey count and may approve, each from 24 hours after that role was bound (roles and legal holds); an admin SCIM suspended counts for nothing. Each admin reads legal-hold challenge, signs its input with fido2-assert and submits it with legal-hold approve.

An admin counts once, user verification is required, and an admin or passkey added less than 24 hours earlier is refused. The M-th approval releases the hold and signs the list that releases it on the machines. M of N binds admins, not whoever controls Central Lite's host, who holds its state directory and keys; the 24-hour rule, the alerts and the chain make an approver made there visible first.

garm-central legal-hold release HOLD_ID --reason "case 2026-17 closed"
garm-central admin list
garm-central legal-hold challenge RELEASE_ID
garm-central legal-hold challenge RELEASE_ID --credential-id CREDENTIAL_ID > assert.in
fido2-assert -G -p -v -i assert.in -o assert.out DEVICE
garm-central legal-hold approve RELEASE_ID --admin alice --assertion assert.out

6. Export a person's records

Central Lite holds a person only as pseudonyms, keyed hashes nodes compute before upload. With --identity-stdin, garm-central dsar export reads an identifier, such as a login name or an email, from stdin and computes its pseudonym in every personal field; the identifier is never stored or logged. Or name pseudonyms directly with --subject kh1:…. It writes the matching events, delegations and per-principal cost rows, held ones included, to a new 0600 file as JSON Lines, and the export is chained with its counts.

The file's first line lists the pseudonyms; each event is as the node uploaded it, base64 and pseudonymised. A person's clear records stay on their machines: there, agentgarmd dsar export writes one user's tasks, events and decisions, by uid.

With SCIM provisioning, Central Lite also holds each person your identity provider sends: their userName, display name, externalId, whether they are active, their groups and, if you chose one, the login attribute. Emails, phone numbers, addresses and every other attribute are dropped as the request is read and never stored. In the console, names, identities at the provider, a timeline's person-level view and evidence exports are shown only to roles allowed to see people: viewer and finops are not (what each role sees).

printf 'alice\n' | garm-central dsar export --identity-stdin --out alice-dsar.jsonl
sudo agentgarmd dsar export --uid UID --out alice-machine.jsonl

Checked by the walk: this command ran as written on a Central Lite host.

7. Erase a person's records

garm-central dsar erase takes the person as the export does, with a reason, and deletes the matching records. What a standing hold covers is kept, and so are security and audit events that arrived less than 183 days ago (or inside a floor a profile raised): the command prints them as pending, and a later retention pass erases them once the hold is released or the floor has passed. When anything was deleted, Central Lite writes a fresh backup and crypto-shreds every earlier one, so no backup still holds what was erased. Its database zeroes the deleted rows' pages and truncates its write-ahead log, and a restore's replaced database or a crashed backup's scratch copy is removed; what the disk itself keeps of old blocks is for the host's full-disk encryption to cover.

Central Lite's audit chain is not erased: its records carry counts and the reason, never a pseudonym. Machines have no erasure yet: their records leave by their own retention, and their audit chains are never pruned.

printf 'alice\n' | garm-central dsar erase --identity-stdin --reason "erasure request 2026-04"

Checked by the walk: this command ran as written on a Central Lite host.

See also

Back up and restore Central Lite

Write Central Lite's encrypted backups by hand and on a schedule, and restore one so that no enrolled node refuses what Central Lite signs next.