Privacy Policy

This Privacy Policy explains how Retarded or Not ("we," "us," or "our") collects, uses, discloses, and retains information when you use Retarded or Not, the website, public Target Handle pages, sign-in flows, mark and voting features, paid market actions, removal and privacy request flows, and related services that link to this Privacy Policy (collectively, the "Service").

1. Scope

This Privacy Policy applies to the website, the Service, public pages, sign-in flows, voting and mark features, paid actions, reports, support requests, removal requests, privacy requests, legal requests, moderation requests, and any future official client that links to this Privacy Policy.

Third-party services, including X/Twitter, Clerk, Stripe, PostHog, Sentry, SocialData, Convex, hosting providers, and other vendors, have their own privacy practices. Their privacy policies apply to their own collection and processing of information.

Public browsing may be available without an age gate where lawful. Signing in, casting Marks, changing Marks, clearing Marks, and buying Paid Actions are intended only for users who are at least 18 years old.

2. Public Target Handles

Only public X/Twitter accounts are eligible to appear as Target Handles. Private, protected, deleted, suspended, unavailable, access-restricted, or otherwise inaccessible accounts are not eligible.

The Service does not knowingly maintain Target Handle pages for accounts operated by, primarily associated with, or reasonably believed by us to be associated with minors. We may hide, restrict, remove, freeze, or review Target Handles that appear to be minor-associated, safety-sensitive, high-risk, private-person-associated, or otherwise inappropriate for the Service.

A Target Handle owner, parent, guardian, authorized representative, or person with a credible safety or privacy concern may request removal, restriction, review, access, deletion, correction, or other privacy assistance. Verification through the same X/Twitter account may be one way to confirm control of a Target Handle, but we may consider other verification methods where appropriate.

3. Information We Collect

We collect information you provide, information generated by your use of the Service, information from authentication providers, public Target Handle information, payment-related information, analytics and logs, and information from service providers.

Information You Provide

You may provide:

• sign-in and authentication information through X/Twitter and Clerk;
• Marks cast on Target Handles;
• Target Handle inputs, searches, and page interactions;
• Paid Action selections and checkout initiation details;
• support, report, appeal, privacy, account deletion, Target Handle removal, legal, safety, or moderation communications;
• any email address or contact information you directly provide in those communications.

The Service does not currently collect or store email address from Clerk or X/Twitter sign-in. The Service collects email address only when a person directly provides it, such as in a support, removal, privacy, legal, safety, or moderation request.

No public free-text user content, comments, direct messages, user bios, user-uploaded media, user-created accusations, or user-to-user communication are planned. User inputs are limited to constrained actions such as Marks, Target Handle inputs or searches, Paid Action selections, and direct support, removal, privacy, legal, safety, or moderation communications.

Authentication Information

When you sign in through X/Twitter using Clerk or another supported identity provider, we may receive and store identifiers and profile fields needed to connect your Signed-In User account to Service activity. This may include provider identifiers, Clerk user ID, X/Twitter user ID, handle, display name, profile image, and authentication metadata.

Public Target Handle Information

The Service may collect or store public information about eligible Target Handles, including display handle, display name, profile image URL, bio, follower count, following count, verification status, X/Twitter user ID, public/protected/suspended/deleted/unavailable status, and fetch timestamps.

This information may come from public X/Twitter pages, SocialData, user searches, cached Service records, or operator/admin tools. It may be displayed publicly on Target Handle pages, leaderboards, search results, share previews, Open Graph images, and other public game-state surfaces unless removed, hidden, restricted, or updated through product rules, authenticated owner removal, legal process, safety review, privacy review, or operator discretion.

Marks, Counts, Game-State, And History

We store each Signed-In User's current Mark for a Target Handle. We also store aggregate counts, parody/opinion output history, count-change events, provenance, source references, and related audit records.

Individual Marks are private in the public UI at launch. Aggregate counts and Target Handle results are public. If voter-reveal features are later enabled, individual Marks or marker identities may be displayed only after clear notice before the user acts. Existing private-launch Marks will not become public automatically after a policy change. A private-launch Mark can become public only if the Signed-In User affirmatively opts in or changes or casts a Mark after a clear voter-reveal notice.

Paid Actions And Payment Information

When Paid Actions are enabled, we may store paid action orders, Target Handle, action kind, package key, amount, currency, status, provider, Stripe checkout session identifiers, Stripe payment intent identifiers, settlement status, timing, and related product-effect records.

Paid Actions may include Tactical Votes, Boosts, Stop Voting, counters, Score Resets, Spins, or other configured paid packages. Paid Actions are paid game effects, market effects, or paid actions. They are separate from organic Signed-In User Marks and do not create synthetic user votes or synthetic user identities.

Stripe processes payment details. We do not intend to store full card numbers. Stripe handles payment receipt emails independently; receipt emails are handled by Stripe and are not stored by the Service as ordinary account profile data.

Market Listings may show a Paid Action's effect, Target Handle, amount, status, and timing. Buyer identity is not exposed by default in public Market Listings. Operators/admins may access buyer identity internally for support, fraud, payment disputes, legal compliance, safety, and enforcement. Targets and public users will not see buyer identity unless the buyer explicitly opts into attribution, the Service is legally required to disclose it, or disclosure is needed for payment, legal, safety, fraud, or enforcement handling.

Payment disputes, chargebacks, refunds, fraud reviews, and paid-action reversals may require us to retain and share relevant payment, order, identity, Target Handle, and product-effect records with payment processors, infrastructure providers, advisors, and legal or compliance recipients.

Analytics, Logs, Device, And Error Data

