Lluvia Privacy Policy
Last Updated:
Service: Lluvia (https://lluvia.dev) and the Rainy Discord application
Privacy at a Glance
Lluvia is designed to collect only information reasonably needed to operate Rainy, manage authorized Discord servers, secure accounts, and provide selected features.
- You sign in using Discord; Lluvia does not ask for your Discord password.
- Lluvia uses a website session to keep you signed in securely.
- Lluvia stores Discord identifiers, relevant account information, server records, and authorized server-access relationships.
- Removing Rainy does not automatically delete all server records or cancel a subscription.
- AI-enabled features may send relevant content to an external AI provider when used.
- We do not intend to sell personal information or use it for third-party behavioral advertising.
1. Scope
This Privacy Policy explains how Lluvia ("we," "us") handles information through lluvia.dev, the Rainy Discord application, and related services. Discord, Twitch, and other independent services have their own privacy policies.
2. Information We Collect
2.1 Discord account and authentication information
When you authenticate with Discord, we may receive and store your Discord user ID, username, display name, avatar reference, and other account details made available through the authorized OAuth scopes. We use this information to create and maintain your Lluvia account, display your identity, support access controls, and operate the dashboard.
We do not request your Discord password. OAuth authorization may involve access tokens needed to communicate with Discord; their storage, protection, and lifetime must be limited to what the implementation requires.
2.2 Server and permission information
To operate Rainy and determine which dashboards you may manage, we process Discord guild IDs and names, installation state, relevant timestamps, and your verified Administrator or Manage Server access to guilds where Rainy is installed.
Depending on enabled features, we may also process channel IDs, role IDs, configuration settings, moderation-related identifiers, and other data required to perform requested actions.
Our registered_servers records may retain installation history, administrative status, subscription tier/status, and related dates even after Rainy is removed. Our user_server_access records reflect last-known eligible user/server relationships and are refreshed when users authenticate. Those cached relationships do not by themselves grant ongoing authorization.
2.3 Configuration and user-submitted content
Server administrators may submit announcement text, onboarding content, reaction-role mappings, application forms, preferences, and other configuration. Some future features may process messages, command inputs, interaction data, or content supplied by Discord users when necessary to provide the enabled feature.
We do not claim to collect all Discord messages. Actual content access depends on enabled features, Discord permissions, and the application's implementation.
2.4 Discord subscription and entitlement information
We may store plan names (Flow, Current, Tide), trial and sponsorship eligibility, entitlement identifiers, subscription status, renewal or paid-through dates, and cancellation timestamps. Paid subscriptions are purchased and billed through Discord, not Lluvia. When subscription integration launches, we will receive Discord entitlement creation, update, and deletion events to maintain access to subscribed features. We do not request or store customers' payment card numbers, billing addresses, or payment credentials. Discord handles billing under its own terms and privacy policy. The entitlement event integration is planned and will be described accurately when launched.
2.5 Support communications
If you contact support, we process the information you provide and any relevant account or server context necessary to investigate and respond.
3. How We Use Information
We use information to authenticate accounts; identify servers users are authorized to manage; provide configured bot and dashboard functionality; maintain subscriptions and trials; enforce server restrictions; respond to support requests; and meet applicable legal obligations.
We do not use Discord data to identify people outside the context of providing and securing the Service unless required by law or reasonably necessary to address misuse.
4. Discord OAuth, Permissions, and Sessions
Discord OAuth is used for website login and access to relevant server information. Lluvia checks Discord permissions to determine whether a user can manage a server through the dashboard.
The website uses session cookies to maintain authenticated access. The current design provides an eight-hour absolute session limit and 30-minute inactivity limit; implementation and cookie behavior should be verified before publication. Necessary authentication cookies are used for session management and security, not as a claim that analytics or advertising cookies are present.
Revoking Discord authorization, leaving a guild, losing permissions, logging out, and uninstalling Rainy can have different effects. Revocation or permission changes may not immediately remove records already retained for legitimate operational purposes.
5. AI Processing
When an AI feature is enabled and used, relevant prompts, messages, configuration, or conversation context may be sent to a third-party AI service to generate a response or perform the requested action.
The categories of data shared depend on the feature. AI providers may process submitted data under their own terms and privacy policies. We will identify the actual providers and relevant retention or training controls when those integrations are launched. Do not submit sensitive or confidential content without authorization.
AI features may be unavailable or disabled for servers without the required entitlement.
6. Future Twitch and Creator Features
The planned Tide tier may include Twitch chat participation, AI responses to mentions, optional scheduled messages, stream-event notifications, and overlays. If launched, those features may process Twitch account identifiers, channel names, chat messages, follows, subscriptions, cheers, raids, and event metadata as necessary for the selected functionality.
These are planned capabilities, not a representation that Lluvia currently collects Twitch data. We will update this Policy and disclose relevant permissions and data practices before enabling those integrations.
8. Data Retention
We retain information for as long as reasonably necessary for the purpose collected, including service operation, entitlement administration, support requests, and applicable legal obligations.
- Account records: May be retained while an account is active and for a reasonable period afterward where needed for security, support, or legal obligations.
- Registered servers: May remain after bot removal to preserve configuration history, paid entitlements, trial eligibility, and administrative restrictions.
- Server-access relationships: Updated following successful permission checks and removed when access or installation no longer qualifies, subject to technical synchronization delays.
- Configuration data: May be retained after uninstall so administrators can restore settings if Rainy returns; specific deletion schedules will be established as features launch.
- Support communications: Retained as needed to resolve requests and maintain appropriate records.
Specific retention durations have not yet been finalized. They must be documented and reflected in actual deletion procedures before publication. Uninstalling Rainy is not an automatic request to delete all associated information.
9. Data Security
We use reasonable technical and organizational safeguards intended to protect information, including access controls, authenticated sessions, secure transport, and restricted database access. Lluvia does not intentionally look up or store client IP addresses or unrelated private client information. No online service can guarantee absolute security.
Please report suspected security or privacy problems through our official support channel. Do not include passwords or other secrets in ordinary support messages.
10. Your Choices and Privacy Requests
You may choose whether to authorize Discord login, install Rainy, enable optional features, or connect future third-party integrations. Authorized administrators may update certain server settings through the dashboard when those controls are available.
You may request access, correction, or deletion of personal information, subject to identity verification, applicable law, legitimate retention needs, and the rights of other server members. We may need to preserve limited information for fraud prevention, ban enforcement, subscription disputes, or legal compliance.
To make a request, visit https://lluvia.dev/support or our official support Discord server. Additional regional privacy rights and appeal mechanisms should be added if required by applicable law.
11. Children's Privacy
Lluvia is intended for users who meet Discord's minimum age requirements and applicable law. We do not knowingly seek personal information from children who are not eligible to use Discord. If you believe such information has been collected, contact us so we can review the situation.
12. International Processing
Depending on hosting and service providers, information may be processed or stored outside your state or country. We will provide any additional disclosures or safeguards required by applicable privacy law once provider locations and transfer arrangements are confirmed.
13. Changes to This Policy
We may update this Privacy Policy as features, integrations, legal requirements, and data practices evolve. We will update the month and year shown above. Once server logging notifications are available, policy updates will also be announced in each server's configured Lluvia logging channel. Other notices may be provided where appropriate or legally required.
14. Contact
For privacy questions, requests, or concerns, visit https://lluvia.dev/support or our official Lluvia Support Discord server (linked from the support page).
