Privacy

Effective 2026-10-26.

This page describes this version of the AlgosWay tools (the effective date is above).

The short version

The calculator, the trade journal and My dashboard run entirely in your browser.
In this version, your journal entries and calculator inputs stay in your browser; AlgosWay's code never uploads them. We cannot see them.
This version has no account, no registration and no email collection. Payments are not enabled.
Apart from loading the site, its code sends nothing except a license key you type on the pricing page, to this site's own /api/license route, which stores nothing.
AlgosWay adds no analytics or tracking. Cloudflare may set the service and security cookies described below.

Your trade journal stays in your browser

Trades, day notes, checklist results, your fee and payout ledger and journal settings (including the accounts you add in Pro) are saved in your browser's own storage on this device (IndexedDB, or local storage if IndexedDB is not available; if your browser blocks storage, the journal is kept in memory only and is lost when you close the tab). AlgosWay's code does not send them to AlgosWay or anyone else.

Anyone who uses the same browser profile on this device can open the journal.
Clearing this site's data, using a private window or switching browser or device removes or hides it. We cannot recover it for you.
CSV import reads the file inside your browser; the file is not uploaded.
CSV export and backup files are created by your browser and saved where you choose. What you do with them is up to you.
You can delete the whole journal at any time from the journal's settings.

The calculator runs in your browser

Simulations run on your device. To keep your inputs while you switch pages or reload, they are saved in this tab's session storage, which your browser clears when you close the tab. Numbers you send from the journal to the calculator travel the same way, inside your browser. So that My dashboard can list them, your last calculator runs (your last 3, or all of them in Pro; the inputs and the headline results only) are also saved in this browser's local storage; you can delete them on My dashboard at any time. The other tools (drawdown floor, stop line and size, payout planner, cost to first payout, plan comparison) keep their inputs in this tab's session storage in the same way. Edge Lab reads the backtest file you choose inside your browser, keeps it in memory only and never uploads it.

Everything this site stores on your device

AlgosWay's code uses these storage keys and no others. None of them is sent anywhere, except the license key, and only when you check it.

Where	Name	What it holds
IndexedDB	`algosway-journal`	Your journal: trades, checklist days (including the before trading checks), settings (checklist items, contract table, saved CSV column mappings, trading day setting) and your fee and payout ledger.
Local storage	`aw.journal.v1`	The same journal, only if this browser does not offer IndexedDB. A test entry, `aw.journal.v1.probe`, is written and removed at once to check that storage works.
Local storage	`aw.tools.scenarios.v1`	Your last calculator runs (inputs and headline results), for My dashboard.
Local storage	`aw.license.v1`	The license key you entered, the last answer of the `/api/license` route and when it was checked.
Local storage	`aw.tools.backup.v1`	When you last downloaded a backup, and whether you asked to be reminded later.
Local storage	`aw.tools.cooldown.v1`	Your cooldown timer while it runs or is paused.
Local storage	`aw.site.theme.v1`	The colour theme you picked, if it is not the default.
Session storage	`aw.tools.calc.inputs.v2`, `aw.tools.calc.handoff`	Calculator inputs, and numbers sent from the journal to the calculator. Cleared when you close the tab.
Session storage	`aw.tools.drawdown.v1`, `aw.tools.risk.v1`, `aw.tools.payoutcheck.v1`, `aw.tools.costs.v1`, `aw.tools.compare.v1`	Inputs of the drawdown floor, stop line and size, payout planner, cost and plan comparison tools. Cleared when you close the tab.

My dashboard

My dashboard is put together in your browser from your own journal and your saved calculator runs. It shows only your data, it never shows AlgosWay's own results as yours, and AlgosWay's code sends nothing from it anywhere.

License keys and payments

Payments are not enabled yet, so no payment details, email address or name are collected anywhere on the site.

Your plan, and the Free plan's limits (3 saved calculator runs, 1 journal account and 50 trades), are checked in this browser. That check is not a security measure.

When you check a license key on the pricing page, your browser sends only that key, as a small JSON request, to this site's own /api/license route. In this version the route checks that the key has the right shape and answers that payments are not enabled yet. It does not store, forward or log the key, sets no cookie and writes no analytics. Like every request, the request itself passes through our host, which receives the standard technical details described below.

Once payments are enabled, a merchant of record will sell the plans and process payments. It will be named on this page, with a link to its privacy policy, before any charge. It will receive what you enter at its checkout (such as your name, email address and payment details), and the route will send it the license key you check, to confirm it.

Our host

The site is hosted on Cloudflare. Like any web host, Cloudflare receives the standard technical details of each request (such as IP address, browser type, the page requested and the time) to deliver the site and keep it secure. AlgosWay does not use these details for tracking, profiling or advertising. Cloudflare's use and retention of those details is described in its Privacy Policy.

What the site loads

The site loads AlgosWay's own pages, scripts, styles, fonts, icons, one rules file (the dated prop firm rules) and, for the compliance audit, one calendar of official release dates, all from the same website. AlgosWay adds no third party scripts, fonts, analytics, advertising or embedded content.

The site does not enable analytics or advertising scripts. Cloudflare may use technical requests, code and cookies to deliver the site and protect it from abuse. We check the hosted pages and network behavior whenever we publish an update. AlgosWay's own code does not upload your journal entries or calculator inputs.

Links to prop firm websites open only when you click them, in a new tab, without telling that site which page you came from.

Cookies

AlgosWay's own code does not set or read cookies. Cloudflare may set cookies to deliver and protect the site. Which cookies are used depends on the protections applied to a request.

__cf_bm may be used for Cloudflare's bot protection. Cloudflare says it expires after 30 minutes of inactivity.
cf_clearance may be used when a visitor completes a Cloudflare security check.

These examples do not mean that every visitor receives these cookies. AlgosWay does not use them for analytics or advertising. See Cloudflare cookies for Cloudflare's descriptions and the host's Privacy Policy linked above for its data use.

A __Host-appgarden-visitor cookie from an earlier hosting version may remain in your browser until it expires or you remove it. Clearing this site's browser storage can also remove your journal; download a backup before clearing site data.

Selling or sharing

We do not sell or share personal information. AlgosWay's tools do not collect it. A license key is not stored by AlgosWay.

Children

The site is intended for adults and is not directed to children under 18.

Changes

This policy covers this version of the tools only. If a later version works differently, its own privacy page will describe it, with a new effective date.

Contact

Questions about privacy: email hello@algosway.com.