Privacy Policy.
What we don't collect, what we can't see, and what happens when you click a link to somewhere else. Written to be read, not skimmed past.
Last updated · October 2026The short version
Edge Console has no server of ours. Nothing you type into it ever leaves
your device unless you turn on cloud sync. Your trades, habits, to-do
lists and playbook live in your browser's localStorage, and
chart snapshots live in OPFS — a private, on-device storage
area your browser gives the app. We can't see any of it.
If you choose to enable sync, a single backup file is written to a hidden app folder in your own Google Drive — not ours. We still can't see it. The only other things that touch data are the external links on the site — Amazon, the charting and execution platforms we use, the prop firms we link to, and the utilities and tools we recommend. Those are separate companies with their own policies, and clicking one takes you off our little static site and onto theirs.
What we collect
Short answer: nothing. Longer answer, because "nothing" needs specifics:
localStorage under the key edgeconsole.app.
edgeconsole.app.habits, so resetting one never touches the other.
edgeconsole.app.todos.
edgeconsole.app.playbook and inside your trade entries.
OPFS,
a private per-site filesystem your browser provides. Never uploaded anywhere
unless you explicitly enable cloud sync.
appDataFolder.
We have no access to it, and you can revoke the connection at any time from
your Google account.
localStorage, which is a different browser API and never
gets sent to a server.
External links
Some pages on this site link out to other places. When you click one of those links, you're leaving our site. The destination site has its own privacy policy and may set its own cookies. We don't control that and never see the data involved.
These are the services this site links to, and why:
Amazon Associates
The shop page is the only part of this site that runs on affiliate revenue, and it's the one place where a third party genuinely does see a slice of your activity. It deserves more than a line in a grid, so here's the full picture.
As an Amazon Associate I earn from qualifying purchases. When you click an Amazon link on this site, your browser takes you to Amazon with a small tracking tag attached to the URL. That tag tells Amazon the visit came from here. If you buy anything within the next 24 hours — even something unrelated to what you actually clicked — Amazon pays a small commission out of its own margin. The price you pay is identical whether the tag is there or not.
What I never see is the part that matters most. No names, no addresses, no payment details, no record of what you bought or how much you spent. That data stays between you and Amazon. The Associates dashboard only ever shows aggregate totals — clicks, purchase count, commission earned — with no way to trace any line back to a person.
And one last thing, said without any pitch attached: every commission from a purchase — usually just a few dollars — is what pays for the hours spent maintaining this console, fixing bugs, and building what comes next. Nobody needs to buy anything they wouldn't have bought anyway. But if something on that page does earn a place on your desk, going through one of those links is the most direct way to keep the project alive for everyone using it.
Cookies
The app itself sets no cookies. Everything it stores lives in
localStorage and OPFS, which are per-browser storage
APIs. Unlike cookies, neither is ever transmitted to a server — because there
is no server of ours to transmit it to.
Cookies may appear on your device when you click through to a third-party site (Amazon, a charting or execution platform, a prop firm, a trade copier or other utility, and so on). Those are set by the destination site, not by us. You can review or clear them at any time in your browser's settings, and you can block third-party cookies entirely without breaking anything on this site.
Cloud sync (optional)
Sync is off by default. If you choose to enable it, Edge Console asks
Google for permission to read and write a single file inside a hidden
application folder in your own Drive (appDataFolder). That folder
is only visible to the app that created it — you won't see it in your normal
Drive view, and neither will anyone else.
What gets stored there is a single edgeconsole.json file containing
a snapshot of your trades, habits, to-dos and playbook, with chart snapshots
embedded. It never touches a server of ours, because there isn't one. It travels
directly between your browser and Google's Drive API.
You can revoke Edge Console's access at any time from your Google account (myaccount.google.com/connections). Revoking it doesn't delete the file — you'll want to remove that yourself from your Drive's hidden app data if you want it gone completely.
Your data, your rules
Because nothing ever leaves your device unless you ask it to, the usual questions about data access, correction, and deletion work differently here. You have full control because you have full possession.
For California visitors: this site does not sell, share, or collect personal information as defined by the CCPA. Same reasoning — nothing is collected in the first place.
Children
Edge Console isn't directed at children under 13 (or the equivalent age in your jurisdiction). Because the app collects no personal data at all, it doesn't knowingly collect anything from anyone, including children. If you're a parent and have questions, the contact address below is the right place to ask.
Frequently asked
Privacy-adjacent questions that come up most — written to give you the plain answer, not the compliant one.
Is it really true that you collect nothing?
Yes, in the most literal sense available. The app doesn't have a database on our side to write to, because there isn't a "our side." There's a static file that gets served, and your browser that runs it. Everything you type goes into your browser's own storage.
The only place a third party sees anything is when you click an external link (Amazon, a platform, a prop firm) or enable cloud sync. Both are things you opt into — nothing happens in the background.
What happens to my IP address when I visit?
Your browser sends it as part of loading the page — that's how the web works. Whoever hosts the static files may keep short-lived HTTP logs including it, in the same way every host does, for diagnostics and abuse prevention.
We don't have access to those logs and don't ask the host to keep them. The app itself never makes a network request that carries anything identifiable about you, because it doesn't make network requests at all (with the two opt-in exceptions already noted).
What does Google actually see if I enable sync?
The minimum that Google's API allows. Concretely, when you sign in,
Google sees that a request came from this app and your Google account,
and the app requests one scope: drive.appdata. That scope
gives access to a hidden folder that only this app can read or write.
Nothing else in your Drive is touched.
From Google's perspective, the content of the file — the actual trades, habits, notes — is entirely opaque unless they had a reason to inspect it, which they don't. From our perspective, it's the same: we never make the API call ourselves, your browser does, with your token.
Do you sell or share any data with anyone?
No — and not because of a policy choice but because there is nothing to sell. No user list exists, no usage data is collected, no profile is being built. You could not buy a dataset from this project if you tried, because none exists.
This applies under every privacy framework worth naming: GDPR, CCPA, CPA, and the rest. The "sale" of personal information is impossible when no personal information was ever collected.
Can you see my trades, habits, or journal entries?
No. There is no mechanism by which any of it reaches us. The trades you log live in your browser's local storage, the snapshots live in OPFS, and neither is ever transmitted over a network by the app.
If you enable cloud sync, the file goes from your browser to Google's servers directly, authenticated with your own Google account. We don't sit between those two endpoints and don't have a token to read the file even if we wanted to.
What's actually in the file that syncs to my Drive?
One file, named edgeconsole.json, containing exactly what
you already have locally: your trades, rules, habit check-ins, to-do
items, and playbook notes. Chart snapshots are embedded as base64 so
the file stays self-contained on any device.
It's a plain JSON file — you can open it in any text editor if you want to see what's inside. There are no hidden fields, no device identifiers, no usage counters, no telemetry.
Why is there a whole policy if you collect nothing?
Two reasons. The first is that external links and optional sync do involve third parties, and it's fair to spell out exactly where those boundaries sit — not in legalese, in plain English.
The second is that a site with no privacy policy is a red flag, even if the site is honest. People reasonably want to see the claim written down and checkable. This page is the written claim. If any part of it ever stops being true, it changes here first.
What about the Amazon and prop firm links?
Those are the one place where a third party sees a slice of activity — but only after you click, and only on their domain. The Amazon section above explains exactly what Amazon records and what it doesn't. The prop firm and tool links follow the same pattern: a referrer tag in the URL, and then everything else happens on their side under their policy.
If you'd rather not deal with referral tracking at all, search for the same product, firm, or platform directly. The recommendation still stands either way.
How do I actually delete everything?
Three ways, depending on how thorough you want to be:
- In the app: delete individual trades, habits, tasks, or notes as you go.
- Browser wipe: clear site data for this domain in your browser's settings. This removes localStorage and OPFS together — everything the app ever stored.
- Cloud file: if you enabled sync, remove the app's hidden folder from your Google Drive (or revoke access from myaccount.google.com/connections).
There's no "delete my account" button because there's no account — the browser wipe is the delete.
Changes to this policy
If this policy changes, the date at the top of this page changes with it. The document itself lives in version control, so anyone reading it in the future can see what it said before — that's the point of keeping a static site with a public history.
Substantive changes — the kind that would matter to a reader — will be announced on the app itself. Small wording tweaks won't be, because they don't change anything you'd need to know about.
Contact
If anything here is unclear, or if you think we've missed something a policy like this should cover, the fastest way to fix it is to say so. Questions, corrections, and disagreements about wording are all welcome.