GearCheck Legal

Privacy Policy

This policy explains what GearCheck collects, why it collects it, who can see it, and how guild owners, staff, and members can think about privacy across the dashboard and Discord bot.

Last updated: May 7, 2026Version: 2026.05.07
This page is a product-specific privacy draft for GearCheck. It should be reviewed by the product owner and qualified privacy/legal counsel before being treated as final legal advice.

1. Overview

GearCheck helps Discord gaming communities manage build requirements, collect evidence, score verifications, assign roles, review submissions, publish packs, send notifications, and operate readiness tools. To do that, GearCheck processes data from the web dashboard, Discord bot, guild configuration, evidence submissions, billing flows, and optional integrations.

GearCheck is not designed to sell personal data. GearCheck uses data to provide, secure, debug, improve, and support the service. Public community stats are aggregate-only and are not intended to expose private guild names, member identities, verification evidence, or private configuration.

2. Data We Collect

Depending on how a guild uses GearCheck, we may collect:

  • Discord identifiers such as user IDs, guild IDs, channel IDs, role IDs, thread IDs, usernames, display names, and avatar URLs.
  • Guild configuration such as staff permissions, channels, roles, language settings, billing state, notification rules, RaidHelper settings, support ticket settings, and setup progress.
  • Pack and build data such as activities, categories, item names, aliases, exclusions, game-specific build requirements, custom messages, custom assets, marketplace listings, and install history.
  • Verification evidence such as uploaded screenshots, pasted text, structured exports, OCR text, export parse results, checklist results, scores, verdicts, review queue state, staff notes, and override history.
  • Discord workflow data such as slash command usage, support ticket messages, notification delivery history, readiness reports, bot DMs, and message links related to GearCheck actions.
  • Billing and entitlement data such as plan, access tier, access pass codes, lifetime access status, Stripe customer or subscription references, payment status events, and billing-related support metadata. GearCheck does not store full card numbers.
  • Operational data such as logs, error traces, IP-derived request metadata, browser/device information, API usage, rate limits, deployment health, and diagnostics needed to operate the service.

3. Where Data Comes From

GearCheck receives data from:

  • Guild owners, staff, and members who use the dashboard or bot.
  • Discord APIs, OAuth, bot interactions, messages, and events.
  • Evidence files, screenshots, exports, and text pasted by users.
  • Third-party integrations such as Stripe and RaidHelper when enabled.
  • Game data providers, community databases, and export add-ons used to interpret evidence.
  • Infrastructure providers, logs, and monitoring systems used to run GearCheck.

4. How We Use Data

GearCheck uses data to:

  • Authenticate dashboard users and determine guild access.
  • Run verification workflows and score evidence against build requirements.
  • Assign, remove, or recommend Discord roles based on guild configuration.
  • Show dashboards, analytics, review queues, data inventory, audit ledgers, and readiness reports.
  • Deliver Discord notifications, bot messages, support ticket updates, and owner/admin alerts.
  • Operate billing, access passes, lifetime access, subscriptions, and entitlement gates.
  • Debug errors, investigate support issues, detect abuse, protect the service, and improve product quality.
  • Generate aggregate community stats and marketplace signals without exposing private guild evidence.

5. How Data Is Shared

GearCheck shares data only as needed to provide the service, with the people and systems involved in that service. For example:

  • Guild staff may see verification results, evidence summaries, review queue entries, staff notes, roster readiness, tickets, and dashboard analytics for their guild.
  • Guild members may see bot messages, thread results, role outcomes, DMs, and other feedback generated by workflows they interact with.
  • Public marketplace listings and community pages may show content a guild intentionally publishes or aggregate usage data.
  • Discord receives bot messages, role updates, channel/thread interactions, and other Discord API actions needed for GearCheck to work.
  • Stripe or other payment processors receive billing data needed to process payments, manage subscriptions, and report payment status.
  • Infrastructure and support providers may process logs, database records, file storage, and monitoring data needed to operate GearCheck.

GearCheck may disclose data if required by law, to protect the service, to investigate abuse or fraud, to respond to security incidents, or as part of a business transfer such as a merger, acquisition, or sale of assets.

6. Data Retention

GearCheck keeps data as long as needed to provide the service, maintain guild history, support exports, debug issues, comply with legal obligations, prevent abuse, and preserve billing or entitlement records.

Guild owners or authorized staff may be able to delete, overwrite, export, or unpublish certain guild content through the dashboard. Some logs, backups, billing records, abuse-prevention records, and operational records may remain for a limited period after deletion or removal.

7. Security

GearCheck uses reasonable technical and organizational safeguards to protect data, including access controls, scoped credentials, managed infrastructure, and operational logging. No online service can guarantee perfect security.

Guild owners should keep Discord permissions tight, avoid sharing dashboard access with untrusted users, review role/channel configuration, and avoid uploading secrets or private credentials as evidence.

8. Your Choices and Rights

Guild owners and authorized staff can change many GearCheck settings in the dashboard, including roles, channels, packs, builds, notifications, marketplace listings, custom assets, and some data exports. Members can choose what evidence they submit, whether to interact with optional workflows, and whether to leave a Discord server using GearCheck.

Depending on where you live, you may have privacy rights such as access, correction, deletion, portability, objection, restriction, or withdrawal of consent. GearCheck may need to verify your identity and guild relationship before acting on a request.

9. Children

GearCheck is intended for Discord communities and is not directed to children under 13 or anyone below the minimum age required to use Discord in their region. Guild owners are responsible for running their communities in a way that follows Discord rules and applicable law.

10. International Use

GearCheck may be used by guilds and members in different countries. Data may be processed in the United States or other locations where GearCheck, its infrastructure providers, or its third-party processors operate.

Third-party services have their own privacy policies. Useful references include Discord's Privacy Policy and Stripe's Privacy Policy.

11. Updates to This Policy

GearCheck may update this policy as the product, integrations, data practices, or legal requirements change. The page will show the latest updated date and version.

12. Contact

For privacy questions or requests, use the support options linked in the dashboard or documentation. You can also review the Terms and Conditions for related service rules.