Privacy

What Broker Pulse reads, where it goes, and how long it's kept. Grounded in what the code actually does.

What it reads

With your consent, Broker Pulse reads — read-only — your brokerage's monthly metrics (commission earned, users registered, active users, trading volume) and your cold-wallet balances, using broker.transaction.read. If you also grant broker.exchange.read, it reads your broker profile once to show your company name in the header. It cannot place an order, move funds, or change any setting on your platform.

Where it goes

Your access and refresh tokens are held server-side only, in a session store, and are never sent to your browser — the browser holds only an opaque session cookie. The dashboard is fetched on demand and cached briefly (a couple of minutes) to avoid re-reading on every render; the cache is keyed to your broker id and expires on its own.

How long it's kept

When you disconnect, the app revokes the token with the platform and deletes everything it held — session, tokens, and any cached dashboard. Sessions also expire on their own after a period of inactivity.

Contact

Questions about this app and its data handling go to the developer who publishes it, not to the platform.