Bull Inference · Last updated July 23, 2026. Covers bullinf.fun, api.bullinf.fun, and the Bull poster Chrome extension.
What we collect
- Account: Privy identity (email, wallet, and/or linked X handle), deposit wallet, and billing/credit balances needed to run the marketplace.
- API usage: request metadata (model, tokens/units, cost, latency). We do not store prompt or completion bodies for marketplace inference.
- Payments: processed by Stripe / on-chain Solana rails; we store payment references and ledger credits, not full card numbers.
Chrome extension
- The extension asks you to connect a Bull Inference account (or paste an
inf_API key). - Your API key and saved prompts are stored in Chrome local storage on your device , not uploaded to a separate extension server.
- On X/Twitter pages it reads the tweet you select (id, author, text) only to open the reply panel and build a prompt. That context stays in the extension session unless you include it in a generate request.
- Image generation calls
api.bullinf.funwith your key (same as the web playground). - The extension does notpost to X for you. You confirm replies in X’s own composer.
- Host permissions are limited to
x.com,twitter.com, and Bull Inference API/site origins.
How we use data
- Provide inference, credits, settlements, and support.
- Operate optional product features (share cards, X gifts, metrics) you choose to use.
- Secure the service (rate limits, fraud / abuse prevention).
Sharing
We do not sell personal data. Processors we rely on include Privy (auth), Stripe (cards), Solana RPCs / settlement infrastructure, and hosting (e.g. Vercel, Railway). Public share pages and opt-in feed metrics may show anonymized or user-chosen content.
Retention & control
- Revoke API keys anytime from /key.
- Disconnect the extension (clears the stored key) or remove the extension from Chrome.
- Buyer privacy prefs (public feed / usage export detail) are on the market desk when signed in.
Contact
Questions or privacy requests: DM @DevGwardo on X.