Privacy

What Rova processes

What Rova uses and saves depends on the features your server turns on:

• Discord identity and server details: user, server, channel, message and role IDs; names and avatars; membership, roles and permission information needed for access and server features.
• Messages and media: content, links and attachments handled by enabled chat, moderation, logging, feeds, highlights or submission features. Deletion records can retain content after the original Discord message is removed.
• Tickets and moderation: participants, messages, attachments, transcripts, staff notes, moderation history and actions, and ticket restrictions.
• Events and giveaways: form answers, uploaded files, participation dates, entries, verification, winners, rewards and delivery records. Giveaway verification can retain an encrypted Discord OAuth grant.
• Community features: partner advertisements, invites and representative assignments; feed records; reaction-role selections, role milestones, welcome and booster records, Wordle scores, and other saved feature settings.
• Operations and support: configuration history and who changed it, errors, usage and delivery diagnostics, and information you provide when asking for help. Optional chat diagnostics can include generated drafts, message excerpts and identifiers.

Rova uses these records to run features, check permissions, investigate problems and recover from failures. Each server’s settings and records stay separate. Another server’s administrators cannot access them.

Alpha access requests

The Alpha install page uses a separate Discord sign-in to read your profile and server list, using Discord’s identify and guilds permissions. This lets you choose a server you own or have Manage Server or Administrator permission in. We do not save your unrelated server memberships.

When you submit a request, we save your Discord user ID, username, display name and avatar URL, along with the selected server’s ID, name and icon URL. The request also includes account and server creation dates derived from Discord IDs, server features, your ownership and permission information, and approximate member and online counts when Discord provides them. We retain the request status, request and update times, and the review decision, reviewer ID and review time to manage Alpha access.

Life reviews the complete request. Other people who can manage the same server can check its approval status on the install page, but cannot see your requester profile there. Request records can remain after a decision; their retention is separate from the short sign-in session. Contact Life through Support to ask about corrections or deletion.

Who can see it

You need current Administrator permission to use your server’s dashboard. Ticket and moderation controls in Discord have their own staff and permission rules. Rova’s operator can access records when needed to run the service, handle support requests or investigate problems.

Publishing an announcement, submission, log or other message shares it with people who can access its destination in Discord. Hosted transcript links can be read by anyone who has the link. Treat those links as private, even when the original ticket was restricted.

Discord processes activity on its platform. Rova’s hosting provider, RackNerd LLC, provides the infrastructure that stores and serves the application. Configured integrations, such as feed sources, partner-ad services and webhooks, also receive the requests or content needed for their features. Their own policies apply to their processing.

Chat and AI features

When an AI feature is enabled, relevant messages, recent conversation context, media or task details may be sent to its selected provider, OpenAI or xAI. This can support replies, reactions, moderation, natural-language moderation commands or Wordle image recognition. Server administrators can review the available switches in System settings.

Rova does not train its own models on your chats. Provider processing and retention depend on the applicable service terms and account settings; turning a feature off does not erase information already processed. See OpenAI’s API data controls and xAI’s API data information. We do not promise zero provider retention.

Sign-in and browser preferences

The dashboard uses Discord OAuth and a session cookie to sign you in and check access. Giveaway verification is a separate authorization flow. Rova does not ask for your Discord password. Display preferences, such as the dashboard accent, can be saved locally in your browser.

Automatic Partner command visibility asks a server administrator for Discord's command-permission authorization. Rova retains an encrypted access and refresh grant, the administrator's Discord ID, authorized server bindings and synchronization records to keep commands restricted to the configured Partner managers. This authorization is separate from ordinary dashboard sign-in. Revoking it in Discord stops future permission updates; Rova still checks permissions when commands are used. Contact Support to remove retained authorization records.

Alpha installation has its own session cookie and a sign-in session lasting up to 30 minutes. Its Discord access token is held only in server memory for that session, and we do not save a refresh token. Signing out discards Rova’s local Alpha session; it does not automatically revoke your Discord authorizations. You can manage those authorizations in Discord.

Rova’s public pages and dashboard do not include advertising or third-party analytics scripts. Following an external link takes you to a service with its own policies.

Storage and retention

How long records stay depends on the feature. Rova keeps a limited amount of recent chat context, while tickets, event results, moderation records and other server history can last longer. Backups and recovery copies may also hold records. There is no single expiry that applies to everything.

Removing Rova from a server stops its server processing, but does not immediately delete the saved data. Disabling a feature generally preserves its settings and existing records. Disconnecting Giveaway verification removes the active authorization, not necessarily earlier entry or winner records.

Chat snapshots and retained Giveaway and command-visibility OAuth grants are encrypted by the application. Other records use access restrictions; this does not mean every file or backup is encrypted. Do not submit passwords, access tokens or other secrets through tickets, forms or chat.

Corrections, deletion and questions

Contact Life, Discord username .ddos, privately through the Ronova Mains community. You can request correction or deletion of your data, ask about stored information, or report a privacy concern.

Include your Discord user ID, the server, the feature involved and what you want changed. We may need to check that the account is yours and confirm which records you mean. We review requests manually, including relevant recovery copies and external processing. A feature’s delete button may not erase every copy.

Keep records and transcript links out of public channels. Never send passwords, tokens, OAuth codes or session cookies. If you cannot message Life, ask community staff for a private contact route without posting the details. See Support for the request checklist.

Changes to this page

We will update this page when Rova’s data handling changes. The date above identifies the current version. Questions about a change can go to the same private support contact.