Privacy Policy

1. Scope and roles

This Policy applies to Modra's services and public website. It does not govern the independent privacy practices of Discord communities or third-party platforms.

For community-specific records—such as tickets, applications, moderation cases, and role assignments—the community owner determines why Modra is used, which modules are enabled, which staff members can access records, and applicable configuration choices. Modra processes that information to provide the service. For account, billing, security, and service-operations information, Modra determines how the information is used as described here.

2. Information we collect

Discord account and community information

• Discord user ID, username, display name, avatar, and authorized server memberships;
• server, channel, role, message, and member IDs;
• community ownership, dashboard access groups, permissions, and support grants; and
• module, branding, notification, launcher, workflow, retention, and safety settings.

Community content and activity

Depending on enabled modules, Modra may process:

• ticket messages, transcripts, answers, attachments, staff notes, participants, actions, timestamps, and closure information;
• application answers, review comments, internal discussion references, decisions, and assigned roles;
• moderation cases, anti-spam and honeypot signals, message metadata, enforcement actions, purge activity, and audit events;
• streamer applications, profile cards, social and platform links, Twitch or Kick account identifiers, live-status metadata, titles, games, thumbnails, and viewer counts;
• suggestions, votes, giveaway entries and winners, role-menu selections, onboarding and verification events, custom commands, announcements, sticky messages, and server-status information; and
• other content submitted through Discord interactions or the dashboard.

Billing information

We receive billing-account identifiers, subscription status, plan, renewal timing, licensed server count, and related transaction metadata from Lemon Squeezy. Lemon Squeezy processes payment-card details and tax information as merchant of record; Modra does not store full payment-card numbers.

Technical and security information

• session identifiers and necessary authentication cookies;
• IP address associated with audited dashboard actions;
• request, error, performance, delivery, and integration logs; and
• security events and information used to prevent abuse or unauthorized access.

3. How we collect information

We collect information:

• directly from you when you configure or use Modra;
• from community owners and authorized staff members;
• from Discord through OAuth, bot events, commands, buttons, menus, and API requests;
• from connected platforms such as Twitch, Kick, Lemon Squeezy, and configured FiveM services; and
• automatically through necessary cookies, logs, and security monitoring.

4. How we use information

We use information to:

• authenticate users and enforce dashboard and category permissions;
• operate configured bot modules and community workflows;
• display, deliver, update, archive, and retrieve community records;
• monitor live-stream conditions and manage configured notifications and roles;
• process subscriptions, trials, complimentary licenses, and server allowances;
• detect abuse, investigate incidents, maintain audit trails, and secure the service;
• provide owner-approved support and troubleshoot errors;
• maintain, analyze, and improve reliability, usability, and features; and
• comply with law, enforce our Terms, and protect Modra, communities, and users.

5. Legal bases

Where applicable law requires a legal basis, we process information as needed to perform our contract, provide requested services, pursue legitimate interests such as security and service improvement, comply with legal obligations, protect vital interests, or act with consent. You may withdraw consent where processing relies on consent, without affecting earlier lawful processing.

6. How we disclose information

We may disclose information:

• to the community owner and staff members authorized through configured roles, categories, direct access, or an owner-approved support grant;
• to service providers that support hosting, databases, infrastructure, security, error monitoring, email, and customer support;
• to Discord, Twitch, Kick, Lemon Squeezy, FiveM-related services, and other integrations when necessary to perform a requested feature;
• when required by law, legal process, or a valid governmental request, or when reasonably necessary to protect rights, safety, and service integrity; and
• in connection with a merger, financing, acquisition, reorganization, or transfer of the service, subject to appropriate safeguards and notice where required.

We do not sell personal information, rent member lists, or share personal information for cross-context behavioral advertising.

7. Community access and support privacy

Dashboard access is scoped by the community owner's Discord-role and category permissions. Modra system operators do not automatically retain access to private community dashboards. When technical support requires access, the community owner must grant a time-limited or revocable support authorization. Access and sensitive transcript views may be recorded in the community audit log.

8. Retention

We retain information only for as long as reasonably necessary for the purposes described in this Policy, including providing the service, maintaining security and auditability, resolving disputes, and meeting legal obligations. Retention varies by record type and may be affected by community-selected settings.

• Community configuration and account records are generally retained while the community uses Modra.
• Ticket, application, moderation, audit, and streaming records follow applicable community settings and operational deletion processes.
• Closed, revoked, or ended records may be retained for the configured archive or retention period.
• Authentication sessions and temporary authorization records are kept for short operational periods.
• Billing and transaction records may be retained as required for tax, accounting, fraud prevention, and legal compliance.
• Backups and security logs may persist for a limited period after deletion from active systems.

Removing Modra from a Discord server does not necessarily delete all retained dashboard records immediately. A community owner may request account or community deletion using the contact information below.

9. Cookies and sessions

Modra uses necessary cookies and similar storage to complete Discord OAuth, maintain signed sessions, prevent request forgery, and protect dashboard access. Modra does not currently use third-party advertising cookies. Blocking necessary cookies may prevent login or other dashboard features from working.

10. Security

We use administrative, technical, and organizational safeguards designed to protect information, including scoped permissions, signed sessions, secret management, access controls, audit logging, and transport encryption where supported. No system is completely secure, and we cannot guarantee that unauthorized access, loss, or misuse will never occur. Please report suspected security issues to support@kenzie.wtf.

11. Your choices and privacy rights

Depending on where you live, you may have rights to request access, correction, deletion, restriction, portability, or an objection to certain processing. You may also appeal a denied privacy request where applicable.

For a ticket, application, moderation record, or other community-controlled content, contact the relevant community first because its owner controls access and configuration. You may also contact Modra at privacy@kenzie.wtf. We may need to verify your identity and coordinate with the community owner before acting. We will not discriminate against you for exercising applicable privacy rights.

You can disconnect Twitch or Kick through available account controls, leave a Discord community, remove Modra from a server you own, cancel a subscription through the billing portal, or revoke Discord authorization through Discord settings.

12. Children's privacy

Modra is not directed to children under 13 and we do not knowingly collect personal information from children under 13. Discord communities remain responsible for following Discord's age requirements and applicable law. If you believe a child has provided information improperly, contact privacy@kenzie.wtf.

13. International processing

Modra is operated from the United States. Information may be processed in the United States and other countries where service providers operate. Where required, we use appropriate safeguards for international transfers.

14. Third-party services

Discord, Twitch, Kick, Lemon Squeezy, linked websites, and configured community services maintain their own privacy practices. We encourage you to review their policies. Modra is not responsible for third-party privacy or security practices.

15. Changes to this Policy

We may update this Policy as Modra, its integrations, or legal requirements change. We will revise the date above and provide additional notice when a change is material. Your continued use after the effective date is subject to the updated Policy.

16. Contact

Privacy requests and questions may be sent to privacy@kenzie.wtf or modra@kenzie.wtf.