LastLoss

Privacy

What we hold.

The desktop app has no server. It talks to Tradovate and to this site for one thing only: on startup and every twelve hours it fetches a version number, so it can tell you when a newer build exists. That request carries nothing about you — no id, no account, no usage. There is no account to create, no analytics and no crash reporting. Your rules, your session token and your trade history are files in your own user folder. They are never uploaded, because there is nowhere to upload them to.

A licence is checked offline. The key you paste in carries its own signature, and the app verifies it against a public key inside the build. Activating Pro contacts nobody, us included, so it works the same whether or not the machine can reach the internet.

Your Tradovate token stays on your machine. The app stores it locally and uses it to read your account. It is not transmitted to us and we could not read it if we wanted to.

This site counts visits. Vercel Web Analytics records page views and where they came from, so it is possible to tell whether anyone is arriving. It sets no cookie and stores no identifier that follows you between visits, so it cannot tell one returning reader from a new one. The desktop app is untouched by this — it has no analytics of any kind.

This website is separate. If you give us an email address, it is stored so we can email you once when a build is ready. It is not sold, shared or added to a newsletter. Ask and it is deleted.

Payments go through Stripe. If you subscribe, Stripe processes the card and holds the billing details under their privacy policy. We never see your card number. Stripe's script loads on every page, not only at checkout, and it sets one cookie (__stripe_mid) that it uses to spot card fraud. That one does persist between visits. It is the only cookie this site sets, and it is Stripe's, not ours.

Downloads are served from GitHub, which sees the request the way any web server would.

Questions, or a deletion request: get in touch.