Data and retention
The account is an email address. A job is a URL, a method, headers, a body, a schedule and a timeout. A run is the scheduled time, the actual start, the status code, the duration and the egress location.
Header values are encrypted at rest. They stay masked in every list, every export and every API response. Revealing one of them on the edit form is the only place a stored value appears.
| Data | Kept for |
|---|---|
| Run history, per job | 100 runs or 30 days |
| Jobs | While the account exists |
| Paused jobs, untouched | 90 days, with a warning at day 76 |
| Dormant accounts | 12 months without a sign-in |
| Sessions | 30 days, or until sign-out |
| Server logs | 7 days |
Nothing from a response body is stored at any point. Full detail sits on the privacy page.