Privacy Policy

Last updated: May 26, 2026

1. Introduction

RoAppeal is owned and operated by Nexus Code, LLC, a Delaware limited liability company ("Nexus Code", "we", "us", or "our"). Nexus Code operates the RoAppeal website, dashboard, backend systems, appeal draft generation, user-authorized submission, email monitoring, and related support features (the "Service"). This Privacy Policy explains what information we collect, how we use it, how we share it, and the choices and rights you may have.

This Privacy Policy is a notice about our data practices, not a request for every possible consent. Where applicable law requires consent for a specific processing activity, we will request it separately or through the relevant product control. If you do not want your information processed as described here, do not use the Service.

2. Information We Collect

Information You Provide Directly

  • Account information - Email address, display name, OAuth identity information, and account settings.
  • Order information - Roblox username, submission or notification email, optional situation description, ban-type selection, order status, pause/resume choices, tokens, and related settings.
  • Notification settings - Discord webhook URLs, Discord direct-message preferences, public approval display choices, email notification choices, and similar preferences.
  • Support information - Messages, screenshots, files, order IDs, appeal details, and other information you send to us for support or dispute handling.

Information Collected Automatically

  • Authentication and security data - Session tokens, account identifiers, OAuth account links, captcha verification results, rate-limit records, and security logs.
  • Order and appeal records - Generated appeal drafts, authorized submission attempts, response status, response metadata, restored/denied/escalated results, sender email, timestamps, and operational history.
  • Email monitoring data - Roblox emails and metadata received through RoAppeal-controlled tracking addresses, email routing infrastructure, IMAP mailboxes, or a connected Gmail or Outlook account.
  • Operational telemetry - Error logs, queue status, job timing, captcha-provider events, proxy-provider events, email-monitoring events, webhook delivery status, and service diagnostics.
  • Browser analytics data - If you opt in through our cookie banner, an analytics provider may collect product usage events such as page views, clicks, device/browser metadata, and session replay data where enabled.

Information from Third-Party Services

  • Discord OAuth - If you sign in with Discord, we receive your Discord user ID, email address if available, username, and profile details. We may use Discord for role sync, direct-message notifications, and webhook notifications where configured.
  • Google OAuth - If you sign in with Google, we receive Google account profile information such as your email address, name, and account identifier.
  • GitHub OAuth - If you sign in with GitHub, we receive GitHub account profile information such as your GitHub user ID, username, email address if available, and profile details.
  • Gmail API - If you connect Gmail, we receive Gmail OAuth tokens and access to search for, fetch, and send relevant Roblox emails, as described in Section 4.
  • Microsoft/Outlook - If you connect Outlook, we receive Microsoft OAuth tokens and access to search for, fetch, and send relevant Roblox emails, as described in Section 4.
  • Stripe - We receive checkout session, payment intent, and purchase confirmation data needed to verify card and supported wallet payments and activate orders. We do not receive your full credit card number, CVV, or payment card details.
  • NOWPayments - We receive crypto invoice, payment status, payment identifier, selected asset, price, and purchase confirmation data needed to verify cryptocurrency payments and activate orders. We do not receive your private wallet keys, seed phrases, or wallet credentials.
  • Roblox - We may receive public account, ban-status, appeal-response, and support-form results associated with the Roblox username you provide.

Information We Do Not Need

RoAppeal does not need and does not ask you to provide:

  • Your Roblox password, Roblox session cookie, two-factor codes, or direct Roblox account credentials.
  • Your full payment card number, CVV, or complete card details.
  • Your cryptocurrency private keys, seed phrases, or wallet credentials.
  • Your precise GPS location.
  • Your browsing history outside the Service.
  • Advertising profiles or cross-site behavioral advertising data.

3. How We Use Information

We use information to operate, secure, and improve the Service, including to:

  • Create, authenticate, secure, and manage accounts and sessions.
  • Validate Roblox usernames and ban status.
  • Process purchases, tokens, checkout intents, and order activation.
  • Generate appeal drafts using AI providers and fallback templates.
  • Submit approved or otherwise authorized appeals to Roblox support flows on your behalf.
  • Monitor Roblox responses through tracking email addresses, email routing infrastructure, IMAP, Gmail, or Outlook where connected.
  • Store matched Roblox response content and metadata so the dashboard, automation, support, and audit history can work.
  • Send transactional notifications by email, dashboard updates, Discord webhooks, or Discord direct messages where configured.
  • Detect abuse, prevent fraud, verify captcha challenges, enforce rate limits, debug failures, and protect the Service.
  • Measure product reliability and usage, including server-side operational events and optional browser analytics after consent.
  • Comply with legal obligations, enforce our Terms of Service, and respond to lawful requests.

