Privacy
Mugpipe Forecast
Last updated: 13 November 2026.
This page is the privacy policy for Mugpipe Forecast. It describes intended and current data practices for this product.
Controller: Mugpipe, privacy@mugpipe.com
The Mugpipe privacy policy is the platform and account policy. The Mugpipe Forecast Terms of Use govern use of the Service.
Mugpipe does not sell personal data.
1. Two separate data domains
Mugpipe Forecast is designed around a strict separation:
- Account data is used to sign you in, authorize access, operate your account, apply usage limits, and, if a paid plan is offered, administer billing. This may include identifiers, contact details, usage records, and payment-related identifiers.
- The Shared Repository holds professional research records used by the Service and by other users, such as forecasts, outcomes, sources, algorithm versions, and algorithm-improvement or no-change records.
The Shared Repository is not intended to store information that identifies you. In particular, it is not intended to store your name, email address, account or user identifier, payment details, IP address, device identifier, or a stable contributor alias or join key that reasonably links a research record to your account, directly or indirectly. Research records may have their own identifiers (for example, a forecast, model, or source ID) for audit and reuse. Those identifiers are for the research record, not for identifying the person or account that submitted it.
Authorization checks who may use the Service. Authorization is not author attribution. Mugpipe authenticates requests at the access boundary and does not intend to write the authenticated account into Shared Repository records.
This separation is a design rule. Sign-in, security, and infrastructure logs may still process identifying data. Mugpipe does not claim that every system involved in the Service is anonymous end to end.
2. Personal data we may collect
Depending on how you use the Service, Mugpipe may collect or receive:
- Account and sign-in data, such as an account identifier and an email address, obtained when you sign in or when an AI application you choose is authorized to call the Service.
- Service-administration data, such as whether you are authorized, trial or plan status if a plan is offered, usage counts or quotas, and similar account-level records needed to operate access.
- Private account features, if offered, such as a personal watchlist. A watchlist is stored as account data. It is not placed in the Shared Repository and is not made available to other users as their watchlist.
- Billing data, if you later purchase a Forecast plan. Polar, as merchant of record, receives the account email and account identifier so a payment can be matched to the account. Card details are entered with Polar. Mugpipe does not receive or store full card numbers. Mugpipe may store Polar's customer identifier and the trial or subscription row for this plugin.
- Technical and security data, such as request times, tool names, outcome or error codes, the host of the AI application, and diagnostic request identifiers. Error and operational logs are used to operate and fix the Service. They may be processed by our infrastructure provider. They are not sold.
- Communications you send to support@mugpipe.com or privacy@mugpipe.com.
Do not email brokerage passwords, API keys, or account statements to those addresses. Email is not a secure channel for that material and is not a Mugpipe Forecast upload path.
Mugpipe does not need, and you should not submit, your portfolio, trades, or brokerage account data in order to use the Service.
3. What the Shared Repository holds
The Shared Repository may hold forecasts, structured explanations, dated quotes and observations, later outcomes and test results, source catalogs and links, recommended and proposed algorithms, and reasoned no-change records. These records are used to provide history, recommended methods, and learning to users of the Service.
The Shared Repository is intended to contain professional research content, not personal profiles. You and the AI application you use must not include personal identifiers or private account or portfolio information in material submitted to the plugin. Chat transcripts from your AI application are not intended to be stored in the Shared Repository.
If personal data is submitted to the Shared Repository in error, Mugpipe may remove or redact it when it becomes aware of it, but the design of the Service is that such data should not be submitted at all.
4. Purposes
Mugpipe uses personal data to:
- create and administer accounts and authorize access;
- provide, secure, maintain, and fix the Service;
- apply usage limits, prevent abuse, and keep records needed to operate the Service;
- communicate with you about the Service, including notices and support;
- meet legal obligations; and
- if a paid plan is offered, match a payment to an account and administer that plan.
Mugpipe uses Shared Repository records, under the license in the Terms of Use, to operate and improve the Service and to make those records available for use by other users and their AI applications. That use does not depend on identifying the contributor.
5. Who receives information
Personal data may be processed by:
- Infrastructure and hosting providers, currently including Cloudflare, which hosts applications, databases, and logs used by the Service. Account data and Shared Repository records are stored in separate data stores.
- Sign-in and authorization providers used to verify that a request is authorized.
- The AI application you choose, such as Claude, ChatGPT, Gemini, Perplexity, or Cursor, which receives the records or tool results needed to answer your request. Mugpipe does not choose the model and does not send your account data to a separate analytics product for advertising.
- Polar Software, Inc., if you check out for a Forecast plan. Polar receives the account email and account identifier. The card stays at Polar.
- Professional advisers or authorities where needed to comply with law, enforce these terms, or protect the Service, users, or others.
Market-data and information providers may receive requests needed to fetch a source, subject to their terms. Mugpipe does not sell personal data.
6. International transfers
Mugpipe and its providers may process information in countries other than the country where you live, including on distributed infrastructure operated by Cloudflare and, if you pay, by Polar. Those countries may have different data-protection laws. We use providers to operate the Service and do not promise that information will remain in a single country.
7. Retention
This section describes current or intended practice. It is not a contractual commitment, a guarantee, or a service level.
- Account and authorization data are kept while the account exists, or until a verified deletion request is completed, unless a shorter period applies or a longer period is required by law.
- Usage, trial, and subscription records, if any, are kept while needed to operate the Service and administer a plan, and may remain until a deletion request is completed.
- Private watchlist or similar account features, if offered, are kept until you change or remove them, or until a deletion request is completed.
- Shared Repository records may be kept for as long as they are useful to the Service and to other users. Because they are not intended to identify you, a request to delete your account is not a request to delete those records, except where applicable law requires otherwise.
- Error and operational logs are intended to be kept for up to 7 days, consistent with the logging approach used for other Mugpipe plugins, unless a provider keeps a copy for a longer period under its own policy.
- Backups. This application does not delete a backup held by Cloudflare or another provider. A backup, if one is kept, may retain deleted account records for a limited period, typically up to 30 days, after which it is overwritten. That process is outside the deletion steps in this product.
The data retention page describes Mugpipe Signals and the Mugpipe account, and it also includes a dedicated Mugpipe Forecast section. It does not set a retention period for Mugpipe Forecast unless it is later updated to say so.
8. Your rights and requests
You may ask Mugpipe about personal data in your account, and you may ask us to correct or delete that account data, by emailing privacy@mugpipe.com from the email address on the account. Where required by the law that applies to you, you may also have rights to access, restrict, or object to certain processing, or to ask for a copy of personal data.
Sending that email does not itself delete the account or any record. Deletion of account data, if completed, is a change to account and authorization records. It does not revoke the license for Contributions already in the Shared Repository, and it does not require Mugpipe to remove Shared Repository records that are not linked to your account, except where applicable law requires otherwise.
If you have an active paid plan, cancel it with Polar first.
This page does not set a response deadline. Mugpipe does not promise a particular retention period beyond what this page states, or that a backup held by a provider is deleted when this application deletes a row.
9. Security
Mugpipe uses access controls, separate stores for account data and Shared Repository records, and provider security features to protect the Service. No method of transmission or storage is completely secure. You are responsible for the security of your account and of the AI application you use.
10. Children
The Service is not directed to children, and it is not offered to anyone under 18.
11. Changes
We may update this page by posting a new version on mugpipe.com. The date above is the latest version on this page. For a material change, we will make reasonable efforts to give notice, for example by a notice on the page or by email to your account address. That is not a deadline for any person.
12. Contact
Questions and privacy requests: privacy@mugpipe.com. Support questions: support@mugpipe.com.