Outlist Labs is operated by Aryan Kaushik. Contact [email protected] about this tool. Last updated October 3, 2026.
Calculator data
The calculator does not send your inputs, results, pricing snapshots, or saved scenarios to Outlist’s server, a database, or an AI provider. It does not require an account or API key. There are no third-party analytics scripts on the calculator page.
Your browser requests the static website from Cloudflare. Cloudflare handles normal hosting and security request data under its own policies. This browser-only calculation boundary does not mean that visiting a website creates no network request or hosting logs.
Local storage
The latest valid scenario and up to three explicitly saved scenarios are stored in this website’s local storage on your device. They are not synchronized between devices. They can be read by people or software with access to your browser profile. Delete saved scenarios using the calculator controls, or clear this site’s browser data to remove everything.
If storage is blocked or full, calculation continues. Use a JSON download if you want to keep a copy.
Share links
A shared scenario is encoded into the part of its URL after the hash sign. That fragment is not sent in the HTTP request. The recipient, browser extensions, and scripts running on the page can read it. Encoding is not encryption. Do not put confidential names or commercially sensitive assumptions in a public link.
Downloads and external links
JSON, CSV, and result-card images are created locally. Their contents are not uploaded by the tool. Import reads a small JSON scenario on your device; it does not upload the file.
Official pricing sources open external websites. Visiting Outlist’s main leaderboard is a separate interaction governed by that website’s policies. Links back to Outlist may include campaign tags identifying Labs as the referral source; they do not include your scenario.
The initial release does not use analytics on any Labs page. Any future aggregate analytics must preserve the calculator’s no-third-party-script boundary and will be documented here.