Last updated 21 November 2026
The short version. We store the minimum needed to know who you are and remember how you like the app set up. We never see your card details. We do not sell anything about you, and there is no advertising or third-party analytics in the app. The one exception is our public pages — the ones anyone can read without signing in, this one included — where Whop’s advertising pixel, and on the landing page X’s as well, count the visits our ads bring (see Our ads, below). In the EU, the EEA and the UK they load only if you say yes.
When you sign in through Whop, we receive and store your Whop user ID, username and email address. The user ID is what your settings are filed under so they follow you between devices.
We store the settings you choose: theme, time zone, the board you had open last, ticker board, display density, whether the morning brief is pushed to your phone, whether the 9:00 AM ET premarket ranges are pushed to your phone (Settings › Alerts › Also send me › Premarket ranges, kept with your alert settings), whether every panel stays open (Settings › Display › Everything open), whether the ticker tape shows on a phone (Show the tape on phones), which alert kinds reach your phone, and on CheeseAI+ your watchlist, its radar and flow push settings, custom Charcuterie sets, per-ticker notes, saved chart defaults and the names you added to Range Finder (up to 20; a range alert for one of them goes only to members whose Range Finder carries it).
For the tour, Start here and the in-app lessons we keep the names you pick for them (up to three), which lessons you have finished and when, when you finished or skipped the three-step tour (so it never shows again, on any of your devices), when you did Start here's alerts and Easy steps, when you first opened the app and whether your account was new then (so the tour and Start here are offered to a new account, in its first two weeks only), and whether you put Start here away. Only you see them, and they are deleted with the rest of your settings. If you say yes when you save your names, they also become your ticker board and, on CheeseAI+, join your watchlist (the settings above), and the first of them goes on screen, as if you had picked it.
If you use both CheeseAI and CheeseAI+, your theme is the same in both. To know whether you do, CheeseAI checks your user ID with CheeseAI+ when you open it. Only if you have both do the two apps pass your theme between them (your user ID and the theme you picked, or that you reset it, nothing else); neither keeps anything for an account that only uses the other.
Check my access (cheeseai.app/access) asks Whop, when you sign in to check, which memberships your account holds, and shows you what each one opens. The answer is drawn for you there and then, and not kept. It shows only the account you signed in with. To say whether a membership opens the other app, the app asks the other one which memberships open it — a list of products, nothing about you. The owner can run the same check for a member who asks for help with access, by user ID or by the email that member signed in with; that check is not kept either.
If you turn on push alerts, we store the subscription endpoint your browser generates for that device, plus which signing key it is bound to. That endpoint lets us send a notification to that browser; it is not a device identifier we can use for anything else. So that Settings can show Your devices, we keep beside it a short label worked out from the browser (“iPhone · Home Screen app”, say), when the app was last opened on that device, when an alert was last sent to it and when it last confirmed one on screen. If your browser’s push service refuses a device for good, we keep the refusal’s code and how many alerts in a row it has refused; after three we remove that device’s subscription, as we do when the service says it has expired, and the app adds it back the next time you open it there. When an alert is held back from your devices — by your quiet hours, a name you muted, a kind you switched off or a device that refused it — we note which alert and why for five days, so the Alerts board can tell you. Watchlist radar alerts and flow pushes are kept with your other alerts, under your user ID; for flow push we also keep, until the next trading session, which option contracts it has already told you about, so none is sent twice. Range Finder's alerts go to the members whose board carries that name; we note which range alerts already fired that day, by ticker, so none fires twice, and that note holds nothing about you.
If you send feedback or request a ticker, we store the message or symbol along with your user ID, so we can count votes and reply.
We keep a count of daily active sessions and of the market-data requests the service makes, to know whether it is being used and what it costs to run. That part is a tally, not a log of what you looked at.
The status page keeps nothing about you or anyone who opens it. To show the last seven days, each service keeps a short log of its own incidents for two weeks — what members would have seen (levels that stopped updating, say) and when it began and ended — and the known-issue note the people who run the service post there. Each service asks the other how it is about once a minute, for this page and so the people who run the service hear when one stops answering; no member data is in that question or its answer.
The people who run the service watch it from a console of their own. It keeps a minute-by-minute record of how the service is running — how fresh the levels are, how quickly prices arrive, whether alerts go out, how many requests each part answered and, as a count, how many people are using it — for 14 days. It holds no user ID, username or email, and nothing you looked at.
From Whop’s notices about memberships, the same console keeps a daily tally by product and by plan length (weekly, monthly, yearly or one-time) of memberships started, ended and paid, for 120 days: how many, never who. Once an hour it also reads the membership list from Whop and boils it down to counts and monthly revenue per product, counts per plan length and, where Whop’s list carries it, a count of the reasons chosen from Whop’s own fixed list when cancelling (never anything typed); that summary is held in memory only and never written down. Only the people who run the service see either, and nothing goes anywhere new: both come from Whop, which already handles your membership.
In the Lab, to count how many people have it open, the service holds a one-way scrambled mark of each open session — never your user ID — in memory for about ten minutes, and forgets it whenever the service restarts. The Lab’s replay keeps each session’s market frames and the times the service went over the names, nothing about who watched; opening a name’s book (from the Lab, or from the Level Clock in the app) or replaying a session keeps nothing about you. Turning the Lab’s Sphere by tilting a phone reads the phone’s motion only while that is on, on the phone itself, and the Lab’s kiosk (and Follow, run full screen on a wall display or in Stream) asks the browser to keep the screen awake while it runs; none of these keeps anything. The Lab’s read, written every 15 minutes from market figures alone, is the same for everyone; each session’s reads are kept for the current session and the five before it, with nothing about who read them.
In Flow, the same page and figures go to every member. To count how many
people have it open, the service holds the same one-way scrambled mark of each
open session — never your user ID — in memory for about ten
minutes. Flow keeps nothing about what you look at; your last tab and name, and
whether the projection and the set-aside filter are on, stay in this
browser’s storage (flow_tab, flow_tk,
flow_proj, flow_aside). Its record of each 10-minute
lean holds market prices and nothing about who read it.
When you copy a levels script from the Share menu (for TradingView or thinkorswim), we add one to that day’s count of copies, by kind of script and by ticker (the script for your whole watchlist, on CheeseAI+, by kind alone). Who copied is not stored. So that one person copying the same script twice counts once, the service holds a one-way scrambled code made from your user ID, the day, the kind and the ticker (if there is one) in memory, and forgets it at midnight or whenever the service restarts. Only the people who run the service see the counts.
We also keep a running total of how long you have the app open, filed under your user ID and username, with a week-by-week breakdown for roughly the last ten weeks, and the time you were last active. It feeds our own usage figures, including a ranking of the most active accounts and a list of who is signed in right now, both of which only the people who run the service can see. It records time, not what you looked at.
On CheeseAI+, where you can use Ask Cheese AI (the box for typing your own questions), what you type is sent to an AI model provider to be answered, and your recent questions and answers (the last dozen) are kept under your user ID so the conversation follows you between devices. A conversation unused for 45 days is dropped, and clear chat deletes it straight away. Every answer is checked against the figures it was given, and that check is logged for the people who run the service: when, which names and expiries (or, for a question about a past day, which session), and whether the answer passed, under a scrambled form of your user ID. When an answer is held back, or you flag one, the question and the answer are kept with it so the check can be improved. The log keeps its newest few thousand lines. The ready-made Cheese AI read on a board sends only market data, never anything about you.
Where a Discord server has added our bot, Discord sends us the details of the command you ran: your Discord user ID, the server and channel IDs it was run in, and whatever you typed as part of the command — a ticker symbol, for example. We use that to answer, and to know which alerts to send you if you ask for any.
We store your Discord user ID only if you set something up that has to outlive the command — a personal watch on a ticker, for instance. A one-off lookup is answered and not kept.
The bot does not read your messages. It only receives commands that are explicitly addressed to it; everything else said in the server never reaches us. It does not request the message-content permission.
If you link a Discord account to a CheeseAI membership, we store the pair so the two can be matched. Run /unlink, or ask us, and that link goes, along with any watch list you set up. Settings › Account shows you whether your account is linked and since when, from that same pair; it shows your own link only, never your Discord ID or name, and keeps nothing more.
We set one signed session value so you stay logged in. Inside Whop’s
embedded view, browsers block that cookie, so the same value is kept in your
browser’s local storage instead — it does the same job either way.
Your settings are also cached locally so the app opens instantly (and the
time of the last Reset to defaults your account's theme took,
cheese_theme_clr, so each device follows that reset once), and the
handbook in the app remembers the chapter and place you last read
(cheese_hbplace), an iPhone remembers the page size you
chose for it (cheese_zoomx, cheese_fit), and the
Price chart remembers whether you turned its aVWAP lines off
(cheese_pxavwap), its VWAP line off
(cheese_pxvwap) or its week’s lines on
(cheese_pxwk), the morning brief, the evening recap and the
week’s Picture Book card each remember that you put that day’s or
that week’s card away (cheese_brief, cheese_eve,
cheese_wk), and Flow remembers your last tab and name and
its two switches (flow_tab, flow_tk,
flow_proj, flow_aside), and The Lab’s Map, in
the Lab or in Heat, remembers which view you last chose (the U.S., the world,
the Bay Area or New York) and what it was shaded by
(lab_map_scope, lab_map_mode), on your device only.
Each device also remembers which panels you opened and left open
(cheese_folds: More’s Tools fold, the Market backdrop,
0DTE’s How the projection has done, the price chart under a
phone’s Heatmap, Replay, the day you unfolded the morning brief, and that
you have seen the one-time notes about folded panels and about leaving Easy
mode, and on a phone’s Home its line of index prices and the CheeseAI+
section: homemaj, homeplus), which boards’ line of key numbers you opened, on a phone or a
computer (cheese_kstrip), the layout you chose for it under
Settings › Display › Layout (cheese_viewmode), and its
own copy of Everything open and Show the tape on phones
(cheese_calm, cheese_tapephone), which your account
keeps too. On a phone or the installed app it also keeps your choice under
Settings › Display › Open the app on and the boards and apps you
pinned to the bar beside Home (cheese_homeopen,
cheese_phonebar), which your account keeps too; the screen you
were on and when you left it, so a return within half an hour lands there
(cheese_here); and when you last opened Alerts, for the count on
Home’s Alerts tile (cheese_alseen). Those last two stay on
the device and are never sent. Settings › Reset to defaults clears all of
these on that device but Open the app on, which it keeps. Three older keys are no longer kept or read: the print-day bar you
could put away (cheese_macro_ack), the side of the Unusual list
that slid in from the edge (cheese_flowside) and the Heatmap’s
old aids row (cheese_hmaids); Reset to defaults clears them from a
device that still holds them. If you
arrive on our public pages from a link tagged with a referral name (such as
?ref=reddit, or share on a board a member shared from
the app, which says nothing about who shared it), we keep that name in a cookie for 30 days and add
one to a daily count of visits and checkout clicks for it, which we also pass
to Whop as the link’s campaign tag when you go to checkout; those counts
are all we keep, with no address, device details or anything else about you.
The app sets no advertising cookies, and nothing we set follows you to other
sites. If we ask whether our ad measurement may run (see Our ads), your
answer is kept in your browser’s local storage
(cheese_ads) and never sent to us; Settings › Reset to
defaults keeps it. The advertising pixels on our
public pages keep cookies and stored values of their own, described next.
We advertise on X, and two advertising pixels let us see how many visits our ads bring and how many of them go on to buy. Whop’s is on every public page of the site — the pages anyone can open without signing in: the address cheeseai.app itself (which sends a visitor straight on to the landing page), the landing page (cheeseai.app/welcome), the handbook, the levels, word and track-record pages, the status page, the brokers page, the front of Check my access (before you sign in to check, never on your answer), the terms, this policy, and the cards Heat and the Lab show a visitor who is not signed in. X’s is on the landing page only.
Neither is ever loaded inside the app — in a browser, as an app on your Home Screen (CheeseAI or Heat), or inside Whop — nor in Heat, nor on any page after you sign in. The public pages also leave them out when you open them from inside the app, and on the pages you go on to from there in the same tab, and when the browser you open them in is signed in at that same address. On a phone, Heat and The Lab open inside CheeseAI+ itself, between its bars, and carry neither. A link from one of our apps to another (from CheeseAI+ to Heat on a computer, say) opens that app, or its sign-in if you aren’t signed in there yet, never a public page. cheeseai.app, plus.cheeseai.app and heat.cheeseai.app each keep their own sign-in, and a sign-in inside Whop stays inside Whop, so a member who reaches a public page another way — from one of our ads, a link in Discord or a search, say — in a browser that isn’t signed in there is counted as a visit like anyone else. We give neither of them anything about you — no email, no Whop account, no user ID — and we see only totals.
In the EU, the EEA and the UK, we ask first. If you are there, neither pixel loads until you say yes: a small box on the first public page you open asks whether we may count your visit for our ads, and until you choose Allow neither script is even requested from Whop or X. No thanks keeps it that way on every page. (The bare address cheeseai.app only passes you on to the landing page, so the question is asked there.) We have no way to see where you are and keep no address to look one up, so your browser decides whether to ask, and it errs towards asking: it asks if its time zone is a European one, or if any of its languages is set for a country in the EU or the EEA or for the UK (en-GB or de-DE, for example). Your answer stays in this browser, is never sent to us, and is asked again after six months. You can change it here at any time; changing a yes to no stops both pixels from then on and removes the visitor ID Whop’s script kept on this site.
Our ad measurement in this browser:
not chosen yet.
X’s pixel (the landing page only). Opening the page tells X about the visit: the page address, the page you came from, how long the page stayed open, an ad-click code if you arrived from one of our ads, and the browser and network details any website receives; it may also note that you went on to a checkout link. X’s script keeps a few small cookies on our site to recognise a returning visit and an ad click. We switch off its features that look through a page for contact details. What X does with the visit is covered by X’s privacy policy.
Whop’s pixel (every public page). Whop runs our checkout, and its pixel is how Whop counts the visits our ads bring and matches them to the purchases that follow. Opening any of those pages tells Whop it was viewed: the page address (with the ad-click code in it, if you came from an ad), its title and the page you came from, and later how long it stayed open, along with your browser type, screen size, language, time zone and the network details any website receives. Its script gives your browser a random visitor ID, kept for two years in a cookie on our site and in your browser’s storage. It also works out an identifier from your browser’s characteristics (a “fingerprint”) and, where the browser allows it, stores another in your device’s graphics cache; both let Whop recognise the same browser again — on its own checkout, for example — even after cookies are cleared. When you follow a link from one of those pages to Whop — to its checkout, or to our store there — the script adds that visitor ID to the link, along with your screen size, time zone, type of device, operating system and browser engine, so Whop can match the purchase to the visit. It would also pick up an email address, phone number or name typed into a form on a page or written into its address; none of these pages has a form, and our links never put one in an address. What Whop does with the visit is covered by Whop’s privacy policy.
Your settings are kept while your account exists. Market data snapshots are kept as a rolling history so the app can show intraday and day-over-day movement, and each session’s levels are kept for years as the record the boards are graded on; those are about the market, not about you. Push subscriptions are removed when you turn alerts off, when you remove a device under Your devices, or automatically once your browser reports the endpoint as dead; the note of why an alert was held is dropped after five days. The record of how the service is running is kept for 14 days and the daily membership tally for 120; neither says who you are.
Traffic is encrypted in transit. Sessions are cryptographically signed, so a session cannot be forged or edited. Access to the app is checked on the server for every request, not just hidden in the interface.
The Service is not intended for anyone under 18.
If this policy changes materially, it will be noted in the app’s update log. For any question about your data, or to request deletion, use the feedback form in the app, contact us through whop.com/pauls-bota, or email mikealphacharlie@protonmail.com and we will action it.