1. Operator and scope

LCARS-Prime is created and operated by Stonedfury. In this Policy, “we,” “us,” and “our” refer to the Operator. This Policy applies to the Bot, the public policy and support pages, and Bot features operated by us. It does not replace the privacy policies of Discord, a Discord server, or third-party services.

2. Information the Bot may process

Discord identifiers and account context

Discord user IDs, server IDs, channel IDs, role IDs, message IDs, usernames, display names, avatar URLs, permissions, and similar identifiers may be processed when needed to provide a feature.

STFC profile and gameplay information

Information a user chooses to save, such as player name, operations level, game server, alliance information, ships, ship progress, officers, officer progress, rosters, fleets, crews, recommendations, and related preferences.

Server configuration and administration records

Server settings, administrator roles, log-channel choices, welcome settings, role panels, embed templates, AutoMod rules and exemptions, alert configurations, moderation cases, reasons, strikes, temporary punishments, permission audit records, and the Discord IDs of people who create or change those records.

Messages and submitted content

Message content may be processed when needed to respond to commands, run interactive DM workflows, apply enabled AutoMod rules, build an embed, save a custom template, log a configured event, or carry out another feature requested by a user or server administrator. The Bot is not intended to maintain a general archive of every server message. Specific content may be stored when it is deliberately saved as a template or configuration, included in a moderation record, or required for a requested feature.

Alert and external-source information

Creator or feed URLs, source identifiers, public post or stream metadata, event identifiers, delivery status, destination channel IDs, custom alert text, provider errors, and related data used to detect and deliver alerts.

Technical and security information

Command timestamps, errors, diagnostic logs, request timestamps, webhook metadata, delivery attempts, and security events. Railway, Discord, or other infrastructure providers may also process network data such as IP addresses, user-agent information, and request logs as part of providing and securing their services.

3. How information is collected

• directly from users and server administrators through commands, forms, buttons, menus, uploads, and DMs;
• automatically from Discord events and API responses needed for enabled features;
• from public feeds, creator pages, provider APIs, webhooks, and other sources a user asks the Bot to monitor; and
• from hosting, logging, security, and delivery systems used to operate the Bot.

4. Why information is used

Information is used to provide requested commands and features; remember user and server settings; manage fleets, rosters, crews, and profiles; apply moderation and welcome configurations; deliver alerts; display saved content; authenticate permissions; prevent abuse; diagnose errors; secure and maintain the service; comply with law and Discord requirements; and respond to support or privacy requests.

Where applicable law requires a legal basis, processing may rely on performance of the service requested by the user or server, legitimate interests in operating and securing the Bot, consent, and compliance with legal obligations.

5. How information is shared

We do not sell personal information. Information may be shared only as reasonably needed with:

• Discord, because the Bot operates through Discord and sends requested results to Discord;
• Railway and infrastructure providers, which host, route, back up, log, or secure the service;
• external providers used by a selected feature, such as creator, social, streaming, feed, image, or game-information services;
• server administrators and members, when a command, moderation log, profile, alert, embed, or other requested result is posted in a server or channel visible to them;
• professional advisers or service providers under appropriate confidentiality obligations; and
• authorities or affected parties when reasonably necessary to comply with law, protect rights or safety, investigate abuse, or enforce our terms.

6. Data location and international processing

The Bot is hosted using Railway infrastructure and interacts with Discord and other providers that may process data in the United States and other countries. Those locations may have different data-protection laws from your country.

7. Retention

We keep information only as long as reasonably needed for the feature, security, dispute resolution, enforcement, legal obligations, or continuity of the service.

• Saved profiles, fleets, rosters, crews, and server configurations may remain until deleted, replaced, no longer needed, or removed following a valid request.
• Moderation and audit records may remain while the server uses them for administration, safety, accountability, or dispute handling.
• Alert delivery records, errors, and operational logs may remain for troubleshooting, duplicate prevention, reliability, and security.
• Backups may retain deleted information for a limited period until the backup is rotated or safely overwritten.

Removing the Bot from a server stops future operation there but may not automatically delete every historical record. An authorized user or server administrator may submit a deletion request through Support & Data Requests.

8. Your choices and privacy rights

Depending on where you live, you may have rights to request access, correction, deletion, restriction, portability, or objection, and to withdraw consent where processing is based on consent.

You may stop using the Bot, avoid optional profile features, remove saved information through any available in-Bot controls, ask a server administrator to change server-controlled records, remove the Bot if authorized, or submit a request through Support & Data Requests.

We may ask for a Discord user ID, server ID, and reasonable verification from the relevant Discord account before acting on a request. Some information may be retained where legally permitted or required, including security, fraud-prevention, backup, or dispute records.

9. Server-controlled information

Discord server owners and administrators independently choose many settings, including moderation rules, logging, welcome messages, role tools, and alert destinations. They may be separate controllers or responsible parties under applicable law. Questions about a server’s own rules or records should first be directed to that server’s administrators.

10. Cookies and website tracking

The public policy and support pages do not intentionally set advertising cookies, use behavioral advertising, or run third-party analytics scripts. Hosting and network providers may still create ordinary security and access logs.

11. Security

We use reasonable technical and organizational safeguards appropriate to the service, including permission checks, Discord role hierarchy, restricted administrative controls, secret environment variables, signature validation for supported webhooks, HTTPS through the hosting platform, and database backups. No system is completely secure, and we cannot guarantee that unauthorized access or loss will never occur.

12. Children

The Bot is not directed to children below the minimum age required to use Discord in their country. Do not use the Bot if you are not permitted to use Discord.

13. Changes to this Policy

We may update this Policy when features, providers, law, or data practices change. The “Last updated” date will show the latest revision. Additional notice will be provided when required by law.

14. Contact and requests

Questions, reports, and data requests may be submitted through the LCARS-Prime Support & Data Requests page. You may also use the official LCARS-Prime Discord community. The public operator name is Stonedfury.

For a privacy request, include the Discord user ID, the relevant server ID if applicable, the type of request, and enough detail to identify the affected data. Do not send passwords, authentication tokens, government identification, or other unnecessary sensitive information.