← Back to GreeksView

Security architecture

Last updated: October 23, 2026

GreeksView never asks for your brokerage password, or for anything copied out of your brokerage account. Before any of the analytics matter, you should know exactly what we hold, what crosses the network, and what we can and cannot see. This page answers that plainly — including the parts that are less flattering than the marketing version.

AES-256-GCM at rest Your Alpaca access token is held in your browser, under a key the browser will not hand back to JavaScript.
Never stored on our servers Our servers refuse to store broker credentials: the sync endpoint rejects them and our code does not write them to a database or a log.
Your broker's data goes direct When your browser asks Alpaca for data with your access token, it calls Alpaca's data host itself and the token does not pass through us.
Orders and account requests cross our relay Account, position, order, market-hours, symbol-list and option-contract requests pass through our broker relay, with your access token in an Authorization header for that one request.

Where your access token lives

When you connect Alpaca, Alpaca issues this browser an access token. It is kept encrypted in this browser and sent only with your requests to Alpaca: account, position, order, market-hours, symbol-list and option-contract requests through our relay; market data and order-status updates straight from this browser to Alpaca; our servers never store it. The encryption is AES-256-GCM, the same authenticated cipher used for TLS 1.3, through the browser's native WebCrypto implementation.

What makes that meaningful is where the encryption key sits. It is generated once per browser profile and stored in IndexedDB with extractable: false, which means the browser will use it to encrypt and decrypt but will never hand the raw key bytes back to JavaScript. localStorage holds only the ciphertext envelope (ovenc1.<iv>.<ciphertext>), with a fresh random IV per write.

The practical consequence: ciphertext copied out of your browser profile cannot be decrypted anywhere else. Someone who exfiltrates your localStorage gets an envelope they cannot open. Decrypted values are held in memory for as long as the tab is open.

The limit of that protection: the vault protects stored data. It does not protect against a script running inside the page, for example through a cross-site scripting flaw. Such a script runs with the page's own access and can use the token the page has already decrypted in memory. That is why cross-site scripting is in scope on our vulnerability disclosure policy.

The honest edge case. If your browser does not provide WebCrypto or IndexedDB at all, the vault cannot start. The access token is then held only in the open page and never written to your browser's storage, so you connect again on each visit. If your browser provides IndexedDB but refuses to open it, the vault cannot create its key and the token is not saved: nothing is written to your browser's storage. The hosted app is served over HTTPS, so WebCrypto is available there.

A related case: the access token sits in plaintext in your tab's session storage for the moment between our callback page and the app picking it up, then it is moved into the vault and deleted from session storage.

What actually crosses the network

This is the part most tools gloss over, so here it is precisely, lane by lane.

Market data from our licensed feed: through our servers

Figures that a screen labels as coming from our licensed market-data feed are requested from our servers, under your GreeksView session, and our servers ask for them with our own credential. Your browser sends no broker credential on those requests.

Market data from your Alpaca account: your browser to Alpaca, directly

The quotes, option chains and streams that your browser requests with your Alpaca access token go to Alpaca's own data host. The token goes from your browser to Alpaca and does not pass through our servers for any of it.

Account, orders and market lists: through our broker relay

Requests for your account, positions and orders, the market hours, the symbol list and option contracts go to our broker relay (/proxy/trading), which forwards them to Alpaca. Your access token crosses our server with each of those requests, in an Authorization header. The relay accepts no other credential. We keep this lane on purpose, because the relay is where two controls live that a direct browser call would not have:

1Your browser decrypts the token in memory We do not write the plaintext to disk.
2The request goes to our relay with the token in one header Authorization: Bearer, over TLS.
3Our server copies that header onto a call to Alpaca Held in a local variable for the life of one request. Not written to our database or to our application logs.
4Alpaca's response is passed straight back The request ends; the token goes out of scope with it.

So the accurate claim is "never stored on our servers". It does not mean that your access token never passes through our servers. We would rather you read that here than discover it in your network tab and wonder what else was overstated. We do not keep a copy for you, so there is nothing of Alpaca's for us to delete when you delete your GreeksView account.

You cannot avoid this relay from the hosted app today. If you would rather not send your access token through it, place orders in Alpaca's own interface. GreeksView cannot cancel or reverse an order for you: if our service is unavailable, place, cancel or close orders in your broker's own interface.

Order-status updates: your browser to Alpaca, directly

Once you have connected, your browser opens Alpaca's order-update stream itself and authenticates on it with your access token. The stream does not pass through our servers. It is how a screen learns that an order you placed has been filled, partly filled, cancelled, rejected or expired. If Alpaca does not accept the token on that stream, the stream stays closed rather than retrying in a loop, and the orders panel, while it is open, still refreshes from your account through our relay.

Connect with Alpaca

You connect with Connect with Alpaca. You authorize on Alpaca's own page — GreeksView never sees your Alpaca password — and Alpaca issues an access token. The token's whole life, precisely:

