Privacy

What we collect, and what we don't

Last updated 18 October 2026

What changed: anyone can now create an account at app.quanlio.com, with an email address or with Google, so the waitlist form on this website has closed. Part 1 now describes the list that form left behind, and the Clerk entry below says what Google shares if you sign in with it. Everything Part 1 promised still holds.

Part 1: This website

Until sign-up opened, this site was a waitlist: you could leave an email address in a form on the home page, and nothing else. That form is gone, because accounts are now created in the app (Part 2), but the addresses it collected are still held as described here. This half also covers the two small things your browser does while you read the site.

What we collect

One email address. It was the only field the form asked for and the only one it stored. We do not ask for your name, your country, your exchange, or anything about how you trade.

Where it goes

Your address is stored as a contact at Resend, the service that sends our email. Resend holds it on our behalf and does not use it for its own purposes. Nothing else touches it: no CRM, no advertising platform, no data broker. We do not sell or share the list.

What we send

Two emails, at most. A confirmation arrived right after you joined, so you knew the address went through. The second, saying your access was open, went out on 18 October 2026. That was the whole plan: nothing more goes to this list, and if that ever changes, this page changes first.

Leaving the list

Every email we send carries a working one-click unsubscribe, and mail clients that support it (Gmail and Outlook among them) show their own unsubscribe control next to the sender. Either one removes you straight away. You can also just email hello@quanlio.com and ask.

Your theme preference

If you switch this site between dark and light, that choice is saved in your browser's local storage under quanlio-theme. It stays on your device, it is never sent to us, and clearing your browser data removes it.

Analytics

We run Vercel Web Analytics and Vercel Speed Insights, on this site and in the app. Both are operated by Vercel, which also hosts us, and both report aggregate figures: pageview counts, referring site, country, device type, and browser. We use them to see which parts of the page people actually read and whether it loads quickly. They are not used for advertising, they are not sold, and they are not linked to your email address if you joined the waitlist.

Stopping automated abuse

The waitlist form is rate limited so bots cannot flood it. Doing that briefly counts requests against the network address they arrive from, in memory only. That count is discarded on its own, and it is never written down beside your email address.

Part 2: The app

Everything below is about app.quanlio.com. Your account is created when you sign up. It is a journal, so most of what it holds is what you deliberately put into it.

What you put in

Your trades (pair, direction, size, entry and exit prices and times, profit and loss, and whether the trade was demo or live), along with the notes, execution grades, mistake tags and confluence tags you attach to them. Your journal entries, which are day-by-day notes with your own mood and discipline ratings. Your settings: your timezone and your starting balance for each mode. This is your record of your own trading, and it is not used for anything except showing it back to you.

What your exchange sends

If you connect an exchange, the app imports your closed trades from it, and those become rows exactly like the ones you would have typed. It reads nothing else from your account.

Your exchange API keys

This is the most sensitive thing the app holds, so it is worth being exact. We accept only API keys the exchange itself reports as read-only, and refuse any key carrying a withdrawal permission. The check runs before the key is stored, so a key that could trade or withdraw never reaches our database at all.

Stored secrets are encrypted, and the check runs again on every single sync: a key that stops being read-only has its stored secret deleted, and syncing stops until you add a read-only one. Quanlio never places an order and never moves funds. Not because we promise not to, but because the keys it is willing to hold cannot.

Your account and your payment

Signing in runs through Clerk, which holds your credentials; we never see your password. The app stores its own account row linked to Clerk's id, and your plan. If you subscribe, Paddle takes the payment as Merchant of Record: card details go to Paddle and never to us. What we keep is the Paddle customer and subscription id, the subscription's status, and when the current period ends, which is what lets the app know you are on Pro.

Feedback you send us

If you send feedback or ask for an exchange from inside the app, we store what you wrote, the page you sent it from, and your email address so we can reply. Resend delivers a copy to our inbox. Only we read it, and it is not used for anything except answering you and deciding what to build next.

Cookies, errors and backups

The app sets a session cookie so you stay signed in, and one small preference cookie remembering how many rows you like per page. There are no advertising cookies and no third-party trackers.

When something breaks on the server, the error is reported to Sentry so it can be fixed. That report is configured to leave out cookies, headers and IP addresses.

The database is backed up off-site every night to a private bucket at Backblaze B2, because losing your journal would be worse than most things on this page. Nightly copies are kept for a week and weekly ones for four weeks, then deleted automatically.

Getting your data out, or deleting it

You can export your trades to CSV from Settings at any time, on either plan. To have your account and its data deleted, email hello@quanlio.com from the address on the account and ask. Deletion removes the rows; backups made before you asked age out on the schedule above rather than being reached into.

Part 3: Who else processes it

The complete list. Each of these does one job on our behalf; none of them is sold your data, because we do not sell it to anyone.

Vercel: Hosting for both the site and the app, plus the aggregate analytics below. The app runs in Frankfurt (fra1).
Neon: The database the app stores your trades and journal in, in Frankfurt (eu-central-1).
Clerk: Sign-up and sign-in. Clerk holds your credentials and runs the login, so we never see your password. If you choose Continue with Google, Google shares your name, email address and profile picture with Clerk; we never see your Google password.
Paddle: Payments, as Merchant of Record. Paddle takes the card details and issues the invoice; they never reach us.
Backblaze B2: The nightly off-site backup of the database, in a private bucket.
Sentry: Server error reports, so a crash can be fixed. Configured to leave out cookies, headers and IP addresses.
Resend: Email. The waitlist confirmation on this website, and feedback you send us from inside the app: your email address and your message, delivered to our inbox.
TypeSafe: The AI that classifies public news headlines as bullish, bearish or neutral. It is sent public headlines only (see Part 4).
Finnhub and Marketaux: Market news and market data, fetched by the app. Requests go out; nothing about you goes with them.

Part 4: What never leaves

Your trades and your journal entries are never sent to the AI. Not summarised, not anonymised, not "just for context". Never.

Quanlio has exactly one place where anything goes to an AI provider: the sentiment read on a news headline. It sends a public headline and its short public summary, nothing else. The code that makes that call never reads your trades or your journal: the only thing it stores is its own read of each public headline, kept apart from your data.

That is an architectural rule in the app's own codebase, written down where the people building it have to read it, not a paragraph on a policy page. It is the difference between a promise and a boundary, and it is why an "AI journal coach" is not something we can ship casually: it would require deciding this question properly first, in public, rather than quietly routing your trades through somebody else's model.

Questions, and changes

Email hello@quanlio.com. Ask what is on file for you and we will tell you. Ask us to delete it and we will, which goes further than unsubscribing: unsubscribing keeps the record and marks it opted out, deletion removes it.

If what we collect or what we do with it changes, this page is updated and the date at the top moves with it.