We do not use your personal information, Gmail data, or Outlook data to sell advertising, serve personalized ads, determine creditworthiness, or build advertising profiles.

4. Gmail API, Outlook, and Connected Email Data

RoAppeal's use and transfer of information received from Google APIs is intended to adhere to the Google API Services User Data Policy, including the Limited Use requirements.

If you connect Gmail, RoAppeal requests Gmail API permissions that allow us to search for, fetch, and send Roblox emails relevant to your active orders. If you connect Outlook, RoAppeal requests Microsoft/Outlook permissions that allow us to search for, fetch, and send Roblox emails relevant to your active orders.

  • Purpose - We use connected email access only to provide user-facing response detection, draft handling, and approved or otherwise authorized submission features for active RoAppeal orders.
  • Limited searching and sending - We search for and send Roblox emails that are relevant to active orders. We do not intentionally search for, fetch, or send unrelated email.
  • Storage - Matched Roblox email content, response metadata, and parsed status may be stored in RoAppeal systems as part of your appeal record. We do not intentionally store unrelated connected-email messages.
  • No prohibited use - We do not sell Gmail or Outlook data, use Gmail or Outlook data for advertising, use Gmail or Outlook data for retargeting or personalized ads, or use Gmail or Outlook data to determine creditworthiness or lending eligibility.
  • Limited transfers - Google and Microsoft user data may be processed by our infrastructure and service providers only as needed to provide or improve the visible response-detection and appeal-management features, for security, for legal compliance, or as otherwise permitted by provider policy and applicable law.
  • Human access - Humans do not read connected-email message content unless you ask us to help with a specific support issue and provide consent, access is necessary for security or abuse investigation, access is required by law, or access is otherwise permitted by provider policy.
  • Revocation - You can revoke Gmail access at any time from Google Account Permissions and Outlook access through your Microsoft account permissions. Revoking access may prevent connected-email orders from detecting new Roblox responses or submitting approved or otherwise authorized new appeals until access is restored or the order is changed by an authorized path.
  • Tokens - Gmail and Outlook OAuth access and refresh tokens are stored so the connected account can continue monitoring relevant Roblox responses and sending approved or otherwise authorized Roblox emails. Tokens may be invalidated or marked revoked if the provider rejects them or you revoke access.

5. Legal Bases for Processing

If you are in the European Economic Area, United Kingdom, or another jurisdiction that requires a legal basis for processing, we rely on the following legal bases where applicable:

  • Contractual necessity - To create your account, activate orders, generate appeal drafts, submit approved or otherwise authorized appeals, monitor responses, and provide support.
  • Consent - For optional integrations, optional browser analytics, optional situation details, and other choices where we ask for permission.
  • Legitimate interests - To secure the Service, prevent fraud and abuse, debug failures, maintain reliability, improve features, and preserve dispute/audit records.
  • Legal obligation - To comply with applicable law, legal process, tax/accounting duties, and lawful requests.

6. How We Share Information

We do not sell your personal information. We share information with service providers and third parties only as needed to operate, secure, and improve the Service, process transactions, comply with law, or enforce our terms.

  • Appeal recipients and platform support channels - Receive approved or otherwise authorized appeal submissions, Roblox username, appeal text, and related form data needed to submit an appeal.
  • Payment processors - Process payments and send checkout, invoice, payment-status, and payment-confirmation data. Payment processors handle payment card details, crypto payment details, and related transaction processing.
  • Application infrastructure providers - Provide backend, database, authentication, account, session, and storage infrastructure.
  • Authentication, connected-account, and notification providers - Support OAuth login, connected-email response detection, approved or otherwise authorized email sending, role synchronization, webhook notifications, and direct-message notifications where enabled.
  • Email delivery and routing providers - Support inbound response routing and transactional email delivery.
  • AI providers - Receive the limited information needed to generate appeal drafts, such as Roblox username, attempt number, and optional situation description.
  • Security, captcha, and network providers - Process technical challenge, routing, and network information needed to submit approved or otherwise authorized appeals, prevent abuse, and measure service health.
  • Analytics, reliability, and debugging providers - Receive optional browser analytics after consent and server-side operational telemetry used for product analytics, reliability, debugging, and abuse prevention.

