Policies

Terms of Service

Effective and last updated: 29 October 2026. These terms cover Skye, the Discord bot operated by jdkcube, and this documentation website. Skye is an independent community project, not a Discord product or an emergency service.

1. Using Skye

By adding Skye to a server or using its features, you agree to these terms. If you do not agree, stop using the bot and, if you administer the server, remove it. The privacy policy below explains data handling; accepting these terms does not replace any consent required by law.

You must meet Discord’s minimum age requirement, including any higher minimum in your country, and follow Discord’s Terms of Service and Community Guidelines. If local law requires a parent or guardian’s permission, obtain it before using Skye.

2. Server administration and permissions

Only install or configure Skye where you are authorized to do so. Server administrators choose enabled modules, channels, roles and moderation rules, and are responsible for informing members about relevant features. Grant only the permissions needed for the features you use. The invite does not request Administrator; additional capabilities may require specific permissions or Discord server features.

Check targets, settings and confirmation prompts before taking action. Deleting messages, channels, roles or webhooks can be irreversible. Moderation and anti-abuse tools depend on Discord permissions, role order, configuration and availability. They do not guarantee prevention of raids, unauthorized changes, lost data or false positives, and they are not a backup service.

Server admission is controlled by the bot owner’s whitelist. Server administrators cannot approve their own servers. In an unauthorized server, Skye attempts one explanatory notice, privately notifies its owner and leaves; reconnect checks also enforce this restriction.

Review automated enforcement before enabling it. Scamcatcher warns members not to post in its configured trap channel and attempts to delete messages and kick eligible senders with the reason “compromised account”. An automated action is not proof of wrongdoing. Invite-tracking “fake” counts describe early departures, not verified malicious or alternate accounts. Server administrators should review disputes and incorrect enforcement.

Administrators are responsible for custom ticket prompts, links, images, support-role routing and who can access each ticket. Do not ask members to submit credentials or unnecessary sensitive information. Preview panels and verify access before publishing them.

3. Acceptable use

• Do not use Skye for harassment, spam, discrimination, doxxing, impersonation, illegal activity or unauthorized access.
• Do not exploit vulnerabilities, bypass permissions or rate limits, manipulate virtual balances through abuse, or deliberately disrupt the bot or other servers.
• Do not submit passwords, access tokens, financial details, health information or other sensitive personal information through commands, confessions or third-party lookups.
• Only submit text, images and other material you are entitled to use. Respect other people’s privacy and intellectual property.
• Report suspected vulnerabilities privately by joining support and opening a ticket. Do not test destructive behaviour on servers without permission or post secrets in public reports.

4. Community content and virtual games

You retain your rights in submitted content. You allow Skye to process and display it as needed for the feature you request—for example, posting an announcement, translating text, delivering a reminder or forwarding a bug report. You are responsible for your submissions.

Confessions are anonymous to ordinary readers, not to the operator: author IDs are retained for abuse investigations. Prefix command text may be visible before a deletion completes. Do not use confessions as a secure or confidential reporting channel.

Coins, XP and casino-style games are entertainment only. Virtual balances are server-specific, have no cash value, and cannot be purchased, redeemed or exchanged for money or goods through Skye. Skye does not accept real-money wagers. Do not use its virtual games to facilitate real-money gambling.

Giveaway hosts are responsible for eligibility, prizes, lawful operation and prize delivery. Skye only manages entries and winner selection; it does not sponsor or guarantee a giveaway.

5. Donations and supporter recognition

Optional donations are made through jdkcube’s Ko-fi page. The official server’s donation integration assigns the Supporter role automatically; opening a ticket is not required to receive it. Follow the donation page’s account-linking instructions where applicable. The bot’s donate command only provides links and information; it does not process payments or assign the donation role itself.

Donations do not purchase virtual currency, moderation privileges, server-whitelist approval or guaranteed availability. Payment processing and any refund request are subject to the terms shown at checkout and applicable law; these terms do not remove mandatory consumer rights. If automatic recognition fails, contact support without sharing payment credentials or full financial details.

6. Availability, changes and suspension

Skye is provided free of charge and is under active development. There is no uptime or support-response guarantee. Maintenance, errors, hosting interruptions, Discord changes and third-party outages may delay commands, reminders or temporary moderation expiry. Features and limits may change or be discontinued.

We may restrict access, disable features or remove Skye from a server to address abuse, security, legal requirements or operational needs. We will provide notice where practical, but urgent protective action may occur first. Stored data may be lost through failures; do not rely on Skye as your only record.

7. Responsibility and your legal rights

To the extent permitted by applicable law, Skye is provided as available, without a promise that it will be uninterrupted, error-free or suitable for a particular purpose. To that same extent, the operator is not responsible for indirect or consequential loss arising from use, downtime or third-party failures.

Nothing in these terms excludes or limits rights, warranties or liability that cannot lawfully be excluded or limited, including applicable consumer rights. Server administrators and Discord retain their own responsibilities; these terms do not replace their rules.

8. Changes and contact

