Privacy Policy

Last updated: 15 July 2026

This policy explains what pip ("pip", "we", "us") collects when you use the pip bot on Discord or Telegram and this website, why we collect it, and the choices you have. By using pip you agree to this policy.

1. Who we are

pip is an AI market-analysis bot operated by its creator (the "operator"). For any privacy question, contact us via the channels in section 10.

2. What we collect

• Messages to pip and its replies. When you @mention pip, DM it, or reply to it, we store your question text and pip's answer, together with the platform (Discord/Telegram), the server/chat identifier, and your platform user identifier. This is what powers memory and context.
• Usage metadata. Timestamps, which tools ran, response latency, token/cost accounting, and success/failure, used to operate, debug, and rate-limit the service.
• Reactions. If you 👍/👎 a pip answer, we record that as feedback to improve quality.
• Account & billing data. If you subscribe, the platform handle you enter at checkout and a payment reference from our payment providers. Card and crypto payment details are handled entirely by those providers, we never see or store full card numbers or wallet private keys.
• Website analytics. On this website only, we record which pages are viewed, which buttons and links are clicked, the site you arrived from (the domain only, never the full address), any campaign tag in the link you followed, your country, and whether you are on mobile or desktop. These are counted against a random identifier stored in your browser, not against your name or email.
• Linking a click to your Pip account. When you click a button here to start Pip on Telegram, or to add Pip to your Discord server, we attach a one-time random code to that link. When you arrive on the other side, we store that code alongside your Telegram account id, or the id of the Discord server Pip was added to. This connects that browser identifier to that account, so we can tell how many people who visit the site go on to actually use Pip. We use it to measure that, not to build a profile of you or to advertise to you. Joining our Discord community server is recorded as a join, and carries no such code, because an invite link cannot carry one.
• Referrals. If you take part in refer & earn, we store your referral code and, for each person who signs up through it, a record linking their account to yours, when they signed up, and whether they subscribed. This necessarily connects two accounts to each other, and both sides can be identified from it. We use it only to work out what a referrer has earned. Referrers see a count and their earnings, never the identity, activity or questions of the people they referred. If you give us payout details (a USDC address, UPI id or PayPal address) we store those to pay you.

We do not collect the contents of channels pip is not mentioned in, your wallet keys or seed phrases, or messages that never involve pip.

Our website analytics are run by us, on our own servers, and are not shared with any advertising or analytics company. We set no advertising cookies and do no cross-site tracking. We do not store your IP address or browser user-agent. If your browser sends a Do Not Track signal we record nothing at all, including the one-time codes described above, and clearing your browser storage for this site erases the random identifier permanently.

3. How we use it

• To answer your questions and provide grounded market analysis.
• To maintain per-server and per-user memory so answers get more relevant over time.
• To operate the service: rate limits, abuse prevention, cost control, and debugging.
• To provision and manage paid access after payment.
• To understand aggregate, anonymized usage trends (e.g. which topics are popular), without identifying individuals.

4. Memory scope

Memory is siloed. A server's memory is used only to answer within that server; a person's history in a chat is used only to serve that same person. One community never sees another's data, and one user's questions are never surfaced to a different user.

5. AI processing

To generate answers, your question and relevant context are sent to our AI model provider (Anthropic) and, where a question requires it, to third-party market-data and web-search providers. These providers process the request to return a result and are not permitted to use it to train their models on your data under our agreements. A list of data sources is described in our docs.

6. Payments

Payments are processed by Dodo Payments (card payments, as merchant of record) and Loop Crypto (USDC payments). When you check out, you are subject to their terms and privacy policies. They share back only what we need to unlock your access (a payment/subscription status and the handle you provided). We never receive your full card details or crypto private keys.

7. Sharing

We don't sell your personal data. We share it only with: the infrastructure and AI providers needed to run pip (hosting, database, model, market-data and payment providers, acting on our instructions), or where required by law. Discord and Telegram themselves are governed by their own privacy policies.

8. Retention

We keep conversation and usage records for as long as needed to provide memory and operate the service. You can ask us to delete your data (section 9); we will remove your stored questions, answers, and profile associated with your platform identifier, except records we must keep for legal, security, or billing reasons.

9. Your choices & rights

• Access / deletion. Ask us to export or delete the data associated with your account.
• Stop using pip. Remove the bot from your server, or stop messaging it, at any time.
• Cancel billing. Manage or cancel a subscription through the link in your receipt.

Depending on where you live, you may have additional rights (e.g. under GDPR or similar laws). We honor valid requests.

10. Contact

Questions, or a data request? Reach us on Discord or Telegram. (A support email can be added here.)

11. Changes

We may update this policy as pip evolves. Material changes will be reflected by the "last updated" date above. Continued use after a change means you accept the updated policy.