We may also disclose information if required by law or legal process, to protect rights and safety, to investigate abuse or fraud, or in connection with a merger, acquisition, financing, reorganization, or sale of assets, subject to applicable law and any required notice or consent.

7. Data Storage and Security

Data is stored and processed using cloud infrastructure that may be located in the United States and other regions used by our providers. We use reasonable technical and organizational measures designed to protect information, including:

  • OAuth authentication and session security controls.
  • HTTPS/TLS for data in transit.
  • Restricted backend access for authorized operators.
  • Session expiration and token invalidation controls.
  • Payment processing, payment card details, and cryptocurrency transaction processing are handled by our payment processors.

No electronic transmission or storage method is completely secure. We cannot guarantee absolute security.

8. Cookies, Local Storage, and Analytics

We use cookies and similar browser storage for the following purposes:

  • Strictly necessary storage - Authentication/session storage, security checks, consent preferences, and bot-protection functionality needed for the Service.
  • Optional browser analytics - Browser analytics and session replay, where enabled, load only after you opt in through the cookie banner or preferences dialog.

You can change browser analytics consent through Cookie preferences in the site footer. Withdrawing analytics consent stops future browser analytics capture and clears local analytics identifiers where supported.

Separately, RoAppeal may generate server-side operational telemetry about approved or otherwise authorized appeal submissions, errors, captcha/provider results, proxy health, and related service events. This backend telemetry is used for reliability, security, debugging, and product operations and is not controlled by browser cookie preferences.

We do not use advertising cookies, third-party ad pixels, or cross-site behavioral advertising tracking.

9. Data Retention

We retain information for as long as reasonably necessary to provide the Service, maintain records, comply with law, resolve disputes, prevent fraud and abuse, and enforce our agreements. Current system behavior includes:

  • Sessions - Authentication sessions are configured to expire after approximately 30 days, subject to renewal while active.
  • Rate-limit records - Rate-limit entries may be cleaned up after approximately 2 hours.
  • Operational logs - Captcha, proxy, and email-monitoring logs are generally cleaned up after approximately 14 days. Some error, admin, payment, webhook, or audit logs may be retained longer where needed.
  • Checkout and connection intents - Temporary checkout and connected-email intents are generally consumed, replaced, or deleted after use or expiration.
  • Orders, appeals, and responses - Order records, generated appeal drafts, sender emails, Roblox response bodies, response metadata, tracking addresses, and related history may be retained after an order ends for support, dispute resolution, fraud prevention, audit, legal, tax/accounting, and service-integrity purposes unless deleted or modified under an authorized process.
  • Connected email tokens - Gmail and Outlook tokens are retained while the email connection remains active or needed for connected orders, and may be marked revoked or removed when no longer needed or after access is revoked.

You may request deletion or correction by contacting us. We may deny, limit, or delay deletion where retention is reasonably necessary for security, fraud prevention, disputes, legal compliance, accounting, audits, or another lawful reason.

10. Children's Privacy

The Service is intended for a general audience aged 13 and older and is not directed to children under 13. We do not knowingly collect personal information from children under 13. If we learn that we collected personal information from a child under 13 without appropriate consent, we will take reasonable steps to delete it or take other steps required by applicable law.

If you are a parent or guardian and believe a child under 13 has provided information to us, contact [email protected].

11. Your Privacy Rights

Depending on your location, you may have rights to access, correct, delete, restrict, object to, or receive a copy of personal information we hold about you. You may also have the right to withdraw consent where processing is based on consent and to lodge a complaint with a data protection authority.

California residents may have rights under the CCPA/CPRA, including rights to know, delete, correct, opt out of sale or sharing, and non-discrimination. We do not sell personal information or share personal information for cross-context behavioral advertising.

To exercise privacy rights, contact [email protected]. We may need to verify your identity before processing certain requests. We will not require verification where applicable law does not permit it, such as certain opt-out requests.

12. International Transfers

Your information may be transferred to, stored in, or processed in the United States or other locations where we or our service providers operate. Data protection laws in those locations may differ from the laws where you live. Where required, we rely on appropriate lawful mechanisms for international transfers.

13. Changes to This Policy

We may update this Privacy Policy from time to time. We will indicate changes by updating the "Last updated" date. For material changes, we may provide additional notice where reasonable or required by law.

Your continued use of the Service after a policy update becomes effective means you accept the revised policy.

14. Contact

If you have questions, concerns, or privacy requests, contact [email protected].