Updates will be posted here with a revised date. Material changes will be announced through support where practical, and any notice or consent required by applicable law will be respected. If you no longer agree, stop using Skye. Questions, abuse reports and disputes should be raised by joining the support server and opening a ticket for jdkcube.

Privacy Policy

Effective and last updated: 29 October 2026. This policy covers data handled by the Skye bot and this website. The operator is jdkcube. For privacy questions, access, correction or deletion requests, join the support server and open a ticket. Do not post personal information in a public support channel.

1. What the bot receives

Discord supplies information the bot is allowed to access: user, server, channel, message and role IDs; usernames and display names; avatars; membership and role information; command arguments and interactions; messages in accessible channels; and relevant server events. Presence data is available only when the operator enables Discord’s presence intent. The bot does not record voice audio.

Receiving an event does not mean all of its contents are permanently stored. Message content is processed to run commands and configured features such as filtering, counting, automatic responses, XP and AFK notices. The Discord client also maintains temporary in-memory caches. Skye cannot read arbitrary private conversations between other users.

2. Data stored for features

• Configuration and access: server preferences, enabled modules, channel and role IDs, panel text, custom aliases/responses, security rules, exemptions, and saved permission states.
• Tickets and voice rooms: channel IDs, owner IDs, ticket panel/support-role references, temporary-room ownership and configuration. Ticket conversation content stays in Discord; the current implementation does not export or retain a separate transcript archive. Saved embed templates and welcome, goodbye and boost messages may also contain administrator-provided text, images and channel references.
• Moderation and membership: warnings and recent moderation cases with reasons, target and moderator IDs, outcomes and timestamps; temporary-ban identifiers and expiry records; moderation counters; and join, leave, nickname and role-change history. Membership history is recorded independently of whether optional event logging is enabled.
• Invite tracking: when explicitly enabled for a server, invite codes and usage snapshots, inviter/member IDs, join and departure times, attribution status, the visit’s configured early-departure threshold and aggregate statistics. Collection is off by default. Attribution can be unknown or ambiguous when Discord does not expose enough information.
• Security and configuration: anti-nuke/anti-raid settings and operational state, trusted-user IDs, saved restriction/permission states, and scamcatcher event records including account identifiers, timestamps and kick/deletion outcomes. A separate persistent configuration journal records actor and server IDs, actions, timestamps and previous/new values, with selected free-text values hashed or redacted. Disabling optional Discord logging does not disable this journal.
• Server authorization: approved server IDs and admission-notification state. Unauthorized-server reports to the bot owner include server name/ID, available owner information, join time and an existing public vanity invite when available; the admission check does not create an invite.
• Community activity: balances, reward cooldowns, XP, reminder text and due times, AFK reasons/timestamps, giveaway entries and winners, counting state, bump-reminder state, and booster-role ownership/sharing.
• Confessions: author ID, confession number and posted message ID for abuse investigation. The posted confession itself remains in Discord. The local record is not a promise of anonymity from the operator.
• Bug reports: report text, reporter ID, server context, report ID and timestamp. Reports may be forwarded to the operator’s Discord messages and a configured report channel, including channel context.
• Deleted messages: the snipe feature temporarily retains author information, a bounded content excerpt, deletion time and an attachment URL when present. Command messages are excluded from this cache.

Ticket customization also stores panel/opening message and embed templates, media/link URLs, menu type, stable reason identifiers and labels, optional per-reason category/support-role routing, channel-name templates and ping preferences. Open-ticket records include the selected reason and option identifier alongside ownership/channel metadata. Ticket messages remain in Discord; these customization records are not a separate transcript archive. Private announcement previews render saved or draft text without changing configuration. Discord may load administrator-provided embed media and links under its own handling.

3. Why data is used and who can see it

Data is used to deliver requested or administrator-configured features, enforce permissions, operate moderation and anti-abuse controls, investigate reports, and maintain the service. We do not sell or license Discord user data, use it for advertising, or use message content to train AI models.

Command responses and feature output are often visible in their Discord channel. Examples include leaderboards, AFK notices, reminders and polls. Ticket participants, support staff and administrators may see ticket content. Authorized moderators can retrieve recent snipes or membership history. When enabled, independently configured logging categories can send message/attachment metadata, member and profile changes, voice connection events, moderation and security actions, role/channel/permission changes, invites, webhooks, emoji/sticker changes, commands/errors and configuration events to selected channels. Actors are identified only where supported by reliable event or audit-log information. Voice logs describe connection events, not audio. Event delivery depends on Discord permissions, intents, availability and bounded processing; message edit/delete logs do not copy message bodies, and command messages are excluded.

Any server member can view saved invite statistics and the latest tracked inviter for another member through the invite commands; these are not moderator-only records. Enabling tracking should therefore be communicated to members. Tracking is per server and is not intended to identify relationships across servers.

Sensitive moderation commands use private responses or appropriately restricted delivery where supported. A successful command-related DM may produce a content-free confirmation in the originating server, without naming its recipient or revealing the message. Prefix commands and their arguments can still be visible in the channel where they were sent.

