Privacy Policy

Last updated: September 17, 2026 UserBadge is a drop-in visitor badge for websites, operated by Brandon (contact: https://x.com/CyberBlueCollar). This policy describes how we collect, use, and share information when you use userbadge.cc, the dashboard, the claim flow, and the badge engine hosted at user.userbadge.cc. 1. Who this applies to We process data for two groups: (a) customers who create an account and install a badge, and (b) visitors to those customer websites who load the badge script. 2. Account and marketing site data If you sign in, we use Supabase Auth. We do not store your password. We may keep your email, account id, plan, message usage, site list, badge appearance settings, and billing status. The marketing site may store a local theme preference and an anonymous analytics id (ln_vid) in your browser and send it with a tiny beacon request so we can tell unique browsers apart in logs. We do not sell that id. 3. Badge and visitor data When a site installs our script (badge.js from user.userbadge.cc), the badge calls our API (including /v1/session-start) and may open a live WebSocket. We generate or read an anonymous visitor id in that browser’s localStorage (userbadge:vid) so we can count unique visitors and returning visits without asking for a name or email. We may resolve approximate location (country, city, and map coordinates) from request headers or IP so the map and country bar can show where visitors are coming from. We store live presence, lifetime visitor totals, and aggregated city/country counts for each site. The public hub page (for example userbadge.cc/your-site) shows those counts and places. The badge may also store local preferences such as hide/minimize, theme follow, and appearance on that device. We do not use the badge to collect form fields, passwords, payment card numbers, or the full contents of the host page. The script is meant to show social proof: who is online, how many have visited, and a map or country bar. 4. Claim on X If you claim a free badge by sharing on X, we receive the tweet URL you submit and may check that the post exists. Do not send secrets in that URL. We may store that you completed a claim. 5. Payments Paid plans are billed by Stripe. Stripe processes your payment details. We keep Stripe customer and subscription ids, plan status, and period dates so we can apply message limits (Free: 5,000 messages per month; Paid: 100,000). We do not store full card numbers on our servers. 6. How we use data We use this information to run UserBadge: authenticate you, render and update badges, count messages, freeze live presence when a free or paid pool is exhausted, show public hubs, prevent abuse, fix bugs, and communicate about the product. Message use is how we meter the live “who’s here” signal. If messages run out, the badge can remain on the page with lifetime visitors while live presence pauses until the pool resets or you upgrade. 7. Sharing We share data with processors that help us operate the product: Amazon Web Services (hosting, CDN, database), Supabase (auth), Stripe (payments), and X (only if you use tweet-to-claim). Public hubs and the badge UI display non-identifying visitor stats and city-level map points on purpose. We do not sell personal information. 8. Retention Account data lasts while your account is open. Live sessions are short-lived. Aggregated visitor and map stats last as long as the site record exists, including after a live freeze. You can ask us to delete an account or site by contacting us on X. Browser localStorage stays on that device until cleared. 9. Your choices You can hide or minimize the badge in the browser (Hide Me). You can clear site data in your browser to reset visitor id and local appearance. Customers can change appearance, disconnect a site, cancel Stripe billing, or sign out. For access or deletion requests, contact Brandon on X @CyberBlueCollar. 10. Children UserBadge is for website operators and is not directed at children under 13. We do not knowingly collect personal information from children. 11. International visitors Servers are in AWS us-east-1. If you visit a customer site or use UserBadge from another country, your information is processed in the United States. 12. Changes We may update this policy. The date above will change. Continued use of UserBadge after an update means you accept the revised policy. 13. Contact Brandon / UserBadge — https://x.com/CyberBlueCollar — https://userbadge.cc