Skip to crypto research
Crypto Trading Strategy GuideVenue / Contract / Settlement

Crypto Worksheet Privacy

Scenario inputs stay in the browser; downloads are local files.

Original desk review: 8 October 2026. Examples are fictional scenarios; no live crypto strategy or paid account was tested. Expanded edition: 14 October 2026.

No Account Connection

The cost worksheet asks for numbers only. It does not request an exchange login, API key or wallet address. Inputs are held in page memory and the JSON action creates a browser download, not an upload.

Hosting and External Links

Cloudflare serves the static pages and may process request metadata. We have not audited its logging. Source links open independently operated sites with their own policies. Fonts are local; there is no promise of anonymous browsing or zero hosting logs.

Primary Sources

Worksheet inputs and page requests differ

The teaching forms calculate declared assumptions inside the browser. They do not request a seed phrase, account password, exchange key, order history or payment card. They have no input upload or broker connection. JSON exports are user-triggered files, not automatic submissions. The original evidence workbench can import a local record chosen by the visitor; that is a separate tool contract. Ordinary hosting requests still reach managed-cloud infrastructure, so browser-local arithmetic is not a claim that visiting a page creates no network traffic or hosting logs.

Retention that is actually implemented

The settlement form stores no draft in localStorage and restores invented defaults on reload. Editing invalid units clears results and disables its exporter so a previous valid record is not mistaken for current input. Changing linear to inverse mode clears funding and valuation because their units have changed. Search uses a public static index and puts the submitted query into its own page URL. That URL can enter normal history and hosting records; it should not contain account secrets. No real trader identity or paid customer population is collected to produce these examples.

Exports need their own handling

An exported assumption record can still contain labels or notes entered by its user. Treat saved files according to their actual contents; a local download is not encrypted storage or a verified account statement. The original workbench's CSV uses formula-safe strings for spreadsheet imports, but that does not certify every downstream spreadsheet workflow. Public case packets are fictional and deliberately contain no private account identifiers. Do not place credentials in evidence references. This static site offers no credential vault, key revocation service or incident-response inbox that has been independently confirmed.

Operational policy needs owner confirmation

TODO(Darren): confirm the legal publisher, hosting/log retention policy and accountable privacy/security contact. Those administrative facts have not been invented. This page describes implemented browser behaviour, not a legal determination about every deployment or jurisdiction. Public-source links lead to other services with their own policies. No analytics claim, measured absence of logging or automatic erasure guarantee is inferred from a quiet interface. Static publication remains cloud-owned with personal computers off; local testing is not a hidden production data processor.