Plobus
Privacy Policy
Last updated: April 26, 2026. This policy describes the Plobus web app (the "Service").
Who we are
The Service helps you paste a short description of an AI or software idea and receive a probability-style read, scores, and optional paid analysis. The party operating this deployment ("we", "us") is whoever hosts the site you are using.
What we collect
- Idea text. What you type into the form is sent to our servers to generate your read. It may be sent to AI and search providers to produce results (see Third parties).
- Scores and read output. We store or derive outputs such as scores, verdicts, insights, and factor breakdowns tied to your submission.
- Session identifier. Your browser may store a random ID in
sessionStorageso we can correlate events in the same visit (for example linking a score to an optional email capture). - Technical and usage data. Standard web information sent with requests may be processed, such as IP address (often via proxy headers), browser type, language preferences, referrer URL, and coarse location signals your network or CDN provides. This supports security, abuse prevention, and—if enabled by the operator—measurement and marketing integrations.
- Email and marketing choices. If you submit your email (for example to receive your read or join a list), we store and use it for those purposes. Checkout may collect email through our payment provider.
- Payment data. Payments are processed by Stripe. We do not receive your full card number; Stripe handles payment credentials under its own terms and privacy policy.
How we use information
- Provide, improve, and secure the Service.
- Send transactional emails you request (for example a copy of your read) and, if you opt in, marketing or product messages.
- If the operator configures webhooks or ad measurement endpoints, we may send structured events (including idea text, scores, email or a hashed form of email, and technical metadata) to those systems for analytics, CRM, or retargeting. You should assume those systems are controlled by the site operator, not by end users.
Third parties
Depending on configuration, we may use vendors such as: AI inference (for example Groq), web search (for example Serper), optional alternate search/LLM (for example Perplexity), email delivery (for example Resend), payments (Stripe), human-verification (Cloudflare Turnstile, when enabled), rate-limiting infrastructure (for example Upstash), and hosting or CDN providers. Each has its own privacy policy. Data you submit may be processed in the United States or other countries where those vendors operate.
Security and abuse prevention
We may apply request rate limits, bot challenges (Turnstile), IP and technical metadata checks, and logging to protect the Service, control cost, and reduce abuse. When limits trigger, you may receive an error asking you to wait before trying again.
Outbound webhooks configured by the operator (for example for CRM or retargeting) may include event types such as idea_scored, lead_captured, and premium_unlock_verified, as described in the operator's deployment documentation.
Retention
We keep information only as long as needed for the purposes above, unless a longer period is required by law. Cached or server logs may persist for a limited time on the hosting platform. If you need deletion of email or marketing data, contact us using the details below.
Your choices
- Do not submit personal data in the idea field if you want to minimize what is processed.
- Use your browser settings to block or clear storage; some features may not work.
- Unsubscribe or contact the operator to opt out of marketing where applicable.
Children
The Service is not directed at children under 13 (or the age required in your jurisdiction). Do not use it if you are not old enough to consent where you live.
Changes
We may update this policy from time to time. The "Last updated" date at the top will change when we do. Continued use after changes means you accept the updated policy.
Contact
For privacy requests, contact the operator of this site using the same channel you used to pay or receive email from them. Operators can set NEXT_PUBLIC_PRIVACY_CONTACT_EMAIL to display a contact address here.