1. Scope
This Privacy Policy explains information processed by the Eclipse Discord bot, public website and authenticated dashboard. It does not replace Discord's own privacy information or the policies of infrastructure providers you visit directly.
2. Discord identifiers
Eclipse may process Discord server IDs, channel IDs, role IDs, user IDs, message IDs, usernames, display names, avatars, server icons and permission information when those identifiers are needed to provide a configured feature.
3. Server configuration
Per-server settings may include ticket definitions, welcome configuration, application questions, role mappings, moderation rules, sticky messages, automatic responses, logging channels, invite settings and other feature preferences. Configuration is stored so Eclipse can continue operating after restarts and deployments.
4. Message content
Message content may be inspected when required for AutoMod, Anti Scam, blocked-word detection, spam detection, sticky behaviour, automatic responses, ticket workflows, applications, logging or commands. Eclipse does not use message content to build advertising profiles.
5. Tickets and applications
Ticket and application features can process user-provided answers, staff replies, timestamps, channel metadata and workflow status. Server administrators are responsible for deciding what questions they ask and should avoid collecting unnecessary sensitive information.
6. Invite and join information
Invite tracking may process invite codes, inviter identifiers, join events, leave events and account age information needed to calculate server invite statistics. Historical accuracy depends on the events Eclipse actually observed while installed.
7. Dashboard OAuth2
The dashboard uses Discord OAuth2 to identify the signed-in user and retrieve servers that account can manage. Eclipse uses this information to determine which server dashboards may be opened. Eclipse does not receive your Discord password.
8. Session cookies
The dashboard uses a signed session cookie and temporary OAuth state to maintain an authenticated browser session and reduce unauthorised access. The cookie is intended for functionality and security rather than advertising.
9. Why data is processed
- To provide the features a server has enabled.
- To preserve server configuration between restarts.
- To enforce permissions and authenticate dashboard access.
- To prevent abuse and investigate security incidents.
- To diagnose failures and improve reliability.
- To present authorised server managers with useful operational information.
10. Storage
Operational data is stored on infrastructure used by Eclipse, including persistent hosting storage where configured. The exact records retained depend on which modules a server enables. Some configuration may remain until a server manager removes it or requests deletion.
11. Retention
Retention is based on operational need. Some records can be deleted directly through dashboard controls. Backups may temporarily contain information after a live record has been removed until those backups rotate out.
12. Service providers
Eclipse relies on third-party providers to operate, including Discord for bot and OAuth APIs, Railway for application hosting and GoDaddy/DNS infrastructure for the public domain. These providers process information under their own terms when applicable.
13. Sharing
Eclipse does not sell personal information. Information may be shared with service providers needed to operate the service, with Discord through normal API interactions, when required by law, or when reasonably necessary to protect users, investigate abuse or secure the service.
14. Public content
Information intentionally published by a server, such as a public server listing, would be visible to visitors. Eclipse does not currently provide a public server-upload form, and a future directory would require explicit server-owner participation.
15. Security
Reasonable technical measures are used to protect credentials and restrict dashboard access, but no online system can guarantee absolute security. Do not send passwords, Discord tokens, backup codes or payment details through tickets, applications or support channels.
16. Your choices
Server managers can remove Eclipse from a server, disable modules, change configuration and use available deletion controls. Browser users can log out or clear site data to remove their local session cookie.
17. Deletion requests
Where deletion cannot be completed through existing controls, a server owner may request assistance through the Eclipse Discord community. Requests should include the relevant server ID so authority can be verified, but must not include account passwords or authentication secrets.
18. Children and age requirements
Eclipse is intended for people permitted to use Discord in their country. Users must comply with Discord's minimum-age requirements. Server owners should not use Eclipse forms or tickets to request unnecessary sensitive information from minors.
19. International processing
Hosting, Discord infrastructure and users may be located in different countries. Information can therefore be processed in regions different from the user's location as required to operate the service.
20. Policy updates
This policy may change as Eclipse adds features, infrastructure changes or legal requirements evolve. The update date will be revised when meaningful changes are published.
21. Contact
Privacy questions, deletion requests and security reports can be raised through the Eclipse Discord community using the Discord icon in the footer. Avoid posting sensitive information publicly.