Privacy Policy

This Privacy Policy explains how Modulus collects, processes, stores, uses, and protects information in connection with the bot, dashboard, documentation, legal pages, moderation systems, and related infrastructure used to operate the service.

Modulus is intended to process only the information reasonably necessary to provide moderation, automation, analytics, configuration, logging, reporting, runtime controls, support, and reliability features for Discord communities.

Depending on which features are enabled, Modulus may collect and store Discord user IDs, guild IDs, channel IDs, role IDs, message IDs, moderation case records, application records, report records, dashboard settings, audit events, timestamps, staff activity statistics, command usage metadata, and technical diagnostics tied to system health or abuse prevention.

Where a feature requires it, Modulus may also process message content, attachments, proof references, invite links, feedback submissions, log payloads, score outputs, configuration snapshots, and moderation metadata related to incidents or staff workflows.

Server message content may be analyzed to provide features such as link detection, repetition checks, spam prevention, moderation review, AutoMod triggers, AI-assisted safety scoring, reports, applications, word automations, and incident logging.

Content is processed only where a feature makes that processing necessary. Not every message is permanently stored, and storage behavior can vary depending on which systems a server enables.

When server administrators enable moderation or safety features, Modulus may evaluate text, message patterns, attachments, risk indicators, or user context to generate local signals such as spam triggers, scam indicators, harassment scores, threat scores, and moderation recommendations.

These outputs may be stored as operational records, incident logs, dashboard-visible events, or review data so staff can audit what happened and why a safety system reacted.

The dashboard uses Discord authentication and session data to determine who is signed in, which servers can be managed, what permissions apply, and which configuration actions are authorized.

Authentication cookies, session tokens, and related state may be used where necessary to maintain access, secure sessions, reduce abuse, and prevent unauthorized configuration changes.

Information is used to operate the service, provide moderation and automation features, resolve dashboard access, store configuration, process reports and applications, monitor runtime health, investigate errors, improve reliability, and protect the service and its communities from abuse or misuse.

Information may also be used to troubleshoot incidents, understand feature failures, verify enforcement outcomes, and maintain continuity between the bot and the website.

Information may be processed by hosting providers, storage providers, authentication systems, analytics systems, and technical vendors strictly to the extent required to operate the service.

Information may also be surfaced to server owners, moderators, or staff where the relevant server configuration enables logs, reports, incident feeds, review queues, or other moderation visibility features.

Modulus does not sell personal information or server data as a standalone product.

Retention periods depend on the feature, operational need, legal risk, technical need, and abuse-prevention need involved. Configuration data, moderation logs, feedback, staff activity records, incident history, system errors, and diagnostic events may be retained for as long as reasonably necessary to operate, secure, support, and improve the service.

Even after removal or deletion requests, some information may remain in backups, cached operational logs, archived error records, or security records for a limited period.

The website may use cookies or similar storage mechanisms to maintain authentication, preserve session state, remember consent choices, and support core dashboard functionality. Some site features may not work correctly without those mechanisms.

Where optional consent flows are shown, they operate in addition to any strictly necessary authentication or session storage required to run the dashboard.

Reasonable technical and organizational measures are used to protect stored data, configuration systems, sessions, and runtime infrastructure. These measures may include access controls, environment isolation, server-side validation, and internal diagnostics.

No internet-connected service can be guaranteed fully secure, and you understand that the use of third-party platforms, hosting systems, and Discord-connected tools involves inherent operational risk.

Modulus is intended for users who meet Discord's minimum age and platform eligibility requirements. The service is not knowingly directed at children outside those platform rules.

Because infrastructure, support, hosting, and storage systems may operate in multiple jurisdictions, information may be processed or stored in countries or regions different from your own. By using the service, you understand and accept that cross-border processing may occur where necessary for service operation.

Server owners and authorized administrators control much of the data processing done within their communities by deciding which features to enable, disable, or configure. If a server enables logs, reports, automations, or safety systems, those settings can affect what operational records are created.

You may request deletion of certain information where applicable by contacting the service owner. Requests may be denied, limited, or delayed where retention is necessary for legal compliance, security, fraud prevention, abuse investigation, or technical integrity.

This Privacy Policy may be updated from time to time to reflect product changes, legal requirements, technical improvements, new infrastructure, or security needs. Continued use of the service after a revised policy becomes effective constitutes acceptance of the updated version.