[koenpunt]

Requested by Koen · project thread

Why

deliverybot/deliverybot#199 starts storing a history of the deployments Deliverybot creates (repository, environment, time, status) and shows it on the operators' admin overview. The policy only covered "the last event" and "the deployment state we need between events", and didn't say that operators can see this data. It also didn't mention that we record which repositories have a deploy config, which shipped in deliverybot/deliverybot#196.

Changes

• Repository data: also mentions whether a repository has a deployment configuration file.
• New item, Deployment history: deployment id, repository, environment, creation time and latest status. The deployment payload isn't stored.
• How we use it: says that the people operating the Service can see installation, repository and deployment details, for support and to see usage and whether deployments succeed.
• Updated date set to October 21, 2026.

Retention needs no change: deployment history is per-repository data, so it's deleted on uninstall or when a repository is removed, as the policy already says.

---

Generated by Claude Code