Aenvor Back to the site

Cookies and local storage

Aenvor Charts · 2026-11-04

Cookies and local storage

Supplied by АЕНВОР СОФТУЕР КЪМПАНИ ЕООД (AENVOR SOFTWARE COMPANY Ltd). Last updated: 04.11.2026

The short version

The terminal stores two things in your browser. One keeps you signed in for as long as the terminal is open. The other remembers whether you chose the dark or the light theme.

There is nothing else. No analytics, no advertising, no tracking, no third party, and nothing that leaves your computer — because there is nowhere for it to go.

Which of the two you are reading about

There are two builds and this page covers both, because the two items below are the same two items in each. Where they differ, it is said in place.

The desktop terminal is not a website. It runs on your own machine and serves itself to your browser at 127.0.0.1, an address that means *this computer*. So the two items below are set by your own machine, read by your own machine, and visible to nobody else — there is no third party to receive them and no network for them to cross.

The hosted terminal is a website, at our address, over the internet. One thing changes and it is named under aenvor_session below: a one-way digest of the token — not the token — is recorded on our server, so that a restart on our side does not sign you out mid-session. What does not change is the part this page is mostly about — nothing in the pages either build draws is loaded from anyone else's servers. The charting library, the fonts and the icons are files inside the product, on both. No Google Fonts, no CDN, no third party with anything to set.

What is stored

1. aenvor_session — a cookie
What it isA random value that tells your own terminal you are signed in
WhyOtherwise every action would ask for your password again
How longUntil you close the browser. It is a session cookie and is not written to disk with an expiry date
AlsoThe terminal expires it after 12 hours regardless, on its side, where it cannot be tampered with
FlagsHttpOnly — unreadable to scripts; SameSite=Strict — never sent on a request that started at another site; first-party only. On the hosted terminal also Secure, so it travels only over an encrypted connection. The desktop build is at 127.0.0.1 and does not set it: there the flag protects nothing and older or stricter browsers refuse the cookie outright, which locks you out of your own terminal
ContainsA random token. Not your email, not your name, not your password, not your licence key
This cookie is strictly necessary. It exists only to deliver the thing you asked for — being signed in to your own installation — so under the ePrivacy rules it needs telling you about, which is what this page is, rather than asking your permission.

Signing out deletes it immediately.

On the desktop terminal, so does restarting it: the token behind the cookie is held in the terminal's memory and does not survive a restart, which is why the terminal asks for your password every time you launch it.

If you are using the hosted terminal at our address rather than the desktop build, that one differs in exactly one way: the session has to survive a restart or a deployment on our side, so it is recorded there rather than held in memory.

What is recorded is a SHA-256 digest of the token, not the token. The arithmetic runs one way only, so the record can confirm a token you present and cannot produce one. A copy of that database — a backup, a snapshot, a stray read — is a file of digests, and a file of digests opens nothing.

It is still a random value, it still expires after twelve hours, and signing out still deletes it. Everything else on this page is the same.

2. aenvor.theme — one line of local storage
What it isThe word dark or the word light
WhySo the first frame after launch is drawn in the theme you chose, instead of flashing white at someone who works in the dark
How longUntil you clear your browser's storage for this address
ContainsFive letters. Nothing else, and nothing about you
The authoritative copy of your theme lives with the rest of your settings, in the terminal's own database on your disk. This is a hint, read once, before the settings have loaded. If your browser has storage turned off, the terminal falls back to the light theme and carries on.

There are two further keys, acc.theme and orion.theme, and both are only ever read. The terminal carried two earlier names, and a browser that still holds one of the old hints would otherwise flash white once on the way in. The value is copied into aenvor.theme the first time either is found and neither old key is written again, so they retire themselves. Each holds the same five letters and nothing else.

What is not stored

Said explicitly, because on most software this list is where the surprises are:

- No analytics or telemetry cookies. There is no analytics in this product at all. It does not count your sessions, time your clicks or report a crash.
- No advertising or tracking cookies. Nothing here is shared with an advertiser, a network or a data broker.
- No third-party cookies. Nothing on the page comes from a third party, so no third party can set one. No fonts from Google, no scripts from a CDN, no embedded video, no chat widget, no social buttons.
- No fingerprinting. Nothing measures your canvas, your fonts, your screen or your hardware to recognise you.
- No cross-site tracking. There is no other site to track you to.

What the terminal keeps outside the browser

Separately from the two items above, the terminal keeps your sessions, orders, strategies, drawings, notes, settings and market data in its own folder on your disk. That is not cookies and not browser storage — it is the product's data, in the same sense a word processor keeps your documents. It never reaches us. See the Privacy Policy.

Turning them off

You can clear or block both from your browser's settings for 127.0.0.1.

Blocking the theme hint costs you nothing but a white flash at launch. Blocking the session cookie means you cannot stay signed in, and the terminal will not be usable — not because we are insisting, but because there is no other way for a page to remember that the password you typed a moment ago was correct.

Questions

Write to [email protected].