Settings
Privacy settings
Frost stores its history on your machine and nowhere else. You decide how long it lives, and you can delete it at any point.
Everything is local
The Privacy page starts by saying what Frost does not do, because it is the part that matters most: there is no backend, no analytics, no telemetry and no crash reporting. Your access token, the accounts Frost discovered and the history of its runs are written to a file on your machine and nowhere else. Security & privacy →
The two controls on this page are about how long that local data lives.
Retention period
How long Frost keeps a record of past refreshes. Runs older than this are deleted automatically.
| Option | Good for |
|---|---|
| 1 day | Keeping essentially nothing while still being able to look at today's failure. |
| 3 days | Covering a long weekend. |
| 7 days (default) | Enough to spot a pattern — "it fails every morning" — without accumulating much. |
| 14 / 30 days | Chasing something intermittent, or gathering evidence for a bug report. |
The same period governs log files. Frost writes one log file per day, and they are swept on the same schedule — so the run record and the log describing it disappear together, rather than the log outliving the history that pointed at it.
Pruning runs at startup and again the moment you save a shorter period, so shortening retention takes effect at once rather than waiting for the next refresh.
Delete History
Erases every stored run immediately, whatever the retention period says. Frost asks for confirmation first — this cannot be undone.
This clears the run history only. It does not sign you out, does not
touch your settings, and does not remove the profiles in
~/.aws/config or the contexts in ~/.kube/config.
Log files are removed on their retention schedule; delete them by hand if
you want them gone now — the paths are in
files & locations.
What a run record contains
- when it started and ended, and whether it succeeded;
- the accounts you could reach — names and ids — and their permission sets;
- the profile names Frost generated;
- the EKS clusters found, with region and profile;
- error text for anything that failed, including AWS request ids.
The access token, the OAuth client secret and the sign-in device codes are never written into the history or the logs. Activity & logs →
Removing everything
To take Frost off a machine completely: quit it, delete the application,
and delete its configuration file and log directory
(paths here). What remains afterwards is the
profiles it wrote in ~/.aws/config, the token cache in
~/.aws/sso/cache/ and the contexts in
~/.kube/config — all of them plain text files you can edit or
delete yourself.