The operator can access locally stored data and reports for operation and support. Discord processes bot interactions, messages and attachments under its privacy policy. Information may also be disclosed where required by law or necessary to address abuse, security incidents or the protection of legal rights.

Where data-protection law requires a legal basis, processing requested features is used to provide the service, and proportionate security, abuse prevention and support processing is based on legitimate interests. Legal obligations or consent may apply in specific circumstances. You may ask the operator about the basis relevant to your situation and exercise applicable rights below.

4. Third-party requests

• Translation: text and language choices are sent to MyMemory / Translated. An operator-configured contact email may accompany requests. Do not translate confidential or sensitive text.
• Weather: a location query is sent to Open-Meteo for geocoding, followed by a weather request for the resulting coordinates.
• Definitions: the requested word is sent to Free Dictionary API.
• Reaction images: an action category is requested from nekos.best; the lookup does not require sending the mentioned member’s ID. Discord may load the returned media.
• Donations: following the Ko-fi link sends you to an external payment/support platform. Ko-fi, its payment providers and the official server’s donation integration handle the information needed for payment and automatic supporter recognition under their own notices. The bot’s link command does not collect card details.
• Images: uploaded images and supported Discord CDN links are downloaded and validated for the requested profile or server customization, then sent to Discord.

These providers receive the request data and network metadata such as the bot host’s IP address. Their handling is governed by their own policies. Skye’s deletion of local data does not automatically delete information already processed by Discord or an external provider. Services may process data outside your country; their policies describe their arrangements.

5. Retention and deletion

Temporary memory: snipe records are limited to 10 per channel, expire after one hour and are periodically removed; a bot restart clears them. Authorized moderators can clear a channel’s snipe cache. Short-lived game and rate-limit state expires, is pruned or is cleared on restart.

Bounded records: the local database retains up to 100 bug reports and 200 confession-author mappings per server, and up to 25 membership-history events per user across at most 1,000 stored users per server. Recent moderation cases are bounded to 1,000 per server; scamcatcher event history is also bounded while aggregate counters may remain. These are count limits, not guaranteed time-based deletion periods.

Persistent records: configuration, balances, XP, warnings, ownership and similar state remain until the relevant feature removes or replaces them, an authorized user/admin uses an available removal command, or the operator handles a request. Reminders are removed after delivery/cancellation, or after their delivery-retry period expires. Invite history and its statistics survive restarts and disabling tracking. The security configuration journal is persistent and has no general automatic expiry. There is no universal automatic deletion period. Disabling a module or removing Skye from a server does not automatically erase its saved database records.

Discord copies: bot responses, log messages, confession posts, reports and support tickets remain in Discord until deleted there under the relevant permissions and Discord’s handling. Clearing a local record does not erase screenshots, third-party copies or messages already posted. Diagnostic logs and any recovery copies are separate from feature records; ask support to include relevant operator-controlled copies in your request. We do not promise a backup-retention period that has not been established.

6. Your choices and requests

Use available feature controls to cancel reminders, remove your AFK status or stop participating. Server administrators can disable optional modules and remove the bot’s permissions or installation. For broader requests, join support and make a ticket.

In the ticket, say whether you want access, correction or deletion, provide your Discord user ID and relevant server ID(s), and describe the records involved. We may ask you to verify control of the account or your authority over server configuration. Never provide your password, bot token or account token. We will assess the request and respond without undue delay and within applicable legal deadlines; requests for Discord API data will be handled consistently with Discord’s developer requirements, including prompt correction or deletion on an applicable user’s request and deletion when the data is no longer necessary or the application stops operating, except where retention is required by law. Any legally required retention or limitation will be explained. The absence of an automatic expiry does not mean records must be kept indefinitely.

Depending on applicable law, you may also have rights to portability, restriction, objection, withdrawal of consent where consent is used, and a complaint to your local data-protection authority. These rights are not all absolute. Server moderation disputes should also be raised with that server’s administrators; only the operator can address Skye’s separate local records.

7. Website, security and children

This website does not include advertising or analytics scripts. It stores your light/dark theme preference in your browser until you clear site data. Search and category filtering run in your browser and are not sent to the bot. The website host may process access/security logs, including IP addresses and request metadata. Google Fonts is loaded from Google, which receives the browser request; see Google’s privacy policy. Following an external link subjects that visit to the destination’s policies.

Skye uses permission checks, bounded processing and restricted local file access to reduce risk. These measures do not guarantee absolute security or confidentiality; no claim of end-to-end encryption is made for bot data. Report suspected exposure privately through a support ticket.

Skye is not intended for anyone below Discord’s minimum age or a higher applicable local minimum. If you believe ineligible child data has been provided, contact support so it can be investigated and appropriately removed. Do not submit sensitive child information in a public channel.

8. Policy changes

Changes will be posted with an updated date. Material changes will be announced through support where practical; additional notice or consent will be provided when required. For questions about these terms or this policy, contact jdkcube by joining support and opening a ticket.