1You click Connect and read the disclosure The redirect carries a state value: a ten-minute signed token bound to your GreeksView account, so a callback forged for someone else is refused before anything happens.
2You approve on app.alpaca.markets Your Alpaca password goes to Alpaca, and nowhere else.
3Our server exchanges the one-time code for the token The only step that needs the app's client secret, which lives in server environment variables. The token is held for the life of one redirect — never a database row, never a log line.
4A one-time handoff delivers it to your browser Burned on pickup, then encrypted into the AES-256-GCM vault described above. The sync API refuses to accept it.
5Requests carry it as a bearer header Account, position, order, market-hours, symbol-list and option-contract requests carry it through our broker relay: in memory for one request, then out of scope. Alpaca market-data requests carry it straight to Alpaca.

Treat the token like a password to your account. We ask Alpaca for the scope account:write trading data. That scope includes trading.

One behaviour worth knowing: Disconnect removes the token from this browser only. To revoke GreeksView's access to your account entirely, remove the app in your Alpaca dashboard. We would rather say that here than let a Disconnect button imply more than it does.

Cloud sync and credentials

Cloud sync is opt-in and available on every plan. It uploads the settings stored in your browser, which can include watchlists, recently viewed symbols, favorites, price alerts, drawings, screener presets and trade-journal notes (and so the tickers in them). It never uploads broker credentials or tokens, market data or AI conversation history.

The sync endpoint is the one place a secret could plausibly have been written to our database by mistake, so it refuses the attempt outright: a payload containing a key whose name matches one of these patterns is rejected with a 400 rather than silently filtered. Belt and braces — the client never sends them either.

The legacy entries are history rather than housekeeping. GreeksView no longer asks anyone for a credential of any kind, for a broker, for market data or for an AI model, and has no field anywhere that would accept one, so nothing in the product can create an entry of those shapes today. The guard stays because a guard you keep costs nothing, while a guard you remove protects nobody.

What an earlier version left behind

Earlier versions of the app let you paste credentials, and a browser that used one can still hold them. Every time you sign in, and every time the desk, the chart, the market pages or another page that can use a broker connection opens in that browser, not just the first time, it removes them, so a restored backup or a tab left open on an old version cannot keep one for long:

Our server does the same for your saved settings: an entry of those shapes that an earlier sync left there stays until you next use cloud sync, and each pull, and each push that reaches our server, accepted or refused, deletes it. A sync turned away unread, for being too large or too frequent, leaves it until the next one.

Start on paper

No analytic in GreeksView places an order. Gamma exposure, gamma flip, IV skew, term structure, max pain, the screeners, the P/L lab — the ones your plan includes read market data and nothing else. One caveat for figures from your Alpaca account: which option quotes it is entitled to is decided by Alpaca. The desk tries the real-time option feed first and falls back to the indicative one, so those figures can be indicative rather than real-time.

So there is no reason to lead with live trading. Paper is the default in the app, and switching to live is a deliberate, separate toggle: decide whether we have earned it only after you have seen the tool work.

OAuth, and still no custody

Alpaca supports OAuth for third-party apps, and at first we deliberately did not use it. The standard OAuth shape would make us the custodian of a long-lived access token for your account — stored in our database, refreshed by our servers, revocable only through a flow we control. That is a better experience for us and a worse position for you: it creates exactly the server-side store of account credentials this architecture exists to avoid, and it makes our database a target worth attacking.

So when we did add Connect with Alpaca, we refused every one of those properties. The access token is handed to your browser once, encrypted into the AES-256-GCM vault, and never a database row or a log line on our side. There is no refresh machinery — Alpaca's tokens are long-lived, and if you revoke one, the first rejected request clears it from your browser and asks you to reconnect. Revocation happens on Alpaca's own dashboard, effective immediately, without asking us. The property that matters is revocation you control unilaterally, and nothing worth stealing on our servers.

QuestionAnswer
Where are credentials stored?Your browser only — your Alpaca access token, encrypted with AES-256-GCM.
Do you have a copy?No. Our servers refuse to store them.
Do they cross your server?Market data from your Alpaca account: no, it goes straight from your browser to Alpaca. Account, position, order, market-hours, symbol-list and option-contract requests: yes, through our broker relay, in an Authorization header, for that one request. Order-status updates: no, your browser opens that stream to Alpaca itself.
Does your market data need one?No. Figures from our licensed market-data feed come from our servers, and no broker credential is sent with those requests.
Are they logged?Not by our application: the relay does not write credentials to our logs or database.
How do I revoke?Remove GreeksView from Alpaca's authorized apps. It is effective immediately, without us.
Can I avoid your server?For market data from your Alpaca account, yes: it never touches us. For account, position, order, market-hours, symbol-list and option-contract requests, not from the hosted app today. Place orders in Alpaca's own interface instead.

The rest of the stack

Found a hole in any of this? We would genuinely rather hear it from you than from someone else. See the vulnerability disclosure policy for scope and how to reach us.

This page describes the shipped architecture. If you find it does not match what the application actually does, that is a bug in one of the two and we want to know — tell us.