Privacy

Effective August 14, 2026.

Scenario data

The workbench runs in your browser. Typing into the calculator does not send scenario content to Aloha AI. “Save in browser” stores the scenario in your browser’s local storage. CSV, JSON, and print/PDF exports are created locally.

“Copy share link” encodes the complete scenario in the URL fragment. The fragment is intended to remain client-side and is not included in ordinary HTTP requests, but anyone who receives the link can decode and read its contents. Do not place confidential, privileged, regulated, personal, client, security-sensitive, or proprietary information in a scenario or share link.

Site operation

This site has no account, payment flow, advertising tracker, lead form, or marketing signup. Hosting infrastructure may process ordinary request information such as IP address, browser information, requested path, and timestamps for security and delivery.

What survives a reload

This is the question the rest of this page is really answering, so it goes first. Typing into the workbench saves nothing. There is no autosave and no draft recovery: if you close the tab, or reload it, with work you have not explicitly saved, that work is gone and cannot be recovered by anyone, including us. Exactly two actions write anything down, and both are buttons you press.

“Save in browser” keeps one scenario — the current one — and replaces whatever was there before. “Save to library” adds a named snapshot to the Compare tab. When you open the workbench again in the same browser, the single saved scenario is what loads. Everything else you did in the previous session is not stored anywhere and never was.

One exception to that order: if you open the page using a share link, the scenario in the link is what loads for that visit, and your browser-saved copy is left alone rather than replaced. Save afterwards and it does get overwritten.

Exactly what is stored, and where

Two keys are written to this browser’s local storage, and nothing else is persisted anywhere. aiCostWorkbenchV2 holds the single scenario saved by the “Save in browser” button. aiCostWorkbenchLibraryV1 holds the Compare library: up to twelve named snapshots, each carrying that scenario’s full inputs, its computed totals, its specification-confidence score, and the timestamp it was saved at. The library holds twelve; saving a thirteenth drops the oldest.

Local storage has no expiry date. What is written stays until something removes it. “Reset” removes the first key, clears the share fragment from the address bar and reloads; removing a scenario from the Compare table removes it from the second. Clearing site data in your browser settings removes both, permanently, with no copy held anywhere else — there is no backup, no sync and no export we hold on your behalf. A private or incognito window discards both keys when you close it, which makes it a reasonable way to try the workbench and leave nothing behind.

Storage is per-browser and per-device. A scenario saved in Chrome on a laptop is not visible in Safari on the same laptop, or in Chrome on a phone. Moving one between them means exporting a file or copying a share link.

What a share link contains

“Copy share link” encodes the complete scenario — every input, every note, every rate override — as base64 text after the # in the URL. It is encoded, not encrypted, and reversing it takes no special tooling. Anyone who receives the link can read everything the scenario contains.

The fragment after # is not transmitted as part of an ordinary HTTP request, so the contents do not reach this site’s server or its host in the normal course of loading the page. That is a narrower protection than it sounds. The full link, fragment included, still lands in your browser history, in the clipboard, and in whatever you paste it into — a chat message, a ticket, an email thread — and every one of those is a copy outside your control. Treat sending a share link as handing over the scenario itself.

Two size limits apply and both are silent about privacy but useful to know: the workbench refuses to build a share link once the scenario exceeds roughly 12,000 bytes, and refuses to read one whose encoded payload runs past 18,000 characters. Beyond that, export JSON and send the file instead.

A scenario arriving from a share link is not trusted on the way in. It is rebuilt field by field against the expected shape before anything is displayed: the version must match, each of the six line-item lists is capped at fifty rows, free-text fields are truncated to fixed lengths, every number is clamped to a sane range, and an unrecognised model identifier falls back to a known one rather than being echoed back to you. A malformed or hostile link produces a sanitised scenario or none, not arbitrary content in the page.

Do not place confidential, privileged, regulated, personal, client, security-sensitive or proprietary information in a scenario, an exported file, or a share link.

No runtime request to anyone

The provider rate catalog is embedded in the page as static data recorded by hand. The workbench does not call a pricing API, a model provider, an analytics endpoint, or any third party while you use it. There are no third-party scripts, fonts, or embeds, and the site is served under a Content-Security-Policy that restricts scripts, styles, images, frame embedding, and form submission to this origin.

Files you create

CSV, JSON and print exports are generated inside the page and handed to your browser's download mechanism. They are never uploaded. An export includes the full scenario, the computed totals, the sensitivity decomposition, the rate catalog with its check date and age, and any rate overrides you entered — so treat an exported file with the same care as the scenario itself.

External links are governed by their respective services. Contact RN Collins through the LinkedIn profile linked on the workbench for privacy questions.