Shiplog

Local workspace

What this browser
is keeping

Every decision and release you record lives in this browser and nowhere else. This page says what is there, how sure it is about that, and the one thing worth doing next.

Everything below stays in this browser.

Shiplog has no account and keeps no server-side copy. The decisions and releases you record are held in this browser's local storage, on this device, under the two keys named in “Where these numbers come from”. Nothing on this page is uploaded, and no cookie, analytics call, or telemetry reads it. Clearing this browser's site data — or erasing below — removes the records, and no copy survives anywhere else.

What is retained

Reading this browser's stored records…

Storage
Not read yet
Retained
Counting…
Confidence
Not read yet

Do this next

Reading this browser

Counting the decisions and releases stored here, and checking whether every one of them can still be read. This page will name one thing to do as soon as it knows.

What you can do

Keeping records

Checking whether this browser is set to keep records…

Backup

Downloads one JSON file holding every decision and release stored here. The file is written in this browser; it is not uploaded anywhere.

Restore

Choose a backup this page wrote. It is read in this browser only, and nothing is stored until you confirm the summary.

Erase

Removes every Shiplog record from this browser. There is no other copy, and this cannot be undone from here.

Where these numbers come from
Sources
Read once this page has finished checking this browser's storage.

AI FinOps · finops-workspace/1.0.0

What AI FinOps would remember here

The AI FinOps page analyses provider exports you open, in that tab, and forgets them when you close it. This browser can keep the derived monthly figures instead — spend, coverage, confidence, and the one material number — so a later import has something to be compared with. It keeps nothing until you say so, and nothing it keeps is uploaded.

Inspect the whole retained shape first, as synthetic example data rendered from the same versioned contract any persistence adapter must consume. Previewing it grants no consent and writes nothing; only the choice below does.

Inspect every retained field and sample value 
Loading the synthetic contract preview…

Never stored

  • Credentials, prompts, raw imports, and network-transfer data are prohibited.

How complete erasure works

Complete FinOps erasure removes every FinOps local-storage key and verifies that all are empty. It leaves Shiplog decisions, releases, and downloaded files alone.

Local means this browser only. There is no account, sync, server copy, or network transfer. Another browser profile and a file you downloaded are outside this page's reach.

What FinOps is keeping

Reading this browser's FinOps keys…

FinOps storage
Not read yet
Kept here
Counting…
Confidence
Not read yet

Do this next

Reading this browser

Checking whether FinOps has been asked to remember anything here, and what it holds if it has. This page will name one thing to do as soon as it knows.

Coming back? Add this month

Choose the FinOps JSON this page downloaded before. Its setup is reused wherever the source declarations in it allow, so adding a month is one step. It is read in this browser only; nothing is written until the review below is answered. With no file, set up from scratch using the choice further down instead.

What you can do

Download

Downloads one versioned JSON file containing derived period summaries, labels, declared rates, and commitment inputs. It never includes credentials, prompts, or raw imported rows.

Import a FinOps workspace file. Provider and HRIS declarations are checked locally against the static v1 contracts, then require review before reuse.

Forget everything

Removes every FinOps key from this browser and reads them back to check they are empty. Your Shiplog decisions and releases are left alone, and so is any file you already downloaded.

Review what this browser is keeping