Data retention
How long Libretto Cloud keeps job results, debug artifacts, and logs.
These are the default retention periods for hosted Libretto Cloud. Custom retention periods can be negotiated. Email
team@libretto.sh if you need a different window.See also the privacy policy.
Defaults
| Data | Default retention |
| Job results and run history | For the life of your workspace |
| Saved credentials | Until you delete them, or the workspace is deleted |
| Deployed workflow code | Until you delete the workflow |
| Failure screenshots and page HTML | 90 days |
| Executor and workflow logs | 30 days |
| Session recordings | 30 days, for runs that captured one |
Job results are the
result payload on POST /v1/jobs/get and on job.completed webhooks. Libretto Cloud does not automatically delete job history. Failed and cancelled runs keep their error and stack instead of a result.Failure screenshots and page HTML are captured when your workflow code throws or times out, so a run that fails before your code starts may have neither. Signed download links are short-lived; request a new one when a link expires. The files themselves follow the 90-day window.
Executor and workflow logs are the records returned by
POST /v1/logs/list. When a run fails and Libretto Cloud prepares a debug report, the logs it collected are stored alongside the other debug artifacts for that run and follow the 90-day window instead.Session recordings are available through
POST /v1/recordings/get. Headful runs, the default, are recorded; runs created with headless: true are not, and neither are runs that fail before a browser starts. A recording is kept for 30 days, and viewing links can expire sooner than that, so request a new link if one stops working while the recording still exists.Custom retention
If you need a longer or shorter retention period, email
team@libretto.sh. Custom retention can be negotiated for job results, logs, and debug artifacts.Deleting data
Delete saved credentials with
POST /v1/credentials/delete and workflows with POST /v1/workflows/delete.Owners can delete their account from the dashboard, under account options on the users page. If you are the only member of the workspace, this also deletes the workspace, its job history, credentials, workflows, and API keys. In a shared workspace it removes your own access and leaves workspace data in place, and a sole owner has to promote another owner first. Debug artifacts already in object storage age out on the schedules above rather than being purged at the moment of deletion.
To delete job history without deleting the workspace, email
team@libretto.sh.