What we keep, and what we never do with it.

When you create an account we collect your email address and, if you sign in with Google, the name and email your Google account shares. When you use the product we store the analyses you run, the trade plans you lock, journal entries you create, and, if you connect a brokerage on Verify, the read-only position and fill data needed to grade your plans. We also keep basic usage counters (such as analyses per day) to enforce plan limits.

We record which parts of the site are used, so we can tell whether it works for the people using it. An event is a fixed name from a short list — a page was opened, a sign-in was started or completed, a check was started or finished, a name was checked again, this browser came back — together with a small set of values chosen from a closed list, such as whether a check cleared or stopped, which of the four checks ended it, which button was used, and whether a return came the same day, within a week, or later. That is all an event contains, plus the time it was recorded: there is no free-text field in it, so an event never holds a ticker, a price, a budget, a balance, an order or a fill. (The checks you run are stored separately, as described above, and when you are signed in an event can be matched to the check it describes.) A stored event does not include your IP address, your browser or device details, or the site you came from. (Our hosting provider, like any web host, sees the IP address and browser details of every request, including these, in its own request logs.) Events carry a random identifier our page creates and keeps in your browser’s local storage, so we can tell a repeat visit comes from the same browser, and your account identifier when you are signed in. Once you sign in on a browser, its earlier events can be linked to your account. Clearing this site’s data in your browser resets the identifier.

We do not sell your personal information. We do not place trades: brokerage connections are read-only. We do not use your journal or brokerage data for anything except showing it back to you and computing your own statistics.

We rely on a small set of processors to run the service: Clerk (authentication), Vercel and Render (hosting), Neon (database), and SnapTrade (optional read-only brokerage sync). If you choose to load a chart, your browser loads it from TradingView, which then receives at least your IP address, browser details, the page address, the widget type and the symbol or symbols, and may set its own cookies and run its own analytics under its own privacy policy; nothing is loaded from TradingView until you ask. Payment processing, when enabled, is handled by Clerk Billing (built on Stripe); we never see your card number. Each provider receives only what it needs to perform its function.

We use session cookies for sign-in across levelcheck.io and its subdomains, and a cookie that remembers when you cleared your record view. In your browser’s local storage we keep your recent tickers and budget (for the check form; these stay in your browser) and, for the measurement above, a random visitor identifier, the time of your last visit, and whether this browser has signed in. Only the identifier is sent to us, and the last-visit time only as a same-day / within-a-week / longer bucket. We do not run third-party advertising trackers, and the usage measurement described above is our own: the events are stored in our database (Neon, listed above) and no analytics or advertising provider receives them. A TradingView chart you choose to load is governed by TradingView’s own policy.

Your data is kept while your account is active. To delete your account and its data, contact us at the address below and we will remove it within 30 days, except records we must keep to comply with law. Usage events are kept for 12 months and then deleted. Deleting your account deletes the events recorded while you were signed in; events from before you signed in carry only the browser identifier and are no longer linked to you once those are gone.

Questions about this policy: alexander.s.reed@gmail.com