DeepStack is a publication, not a platform. This page says what the site, the email list, the contact form, the forecasts and the MCP endpoint keep, what each is kept for and for how long, which carriers see it on the way, and how to have it removed. It is short because there is little to list.
Email, inquiries and audience counts
Email sign-up runs on DeepStack’s own list. The address you enter is stored by DeepStack, in a database it controls, only to send The Weekly and dated results; it is confirmed by one opt-in email, is never shared or sold, and the first unsubscribe click ends every edition and every follow. An address never confirmed is deleted after thirty days; an unsubscribed one stays up to ninety days, with the page it was entered on, its dates and its followed topics, as the record of your consent, and is deleted by the list’s own retention run after that. Each edition is delivered by Resend, which keeps its own delivery log under its own terms. Reply to any edition to ask what is held about you or to have it deleted at once.
Partnership inquiries and support requests sent from this site go to DeepStack and to no one else. Each is stored with the name, the address and the message you give, plus a salted hash of your connection address that cannot be turned back into it, and is copied once to the editor’s own Telegram chat so it is read the same day. The record is kept for up to twelve months and is deleted on request.
There are no advertising trackers, and DeepStack sets no cookie. Audience counts come from Cloudflare Web Analytics, which sets no cookies and stores no personal data. A click on a control that carries a name is counted once per day per page, as a number, never with who clicked; the address is used for the rate limit and not kept. Fonts are served from deepstack.ltd, from DeepStack’s own files; no request goes to a third party for a font. Links to sources take you to external sites with their own policies.
The search box and the MCP tools
Questions typed into the search box or asked through the MCP tools are kept as text with the date, the tool used, the number of results, a session id, the name and version the calling program gives itself, the time the call took and a short digest of its arguments, and nothing that identifies you: no address, no user agent, no cookie. They are kept to decide what DeepStack covers next.
The record is read in aggregate, to see which disputes readers and agents bring and where DeepStack has no formed side; it is never published per question and never shared. No conversation text beyond the tool's own arguments is kept. The MCP server keeps no address, no user agent, no cookie and no header beyond its own session id, and its own code writes no log line. Its host, Cloudflare, keeps its own operational log under its own terms.
The record also carries the version number the calling program gives itself at the handshake, the time each call took to answer, in milliseconds, and a short fingerprint of the call's arguments, used to tell repeated calls apart; nothing else was added, and the three are read only as counts and averages.
A question and its session id are deleted twelve months after the day they were asked, by a monthly pass on the first of the month; the weekly queue and the monthly note read them long before that, and the aggregates they fed are what remains.
Forecasts by signed-in readers
Signing in keeps your email (to send sign-in links, a reminder before a test you forecast closes and a note when it resolves, each with a one-click stop), the pseudonym you choose and each forecast with its time; never your IP address, your browser or a cookie. Deleting the account removes all of it at once.
A reader who signs in by email can put a number from 1 to 99 on each pending Docket test: the chance, in that reader’s view, that the answer is yes. The sign-in is a link sent to the address, which works once, for thirty minutes; the session it opens is a token kept in the browser’s own storage, not a cookie, and lasts ninety days or until the reader signs out. No one who does not sign in is asked for anything.
Each thing kept has one use. The address is used to send sign-in links and two short emails about the reader’s own numbers: a reminder before a test the reader forecast closes, with the reader’s number, and a note when one resolves, with the answer and the Brier score beside the Call’s. Each comes at most once a day, never twice for the same test, and carries a one-click stop; the reader’s own page turns either back on. To keep that promise the forecast service keeps, per reader, the two switches, the day each email went and the tests it named, and the stop link only as a hash. No edition goes to the address unless the reader also signs up for The Weekly. The pseudonym is printed on the readers’ table. Each number, with its time, is scored: when a test resolves, each reader’s last number before the date gets a Brier score, the rule the Call’s own number follows. A reader with at least five scored numbers appears on the readers’ table under the pseudonym they picked, never the address; a test shows the readers’ median, from 25 readers, with no name. Rate limits read a salted hash of the connection address, which cannot be turned back into it.
An address that never completes a sign-in is deleted thirty days after it was entered, and an expired link or session on the first of the next month. A signed-in reader’s address, pseudonym and numbers stay until the reader deletes them: the reader’s own page removes all of it at once, with no copy kept, and the readers’ median and table stop counting them at their next daily build. The sign-in email, the reminder and the result note are sent by Resend, which keeps its own delivery log under its own terms; they carry no tag, so DeepStack keeps no open or click for them.
The anonymous yes-or-no click on Docket tests ended on 20 October 2026, when the forecasts began. Its counts, kept per test and day and never with who clicked, stay as they were and are no longer shown.
Where a visit came from
Arrivals are counted per channel and day, without an IP address or an identifier. When a link into the site carries a campaign tag, or the visit comes from a site DeepStack recognizes, such as an AI assistant or a social network, the site counts that arrival once, with the medium, the campaign, the creative and the page it landed on: a number per day, never a person. The referrer is kept as its host alone, never its page, and the tab holds those fields only while it stays open. When you sign up, the list keeps on your row the channel you arrived from, the medium, the campaign, the creative, the referrer's host and the page you landed on, so DeepStack knows which channels bring readers who stay; all of it is deleted with the address.
Opens and clicks in email
Emails from DeepStack carry an open pixel and tracked links, set by Resend, the carrier, once tracking is on for the sending domain. What comes back is kept per address: that an edition, a result or a welcome note was delivered, opened or clicked, the day and hour, the send it belonged to, and for a click the page it went to; never the address, the device or the location the carrier reports with it. The record is read to see which editions and results are read, to count who comes back for a result, and to stop writing to addresses that never open. It stays with the address until the first unsubscribe click and thirty days after it, then it is deleted; a deletion request removes it at once.
An address that bounces, or that reports an edition as unwanted, is taken off the list the same day, and the reason stays with the rest of its record for ninety days.
The welcome emails
The four welcome emails that follow a confirmation keep three more things, each on the address alone: the role you choose with one click in the second email (one of eight labels, such as press or individual investor), the date you click “keep sending” in the fourth, and which of the four went out. An address that neither opens, clicks nor asks to be kept in its first weeks is taken off the list with the reason recorded, and the retention rules above then apply.
The partners page and the arrival codes
The two audience counts are totals from DeepStack’s own weekly count: no address and no caller is in them. The Docket and Results counts come from the content files at each build. A page reached through a podcast or video code (an address that starts with /pod- or /yt-) carries only the channel’s name and, when the code names them, the campaign and creative labels into the sign-up page it forwards to; the code page itself keeps nothing.
What DeepStack never does
- Sell, rent or share an address, a message or a question. The only outside parties that see them are the carriers named on this page, Resend, Telegram and Cloudflare, each under its own terms.
- Set a cookie or run an advertising tracker.
- Score, rank or profile a person named in a story. A reader is scored only after signing in and giving a number, and appears only under the pseudonym they chose.
- Keep an address, a user agent or a cookie on the MCP endpoint or in the search log.
- Keep the address, the device or the location the email carrier reports with an open or a click.
Your rights
Reply to any edition, or write through the contact page, to ask what is held about you, to correct it, or to have it deleted. Deletion removes the address, its follows, its opens and clicks and any message at once. The unsubscribe link in any edition ends every edition and every follow at once; the address then stays up to ninety days, with the page it was entered on, its dates and its followed topics, as the record of your consent, and is deleted by the list’s own retention run after that, or sooner on request.
Changes
The date at the top is the date of the current version. A change that keeps more, or keeps it longer, is announced in The Weekly before it takes effect. Questions about this policy go through the contact page.
Analysis and opinion, not investment advice.