From 757bf81cb95edde6ade1312d2d67d8e96586688c Mon Sep 17 00:00:00 2001 From: Mohamed Boudra Date: Thu, 10 Sep 2026 08:21:13 +0200 Subject: [PATCH] docs(hub): clarify credential storage and retention --- public-docs/hub/github.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/public-docs/hub/github.md b/public-docs/hub/github.md index b3b77a4e16..c23f7a11d5 100644 --- a/public-docs/hub/github.md +++ b/public-docs/hub/github.md @@ -79,4 +79,8 @@ env: SOME_TOKEN: "${{ paseo.connections.some-connection.token }}" ``` -Hub persists resolved values as private execution data so it can recover after a restart. Authored configuration retains the expressions. See [Hub security](/docs/hub/security) for provider and host boundaries. +Hub persists resolved values as private execution data so it can recover after a restart. Authored configuration retains the expressions. + +These values are stored in the Hub database without application-level encryption. Protect database access, storage, and backups as credentials. Hub deletes the execution authority record when the execution becomes terminal; token lease records remain until revocation succeeds or the token expires, so interrupted cleanup can resume. This cleanup is not a guarantee that every copy is erased: retained agent/session data and database backups may still contain resolved values. Token revocation ends access; it does not erase those copies. Backup retention and deletion remain the operator’s responsibility. + +See [Hub security](/docs/hub/security) for provider and host boundaries.