What this site stores,
and why.

Every page view is recorded for site operation: a random session identifier created when the page loads, the page path, the referring address, campaign parameters from the address, the screen size, and the time spent on the page. Interactions such as a search or a download are recorded with the same session identifier, the event name and its details. These records hold no IP address and no browser user agent string; records made before 15 November 2026 may hold both. No third-party analytics script runs on the site.

Your theme choice (paper or dark) is kept in your browser's local storage and never sent to the site.

An account holds your email address, when it was created, when you last signed in, the plan you registered interest in, your current plan and its status and end date, and the symbols in your watchlist.

• Email code and link. The sign-in email carries a one-time 6-digit code and a one-time link. Both are stored as hashes, work once (using one ends the other) and expire after 15 minutes. The code works only in the browser that asked for it. The email is sent through our cloud provider's email service.
• Automated-request check. When you ask for a sign-in email, a check run by our cloud provider may run on the sign-in page to tell a person from an automated request. Its script loads from that provider on the sign-in page only. It reads signals about your browser and device and your IP address, and tells the site whether the request passed. The site stores none of those signals. Most visitors see nothing; a few are asked to tick a box, which shows that provider's mark.
• Google sign-in. The site runs the Google sign-in itself and asks Google only for the openid and email scopes: your Google account identifier, your email address and whether Google verified it, with no name or picture. The site stores the identifier and the address so that the same person opens the same account; it never stores Google access tokens, and it does not read your contacts, files or any other Google data. Google sign-in opens an account only for a Gmail or Google Workspace address; any other address signs in with an email code. Use of information received from Google follows the Google API Services User Data Policy, including the Limited Use requirements.
• Session. A signed-in session is a cookie named vnp_session (HttpOnly, Secure). The site stores a hash of it with your email address until you sign out or it expires. A session in use is extended, 30 days at a time, and ends at the latest 180 days after you signed in. While an emailed code is awaited, a cookie named vnp_signin (HttpOnly) lives for 15 minutes and ties the code to the browser that asked for it. During a Google sign-in a cookie named vnp_oauth lives for 10 minutes and holds a one-time value for that attempt only. The sign-in page also keeps, in this browser's storage and nowhere else, the email address and method you last signed in with, so it can offer them next time; "Not you?" on that page removes them.

The site sets no other cookies.

A signed-in account can ask a question about the market or company page on screen. The site sends your question, together with the data already stored for that page, to a third-party language-model provider based in China, which writes the answer. The site sends no email address, account identifier or IP address with it. Do not put personal information in a question.

A signed-in account can also start event research for a page. The site then sends that provider web-search queries built from the series or company name and the dates of its largest moves, and the search results go to the model to match each move to an event. A signed-in account can start the forecast drivers for a market page in the same way: the queries are built from the series name and the dates of its forecast window, and the model also receives the stored forecast. Nothing you type and nothing about you is part of either request. Each result, with its source links, is stored and shown to every visitor.

The site stores one record per question or research run: your account identifier, the page concerned, the time and the cost. It does not store the question or the answer. The provider processes each request under its own privacy policy.

A signed-in account can keep notes and theses. They are stored with your account and shown only to you. The site does not use them in analytics, does not use them to train any model, and does not use them for any purpose other than showing them to you and answering your own questions.

Your notes are sent to no one unless you turn on “Use my notes in answers”. With that setting on, excerpts leave your account in two cases. With a question you ask while the “Use my notes” switch under the question box is on (the switch is off at the start of every visit), the site sends the language-model provider, with your question and the page's data, excerpts of up to six notes, at most 6,000 characters in all: the notes you linked to the series on screen, and notes that share at least two words with your question. A request you start from a note or a thesis (summarize, draft, challenge, what changed) sends the notes it names (the ones you picked, the thesis you opened, or the first six listed for the series), whether or not the switch is on.

An excerpt holds the title and tags and, for a thesis, its statement, direction, horizon, status, review date, conditions, outcome notes and recorded entry context, plus part of its text. Links written with https://, www. or a similar scheme are removed; everything else you wrote, including names, email addresses and bare domains, is sent as written. The site adds no email address, account identifier or IP address of yours. Each answer lists the notes that were sent, and so does a request that fails after sending. The provider, based in China, processes excerpts under its own policy; deleting a note does not recall what was sent. Turning the setting off stops further sending at once.

You can download all your notes as a file and delete one note or all of them at any time from the notes page. A deletion removes the note from the live database at once. Copies stay in the database's 30-day recovery history and in daily backup archives, which are kept privately and are not deleted automatically; email us to have them removed. While the setting is on, the site records the wording and when; turning it off clears that record.

When you join a founding list or an issue list, the site stores your email address, which form you used, the consent text shown to you and the time. Each list sends only what its consent text says.

Checkout and the billing portal run on our payment processor, the merchant of record named in the terms of service. It collects your payment details and billing address; the site never sees a card number. The site stores the payment processor's customer and subscription identifiers for your account and receives subscription status events from it to apply your plan.

• Our cloud provider hosts the site, its database and its backups, sends sign-in email and runs the automated-request check on the sign-in page.
• Google takes part only when you choose "Continue with Google".
• Our payment processor, the merchant of record, handles checkout, invoices and subscriptions.
• A language-model provider based in China writes the desk analyst's answers. It receives your question and the page's data and, when you attach them, excerpts of your notes.

No record is sold or rented, nothing is used for advertising, and no record is shared with anyone except these processors, as this notice describes.

For the current list of these processors by name, email the address under “Your requests” below.

Sign-in codes and links expire after 15 minutes and sessions when you sign out or they expire. Account, watchlist, list and billing records stay until you ask for deletion. Page view and interaction records are kept for about three months and then expire; they carry no account or email address, so a single record cannot be picked out sooner. Page view and interaction records made before 15 November 2026 are kept as operating records; they are removed on request. Notes and theses stay until you delete them or ask for deletion. The database keeps a 30-day recovery history, and daily backup archives are kept privately and are not deleted automatically; a deletion request covers those copies when you ask for it (see below).

To receive a copy of what the site holds about you, to correct it, or to have your account and its records deleted, email hajiwansau15@gmail.com from the address on the account. Deleting an account ends its plan and removes its watchlist, list entries, sign-in records and its notes and theses; invoices stay with the payment processor as required for accounting. The site has no button that deletes an account: the account and its notes are deleted on request, and you can delete your notes yourself at any time from the notes page.

When this notice changes, the date at the top changes with it.