ngmixTerms

Last updated: June 5, 2026

Privacy Policy

This Privacy Policy explains how ngmix collects, uses, shares, and stores information when you use the website, generated analysis pages, payment flows, and the ngmix X bot.

1. Information We Collect

We may collect public X account information needed to generate an analysis, including username, user id, verification status, public profile metadata, public post counts, public reply counts, request tweet text, and limited public thread context. We also collect generated analysis data, public bot reply ids, donation checkout metadata, contribution amounts, timestamps, IP-derived request keys for rate limiting, and basic server logs.

2. Information We Do Not Intend to Collect

ngmix does not require account registration and does not intend to collect passwords, private X messages, non-public X account data, full payment card numbers, government identifiers, or sensitive personal information. Payment card details are handled by the payment provider.

3. How We Use Information

We use information to generate and cache analysis pages, render graph exports, operate the X bot, enforce one-request and anti-abuse rules, process community pool contributions, maintain service reliability, debug errors, estimate scrape costs, and respond to support or removal requests.

4. Public Outputs

If you request analysis through the X bot, the bot may publicly reply on X with generated images, a short generated line, a funding disclosure, and a link to a public ngmix page for your username. Public analysis pages may remain available unless removed or expired under our operational rules.

5. Service Providers

We use service providers to run ngmix. These may include Vercel for hosting, Supabase for database storage, Polar for payments, X for account activity and posting, Apify or X API providers for public data access, and OpenAI for generating the short bot reply line. OpenAI receives bounded public request/thread context and aggregate public analysis stats for tone; it does not receive ngmix API keys, payment tokens, webhook signatures, or environment secrets from us.

6. Payments

Payment checkout is handled by Polar. We receive metadata such as checkout status, contribution amount, fee split, timestamps, and provider identifiers. We do not store your full card number.

7. Retention

We keep analysis cache records, bot request records, contribution events, logs, and payment metadata for as long as needed to operate the Service, prevent abuse, maintain accounting records, and comply with legal obligations. Some cached analysis data may expire or be refreshed over time.

8. Your Choices

You can avoid bot-triggered public analysis by not requesting it from the bot. You can contact us to request support, correction, removal, or access to information associated with your X username. We may need enough information to verify the request.

9. Security

We use technical and organizational measures intended to protect the Service, including protected backend endpoints, webhook signature verification, server-side secrets, rate limits, and database access controls. No internet service can guarantee perfect security.

10. Children

ngmix is not directed to children under 13. If you believe a child provided information to ngmix, contact us so we can review and remove it where appropriate.

11. Contact

For privacy questions, support, or removal requests, contact help@ngmix.app.