DeepStack is a publication, not a platform. This page says what the site, the email list, the contact form 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. Fonts are served by Google Fonts. 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 and the name the calling program gives itself, 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.
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 reader, or a person named in a story.
- Keep an address, a user agent or a cookie on the MCP endpoint or in the search log.
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 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.