TRUST & TRANSPARENCY

Privacy Policy

A clear view of what happens when you visit and sign in.

1. Scope and operator

This draft covers the Rubidus website and all Rubidus bots. The formal legal operator name must be confirmed before publication. Privacy requests are submitted through privacy.rubidus.xyz, which directs you to our privacy request page.

2. Information this website uses

Public pages do not require an account. If you choose Discord sign-in, the server requests the identify and guilds permissions. Discord sends a user identifier and username, which the server uses to verify your identity. The website keeps your Discord ID and username in a temporary server-side session. It uses your server list to show servers you can manage. It does not request email, message access, or your Discord password.

A temporary authorization token stays in server memory until Discord’s token expiry or the end of your website session, whichever comes first. It is never sent to your browser or saved to a database. The site uses essential cookies for login verification and your session. No analytics, advertising scripts, or third-party fonts are included.

Rubidus bot information

Depending on the service and features enabled by your server, we may use the following information:

• Rubidus: Discord and server identifiers, membership and roles, activity and leveling information, moderation records, and message content or attachment information where moderation, logging or other enabled features require them.
• Chronarch: event details, schedules, time zones, RSVPs and related Discord identifiers.
• Sigil: linked game-account identifiers, membership, and game activity or progress needed for account linking and related features.
• Waystation: support requests, participant identifiers, messages, attachments and transcripts needed to handle support conversations.

Not every feature uses every category. Server administrators and authorized staff may receive relevant information through features they enable. This is a summary; the complete data inventory and actual service configurations must be reviewed before publication.

3. Purpose and sharing

Identity information is used to sign you in and display your account page. The sign-in flow communicates with Discord. Hosting infrastructure may process network information such as your IP address; the hosting provider and its logging practices must be documented before launch. This application has no sale, advertising, or data-export integration.

4. Retention and control

Your website session expires after one hour or ends when you sign out. Expired server entries are removed by a cleanup task at intervals of up to 30 seconds. Restarting the website clears its in-memory sessions. See data retention for details.

You can sign out to remove the active website session. You can also remove the app from Discord's Authorized Apps settings. Removing authorization in Discord does not immediately clear an existing website session: sign out here as well.

5. Privacy requests

Submit an access, correction, or deletion request through our privacy request page, reached via privacy.rubidus.xyz. Sign in with Discord so the operator can identify the requesting account. Requests are saved for manual review; submission does not automatically change bot databases. Do not send passwords or access tokens in a request. Bot records require verification of ownership, scope, and applicable retention obligations before the operator fulfills a request. The request workflow and response channel must be operationally verified before launch.

6. Changes

The published policy will carry an effective date. Material changes to data handling must be reflected here before the changed behavior is introduced.