We may collect page views, product events, device information, browser information, URLs, request metadata, IP address, logs, and security events. PostHog may collect analytics when configured. PostHog is configured for identified profiles only and may identify users by Clerk user ID when enabled. Sentry may collect error details, stack traces, browser/device information, URLs, and contextual diagnostics. Hosting and backend providers may collect IP address, request metadata, logs, and security events.

4. How We Use Information

We use information to:

• operate, authenticate, maintain, and secure the Service;
• create and manage Signed-In User records;
• determine Target Handle eligibility, including whether an account is public, private, protected, deleted, suspended, unavailable, restricted, minor-associated, or safety-sensitive;
• show public Target Handle pages, aggregate counts, parody/opinion outputs, charts, share previews, and market state;
• record, enforce, and display Marks, Paid Actions, Target Handle policies, counters, and public count safety;
• process payments and settle paid product effects;
• handle support, removal, privacy, legal, moderation, appeal, safety, fraud, and chargeback requests;
• detect abuse, harassment, spam, fraud, rate-limit evasion, automation abuse, security incidents, targeting of minors, and payment risk;
• enforce Terms, policies, legal rights, and safety controls;
• debug, measure, analyze, improve, and develop the Service;
• comply with law, legal process, and enforceable government requests.

5. Public Information

Target Handle pages are public account-level game surfaces. Public pages may show Target Handle information, aggregate counts, parody/opinion outputs, history, charts, Market Listings, share previews, Open Graph images, and other product state.

Market Listings may publicly show a Paid Action's Target Handle, effect, amount, status, and timing, but not buyer identity by default.

Public X/Twitter profile information may remain visible on the Service unless removed, hidden, restricted, or updated through product rules, authenticated owner removal, legal process, safety review, privacy review, or operator discretion.

The Service does not provide comments, direct messages, public free-text posts, user bios, user-uploaded media, user-created accusations, or user-to-user communication.

6. How We Share Information

We may share information with:

• service providers and infrastructure providers, including Clerk, Convex, Stripe, PostHog, Sentry, SocialData, hosting/CDN providers, and email/support tools;
• payment processors and financial providers to process payments, refunds, chargebacks, disputes, fraud reviews, and settlement;
• public users, through public Target Handle pages, aggregate counts, parody/opinion outputs, Market Listings, share previews, and Open Graph images;
• advisors, lawyers, accountants, auditors, insurers, and professional service providers;
• authorities, courts, law enforcement, payment networks, or other recipients when we believe disclosure is required or appropriate for legal, safety, fraud, payment, abuse, privacy, or enforcement reasons;
• successors or acquirers in connection with a merger, acquisition, financing, reorganization, sale of assets, or similar business transaction.

We use X/Twitter-related data sources for authentication and public profile data. Whether the Service directly discloses information back to X/Twitter beyond ordinary authentication/provider interactions remains a final lawyer/product review item.

7. User Choices, Non-User Requests, And Rights

If Mark removal is enabled, you may be able to clear your own existing Mark. You may request access, deletion, correction, or other privacy assistance by contacting the contact listed in this Privacy Policy.

A Target Handle owner, parent, guardian, authorized representative, or person with a credible safety or privacy concern may request removal, restriction, review, access, deletion, correction, or other privacy assistance. Approved Target Handle removal should stop the Target Handle from being publicly viewed and voted on, subject to retained legal, safety, fraud, payment, audit, abuse-prevention, settlement-integrity, public count coherence, and operational records.

You may also be able to manage some authentication information through the identity provider you used to sign in.

You may have rights under California, other U.S. state, EEA/UK, or other privacy laws depending on where you live and whether those laws apply to us.

8. Retention

We retain information as needed to operate, secure, enforce, audit, improve, and defend the Service; process payments; resolve disputes; prevent fraud and abuse; maintain public count and paid-action integrity; comply with legal obligations; and support moderation, safety, privacy, and legal requests.

Some records may be retained after account deletion or Target Handle removal for integrity, safety, fraud prevention, legal compliance, payment disputes, public auditability, abuse prevention, or settlement integrity.

Account deletion may delete, hide, or de-identify associated user data where practical and legally appropriate. Financial transaction records and related payment, dispute, fraud, compliance, audit, safety, and settlement-integrity records may be retained when needed. After account deletion, old Marks will be deleted or de-identified from the Signed-In User's identity where practical while retaining minimal de-identified aggregate, audit, fraud, history, abuse-prevention, and settlement-integrity records needed to keep public counts and paid-action history coherent.

9. Target Handle Requests

A Target Handle may be public information but can still create privacy and safety concerns. A Target Handle owner, parent, guardian, authorized representative, or person with a credible safety or privacy concern can request removal, restriction, or review.

We may hide or restrict Target Handle pages and voting surfaces for private, protected, deleted, suspended, unavailable, restricted, minor-associated, safety-sensitive, high-risk, or otherwise inappropriate handles.

10. Children And Sensitive Information

Signing in, casting Marks, changing Marks, clearing Marks, and buying Paid Actions are restricted to users who are at least 18 years old. The Service does not knowingly maintain public Target Handle pages for minor-associated accounts and may hide, restrict, remove, freeze, or review minor-associated handles.

Do not submit sensitive personal information in support, removal, privacy, legal, safety, or moderation requests unless it is necessary for the request.

11. International Processing

We and our providers may process information in the United States and other countries. Those countries may have data protection laws different from where you live.

12. Security

We use reasonable safeguards designed to protect information. No security measure is perfect, and we cannot guarantee that information will always remain secure. This policy intentionally avoids detailed security promises that have not been separately approved.

13. Changes To This Policy

We may update this Privacy Policy by posting a revised version. Continued use after changes become effective means the updated Privacy Policy applies.

For material privacy changes, we will use reasonable notice such as posting, in-app notice, or email where we have an email address from direct user communication.