1. Scope and deployment model

This policy applies to Skynet-operated services and public deployments using the Skynet website and bot stack. If the software is self-hosted by another operator, that operator may control the data for their deployment and may publish additional or different privacy terms.

2. Information we may collect

• Authentication and profile data: Discord ID, username, avatar, email address if provided by Discord, server membership list, and server-level permissions needed for dashboard access control.
• Service configuration data: server settings, command preferences, moderation rules, extension settings, social alert configurations, role mappings, embed templates, and related admin-entered data.
• Bot interaction data: slash command usage, command arguments, channel or guild identifiers, audit events, moderation events, points/economy events, or other operational metadata required to fulfill the feature you use.
• Content you submit: messages sent to AI features, form responses, extension content, support requests, public profile content, custom text entered into dashboards, and other data intentionally submitted by users or administrators.
• Technical data: IP address, browser and device details, session identifiers, request metadata, security events, real IP forwarding headers, and related log information.
• Billing and account status data: subscription state, payment processor customer identifiers, invoice metadata, redemption status, and transaction-related records needed to enable premium services.
• Analytics and operational telemetry: page views, downloads, clicks, command metrics, performance metrics, crash reports, and service health information.

3. How we use information

We process information for the following purposes:

• to authenticate users and secure access to the website and dashboard;
• to operate bot commands, dashboard tools, moderation features, activity tracking, forms, social alerts, music, AI tools, extensions, and premium features;
• to customize outputs, maintain preferences, and store server or user configuration;
• to prevent spam, fraud, abuse, malicious traffic, extension misuse, and other harmful behavior;
• to monitor uptime, debug failures, improve performance, and understand which features are being used;
• to process subscriptions, payment confirmations, and support or billing requests;
• to comply with legal obligations and enforce platform rules.

4. Cookies, sessions, analytics, and tracking

Skynet uses cookies, sessions, and comparable browser storage to support login sessions, security controls, form protection, analytics, and site reliability. Some third-party services may also set cookies or use similar identifiers.

• Essential session cookies: used to keep you signed in and protect authenticated routes.
• Security and anti-bot technologies: may include Cloudflare security tooling and Turnstile where enabled.
• Analytics: may include Matomo and other observability systems to measure visits, events, downloads, errors, and performance.
• Advertising-related technologies: if advertising is enabled on a deployment, third parties may use cookies for delivery, measurement, or personalization.

You can manage cookies through your browser settings, but disabling them may impact sign-in and certain site features.

5. When information may be shared

We do not sell personal information. We may disclose or make information available to subprocessors and vendors only where necessary to operate or protect the service. Depending on enabled features, this may include:

• Discord for login, bot events, guild data, and platform functionality.
• Cloudflare for CDN, network security, proxying, country filtering, Turnstile, and related traffic services.
• Monitoring and analytics providers such as Sentry, Matomo, Prometheus, Grafana, Loki, or comparable telemetry tools.
• Payment and membership providers such as Stripe, PayPal, Patreon, or BTCPay where subscriptions or purchases are offered.
• AI and infrastructure providers such as OpenAI, Anthropic, Groq, Ollama-compatible providers, Redis, Qdrant, database services, or cloud hosting providers where those features are used.
• Integration providers such as Twitch, YouTube, GitHub, Google, or other APIs used by social alerts, account linking, analytics, or related features.

We may also share information if required by law, to respond to valid legal requests, to investigate suspected abuse, or to protect the service, users, or the public.

6. Retention and security

We retain data only for as long as reasonably necessary for service operation, security, troubleshooting, auditability, contractual performance, and legal compliance. Different data categories may be retained for different periods based on operational need.

We use technical and organizational safeguards intended to protect information from unauthorized access, disclosure, alteration, or destruction. However, no internet-connected system is completely immune from risk.

7. Your rights and choices

Depending on your location and applicable law, you may have rights to:

• request access to information associated with your account or use of the service;
• request correction of inaccurate information;
• request deletion of certain information, subject to legal and operational exceptions;
• object to or restrict certain processing activities;
• withdraw consent where processing is based on consent;
• disconnect integrations or stop using the service at any time.

To make a privacy request, contact us with enough information to identify the relevant Discord account, server, or website account context.

8. Children and minimum age

The service is intended for users who meet Discord’s minimum age requirements and any applicable legal age requirements in their jurisdiction. If you believe a child provided personal information unlawfully, contact us so we can review and respond appropriately.

9. Contact and policy updates

Questions, access requests, deletion requests, and privacy concerns can be sent through the support server or the GitHub repository.

We may update this Privacy Policy from time to time. When we do, we will revise the effective date on this page. Continued use of the service after an update becomes effective means you accept the revised policy.