WeeHub Privacy Policy

Last updated: October 25, 2026

1. Scope and contact

This policy describes information handled by the WeeHub Discord bot, the WeeHub website at weehub-site.pages.dev, the WeeHub store at weehub.mysellauth.com, and the associated key and licensing backend. For privacy questions, access, correction, or deletion requests, contact WeeHub through https://weehub.mysellauth.com/customer/tickets or ask the WeeHub Discord server staff to put you in contact with the bot owner. The owner can also be identified by Discord user ID 837510996075610194. Do not send passwords, payment-card numbers, wallet private keys, or other unnecessary sensitive information in a request.

2. Discord bot information

Depending on the features you use and the permissions granted by your server, the bot receives Discord user IDs, server IDs, channel and message IDs, usernames or display names, command and button interactions, role and permission information, and information you submit to a command or support channel. The bot stores feature records such as moderation warnings and reasons, moderator IDs, ticket ownership and status, submitted script titles, descriptions and URLs, review decisions, XP and coin balances, daily-reward timestamps, and giveaway prizes, entries and results. It processes message events to award XP; the current rewards implementation does not store the body of ordinary chat messages in its profile database. Content you submit to tickets, commands, announcements or moderation features may be processed by Discord and may be visible to the relevant server staff or channel members. License-management commands may process a key you submit to validate access or reset a device binding.

3. Website, keys, and software verification

The key service processes access-session identifiers, checkpoint completion proofs, license identifiers, key hashes, activation and expiration times, revocation status, and device-binding hashes. Device identifiers supplied by the loader are hashed for the license binding. Network requests include your IP address; the key backend uses it for rate limiting and may store a keyed hash for session verification. Free-key verification can involve LootLabs or Linkvertise. The loader may also report a temporary session ID, Roblox user ID, username and last-seen time for live-session statistics. The configured WeeHub owner can view the live account list; it is not a public account list.

4. Purchases and external services

SellAuth processes checkout information, which can include your email address, IP address, order details and payment status. Stripe and other enabled payment providers process payment details under their own policies. WeeHub's SellAuth delivery handler receives signed delivery data but does not persist the supplied buyer email or IP in its delivery records; it stores order and delivery identifiers, verification metadata and licensing information. We do not ask for or store full payment-card details or wallet private keys in the WeeHub bot or licensing database.

Discord, Bot-Hosting, Cloudflare, SellAuth, Stripe, LootLabs, and Linkvertise may process information as needed to provide their services. Free-key providers may use cookies, advertisements and their own verification systems. Clicking a provider or checkout link takes you to that provider's service and privacy practices. Infrastructure providers may retain technical or security logs under their own policies, including outside your country.

5. Why information is used and who can see it

Information is used to run requested bot features, manage server safety and support, maintain rewards and giveaways, process purchases, verify checkpoint completion, issue and validate keys, enforce one-device licensing, prevent fraud and abuse, and diagnose errors. Server moderators can access records relevant to their permissions; the WeeHub operator can administer bot and licensing records. Public submissions, leaderboard results, announcements or giveaway results may be visible to others according to the feature and channel. Discord API data is not sold or used for advertising, profiling for advertising, or training AI models. Advertising services reached through free-key links operate separately under their own policies.

6. Local storage and retention

The website uses browser local storage to remember key sessions and preferences. The Linkvertise route uses a signed, secure, HTTP-only session cookie to associate the checkpoints with your browser. Clearing storage can prevent you from recovering an unfinished session. Storefront and payment providers may use additional cookies and present their own cookie controls.

Bot feature records, moderation history, licensing and order-verification records do not all have automatic deletion schedules. They are retained as needed for the feature, support, security, disputes or applicable legal requirements, and may require manual removal. License expiration does not automatically delete its records. Live-session reporting uses a short activity window and removes stale records as updates are processed. Hosting logs and backups may have separate retention periods. Removing the bot from a server does not itself guarantee deletion of existing records.

7. Your choices and requests

You may stop using optional features, clear browser storage, leave a server, or ask server administrators to change permissions or remove the bot. Contact WeeHub using the methods above to request access, correction, deletion or other rights available under applicable law. Include only the Discord user or server ID, or order reference, needed to identify your records. We may need to verify that you control the relevant account and may retain limited information when required by law or reasonably necessary for security or an unresolved dispute. Removing data may reset rewards, remove submissions or affect the ability to verify a license. Requests about data held independently by Discord or a payment or advertising provider should also be directed to that provider.

8. Security, age requirements, and changes

We use measures such as restricted administrative access, server-side secret storage, signed provider verification, and hashed licensing identifiers. No system can guarantee complete security. Use Discord and other services only if you meet their applicable age requirements; do not submit children's personal information unnecessarily. Material changes to this policy will be posted here with an updated date. Contact WeeHub if you have questions about how a change affects your information.